Release Notes - BTLIB V1.04

Header image

Index


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


Ticket: #1
Component: General
Type: enhancement
Summary: Parsing of AT replies
Description: To avoid possible failures the AT strings replied by the Bluetooth deviced shall be better parsed.
Solution: Implemented, several API functions will return new error code BT_PARSE_REPLY_ERROR (-20) in case of such a failure.



Ticket: #3
Component: General
Type: enhancement
Summary: Support for SC243
Description: The BTLIB must be adapted for the new IPC@target SC243.
Solution: Implemented



Ticket: #4
Component: General
Type: enhancement
Summary: Reset/stop the module
Description: BtDeInit() shall reset the module and keep it in reset state.
Solution: Implemented. BtDeInit() hold the module in reset state by setting the reset PIO to low.



Ticket: #8
Component: General
Type: enhancement
Summary: Support of successor modules BT03/4
Description: The bluetooth library must support the BT01/2 successor module BT03/4.
Solution: Implemented. Old applications which are using now BT03/4 needs to be recompiled with the new library.



Ticket: #9
Component: General
Type: enhancement
Summary: Storing of serial settings
Description: The RS232 serial settings (Baudrate ,Wordlen, Parity, Stopbits,FlowCtrl, MinAfterTime and MinBeforeTime) shall not be permanently stored at the internal memory of the BT0x. They shall be only stored at chip.ini, section [BLUETOOTH]. This assures, that the BT0x module will always boot with its serial default settings and then becomes reprogrammed by API function btInit() accordant to its chip.ini settings. At the current implementation it can happen that internal settings of BT0x and of chip.ini can become different (e.g. If the chip.ini was manipulated by-hand). In that case the BT0x module is no longer detectable by the software. Change: If the API functions btWriteRS232Settings() and btWriteEscSequenceTiming() are called with parameter BT_STORE_IN_STARTUP_BT01_DATABASE, the settings becomes valid for the current power cycle and the chip.ini entries are updated to use this settings again after next call of btInit() (or after reboot of the IPC@CHIP). After the boot the BT0x comes up with its default settings (57600 Baud,...). The BtInit() call will check the module and sets then the chip.ini settings (if available).
Solution: Implemented



Ticket: #10
Component: General
Type: enhancement
Summary: Mark ConnStatus PIO and ConnDSR PIO as unused at chip.ini
Description: It should be possible to mark the DTR and DSR Pio at chip.ini (section [BLUETOOTH]) as unused by entering value -1.
Solution: Implemented








Top of page | Index

Copyright © 2010 Beck IPC GmbH