Debugging custom application with the IDE

[g24sharma]

Hi,

I'm trying to debug a custom application built outside of the IDE. I have created a new MCUXpresso IDE project with most of the standard files stripped off. The Run/Debug settings have been changed to use the custom .elf application(which is being built in vs code) instead of the project build output from the IDE. I have provided the link to my source folders under the source section. However, when I try to debug it I see the following messages on the console:

"NXP: MIMXRT1064xxxxA
DAP stride is 1024 bytes (256 words)
XML Error - no license-type XML file 'crt_common.xme' on path.
note - part information contained no product license-type data
can't find a flash driver called ''

Can you please tell me if I'm following the right steps, and what else needs to be done for this to be successful. The main idea is to debug the application and do a routine 'step-through' operation.

Thanks

GS

[g24sharma]

Hi Jeremy,

Thanks for getting back. Here are the responses to your questions:

2. The board is the MIMXRT1064-EVK.

3. The debugger is on the onboard CMSIS-DAP probe.

1. Yes, a project created in VS code on Ubuntu. The output is binary, hex and ELF. I use the ELF with the hope to facilitate a debug session in the MCUXpresso IDE. Steps:

    a) Create  a MCUXpressoIDE C/C++ project with the configuration as in attached pictures - project_config and       project_config_advanced_settings.

     b) Project Properties -> Run/Debug Settings- Change the application to the custom application (under the Main tab)built outside of the IDE (custom_app.elf). Keep everything else the same(connect scripts and settings etc.)

    c) Link the source code folders under 'source', not copy but just link.

2. Change the SW7 settings to 'Serial Download'.

3. Debug the application after it chooses the right debug adapter.

With the above I'm not able to even get the debug session started as it is still looking for the project's .axf file even though I had changed the target to my custom application. I was however able to change the target to mine during one of my poking around experiments but even that lead to a session where it would start debugging, throw some exceptions- show me the disassembly, but couldn't locate the source code path. I explicitly added the path as well but it still couldn't find it. So two questions from here-

i) How do I reliably have it use my custom application file instead of looking for the project's default .axf?

ii)When it does use my custom application how can it use my source code to step through and show me where the issues are occurring?

Thanks for your help,

GS

[jeremyzhou]

Hi,
Thanks for your reply.
From the NXP tech support engineer's view, I'll suggest the customer stop the kind of try, as it's not conventional debug behave and we've not encountered other customers to try this debug action.
From a tech geek's view, I appreciate your exploring spirit, however, I'm not sure whether this method can work out, as it beyond my knowledge scope.
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

[jeremyzhou]

Hi,
Thank you for your interest in NXP Semiconductor products and for the opportunity to serve you.
Before answering your question, I'd like to confirm some queries with you.
1) According to your statement, it seems that you want to debug a project which is created by the VS in the MCUXpresso IDE.
If my understanding is right, I was wondering if you can introduce the testing steps in detail.
2) Which board did you test with?
3) Which debug tool did you use?
Have a great day,
TIC

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------