I tried searching for a previous answer but could not find one. Maybe my google-fu is weak...
I'm seeing that it takes about 2 seconds for my sketch to start being able to operate. I plug in USB and nothing happens for 2 seconds then it starts to work and print things to screen. Previously while using Arduino Due boards I'm pretty sure it would boot basically instantly and anything I tried to write to USB would just plain be lost until USB was fully set up and running. I'm assuming the Teensy is instead pausing the sketch until USB actually succeeds. I'd rather not do this. There are some cases where it's handy for a program to start up within a very short time and be able to assume control of other hardware.
So, the questions are:
1. Is this normal for Teensy boards?
2. Is there any way to tell the core not to wait for USB to actually connect?
3. Am I to assume (I will test) that connecting without USB would instead allow me to start up at breakneck speed?
I'm seeing that it takes about 2 seconds for my sketch to start being able to operate. I plug in USB and nothing happens for 2 seconds then it starts to work and print things to screen. Previously while using Arduino Due boards I'm pretty sure it would boot basically instantly and anything I tried to write to USB would just plain be lost until USB was fully set up and running. I'm assuming the Teensy is instead pausing the sketch until USB actually succeeds. I'd rather not do this. There are some cases where it's handy for a program to start up within a very short time and be able to assume control of other hardware.
So, the questions are:
1. Is this normal for Teensy boards?
2. Is there any way to tell the core not to wait for USB to actually connect?
3. Am I to assume (I will test) that connecting without USB would instead allow me to start up at breakneck speed?