- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Why does enabling the USB_DEBUG_INTERFACE in the AN75779 code using SDK version 1.3.4 let the firmware run under the debugger when the debugger has problems with it disabled.
This question is not on how to use the USB_DEBUG_INTERFACE or how it works;
This question is to understand what else may be affected due to a known issue with the debugger in 1.3.4 as discussed in Community Post FX3 SDK version 1.3.4 won't put breakpoints while running
Greg
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
Please check the below thread for the enhancements/fixes that are planned for SDK 1.3.4
Regards,
Hemanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
Please share the step by step procedure about how the debugging is being done.
Regards,
Hemanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The step by step procedure is posted separately @ Can a Debug Session run on AN75779 AVC code using EZ USB Suite and CYUSB3KIT-003? .
From that post, Sridhar responded:
KernelEntry() function is a non return function. There is no way to debug it.
You can use the RTOS APIs to check the thread performace. For this, you need to build the firmware with Profile Debug or release mode
Check this out: debug and release mode
So the question for this post is for a full or working list of errata of potential issues using SDK version 1.3.4.
Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Greg,
Please check the below thread for the enhancements/fixes that are planned for SDK 1.3.4
Regards,
Hemanth