IPC@CHIP® RTOS-PPC – API Documentation

Header image

Main page


Release Notes – SC2x3 @CHIP-RTOS-PPC V1.40

The tickets are grouped by component and then sorted by type and ticket number.


RTOS - File system
Ticket: #388
Component: RTOS - File system
Type: defect
Summary: "No file sharing" and "file sharing" modes not implemented correctly
Description: When file sharing is not enabled, the open() file method fails to prevent an open for read when that file is already opened for write.
Solution: Implementation corrected.



Ticket: #389
Component: RTOS - File system
Type: defect
Summary: BIOS_LFN_Findfirst() node lock problems
Description: 1) Documentation states that this is a "write" lock. Actually it inhibits only a directory remove or rename operation. (Files within the directory can be added or deleted during this lock period.)

2) The node lock is not working at all when the search does not include the *.* after the directory name.

3) When file list editing is done during a directory scan, the scan may report non-sense on drives formatted with the PLP option.
Solution: Problems corrected inside @Chip-RTOS. Also the previous limitation on PLP drives which allowed for only 6 concurrent directory scans has been eliminated. Now any number of directory scans can be done concurrently on a PLP drive (same file system resource limitations as for a normal drive). The PLP directory scan redesign required the enforcement of the 65536 node directory size limit specified by Microsoft's FAT specification. So now this limit is checked when nodes are added to a directory. (Before this was not checked.)



Ticket: #390
Component: RTOS - File system
Type: defect
Summary: File System PLP mode was not thread safe
Description: On drives formatted with the PLP (Power Loss Protection) option, the drive can become corrupt due to concurrent write access by multiple tasks. For example, one task deleting files while another is creating files.
Solution: Make all accesses to PLP type drives exclusive, so that all actions taken on the drive are executed sequentially rather than potentially concurrent.



Ticket: #392
Component: RTOS - File system
Type: defect
Summary: BIOS_Fast_Findnext() does not release lock on completion
Description: It was intended that BIOS_Fast_Findnext() would release the directory node lock when ever this function returns a 0 indicating "No file found", as is stated in this function's documentation.

This automatic lock release does not occur, forcing the user to always call BIOS_Fast_Find_Done() in order to not leak file system resources.
Solution: Implementation corrected so that lock is released when "No file found" condition is true.




RTOS - TCP/IP
Ticket: #391
Component: RTOS - TCP/IP
Type: defect
Summary: Invalid parameters in IP outgoing callback
Description: With ticket #355 the IP outgoing callback has been moved to an earlier stage in order to be able to change the destination IP inside the callback. It seems that due to this change not all input parameters, e.g. the totalLength inside the IP header, are valid on entry to the callback.
Solution: Fixed.




RTOS - Web server
Ticket: #394
Component: RTOS - Web server
Type: defect
Summary: Web server overwrites memory address 0
Description: The memory address 0 can get overwritten by the web server on some operations like incoming POST requests or multipart messages.
Solution: Fixed.




RTOS - System
Ticket: #393
Component: RTOS - System
Type: enhancement
Summary: Support SC243 hardware revision 2.02
Description: Should support the new SC243 hardware revision 2.02 with changed flash devices (Micron).
Solution: Implemented. Also created new Bootloader version V4.07.








Top of page | Main page

Copyright © 2009 Beck IPC GmbH