User forums > Embedded development

MSP430 debugging closes immediately after connection

<< < (2/3) > >>

ljstrickler:
Thanks, what good is the predefined entry for the 430 then? I'd think that it would be setup correctly if it is predefined.
Sorry, I thought I was using code tags, who would have thought that a # was code instead of a typewriter, # is a number to me

ljstrickler:
Could there be an entry by the debugger configuration that takes you to the setup? This would make it more obvious and create the one for the MSP430 by default since the menu entry is there.

This has been a great application other than some confusing parts.

oBFusCATed:
And the defaults would be?

ljstrickler:
The same as the set up for the rest of the msp430 files, add "msp430-" to the beginning, msp430-gdb. It auto-populated the rest of the file names.

Maybe instead of labelling the line "Debugger" in the compiler setup you can change it to "Configured Debuggers", this at least would give you a clue that it CAN be configured. As it stands now there is nothing there indicating that the debugger can be configured.

ljstrickler:
Have you got a clue as to what needs to be done to get the "Additional shell commands" to actually execute? The tools menu effectively prevents you from running pkill or killall as the first command of a multi-command tool when hidden. If not hidden you can use them just fine but you can't exit without a keypress.

The debugger interface starts fine but it can get annoying if you constantly have to either start it by hand or kill it by hand once done, this is why I'm trying to get this to work. Adding the ability of the first line of launching options but allow it to exit without a keypress would also help.

Navigation

[0] Message Index

[#] Next page

[*] Previous page