Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

2016-08-11 Thread MarkoC
Hello, thanks to all that have replied, I will be able to dig into this now. I'll try to check the clock too, to see if I have to buy a new interface... I bought this one a LONG time ago, and now had to resurrect an old laptop, to have LPT port at all! Marko -- View this message in context: h

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

2016-08-11 Thread Daniel Beer
On Thu, Aug 11, 2016 at 04:54:18AM -0700, MarkoC wrote: > mc@bpc2 ~/MSP430/MSP-FET $ mspdebug pif -j -d /dev/parport0 > MSPDebug version 0.22 - debugging tool for MSP430 MCUs >From the output, it doesn't look like there's anything wrong obviously wrong with your ELF file, but one thing to be aware

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

2016-08-11 Thread David W. Schultz
It has been a while but I seem to remember having a similar problem. Too long ago to remember details but I think it was a problem with the section flags. You can check the flags using msp430-elf-readelf -S XX.elf -- David W. Schultz http://home.earthlink.net/~david.schultz "Life without stock

Re: [Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

2016-08-11 Thread Ben Green
Hello MarkoC, To rule out a problem with the ELF file (it looks like it is OK from the prog output) use the msp430 binutils to disassemble: msp430-objdump --disassemble main.elf That should confirm you have some valid code in your ELF. The flash offsets seem correct for the device you are using

[Mspgcc-users] Mspdebug: "prog" programs vectors, not program code

2016-08-11 Thread MarkoC
Hello, I am new to the list. Bought an MSP-FET many years ago, but only got to use it now. I have encountered a strange problem: when I try to flash my chip (MSP430F149), only the interrupt vectors get programmed at 0xFFE0, the code area at 0x1100 remains blank. Are there F149 versions with less