Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Thanks for your reply. All of the required libraries are included.
I start out with a working USB UART application and then slowly add in my code, while testing along the way. After a while the compiler starts complaining. Sometimes it is intermittent and sometimes it fails repeatedly. If I hover over USBUART_MAX_EP , the IDE shows the value, so it can find it. If I hard code the value at the problem statement, the error just moves to another similar error else where in the USBUART API.
One time, as a clean and build was running, I saw that the USB pins were reassigned (to the same ones I had assigned) and it compiled. I changed my my USB pins to "auto assign" and unchecked "lock". It now seems to regularly compile without any changes to the firmware???
I am not sure what is going on, but at least I was able to complete my firmware. I still have another test program that was not fixed by that trick, so it is not a magic bullet.