Skip to content

Releases: telink-semi/tc_ble_sdk

Release V4.0.2.1

28 Mar 06:12
@mwchen269 mwchen269
V4.0.2.1
04d3a57
Compare
Choose a tag to compare
Release V4.0.2.1 Latest
Latest

V4.0.2.1(PR)

Version

  • SDK version: tc_ble_sdk V4.0.2.1
  • Chip Version
    • B85: TLSR825X
    • B87: TLSR827X
    • TC321X (A0)
  • Hardware Version
    • B85: C1T139A30_V1_2, C1T139A3_V2_0
    • B87: C1T197A30_V1_1, C1T201A3_V1_0
    • TC321X: C1T357A20_V1_1, C1T362A5_V1_0
  • Platform Version
    • tc_platform_sdk V3.1.0
  • Toolchain Version

Features

  • Application
    • Add demo "ble_remote" into TC321X, which supports "TL_AUDIO_RCU_ADPCM_GATT_TELINK" audio mode.
    • Add ble_controller demo.

Bug Fixes

  • Application

    • Fix(TC321X): The flash information is not initialized normally when enabling macro "APP_FLASH_PROTECTION_ENABLE" and using Flash "P25Q80SU".
    • Fix: Fix compile error when enabling macro "APP_BATT_CHECK_ENABLE".

  • PM

    • Fix(TC321X): The MCU can not be waken up normally when using long suspend sleep mode.

Refactoring

  • Application
    • Modify "USED_DEEP_ANA_REG" setting in "acl_c1p1_demo", "acl_peripheral_demo" and "acl_connection_demo".

BREAKING CHANGES

  • N/A.

Flash

  • B85

    • ZB25WD40B
    • ZB25WD80B
    • GD25LD40C/GD25LD40E
    • GD25LD80C/GD25LD80E

  • B87

    • GD25LD40C/GD25LD40E
    • GD25LD80C/GD25LD80E
    • ZB25WD40B
    • ZB25WD80B

  • TC321X

    • P25D40SU
    • GD25LD40EGEG (Not Test)
    • P25Q80SU
    • P25Q16SU

CodeSize

  • B85

    • acl_peripheral_demo
      • Firmware size: 81.4 kBytes
      • SRAM size: 31.9 kBytes
      • deepsleep retention SRAM size: 28.3 kBytes
    • acl_central_demo
      • Firmware size: 72.8 kBytes
      • SRAM size: 37.0 kBytes
    • acl_connection_demo
      • Firmware size: 87.3 kBytes
      • SRAM size: 43.0 kBytes
    • acl_c1p1_demo
      • Firmware size: 93.4 kBytes
      • SRAM size: 36.0 kBytes
      • deepsleep retention SRAM size: 31.9 kBytes

  • B87

    • acl_peripheral_demo
      • Firmware size: 79.4 kBytes
      • SRAM size: 31.7 kBytes
      • deepsleep retention SRAM size: 28.1 kBytes
    • acl_central_demo
      • Firmware size: 71.8 kBytes
      • SRAM size: 37.0 kBytes
    • acl_connection_demo
      • Firmware size: 91.2 kBytes
      • SRAM size: 43.0 kBytes
    • acl_c1p1_demo
      • Firmware size: 91.3 kBytes
      • SRAM size: 35.8 kBytes
      • deepsleep retention SRAM size: 31.7 kBytes

  • TC321X

    • acl_peripheral_demo
      • Firmware size: 79.3 kBytes
      • SRAM size: 31.8 kBytes
      • deepsleep retention SRAM size: 28.3 kBytes
    • acl_central_demo
      • Firmware size: 71.6 kBytes
      • SRAM size: 37.3 kBytes
    • acl_connection_demo
      • Firmware size: 86.7 kBytes
      • SRAM size: 43.3 kBytes
    • acl_c1p1_demo
      • Firmware size: 91.5 kBytes
      • SRAM size: 35.9 kBytes
      • deepsleep retention SRAM size: 32.0 kBytes
    • ble_remote
      • Firmware size: 95.5 kBytes
      • SRAM size: 40.4 kBytes
      • deepsleep retention SRAM size: 35.5 kBytes
Assets 2
Loading

Release V4.0.2.0

28 Feb 18:02
@mwchen269 mwchen269
V4.0.2.0
21ba977
Compare
Choose a tag to compare
Release V4.0.2.0

V4.0.2.0(PR)

Version

  • SDK version: tc_ble_sdk V4.0.2.0
  • Chip Version
    • B85: TLSR825X
    • B87: TLSR827X
    • TC321X (A0)
  • Hardware Version
    • B85: C1T139A30_V1_2, C1T139A3_V2_0
    • B87: C1T197A30_V1_1, C1T201A3_V1_0
    • TC321X: C1T357A20_V1_1
  • Platform Version
    • tc_platform_sdk V3.1.0
  • Toolchain Version

Note

  • All changes up to telink_b85m_ble_sdk V4.0.1.3_Patch0003 are included.

  • TC321x has not been fully tested, subsequent iterations will be updated.

  • B85m_controller has been removed in this version, and will be added back in the next version.

  • Battery Voltage Check is a very important function for mass production. The user must check battery voltage to prevent abnormal writing or erasing Flash at a low voltage.

  • Flash protection is a critical function for mass production.

    • Flash protection is enabled by default in SDK. User must enable this function on their final mass-production application.
    • Users should use "Unlock" command in the Telink BDT tool for Flash access during the development and debugging phase.
    • Flash protection demonstration in SDK is a reference design based on sample code. Considering that the user's final application may be different from the sample code, for example, the user's final firmware size is bigger, or the user has a different OTA design, or the user needs to store more data in some other area of Flash, all these differences imply that Flash protection reference design in SDK can not be directly used on user's mass production application without any change. User should refer to sample code, understand the principles and methods, and then change and implement a more appropriate mechanism according to their application if needed.

  • Correct some spelling mistakes

    • For example, change OTA_DATA_UNCOMPLETE to OTA_DATA_INCOMPLETE.

Features

  • Chip

    • Support TC321X A0
      • Support 1M phy and 2M phy.
      • Support PM, including suspend mode, deepsleep retention mode and deepsleep mode.
      • Support Flash Protection.
      • Support Battery Voltage Check.
      • Support Demo:
        • acl_connection_demo
        • feature_test
        • acl_c1p1_demo
        • acl_peripheral_demo
        • acl_central_demo

  • Application

    • Add Flash Protection module and sample

      • Add flash_prot.h/flash_prot.c in vendor/common folder as a common module for all applications.
      • Add Flash protection sample code in project acl_connection_demo/acl_c1p1_demo/acl_central_demo/acl_peripheral_demo. User can refer to the sample code and make sure the Flash protection function must be enabled on their own application.
      • "app_flash_protection_operation" is a common entrance for all Flash operations (Flash write and erase), Flash locking and unlocking are processed in this function.
      • "blc_appRegisterStackFlashOperationCallback" and "flash_prot_op_cb" are used to process some stack internal Flash operation callback which may need Flash locking and unlocking.
      • The Telink OTA and SMP module already add callbacks related to blc_flashProt to inform the application layer that they need to write/erase Flash. Then, the application layer processes Flash lock and unlock.
      • If users do not use Telink OTAs, they need to refer to this design to add similar callback functions in their own OTA code for upper-layer use.
      • Now only firmware is protected in the sample code. System data and user data are not protected now.
      • IRQ disabling time too long in driver API "flash_write_status", BLE system interrupt is delayed, causing RX data error.
      • Driver API "flash_write_status" be replaced by "flash_write_status" in flash_prot.c to solve this issue by calling LinkLayer API "blc_ll_write_flash_status".

    • Add tlkapi_debug module to print logs

      • Add tlkapi_debug.h/tlkapi_debug.c in vendor/common folder as a common module for all applications.
      • Add debug.h in stack/ble/debug. Add APIs "blc_debug_enableStackLog", "blc_debug_addStackLog", "blc_debug_removeStackLog" to control the print stack log.
      • Use GPIO simulating UART TX sequence to output data information to PC UART tool, same function with "printf" function in old SDK.
      • API "tlkapi_printf" and "tlkapi_send_string_data" are recommended for usage, with some macro in app_config.h to control log enabling such as "APP_LOG_EN".
      • Only 1M baud rate can be used. When the system clock is 16M/24M, the assembly is used to control the UART TX timing. When the system clock is 32M/48M, the system_timer is used to control the UART TX timing. IRQ disabling and restoring are used in function "uart_putc" to guarantee UART TX byte data integrity is not broken by IRQ.
      • If the baud rate is too low, IRQ disabling time too long, BLE system interrupt and user interrupt will be affected which may lead to critical error.

  • feature_test

    • Add feature_privacy_peripheral: Sample code for testing peripheral RPA. This sample code to get peer Central(Master) IDA(identity address) if RPA(resolved private address) is used in packet "CONNECT_IND".
    • Add feature_privacy_central: Sample code for testing Central RPA.
    • Add feature_l2cap_coc: Sample code for testing peripheral L2CAP COC.
    • Add Sample code for SC OOB in feature_smp_security.
    • Add feature_phy_test: Sample code for testing PHY functions.
    • Remove feature_misc.

  • Controller

    • Add APIs:
      • "blc_ll_setAdvCustomizedChannel" is used to set some other channel to replace primary advertising chn37/38/39 in ADV state.
      • "blc_ll_configLegacyAdvEnableStrategy", which is used to configure leg_adv enabling by API only.
      • "blc_ll_setScanCustomizedChannel" is used to set some other channel to replace primary advertising chn37/38/39 in SCAN state.
      • "blc_ll_configScanEnableStrategy" is used to configure scan enable by API.
      • "blc_ll_isInitiationBusy" is used to check if initiation is busy.
      • "blc_ll_setCreateConnectionRetryNumber" is used to set create connection retry number.
      • "blc_ll_disableConnUpdHighAuthority" is used to disable connection update high authority for central.
      • "blc_ll_getAclLatestRSSI" is used to obtain the latest RSSI of ACL connections.
      • "blc_ll_getAclConnectionInterval" is used to read current ACL connection interval.
      • "blc_ll_getAclConnectionLatency" is used to read current ACL connection latency.
      • "blc_ll_getAclConnectionTimeout" is used to read current ACL connection supervision timeout.
      • "blc_ll_dataLenAutoExgDisable" is used to disable DLE exchange automatically.
      • "blc_ll_customizeConnectionEstablishEvent" is used to customize Connection Establish Event.
      • "blc_ll_removeDeviceFromResolvingList" is used to remove a device from resolving list.
      • "blc_ll_readResolvingListSize" is used to read resolving list size.
      • "blc_ll_setResolvablePrivateAddressTimeout" is used to set the length of time the controller uses a Resolvable Private Address before a new resolvable private address is generated and starts being used.
      • "blc_ll_setPrivacyMode" is used to allow the Host to specify the privacy mode to be used for a given entry on the resolving list.
      • "blc_contr_setBluetoothVersion" is used to set Bluetooth core specification version in controller.

  • L2CAP

    • Add Peripheral L2CAP COC feature.

      • Add stack/ble/host/signaling/folder, and add signaling.h in this folder.
      • Add some APIs for this feature.
        • blc_l2cap_registerCocModule is used to register the COC Module.
        • blc_l2cap_disconnectCocChannel is used to disconnect with the COC Channel.
        • blc_l2cap_createLeCreditBasedConnect is used to create LE Credit Based connection.
        • blc_l2cap_createCreditBasedConnect is used to create Credit Based connection.
        • blc_l2cap_sendCocData is used to send COC Data.
      • Add some host events in gap_event.h
        • GAP_EVT_L2CAP_COC_CONNECT is triggered by the COC connection.
        • GAP_EVT_L2CAP_COC_DISCONNECT is triggered by the COC disconnection.
        • GAP_EVT_L2CAP_COC_RECONFIGURE is triggered by the COC reconfigure.
        • GAP_EVT_L2CAP_COC_RECV_DATA is triggered when receiving COC Data.
        • GAP_EVT_L2CAP_COC_SEND_DATA_FINISH is triggered after COC Data is sent.
        • GAP_EVT_L2CAP_COC_CREATE_CONNECT_FINISH is triggered after the create COC channel command is sent.

    • Add API "blc_l2cap_reg_att_sig_handler", which is used to register the function to process L2CAP SIG CHANNEL packet.

    • Add API "blc_l2cap_SendCommandRejectResponse", which is used to send command reject response in central.

  • SMP

    • Add Peripheral SC OOB.

      • Add some APIs for this feature.
        • blc_smp_generateScOobData is used to generate SC OOB data.
        • blc_smp_setScOobData is used to set SC OOB data.
      • Add some host events in gap_event.h.
        • GAP_EVT_MASK_SMP_TK_SEND_SC_OOB_DATA is triggered when the peer requests SC OOB.
        • GAP_EVT_MASK_SMP_TK_REQUEST_SC_OOB is triggered when SMP requests SC OOB data.

    • Add some APIs:

      • "blc_smp_setLocalIrkGenerateStrategy" is used to set local IRK generating strategy.
      • "blc_smp_triggerMasterManualSmp" is used to trigger central sending Pairing Request.
      • "blc_smp_sendKeypressNotify" is used to send keypress notify during TK input phrase.
      • "blc_smp_cancel_auth" is used to cancel SMP process.
      • "blc_smp_setDevExceedMaxStrategy" is used to configure the bonding strategy.

  • OTA

    • Add some APIs:
      • "blc_ota_setOtaScheduleIndication_by_pduNum" is used to set resolution of OTA schedule indication by PDU number.
      • "blc_ota_setAttHandleOffset" is used to calculate OTA notify data ATT handle by OTA write data ATT handle.

  • GATT
    ...

Read more
Loading

Release V4.0.1.3_Patch_0003

01 Mar 01:36
@mwchen269 mwchen269
V4.0.1.3_Patch_0003
ac4d07c
Compare
Choose a tag to compare
Release V4.0.1.3_Patch_0003

V4.0.1.3_Patch_0003

Bug Fixes

  • drvier/adc
    • (B87): Fix issue of large ADC error on some chips.

BREAKING CHANGES

  • drvier/adc
    • (B85/B87):Update ADC driver to V2.0.0 and add two-point calibration.

Bug Fixes

  • drvier/adc
    • (B87):修复部分芯片ADC误差偏大。

BREAKING CHANGES

  • drvier/adc
    • (B85/B87):更新 ADC 驱动至 V2.0.0 并添加两点校准功能。
Loading

Release V4.0.1.3_Patch_0002

01 Mar 01:35
@mwchen269 mwchen269
V4.0.1.3_Patch_0002
13e8405
Compare
Choose a tag to compare
Release V4.0.1.3_Patch_0002

V4.0.1.3_Patch_0002

Bug Fixes

  • driver

    • xtal

      • Solved the B85 problem that when the crystal oscillator is abnormal, the program crashes and the software cannot reset by itself.

    • uart

      • Fixed a bug that caused the uart_send_byte() interface to send bytes incorrectly if the DMA data was not sent to completion due to the function exiting and the array memory defined in the stack being freed.
      • uart_clear_parity_error(): Fixed the problem that when clearing uart clear rx status, other uart status bits may be operated by mistake.

    • irq

      • irq_clr_src2(): Fixed the problem that when clearing the specified IRQ source, other IRQ source bits may be operated by mistake.

    • USB

      • usb_handle_irq(): Fixed the problem that when clearing USB reset status, other status bits may be operated by mistake

    • gpio

      • Fixed an issue in the gpio_set_interrupt()/gpio_set_interrupt_risc0()/gpio_set_interrupt_risc1() interface that could mistakenly clear other interrupt status bits.

    • timer

      • timer0_set_mode/timer1_set_mode/timer2_set_mode/timer_start/timer_stop: in addition to the corresponding functions, the interrupt flags of time0/timer1/timer2 are also incorrectly cleared on the preceding interfaces. this problem occurs in the following application scenarios: when multiple timers work at the same time and the interrupt time is very close, the interrupt interface processes the timer that requests the interrupt first. if the above interface is called, the interrupt flag of other timers will be mistakenly cleared, resulting in no response to other timers' interruption. at present, it is modified to only set the corresponding function.
      • Modify the timer0_gpio_init and timer1_gpio_init functions to fix the problem that the gpio interrupt will be accidentally touched when the gpio trigger and gpio width modes are used.

    • watchdog

      • wd_set_interval_ms/wd_start/wd_stop: in addition to the corresponding functions, the interrupt flags of time0/timer1/timer2 are also mistakenly cleared on the above interfaces. At present, they are modified to set only corresponding functions.

    • pm

      • cpu_stall_wakeup_by_timer0/cpu_stall_wakeup_by_timer1/cpu_stall_wakeup_by_timer2:add setting timer0/timer1/timer2 mode0 to prevent these interfaces from working until timer0/timer1/timer2 is not mode0.
      • Solved the problem that the sleep time is incorrect due to a small probability that the total interruption time of the shutdown is not timely.
      • Eliminates the risk that STATUS_GPIO_ERR_NO_ENTER_PM may be set to 1 in the return value of cpu_sleep_wakeup.
      • Resolved the risk that cpu_sleep_wakeup_32k_rc()/cpu_sleep_wakeup_32k_xtal() could crash due to misreading the 32K tick. (The digital reading 32K tick inside these two functions has been replaced with reading using analog registers).
      • Solved the B85 problem of disconnection caused by the 32k calibration value not being updated in time in high and low-temperature environments.

    • clock

      • rc_24m_cal() is added to the clock_init() function to solve the B85 problem of possible probabilistic crash.

  • Extended Scan

    • Fixed the bug that creating connection could fail when using extended scan and times of creating connection have been exceeding 4.

  • SMP

    • Fixed the bug that blc_smp_loadBondingInfoByAddr may load fail when the peer address is RPA.

BREAKING CHANGES

  • pm
    • Delete the cpu_get_32k_tick interface. If you want to read a 32K tick value, use pm_get_32k_tick().

Bug Fixes

  • driver

    • xtal

      • 解决了B85晶振异常时，程序死机，不能自行软件复位的问题。

    • uart

      • 修复了由于 uart_send_byte() 函数退出后，DMA 还未将数据搬运完成前，函数内部定义的数据内存已经被释放，导致数据发送出错问题。
      • uart_clear_parity_error(): 修复了清除uart clear rx状态时，可能误操作其他uart状态位的问题。

    • irq

      • irq_clr_src2(): 修复了清除指定的中断源时，可能误操作其他中断源的状态位的问题。

    • usb

      • usb_handle_irq(): 修复了清除usb reset状态位时，可能误操作其他状态位的问题。

    • gpio

      • 修复了gpio_set_interrupt()/gpio_set_interrupt_risc0()/gpio_set_interrupt_risc1()接口中可能误清其他中断状态位的问题。

    • timer

      • timer0_set_mode/timer1_set_mode/timer2_set_mode/timer_start/timer_stop::以上这些接口除了设置了对应的功能以外，还误清了timer0、timer1、timer2的中断标志位。在如下应用场景下会有问题：当使用多个timer同时工作，并且产生的中断时间很接近时，中断接口中先处理第一个请求中断的timer时，调用了以上接口的话，将其他timer的中断标志位误清，导致其他timer中断没有响应，目前将其进行修改为只设置对应功能。
      • 修改timer0_gpio_init和timer1_gpio_init函数，修复了使用gpio trigger和gpio width模式会误触gpio中断的问题。

    • watchdog

      • wd_set_interval_ms/wd_start/wd_stop:以上这些接口除了设置了对应的功能以外，还误清了timer0、timer1、timer2的中断标志位，目前将其进行修改为只设置对应功能。

    • pm

      • cpu_stall_wakeup_by_timer0/cpu_stall_wakeup_by_timer1/cpu_stall_wakeup_by_timer2:添加设置timer0/timer1/timer2 mode0功能，避免在调用这些接口之前，timer0/timer1/timer2不是mode0，这些接口不能工作。

      • 解决了因关总中断时间不及时，小概率地导致的睡眠时间不对的问题。

      • 规避了cpu_sleep_wakeup的返回值中STATUS_GPIO_ERR_NO_ENTER_PM 可能会被异常置为1的风险。

      • 解决了cpu_sleep_wakeup_32k_rc()/cpu_sleep_wakeup_32k_xtal()可能因为读错32K tick引发死机的风险（已将这两个函数内部，数字读32K tick的方式替换成模拟方式读32Ktick）。

      • 解决了B85在高温和低温环境下，因32k校准值没有及时更新，导致的断联的问题。

    • clock

      • 在B85 clock_init函数中加入rc_24m_cal()解决可能概率性死机的问题.

  • Extended Scan

    • 修复了当使用扩展扫描创建连接的次数超过4次时，创建连接会失败的问题。

  • SMP

    • 修复了当对端地址为RPA时，blc_smp_loadBondingInfoByAddr可能会读取失败。

BREAKING CHANGES

  • driver
    • pm
      • 删除cpu_get_32k_tick接口，如果想要读32K的tick值，可以使用pm_get_32k_tick()。
Loading

Release V4.0.1.3_Patch_0001

01 Mar 01:34
@mwchen269 mwchen269
V4.0.1.3_Patch_0001
83f7215
Compare
Choose a tag to compare
Release V4.0.1.3_Patch_0001

V4.0.1.3_Patch_0001

Bug Fixes

  • Fixed: A very small number of chips rarely experience insufficient oscillation of the 24M crystal after waking up from sleep, leading to MCU abnormality.
  • Fixed: Pairing failure occurs when using Secure Connection with low power deepsleep retention mode.
  • Fixed: The primary Channel advertising packet can not be received when using Coded PHY in Extended Scan.
  • Fixed: The RSSI value is incorrect in the Extended advertising report event.
  • Fixed: The AUX_CONNECT_RSP PDU can not be received when initiating a connection request under Extended Scan Coded PHY S8 mode, resulting in creating connection failure.

BREAKING CHANGES

  • N/A

Bug Fixes

  • 修复: 极少数芯片，低概率出现睡眠唤醒后24M晶体起振不充分，导致MCU异常
  • 修复: Secure Connection，低功耗使用deepsleep retention mode，出现配对失败。
  • 修复: Extended Scan，无法收到Primary Channel使用Coded PHY的广播包。
  • 修复: Extended Scan，Extended ADV report event中RSSI值异常。
  • 修复: Extended Scan，在Coded PHY S8模式发起连接，会出现无法接收AUX_CONNECT_RSP数据包，导致创建连接失败。

BREAKING CHANGES

  • N/A
Loading

Release V4.0.1.3

01 Mar 01:29
@mwchen269 mwchen269
V4.0.1.3
05e2905
Compare
Choose a tag to compare
Release V4.0.1.3

V4.0.1.3

Features

  • SDK version：telink_b85m_ble_sdk_V4.0.1.3
  • Normalizes the naming of content related to private schemas.

BREAKING CHANGES

  • N/A.

Features

  • SDK 版本：telink_b85m_ble_sdk_V4.0.1.3
  • 规范化与私有模式相关内容的命名

BREAKING CHANGES

  • N/A.
Loading