Hi,

Erratic behaviour with the debug tools, especially erasing and writing flash, is usually due to inadequate power. It is more common with the flash operations, as they require a higher voltage.

Depending which revision of the FG439 you have, you may need the newer version of msp430-gdbproxy available at ftp.opencall.org. The current one is dated July 22nd. However, if you use an older version it should not give erratic results. It should just say it does not recognise the device.

Regards,
Steve

Arnd-Hendrik Mathias wrote:

Hi everybody,
has anyone some experience with debugging an FG439. The new msp430-gdbproxy version supports the FG439 by being sometimes (!!!) able to identify the target (at least after a couple of resets and/or pulling off and re-plugging the JTAG-interface). But generally the most frequent responses I'm dealing with are masses of
- "Could not reset device (11)",
- "Could not read device memory (6)" and
- "Could not preserve/restore device memory (12)"
usually followed by debugger's attempts "Trying to regain control of the target...". In fact I haven't managed to "monitor erase ..." anything until now. "monitor reset/dump/vcc" seem to work properly and so do regular gdb commands (as far as target connection is "stable"). Can anyone tell me what I'm doin' wrong? I have no idea.
Arnd-Hendrik

SysInfo: I'm working with
- a Linux (S.u.S.E. 9.1) PC (Celeron 233MHz) on a
- msp430fg439 (TI's "Retro-Watch") via
- parallel port JTAG interface (Olimex) using
- the new version of msp430-gdbproxy (build: 2004/04/15 but with the same version "0.7.1" as the old one!),
- msp430-gdb (basis: gdb 5.1.1)
...


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Reply via email to