
Release Notes for StellarisWare Revision 7611 (July 2, 2011)
3.10 New Features in Stellaris Utility Librar y
3.10.1 swupdate.c can be configured not to use ROM boot loader (Refer-
ence 13270)
Previous versions of swupdate.c, the module used to notify Ethernet applications that a firmware up-
date is being requested and to transfer control to the Ethernet boot loader, always called the ROM-
based Ethernet boot loader if it was available. When an application is making used of a customized
Ethernet boot loader in flash, however, this is undesirable so a #define has been added to allow this
behavior to be overridden and have swupdate transfer control to a flash-based boot loader even if a
ROM-based one is available. To activate this behavior, ensure that USE_FLASH_BOOT_LOADER
is defined when you compile swupdate.c.
3.10.2 ustrncpy and ustrlen functions added to ustdlib (Reference 13422)
New function ustrncpy and ustrlen mimicing the C runtime functions strncpy and strlen, have been
added to the ustdlib module and usvnprint and ustrstr have been modified to use these functions
rather than the C runtime versions. This allows ustdlib to be completely independent of the C
runtime library.
3.11 Bug Fixes in DK-LM3S9B96 Firmware Package
3.11.1 SimpliciTI addresses corrected to ensure uniqueness (Reference
13505)
Despite the fact that the code commenting indicated that SimpliciTI low power RF device addresses
were being set using the least significant 4 bytes of the Ethernet MAC address, the code was, in
fact, using the most significant 4 bytes. As a result, attempts to communicate between multiple
Stellaris boards via the SimpliciTI protocol would frequently fail since the boards had the same de-
vice addresses. This has now been corrected and the correct information is being used to generate
the device addresses, thus allowing multiple Stellaris boards to communicate correctly.
3.11.2 Fix value of dummy CRC in FatFs SD card dr iver that was causing a
problem with some SD cards (Reference 13300)
A value of 0 was being used for dummy CRC for some SD card transactions, when it should be
0xFF. This only affected some SD cards. The driver was changed to use 0xFF for the dummy CRC
value.
September 16, 2011 39
Commenti su questo manuale