Dear All,

Please remove my e-mail adress from your list

E-mail: e.bo...@chello.nl
Thanks,

E van den Boom
----- Original Message ----- From: "Chris Liechti" <cliec...@gmx.net> To: "GCC for MSP430 - http://mspgcc.sf.net"; <mspgcc-users@lists.sourceforge.net>
Sent: Tuesday, January 12, 2010 12:10 AM
Subject: Re: [Mspgcc-users] BSL InfoSegs Error


Larry Young schrieb:
Thanks to this group, I have been using the msp430/gcc toolchain and the
BSL updater "bsl-updater.nsi" successfully with an MSP430F448.
Yesterday I added some fixed parameters to be stored in the information
segments at 0x1000-0x10ff, by adding a const array of ints with the
__attribute((section(".infomemA"))) syntax and adding this section to
the linker command line.  The resulting hex file shows the new values
correctly, and I can program the MSP430 with msp430-jtag through the
JTAG hardware.  All good, so far.

Unfortunately, when I use the same hex file as the input to the
bsl-updater and create the standalone updater.exe and run it, the update
process dies after:

did you try msp430-bsl on the command line too? you could also
experiment with -D, -DDD (enables more or less debug messages)

  Download on COM4...
  MSP430 Bootstrap Loader Version: 2.0
  Mass Erase...
  Transmit default password ...
  Invoking BSL...
  Transmit default password ...
  Current bootstrap loader version: 1.60 (Device ID: f449)
  Program ...
  40978 bytes programmed.
  Write InfoSegs ...

i do not find this string in the sources. is this an original msp430-bsl
from mspgcc?

  An error occoured:
  NAK received (wrong password?)

it would also report an error if the information memory was not erased
(it would be by default when using -e) or if the hexfile contains the
same segment twice with different data.

  An error occurred, could not write target.
  Aborted.

Can anyone advise me as to why adding data in the 0x1000-0x10ff range
would cause the BSL to fail?  What is happening at the line "Write
InfoSegs"?

good question as i don't find something like that in my sources ;-)
information segments should be programmed along with the normal "Program
..." that happens above.

chris

Larry

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users


Reply via email to