Hi Darrel
Thanks for the reply, that certainly makes some sense. However I have replaced my tick timer routine with this one:
And in the main loop I can check USBRXBuffer[0] for a non zero value which indicates a valid command has been received and I can act on it. Given that the only thing not USB related is setting that byte to 0 I would not have thought that the device would drop off the bus, especially given that this is the 'traditional' way of handling USBSERVICE routines. I have also set the tick_timer interrupt to be Low Priority.Code:tick_timer: USBSERVICE USBIn 1, USBRXBuffer, USBRXBufferCount, NoData ' read data, if available USBSERVICE goto DataOK NoData: ' zero out the USBRXBuffer[0] byte USBRXBuffer[0] = 0 DataOK: @ INT_RETURN
However this suffers from the same problem as before. Any thoughts?
Thanks
Andy




Bookmarks