Hello, Everyone!
I created a project in the RT-Druid Eclipse, and I want to debug it.
I have a development board USB-TRK-MPTS5643L, and I'm going to use built-in OSBDM Debuger, but RT-Druid Eclipse does not support it.
How can I debug in my case?
Maybe someone know what kind of software need to use with OSBDM Debuger?
Interested in free solutions, or at least temporarily free.
Many Thanks!
Debuging with OSBDM JTAG Debugger
Moderator: paolo.gai
Re: Debuging with OSBDM JTAG Debugger
I succeeded Debug sample OSless project in CW MCU 10.5, witch support OSBDM Debuger. Now I would like to debug the project in the CW MCU 10.5, created in RT-Druid ECLIPSE using *. ELF file how it possible? What action needs to be done for this?
Thank You
Thank You
Re: Debuging with OSBDM JTAG Debugger
I succeeded to debug a OS-based project created in Eclipse using CW MCU 10.5 using "Import MCU executable file" via *.elf.
However, I always have to port the the project from the beginning with any change in the source / elf file.
question:
how can I dynamically update source and elf files in CW MCU 10.5 on each successful build from Eclipse?
Thank you)
However, I always have to port the the project from the beginning with any change in the source / elf file.
question:
how can I dynamically update source and elf files in CW MCU 10.5 on each successful build from Eclipse?
Thank you)
Re: Debuging with OSBDM JTAG Debugger
Hi! Thanks for your messages...
The procedure of importing the generated file is correct.
Maybe you can think of creating a batch file which maybe could call the CW debugger directly passing the elf file as an option (guessing, never used that debugger).
Anyway i do not see any other possibility so far for doing the thing. Unfortunately we never used that debugger, as most of our customers used other debuggers...
Ciao,
Paolo
The procedure of importing the generated file is correct.
Maybe you can think of creating a batch file which maybe could call the CW debugger directly passing the elf file as an option (guessing, never used that debugger).
Anyway i do not see any other possibility so far for doing the thing. Unfortunately we never used that debugger, as most of our customers used other debuggers...
Ciao,
Paolo