User forums > Embedded development

MSP430 linux toolchain with C::B

<< < (6/7) > >>

ywi:
I come back to a request for monitoring specific remote registers (not only the remote CPU registers). What I basically need is to be able to load at C::B start a memory map description file of volatile variables that gdb will have to update at each step/bkp. Any suggestions?

MortenMacFly:

--- Quote from: ywi on May 18, 2012, 08:50:05 pm ---I come back to a request for monitoring specific remote registers (not only the remote CPU registers). What I basically need is to be able to load at C::B start a memory map description file of volatile variables that gdb will have to update at each step/bkp. Any suggestions?

--- End quote ---
Use the debugger initialisation commands and (if needed) the debugger console for that purpose.

ywi:
This is not quite convenient. It should behave like a watch, i.e read and display automatically the list of remote registers (addresses). GDB should execute command "x/b <addr>" for every address of the registers address list when a bkp/step is reached.

oBFusCATed:
I guess you can use python enabled gdb and use some fancy python scripts...

ywi:
That is an interesting option indeed, but maybe too fancy for me for the moment. Is there any possibility to pass commands to the GDB launched by C::B by an external shell command?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version