IPC@CHIP® RTOS – API Documentation

Header image

Main page


Release Notes – SC1x3 @CHIP-RTOS V1.54

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


RTOS - Web server
Ticket: #2290
Component: RTOS - Web server
Type: defect
Summary: No possibility to add a self-signed certificate to the WEB/FTP server
Description: The WEB/FTP server does not allow to work with self-signed certificates. Currently, it's always required to setup a CA.
Solution: Change manor that Web server task load's its certificate.
The self signing certificate must be entered twice, as a CACERT and SERVERCERT.




RTOS - System
Ticket: #2291
Component: RTOS - System
Type: defect
Summary: Return value from BIOS_Execute() and BIOS_ExecuteExt() inadequate
Description: When an internal command executes and fails, the return value from either BIOS_Execute() or BIOS_ExecuteExt() is zero which is the "successful" indication.

This should be corrected.
Solution: Change the return values from these API to better indicate the status.



Ticket: #2017
Component: RTOS - System
Type: enhancement
Summary: Relocation Table
Description: The MX style EXE header's 16 bit slot for relocation table entry count may not be adequate and perhaps should be extended with another 16 bit MSW.

The UPX_Beck tool's previous limit of maximum 0x6000 relocation entries has already given a customer problems. This was for a program of size around 1 MByte. So at this rate, a large application of 3 MBytes would overflow the 0xFFFF EXE header limit for relocation table entries.

Such an EXE header change will impact:

1) This RTOS's EXE Loader
2) UPX_Beck.EXE compression tool

The Paradigm-Beck linker already provides the MS 16 bits of the relocation count in their MX file header.
Solution: Revise DOS EXE loader so that the 32 bit count of relocations is used. And UPX_Beck.EXE tool has also been updated to use the 32 bit count.




RTOS - TCP/IP
Ticket: #2289
Component: RTOS - TCP/IP
Type: enhancement
Summary: Interface handle in IP callback
Description: The IP callback function should be able to determine the interface of the incoming packet. Should add the device interface handle to the IpCallbackUserInfo structure.
Solution: Implemented.








Top of page | Main page

Copyright © Beck IPC GmbH