Hi,
I tried that: downgraded to V2 with windows utilities because I do not have V2
image saved and I wanted to save it just in case.
With V2 firmware I moved to mspdebug (git version):
>mspdebug uif-bsl -d /dev/ttyUSB16 "hexout 0x2500 0xdb00 old-v2-firmware.hex"
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Device ID: 0xf16c
BSL version is 1.61
Reading 4096 bytes from 0x2500...
Reading 4096 bytes from 0x3500...
Reading 4096 bytes from 0x4500...
Reading 4096 bytes from 0x5500...
Reading 4096 bytes from 0x6500...
Reading 4096 bytes from 0x7500...
Reading 4096 bytes from 0x8500...
Reading 4096 bytes from 0x9500...
Reading 4096 bytes from 0xa500...
Reading 4096 bytes from 0xb500...
Reading 4096 bytes from 0xc500...
Reading 4096 bytes from 0xd500...
Reading 4096 bytes from 0xe500...
Reading 2816 bytes from 0xf500...
>mspdebug uif-bsl -d /dev/ttyUSB16 "prog Uifv3Updater.txt"
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Device ID: 0xf16c
BSL version is 1.61
Erasing...
Programming...
Writing 4096 bytes to 2500...
Writing 4096 bytes to 3500...
Writing 4096 bytes to 4500...
Writing 3374 bytes to 5500...
Writing 2 bytes to f7f0...
Writing 2 bytes to f7fe...
Done, 15666 bytes written
bsl: failed on command 0x3b (addr = 0x0000, len = 0x0000)
>mspdebug tilib -d /dev/ttyACM0 --allow-fw-update
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
MSP430_Initialize: /dev/ttyACM0
FET firmware update is required.
Starting firmware update (this may take some time)...
Initializing bootloader...
Erasing firmware...
tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active
(error = 56)
tilib: device initialization failed
>mspdebug tilib -d /dev/ttyACM0 --require-fw-update Uifv3Downgrader.txt
MSPDebug version 0.18 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
MSP430_Initialize: /dev/ttyACM0
Updating firmware using Uifv3Downgrader.txt
Starting firmware update (this may take some time)...
Initializing bootloader...
Erasing firmware...
tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader active
(error = 56)
tilib: device initialization failed
I try that next: upgrade to V3 with windows, and then downgrade to V2 with
mspdebug and then again upgrade to V3 also with mspdebug.
As mentioned before with "windows" V3 version mspdebug does not work and for
some reason auto update did not work with mspdebug.
Andres
On 12.02.2012, at 23:26, Daniel Beer wrote:
> On Sun, Feb 12, 2012 at 04:10:12PM +0200, Andres Vahter wrote:
>> I am having some trouble with the latest tilib.
>> I got lib from: http://www-s.ti.com/sc/techzip/slac460.zip. Actually the
>> file is now called slac460a.zip.
>>
>> It seems like patches mentioned here are not required anymore
>> http://mspdebug.sourceforge.net/tilib.html.
>> However there seems to be still one patch needed:
>> http://sourceforge.net/projects/msp4linux/files/
>
> That's correct, although the patch you've linked to may not work
> correctly for 64-bit systems. A better fix would be to change the
> argument type of getTiFileBytes from size_t * to uint32_t *.
>
>> There is something about it:
>> http://sourceforge.net/mailarchive/forum.php?thread_name=20120110173558.232840%40gmx.net&forum_name=mspgcc-users
>>
>> So I just added the patch: patch -p1 < slac460a.patch
>> And build the driver (Ubuntu 11.04 32 bit)
>>
>> Then I upgraded FET debbuger firmware with CCS (windows).
>>
>> After that I returned to Ubuntu and tried mspdebug:
>>> mspdebug tilib -d /dev/ttyACM0
>> It also asked for software upgrade, which was successful.
>> Anyway it worked after that.
>>
>> Then I did some work in CCS and it also wanted again do to firmware upgrade.
>>
>> After that git version mspdebug upgrade did not work anymore. Actually it
>> worked one time. But now I get error:
>>
>> mspdebug tilib -d /dev/ttyACM0 --allow-fw-update
>> MSPDebug version 0.18 - debugging tool for MSP430 MCUs
>> Copyright (C) 2009-2011 Daniel Beer <dlb...@gmail.com>
>> This is free software; see the source for copying conditions. There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>
>> MSP430_Initialize: /dev/ttyACM0
>> FET firmware update is required.
>> Starting firmware update (this may take some time)...
>> Initializing bootloader...
>> Erasing firmware...
>> tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader
>> active (error = 56)
>> tilib: device initialization failed
>>
>>
>> It still works perfectly under CCS, after CCS upgrades its firmware.
>
> That's the one issue with the library -- the library only works with a
> matched version of firmware. I'm not sure what the problem is in this
> case, but it looks like a library issue. One thing you could try is
> running through the downgrade/upgrade cycle just using mspdebug (don't
> do anything in Windows):
>
> http://mspdebug.sourceforge.net/tilib.html#fet_firmware
>
> Note that in the document above, the upgrade procedure is given first.
> I've run through this procedure a few times with the FET I have here,
> and it seems to be fairly reliable. Let me know if it doesn't work for
> you.
>
> Cheers,
> Daniel
>
> --
> D.L. Beer Engineering
> www.dlbeer.co.nz
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
