This content has been marked as final.
Show 2 replies
-
1. Re: USBCOM interrupt priority and debugging
AnkitaS_51 Oct 11, 2017 2:06 AM (in response to marcov)2 of 2 people found this helpfulPriority – This is used to enter the interrupt priority. The valid range is displayed in the header. The smaller the number, the higher priority.
From the discussion it seems that the USB is required to be of Higher priority in the application
For debugging query-
You can post opensource applications using PSoC on hackster-
-
2. Re: USBCOM interrupt priority and debugging
marcov Nov 10, 2017 4:49 AM (in response to AnkitaS_51)I found out that priority is not the issue. The problem happens when I connect the device and I start immediatly to write strings to the serial port (because interrupt are fired). Maybe this is because the board was already powered through KitProg when connecting the main USB. I confirm that lowering the interrupt priority WORKS.
Thanks for your detailed responses about debugging and hackster