User forums > Embedded development

MSP430 linux toolchain with C::B

<< < (3/7) > >>

oBFusCATed:
Does it work if you execute the same commands in a command line gdb?

Also what happens if you put a breakpoint before you start the debugger?

ywi:
It works OK as command line and with 10.05. I will be able to answer the second question on Monday. Thx.

oBFusCATed:
Can you post the log from command line debugger?
But make sure to execute all gdb commands C::B is executing...

ywi:
This is the minimal commands executed on msp430-gdb


--- Code: ---Reading symbols from /projects/cb/test/bin/Debug/test...done.
(gdb) target remote :2000
Remote debugging using :2000
_reset_vector__ () at ../../../gcc-4.5.3/gcc/config/msp430/crt0.S:118
~/msp430/gcc-4.5.3/gcc/config/msp430/crt0.S:118:3824:beg:0x9800
(gdb) break *0xdcd0
Breakpoint 1 at 0xdcd0: file /projects/cb/test/test, line 79.
(gdb) continue
Continuing.

Breakpoint 1, plat_mpipe_rx_isr (id=2) at /projects/cb/test/test.c:79
/projects/cb/test/test.c:79:2857:beg:0xdcd0
(gdb)
--- End code ---

I found that the difference with the nightly is that it sends the command "run" rather than "continue" to continue after a break. msp430-gdb does not support (for some reason) the command "run". I think we can consider this is more a problem with msp430-gdb than the nightly, unless there some other reason to differentiate both.

Maybe at this point you can explain to me the usage of the config "do *not* run the debuggee".

Also, for remote target debugging it is mandatory to have two separate buttons in the debugger toolbar, one to burn the code on the remote's flash, the other to start/continue. Burning takes some time and you do not want to burn every time you start a debugging session.

I would appreciate your suggestions on how to display the regs information in the appropriate debug window.

Than you.

oBFusCATed:
Hm, as far as I can see in your previous logs continue is used, as it should.
There is no run in the log.

"do *not* run the debuggee" - does not run the debuggee, just starts the debugger, sets the breakpoints and probably connects to the target, then the user has to press the continue button in order to start debugging.

How do you burn something to a flash? I don't think C::B knows how to do it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page