IPC@CHIP® RTOS-PPC – API Documentation

Header image

Main page

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

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

Ticket: #441
Component: RTOS - CAN
Type: enhancement
Summary: Function to get error state
Description: The CAN API should provide a function to get the error state (e.g. error active) of the CAN node.
Solution: Implemented

RTOS - FTP server
Ticket: #439
Component: RTOS - FTP server
Type: enhancement
Summary: SYST command should return "UNIX Type: L8"
Description: To increase the compatibility with FTP clients, the FTP server should return the string "UNIX Type: L8" on the FTP SYST command. Currently, the server only return "UNIX".
Solution: Implemented.

RTOS - IPsec/IKE/Crypt
Ticket: #444
Component: RTOS - IPsec/IKE/Crypt
Type: enhancement
Summary: Add SHA-384 and SHA-512 hash methods
Description: The SHA-384/SHA-512 hash methods shall be added for use by TLS certificates and IPSec. API functions shall also be made available.
Solution: SHA-384 and SHA-512 hash methods have been added for use by TLS certificates, IPsec and new hash API functions. The RSA API has been expanded to include these new hash methods.

RTOS - System
Ticket: #437
Component: RTOS - System
Type: enhancement
Summary: Add stime(), RTX_time() and RTX_stime() API
Description: Thr RTOS-PPC should support the API functions stime(), RTX_time() and RTX_stime() for compatibility with SC1x3/SC2x RTOS.
Solution: Implemented the stime() API and provide the RTX_time()/RTX_stime() macros for source code compatibility.

Top of page | Main page

Copyright © 2009 Beck IPC GmbH