
Release Notes for StellarisWare Revision 4674 (May 19, 2009)
22.8 Bug Fixes in Stellaris USB Library
22.8.1 Fixed a USB host MSC bug causing a hang on multi-block reads
(Reference 9411)
A bug existed in the previous release which would cause USBHMSCBlockRead() and USBHM-
SCBlockWrite() to hang if passed a ulNumBlocks value greater than 1. This was due to an as-
sumption in usbhscsi.c that all reads and writes would be performed on a block-by-block basis
resulting in incorrect block numbers being written to the read and write command blocks generated
in USBHSCSIRead10() and USBHSCSIWrite10().
22.8.2 USBDCDInit() now disconnects before reconnecting (Reference
9442)
The USBLib device initialization function USBDCDInit() now explicitly disconnects the device from
the bus and delays approximately 100mS before connecting it once again. The previous version
of the function did not perform this disconnect operation and, as a result, if the function was called
when the device was already connected to the USB bus, it would not be reenumerated resulting in
missing callbacks to the application and resulting application confusion.
22.9 New Features in Stellaris Utility Librar y
22.9.1 Added function fs_map_path() to fswrapper module (Reference
9322)
The fswrapper module offers a method to give multiple file system images user-friendly names
in web URLs. It can support FAT logical drives and binary file system images but only provides
the subset of file system operations typically required by a web server. To allow access to the
more advanced functions provided by FatFS for FAT logical drives, a new API has been provided,
fs_map_path(), which will map a path in the fswrapper namespace to the equivalent path at the
FatFS level (for mount points that correspond to FAT logical drives). For example, passing the
string “/sdcard/index.htm” would return “0:/index.htm” assuming the mount point name “sdcard” is
associated with FAT logical drive number 0.
22.10 Bug Fixes in Stellaris Utility Library
22.10.1 Change between static and DHCP IP sometimes fails (Reference
9438)
The function, lwIPNetworkConfigChange, does not always switch properly between static IP and
Auto IP (with DHCP). This is due to the fact that the variable that retains the current IP mode setting
September 16, 2011 183
Commenti su questo manuale