Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

USB superspeed peripherals Forum Discussions

GrCa_1363456
Level 5
Level 5
First comment on KBA First comment on blog 250 sign-ins

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

0 Likes
1 Solution
Hemanth
Moderator
Moderator
Moderator
First like given First question asked 750 replies posted

Hi Greg,

Please check the below thread for the enhancements/fixes that are planned for SDK 1.3.4

FX3 SDK new release date

Regards,

Hemanth

Hemanth

View solution in original post

3 Replies
Hemanth
Moderator
Moderator
Moderator
First like given First question asked 750 replies posted

Hi Greg,

Please share the step by step procedure about how the debugging is being done.

Regards,

Hemanth

Hemanth
0 Likes

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

0 Likes
Hemanth
Moderator
Moderator
Moderator
First like given First question asked 750 replies posted

Hi Greg,

Please check the below thread for the enhancements/fixes that are planned for SDK 1.3.4

FX3 SDK new release date

Regards,

Hemanth

Hemanth