1. Home
  2. Electronics Design
  3. MSP430 Programming problem using MSPGCC win32 pkg - help!

MSP430 Programming problem using MSPGCC win32 pkg - help!

message

relevance.Has

I had all sorts of similar problems when I started using a setup like yours - MSP430F449, parallel port JTAG, mspgcc. My target hardware was powered by an external DC supply. When using the JTAG however the board was also getting power through the JTAG connector. I found that if I unplugged the external supply whenever I was using the JTAG then all the problems went away.

With the external power disconnected, and the JTAG connected I use the command:

"msp430-jtag -ep a.out"

to both erase then program the flash. Typing the command causes the board to power up through the jtag connector.

Don't know if this is relevant to your problem but maybe?

Regards, Richard.

formatting link

Reply to
Richard
Loading thread data ...

Hi guys - we are using the Win32 MSPGCC package from sourceforge and are having a little trouble programing the microcontroller (MSP430F149).

Via our JTAG programmer board we can connect to the micro, read the device identity, Vcc voltage and dump the register values etc ok. However when we try to download the binary program file we have problems.

The messages we receive are:

Debug window - "memory access error when loading section.txt". GDB Proxy Window - "Could not write to device memory"

If we try to erase the device using - "monitor erase all", we get a message back stating "received command erase, could not preserve/restore device memory (12)"

From the above it seems our JTAG programmer and the test board/connections are all working ok. The PC is running Win XP if this is of any relevance.Has any one any advice as to what our problem is?

TIA

regards rob

Reply to
Rob

////////////>

Hi Richard - thanks for the feedback, it could be the problem. I'll check it out during the week. regards rob

Reply to
Rob

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.