Question: seer connect mspdebug?

[hacksterous]

Is it possible for seer to talk to a running instance of mspdebug connected to a TI MSP430 microcontroller over USB?

[epasveer]

Hi.

(Thanks for looking at Seer)

I'm not sure. I don't know much about mspdebug. I found a YouTube video. It seems you can run mspdebug like:

$ mspdebug rf2500 "prog blink.elf" gdb

Which may mean it can act as a gdbserver type session. It seems to default to port 2000. So you could try this:

$ seergdb --connect localhost:2000 --sym blink.elf

I'll send an email to the author of mspdebug to see if any gdb GUI frontends can work with his program.

[epasveer]

To point out, here's the FAQ for mspdebug. It has some relevant info.

https://dlbeer.co.nz/mspdebug/faq.html

How do I use MSPDebug to debug from within Eclipse?
...
The GDB Command needs to point to your msp430-gdb
Use remote target
The JTAG device is Generic TCP/IP
Host name is where the JTAG is connected, probably localhost
Port number is the port MSPDebug is listening on.

This suggests you need a custom gdb program. Seer will be okay with that. Just go into Seer's config dialog to change the gdb to use. Make sure to save the new settings. The other settings are fine. Just use the "connect" method I mentioned above.

[epasveer]

I should have mentioned you can test a different gdb program from Seer's command. You don't need to go into Seer's config settings.

$ seergdb --gdb-program /usr/local/specialgdb/bin/gdb --connect localhost:2000 --sym blink.elf

[hacksterous]

I got mspdebug working with msp430-gdb and was able to stop and continue the microcontroller program, but with seerdbg, the mspdebug session just disconnects. I will try with the command line options above. Thanks very much.

[epasveer]

Thanks for kicking the tires with Seer.

Your command would be something like:

$ seergdb --gdb-program /usr/local/specialgdb/bin/msp430-gdb --connect localhost:2000 --sym blink.elf

To help out. First run seer by itself and enable the gdb output and seer output to the log windows.

Then run Seer again when you attempt to debug. The two log views have "save-to-file" buttons. When it disconnects, save the two log files and attach it to this task. It would be greatly appreciated. It will help me debug the problem (hopefully).