Logo
  • ble_app_all_in_one crashes with hardfault when program DA14535 Module
  • ble_app_lecb L2CAP application can’t handle different src and dest cids
  • ble_app_lecb L2CAP L2CAP app does not reject with Insuff. Auth. when necessary.
  • ble_app_lecb L2CAP app does not add credits to its own channel
  • The DA14585 and DA14531-00 do not include the complete ‘SMP Timeout after Security Request’ fix.
  • syscntl_dcdc_turn_on_in_boost_ROM() leads to a hardfault when DA14531-01 and DA14535 configured in bypass mode
  • Driver configuration structures are not compatible with ROM functions on LLVM
  • UART with DMA flow control
  • Improve error handling in case of AES issue
  • UART ROM driver: Not all baud rates are supported by the stack
  • Wrong register attributes allow modification of the device specific manufacturing data
  • Random number generator incorrectly seeded
  • DA14531 Temperature sensor driver in SDK
  • DA14531 prod_test otp_write function issue
  • DA14531 Trim value issue when waking up from hibernation with no ram retained
  • ADC interrupted with BLE activity
  • DA14585 Secondary Booter - Booting encrypted image bigger than 80KB
  • DA14531 IAR Example : Some missing configuration
  • SMP timeout caused by encryption request during SMP session
  • Always passing ATT_ERR_APP_ERROR in custs1_value_req_rsp_handler()
  • High temperature and RCX
  • PDM support
  • GLPS minor improvement
  • Weight Scale Service : Missing app-callback communication
  • DA14585/DA14586 Crystal trimming lost after sleep
  • Coexistence driver limits the pins for BLE_EIP from P00 up to P07
  • DA14531 ROM booter Limitations
  • I2C asynchronous slave reception
  • UART2 initialization infinite loop
  • Build error with PRODUCTION_DEBUG_OUTPUT enabled
  • HTPT Indication Problem
  • DA1453x bootROM boot specific configuration Limitation
  • Error in unused defines
  • Default system rand() function is not NIST compliant
  • HCI ACL fragmentation does not work correctly
  • Static Random BD Address calculation issue
  • Reset Indication characteristic not firing callback when status error is returned after first read
  • DA14531 Further secondary bootloader optimization for large image files
  • DA145x App_Easy_timer problem during long sleep time
  • Update XTAL32M settings to the robust settings as recommended in the HW guidelines
  • No GTL reply is sent to the host after a failed pairing attempt
  • SDK metric and RCX
  • DA14585 Peripheral does not generate GAPC_PARAM_UPDATED_IND
  • Secondary bootloader runs on both encrypted and un-encypted images
  • If during an SMP session the Master attempts to re-encrypt the link, the encryption request reaches the 531 Host after an SMP timeout is generated
    • Description
    • Workaround
  • ROM version of adc_input_shift_config() includes wrong delay
SDK6 Known Limitations List
  • If during an SMP session the Master attempts to re-encrypt the link, the encryption request reaches the 531 Host after an SMP timeout is generated

If during an SMP session the Master attempts to re-encrypt the link, the encryption request reaches the 531 Host after an SMP timeout is generated

ID: LPCBARESDK-993

Status: Open

First reported: SDK6.0.14

Fixed in: TBD

Description

During an SMP session, the Master (usually the smartphone) issues a request to an encryption protected attribute. The Slave (DA14531) replies with an “Insuffienct Encryption” response, and this causes the Master to refresh the encryption (pause and restart it) right after Slave’s key transfer and before Master’s key transfer during Bonding.

The DA14531 Controller stalls and does not forward the new encryption request to its Host in time. The phone remains waiting in the new Encryption Procedure and unavoidably an SMP timeout occurs in DA14531. After the SMP timeout, the Encryption Request is forwarded to the DA14531 Host. The encryption may be succesfull afterwards, but the SMP session is lost (despite the Master transmitting its pending keys).

Other Link Layer procedures that require Host confirmation (parameter update) reach the DA14531 Host in time with no trouble.

Workaround

No workaround is known at this time. Please Contact your Renesas representative to obtain appropriate support.

Previous Next

© Copyright 2025, Renesas Electronics Corporation.