Known Bugs SC12 @CHIP-RTOS V1.

10
Date: April 6, 2005
This document lists all known defects of the @CHIP-RTOS version above. The list is sorted by
our internal change request numbers "CR Number" and by "Component". The report fields
"Component" and "Category" are describing the affected part(s) of the @CHIP-RTOS.
"Synopsis" and "Description" are used for description of the defect.

Component: @CHIP-RTOS (1 item(s))

CR Number: 1039
Component: @CHIP-RTOS
Checked:
Synopsis: Delayed RTOS Timer interrupt
Description: The RTOS Timer interrupt becomes delayed, if serial communication is done with
one of the following settings:
1) 8N2
2) 8M1
3) XON/XOFF flow control
4) RS485
Work Around:

Component: BIOSINT API (1 item(s))

CR Number: 1077
Component: BIOSINT API
Checked:
Synopsis: Write/Read user persistent data
Description: At every call of BIOSINT functions 0x45 or 0x46 512 bytes of memory are
allocated but not released.
Work Around: Should be not a problem, if this function is not called very often.
Component: Chip.ini (2 item(s))

CR Number: 1005
Component: Chip.ini
Checked:
Synopsis: Inserting CHIP.INI entries can lead to invalid opcode interrupts.
Description: If all arguments of BIOS API call "Interrupt 0xA0 service 0x23: Insert an entry in
chip.ini" have maximum length, memory gets corrupted.

If section name does not exist, the sum of section name, item name and the
inserted item text should not be more than 90 characters. If section name does
exist, the sum of item name and inserted item text should not be more than 90
characters.
Work Around:

CR Number: 1040
Component: Chip.ini
Checked:
Synopsis: Writing empty keyword strings to chip.ini
Description: Writing an (illegal) empty string to a keyword in a section, the keyword will be
duplicated every time it is written.
Work Around:

Component: FTP server (1 item(s))

CR Number: 983
Component: FTP server
Checked:
Synopsis: Close failure at terminated incomplete file download
Description: Close failure at terminated incomplete file download.
After a terminated incomplete transfer of a file to the IPC@CHIP, it seems that the
FTP server doesn't close the file, because deleting of this file is only possible after
a reboot of the IPC@CHIP.
Work Around:
Component: HW API (2 item(s))

CR Number: 999
Component: HW API
Checked:
Synopsis: Save non-volatile data
Description: Save non-volatile data doesn't work on older SC12's with Mosel flash memory.
Work Around: For SC12 RTOS Version V1.10 LARGE, LARGE_PPP, MEDIUM, MEDIUM_PPP,
SMALL (not TINY)
reformat the filesystem after the RTOS download with
"format a: /r:48".

CR Number: 1031
Component: HW API
Checked:
Synopsis: Restore of non-volatile data don't work if data is greater 32767 bytes.
Description: If non-volatile data is greater 32767 bytes, the function "restore non-volatile data"
re-creates the REMA.BIN file and sets all variables to zero.
(This problem was already fixed in SC12 RTOS 1.10 Beta, but appears again in
SC12 RTOS 1.10)
Work Around:

Component: Int21h (1 item(s))

CR Number: 1065
Component: Int21h
Checked:
Synopsis: Total clusters is reported wrong.
Description: The number of total clusters in DOS INT21h function 0x36 is reported wrong on
large drives.
Work Around:
Component: Packet API (2 item(s))

CR Number: 1033
Component: Packet API
Checked:
Synopsis: RTOS Tiny version: Installation of ARP and IP packet handlers
Description: Installation of ARP and IP packet handlers at the RTOS TINY version is not
possible.
Work Around:

CR Number: 1036
Component: Packet API
Checked:
Synopsis: Minimum length of an ethernet packet
Description: At function 0x04 (Send packet) the packet size must round up to 65, if the given
packet has a smaller length.
Work Around: Take care, that you call the Packet send function with a minmum length of 65

Component: RTOS API (1 item(s))

CR Number: 988
Component: RTOS API
Checked:
Synopsis: API function 0x46, Find an event group
Description: Calling API function 0x46 (Find an event group) returns an invalid event group ID.
The returned ID cannot be used for further event group API calls.
Work Around: Inside of an @CHIP-RTOS application you should store the wanted Eventgroup-ID
at a global variable.
Use this global variable for calling further Eventgroup API functions. Between two
or more several RTOS programs you can exchange the Eventgroup ID e.g. via an
own defined software interrupt.
Component: SPI API (1 item(s))

CR Number: 1037
Component: SPI API
Checked:
Synopsis: Read and write function
Description: This function does not work correct.
Work Around: Please use the separate read and write functions 0x95 and 0x96

Component: TCPIP API (1 item(s))

CR Number: 1062
Component: TCPIP API
Checked:
Synopsis: Adding addtional Ethernet TCP/IP device driver
Description: Adding an additional Ethernet TCP/IP device driver interface is only possible at
RTOS variants for IPC@CHIP target SC11
Work Around:

Component: TCPIP stack (2 item(s))

CR Number: 989
Component: TCPIP stack
Checked:
Synopsis: Changing the default gateway
Description: In very rare cases it can lead to an internal TCPIP deadlock, if the default gateway
configuration is changed, during a running TCPIP socket communication. If the
deadlock has occured, TCPIP communication is no longer possible. It is necessary
to reboot the IPC@CHIP. The problem can come into existance, if command ipeth
is called (after changing the chip.ini gateway entry) or if TCPIP API function 0x80
(Add_Default_Gateway) is called.
Work Around: Avoid the changing of the gateway during a running TCPIP socket communication.
 CR Number: 1085
Component: TCPIP stack
Checked:
Synopsis: Security leak
Description: Detected by Nessus security check:
A so-called "Land attack" can lead to corrupted TCP/IP stack and invalid opcode
interrupts.

Work Around: It is possible to filter out incoming "Land attack" packets. With TCPIP API function
0x7A, the user can install a filter function, which is executed by the TCPIP stack at
any incoming IP packet. Inside of this function the user is able to check the
incoming packet and decide wether the TCP/IP stack should process the packet or
ignore it. BECK provides an example program for installing an "Land attack" filter
function. Please contact support@beck-ipc.com.

Component: Webserver (1 item(s))

CR Number: 984
Component: Webserver
Checked:
Synopsis: Fault at file upload
Description: If a file is uploaded to the IPC@CHIP by using Netsacpe 4.6, one byte more than
the original filesize is stored. Problems with other browsers are not known.
Work Around:

Total: 16