IPC@CHIP® RTOS-Linux – API Documentation

Header image

Main page

Release Notes – SC1x8 @CHIP-RTOS-LNX V01.00 [29.07.2015]

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

UDPCfg server
Ticket: #193
Component: UDPCfg server
Type: defect
Summary: Correct the IP configuration of multi-home indexes on interfaces where DHCP is enabled.
Description: If DHCP is enabled on an interface then configuring a new multi-home index overwrites the DHCP settings of that interface on the CHIP.INI. A multihome-home index on an interface where DHCP is enabled will also appear as having DHCP thus promting the @CHIPTOOL to report that it was not correctly configured.
Solution: Fixed.

Ticket: #194
Component: UDPCfg server
Type: defect
Summary: Implement watchdog mode setting in udpCfgSrv.
Description: The udpCfgSrv must set the correct watchdog mode when programming the RTOS.

Also, inhibit the user from changing the watchdog mode while the system is being programmed.
Solution: Fixed.

Ticket: #196
Component: Clib
Type: defect
Summary: Configure the eth1 interface from the IP_ETH1 chip.ini section
Description: The eth1 interface should be configured from the IP_ETH1 chip.ini section and not the ETH1 section.
Solution: Fixed.

Ticket: #197
Component: HW-API
Type: defect
Summary: Refreshing watchdog could block for 10ms and more
Description: The functions hal_watchdog_manager_refresh() and watchdogManagerRefresh() could block the execution of the calling task for 10ms and more.
Solution: Fixed. Avoid the priority inversion at an internal semaphore.

Ticket: #203
Component: RTX-native
Type: defect
Summary: Creation of RTX object leads to long not pre-emptible sections
Description: Some RTX API functions (e.g. for creating new tasks, message exchanges, etc.) are blocking the RTX API. In that case other tasks must wait until the creation was done. Some of these function need 400us or more. These long not pre-emptible sections have to be avoided. Note that also starting a BEX file is concerned with that since here the main task is created.
Solution: Fixed.

Ticket: #204
Component: RTX-native
Type: defect
Summary: Watchdog is still triggered in scheduler locked section
Description: When the user locks the scheduler with RTX_Disable_Task_Scheduling() the watchdog is still triggered by the system. This should be corrected.
Solution: Fixed.

Ticket: #198
Component: RTX-native
Type: enhancement
Summary: Optimize execution times of non-blocking RTX calls
Description: In some cases non-blocking RTX calls need execution times of 300us and more. This should be optimized.
Solution: Fixed. Switched the internal mutex type from "priority protect" to "priority ceiling" type. This avoids context-switches during the these locked sections.

Ticket: #195
Component: Shell
Type: enhancement
Summary: Should add mem command
Description: Should add the shell "mem" command to output the memory usage.
Solution: Implemented.

Top of page | Main page

Copyright © Beck IPC GmbH