Kevin
The USB task is called once to initialise the USB interface.
It is called a second time only after enumeration.
I have just checked again how the Blaze configuration operates and see the following, which is a little different to normal. It only actually enables the USB interface when the user taps on the display!
This is controlled in TaskConfig.h as follows:
#if defined BLAZE_K22
{ "usb", fnTaskUSB, SMALL_QUEUE, (DELAY_LIMIT)(NO_DELAY_RESERVE_MONO), 0, UTASKER_STOP }, // USB (application) task is only started if commanded
#else
{ "usb", fnTaskUSB, SMALL_QUEUE, (DELAY_LIMIT)(NO_DELAY_RESERVE_MONO), 0, UTASKER_ACTIVATE}, // USB (application) task
#endif
Notice that the USB task is not started (it will be later started from the code that detects the user taping on the display). Therefore, since you don't have a display, you will need to change this so that the task is indeed started
For example, change the define decision to
#if defined BLAZE_K22 && defined SUPPORT_TOUCH_SCREEN
which will then cause the USB task to be started immediately if the touch display is not enabled.
This will very probably solve your problem!
Regards
Mark