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. Maybe it
> gets loaded to a wrong location? Anything I can do to help you debug it?
> The output looks perfectly fine:
>
> Trying to open UIF on /dev/ttyUSB0...
> Device: MSP430F249
> Erasing...
> Programming...
>
> It does identify the device as a 249, maybe causing it to assume a
> different memory layout?
Hi Michiel,
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 copy/paste the msg28 data, I could probably put together a patch
that'll get this working. If you really need to get it working in the
meantime, the hack below should do it, if you apply it on top of the
git version.
Cheers,
Daniel
diff --git a/fet_db.c b/fet_db.c
index d77e999..76c426e 100644
--- a/fet_db.c
+++ b/fet_db.c
@@ -269,7 +269,7 @@ static const struct fet_db_record fet_db[] = {
},
.msg29_params = {0x00, 0x4f, 0x47},
.msg29_data = {
- 0x00, 0x11, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x10,
+ 0x00, 0x80, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x10,
0xFF, 0x10, 0x40, 0x00, 0x00, 0x02, 0xFF, 0x09,
0x00, 0x00, 0x00, 0x00, 0x03, 0x00, 0x02, 0x00,
0x02, 0x00, 0xD7, 0x60, 0x00, 0x00, 0x00, 0x00,
------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
