Cannot step through debugging on PN7642 (PNEV7642A)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot step through debugging on PN7642 (PNEV7642A)

Jump to solution
1,511 Views
V_Palacio
Contributor V

Hi,

I'm trying to debug a PCSC fw based on example UsbCcid_Freertos_Pub, running on an evaluation kit board PN7642 (PNEV7642A)

I've followed instrucctions from FREERTOS Debug Document.
UG10059 - MCUXpresso IDE 25.06 FreeRTOS Debug Guide.

From what I can see in logs, FreeRTOS Thread awareness should be OK, but it is not fully working.

I have a list of thread in Debug, but Thread states de RTOS has not been detected.

Debug statusDebug status

Using an MCULink, I can step over until after launching the thread scheduler with phOsal_StartScheduler();

After that, a breakpoint in the working thread stops it, but I cannot step over or step out.

I got messages in Disassembly that could be relate to the problem.

0020ae54: Failed to execute MI command:
-data-disassemble -s 2141780 -e 2141824 -- 3
Error message from debugger back end:
Cannot access memory at address 0x20ae54

Can someone give me some pointers?

Regards,

Tags (2)
0 Kudos
Reply
1 Solution
1,424 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

Please use the latest versions of PN7642 SDK and Firmware available on PN7642 product page, "Software" section.

You can also try updating CMSIS-DAP firmware of your MCULink.

Regards,
Eduardo.

View solution in original post

0 Kudos
Reply
5 Replies
1,456 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hello @V_Palacio,.

Hope you are doing well.

An SDK is bound to a certain firmware version. If FW version of PN7642 does not match the FW used by the SDK, some issues and unexpected behaviors can occur. Please make sure you are using the latest firmware version available; you can run the check_nxpfw_update demo from PN7642 SDK, and if PN7642 and SDK firmware versions do not match, this demo will help you updating the FW.

You can also try deleting the debug configuration (*.launch file that is generated for the debugging) and start the debugging session again. If possible, please do some tests using J-Link firmware for your debugger.

Still, the behavior you observe during debugging should be related to the OS, and as you pointed out, it would be expected after the Scheduler starts running. To debug, please consider setting a breakpoint, reach it, disable it, and run until the next one.

Regards,
Eduardo.

0 Kudos
Reply
1,440 Views
V_Palacio
Contributor V

Hi @EduardoZamora ,

check_nxpfw_update demo reports FW as 02.02, and 02.02 for SDK as well.

Returns STATUS_FW_SAME_VERSION.

I'll try to find a JLink to further testing, but I adquired a brand new MCULink just for debugging this board.

As for the OS... Do you mean the HOST OS? I'm using ubuntu 22.04.5 LTS:

Regards,

 

Regards,

0 Kudos
Reply
1,425 Views
EduardoZamora
NXP TechSupport
NXP TechSupport

Hi,

Please use the latest versions of PN7642 SDK and Firmware available on PN7642 product page, "Software" section.

You can also try updating CMSIS-DAP firmware of your MCULink.

Regards,
Eduardo.

0 Kudos
Reply
391 Views
V_Palacio
Contributor V
With latest SDK (2.15) and launch debug config as "All Stop", now I can manage myself to debug.
0 Kudos
Reply
1,493 Views
V_Palacio
Contributor V
Correction: RTOS not detected comes from Azure RTOS.
FREERTOS Task shows 3 Task:
-IDLE
-ClTaskEvent
-Tmr Svc
0 Kudos
Reply