Re: [threadx-users] threadx module debug via jtag

[Frédéric Desbiens <frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx>]

Hi.

Here is what one of the team members suggests:

You are correct that a raw binary image contains no symbolic information. One possible solution is generating both an ELF file and a binary image. The ELF file output could be imported into your debugger (typically something like “load symbols only”).  You might also need to match the instruction address in the linker control file to the module's physical location.  

Best Regards, 

Frédéric DESBIENS

Senior Manager — Embedded and IoT | Eclipse Foundation

Project Lead | Eclipse ThreadX

Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx

Eclipse Foundation: The Community for Open Innovation and Collaboration

On Wed, 6 Nov 2024 at 08:45, Frédéric Desbiens <frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi!

I am not sure about this. I will discuss the topic with the team during our weekly meeting tomorrow (November 7).

Best,

Frédéric DESBIENS

Senior Manager — Embedded and IoT | Eclipse Foundation

Mastodon: @fdesbiens@xxxxxxxxxxxxxxxxxxxxx

Eclipse Foundation: The Community for Open Innovation and Collaboration

On Thu, 31 Oct 2024 at 21:11, ym zhang via threadx-users <threadx-users@xxxxxxxxxxx> wrote:

hi,

When the ThreadX module manager loads a module in binary form(not elf form) through the function _txm_module_manager_in_place_load, the binary does not carry any debugging information. Is there a way to debug the module through JTAG?

thanks

_______________________________________________
threadx-users mailing list
threadx-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org