Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-26 Thread JMGross
Since every device has had a reset sooner or later before you can connect it, I guess it's rather a question of timing, depending on the default settings for MCLK/DCO and the BSL. If you try too soon, you'll fail, if you try too late, you'll be after the BSL code and maybe in the middle of

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-25 Thread Daniel Beer
On Mon, Oct 25, 2010 at 10:21:22AM +0200, Michiel Konstapel wrote: Could you try this patch, and see if it gets the erase/program working? The patch should be applied on top of the latest git version. If you could paste the same startup text you've included above that would also be

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-21 Thread Daniel Beer
On Thu, Oct 21, 2010 at 12:38:20PM +0200, Michiel Konstapel wrote: It looks like it's only erasing now? [...] That's a bug... it should actually be programming, but it doesn't say so in quiet mode. I've just pushed a fix for this through to the git repository. Aside from that, does it

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-19 Thread Daniel Beer
On Tue, Oct 19, 2010 at 10:27:58AM +0200, Michiel Konstapel wrote: Hi Daniel! Probably the reason erase doesn't work is that MSPDebug is sending the wrong address for the segment in the erase request. If you could do: mspdebug uif -d /dev/ttyUSB0 --fet-force-id foo And

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-15 Thread Peter Bigot
The 247 and 249 do have different layouts, but I would have expected mspdebug to write data to the addresses specified in the object file, but perhaps it does something else. If the object file is built for -mmcu=msp430x247, the text section should start at 0x8000 and data at 0x1100. If for

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-15 Thread Michiel Konstapel
- From: Peter Bigot [mailto:p...@peoplepowerco.com] Sent: vrijdag 15 oktober 2010 15:56 To: GCC for MSP430 - http://mspgcc.sf.net Subject: Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247 The 247 and 249 do have different layouts, but I would have expected mspdebug to write data

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-15 Thread Peter Bigot
[mailto:p...@peoplepowerco.com] Sent: vrijdag 15 oktober 2010 15:56 To: GCC for MSP430 - http://mspgcc.sf.net Subject: Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247 The 247 and 249 do have different layouts, but I would have expected mspdebug to write data to the addresses specified

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-15 Thread Michiel Konstapel
-Original Message- From: Peter Bigot [mailto:p...@peoplepowerco.com] Sent: vrijdag 15 oktober 2010 16:37 To: GCC for MSP430 - http://mspgcc.sf.net Subject: Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247 Bad flash on the chip? From a quick look, it seems that the hex

Re: [Mspgcc-users] MSPDebug 0.11 and msp430f247

2010-10-15 Thread Daniel Beer
On Fri, Oct 15, 2010 at 10:00:07AM +0200, Michiel Konstapel wrote: Hi Daniel and others, I've been using mspdebug for flashing (mainly 2418s), which works great. However, when I try to program a 247, there seems to be a problem: flashing completes without errors, but the program doesn't run.