User forums > Embedded development
MSP430 linux toolchain with C::B
ywi:
Hello Developers,
First, thank you for supporting this project. I've been using C::B over the last few years on both Linux and Windows and I find it light and friendly.
I am currently using C::B as IDE for developing and debugging code on an MSP430-based embedded target. I would like to address here some issues and several amelioration that would help a better integration of the mspgcc toolchain in C::B (mspgcc + mspdebug). Of course I would be ready to contribute as far as I can.
Thank you in advance for your support,
Yordan
Here a list of issues/ameliorations:
1) CPU register is empty. How to setup correctly this window for mspgcc?
2) Impossible to select another debugger executable than GDB with the latest nightly build (would need to be msp430-gdb)
3) Need to send some default commands to mspdebug when msp430-gdb connects to it ("target remote :2000", "erase", "load"...). Would ideally like to write a new plugin for mspgdb with an extra button to load code to the remote, based on the debugger plugin. Would appreciate to get some support on this.
oBFusCATed:
1) What is the output of the cpu registers gdb command? Does it look like the one for x86?
2) Have you tried "Settings -> Debugger -> GDB Debugger -> Your config -> Executable path" ?
3) Have you tried the settings in Project -> Properties -> Debugger?
ywi:
1) What is the output of the cpu registers gdb command? Does it look like the one for x86?
-> The command passed from gdb to the proxy is "regs". It is works correctly when manually invoked through the debugger window command line. But there is no polling and display on the "CPU registers" window
2) Have you tried "Settings -> Debugger -> GDB Debugger -> Your config -> Executable path" ?
-> Thx, I did not catch that upda
3) Have you tried the settings in Project -> Properties -> Debugger?
oBFusCATed:
--- Quote from: ywi on May 11, 2012, 03:28:42 pm ----> The command passed from gdb to the proxy is "regs". It is works correctly when manually invoked through the debugger window command line. But there is no polling and display on the "CPU registers" window
--- End quote ---
I said output, not the command. Paste it please.
ywi:
1) What is the output of the cpu registers gdb command? Does it look like the one for x86?
-> The command passed from gdb to the proxy is "regs". It is works correctly when manually invoked through the debugger window command line. But there is no polling and display on the "CPU registers" window
2) Have you tried "Settings -> Debugger -> GDB Debugger -> Your config -> Executable path" ?
-> Thx, I did not catch that update. I can now configure my own debugger, but I get the following error message when I run it: "Starting the debuggee failed: Don't know how to run." I do not have this message with 10.05 ("do *not* run the debugee" option is disabled in both cases). When I use a custom command file (-x option) I don't get the previous error, I can talk to the proxy, erase and load the flash, but gdb does not seem to release the target from reset, so I cannot debug.
3) Have you tried the settings in Project -> Properties -> Debugger?
Yes, I call the proxy as an additional shell command, but it does not seem to work. But I still need a separate button to load the flash.
Navigation
[0] Message Index
[#] Next page
Go to full version