Frederic Beaulieu wrote:
I think I have found the problem but I don't understand it very well. It seem that msp430-jtag restart the mcu and it have time to erase the section @ 0x6000 (did in the very first line of code) before I read it. Is there someone who know how msp430-jtag work? Is it a possible explanation?
absolutely. msp430-jtag resets the CPU to get a clean state on the connection. gdbproxy does that too on first connection, but then you have the posibility to run the program and stop it later without an additional reset. msp430-jtag currently does not support that, as the library it uses does not support it direclty (which in turn is based on the flash writing appnote from TI).
chris
