Release notes Sc1x3 @CHIP-RTOS V1.10 ... - Beck IPC Gmbh
Release notes Sc1x3 @CHIP-RTOS V1.10 ... - Beck IPC Gmbh
Release notes Sc1x3 @CHIP-RTOS V1.10 ... - Beck IPC Gmbh
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Description: CGI post method does not work correct after a CGI page with the get method is called.<br />
Fix: Fixed<br />
Type: Suggestion, Component: Command Shell (1 item(s))<br />
CR Number: 1269<br />
Type: Suggestion<br />
Component: Command Shell<br />
Category: FORMAT command<br />
Synopsis: Specify FAT16/FAT32 format<br />
Description: Would be nice if user could specify FAT32 or FAT16 for CF B: drive formatting.<br />
Fix: Add /F:32 or /F:16 option to FORMAT command for FS_FAT32 configuration. Restrict option to B:<br />
drive.<br />
Type: Suggestion, Component: DHCP (1 item(s))<br />
CR Number: 1255<br />
Type: Suggestion<br />
Component: DHCP<br />
Category: Hostname and client identifier option<br />
Synopsis: Separate client identifier option<br />
Description: If chip.ini entry HOSTNAME_OPT is set, DHCP request are extended with the hostname option<br />
12 and client identifier option 61. For both entries the Chip.ini defined device name is used. The<br />
usage of hostname for both options shall be improved. It's common usage to use the ethernet<br />
mac address as Client identifier. It is necessary to provide an extra chip.ini entry for the DHCP<br />
client identifier option 12.<br />
Fix: Implemented: If Chip.ini entry CLIENT_IP is defined, DHCP inserts the stepcified String into its<br />
request as option 12. If the reseverd keyword MAC_ADDR is used, DHCP inserts the ethernet<br />
address. If CLIENT_IP is not defined, but HOSTNAME_OPT=1 is set, DHCP will still insert the<br />
chip.ini device name.<br />
Type: Suggestion, Component: Filesystem (1 item(s))<br />
CR Number: 1215<br />
Type: Suggestion<br />
Component: Filesystem<br />
Category: Findfirst/findnext<br />
Synopsis: Recursiv call of findfirst/findnext fails<br />
Description: Recursive calls into DOS findfirst()/findnext() operations fail due to use of static data within the<br />
implementation.<br />
Fix: Add FindNext.C module to AMXFS, to replace existing _findfirst()/_findnext() implementation.<br />
This new implementation saves the directory scan context in caller's ffblk data structure, which<br />
makes the function now reentrant (See new fjffPark() and fjffResume() functions).<br />
Type: Suggestion, Component: <strong>RTOS</strong> API (1 item(s))<br />
CR Number: 1234<br />
Type: Suggestion<br />
Component: <strong>RTOS</strong> API<br />
25 von 30
Change language