5.3 Resolved Issues

  • Addressed a reported issue where if the module is re-configured using commands which write NVM like paired device list clear (U,<1-8,Z>) or any set commands and rebooted and the application hardware is unable to meet the power requirements of the module, then the Bluetooth LE configuration is restored to defaults as the NVM write triggered by the commands issued fails. The workaround tries to re-write the NVM when the NVM write fails, providing enough time for the application hardware to soon satisfy the power requirements of the module to successfully complete the NVM write operation.
  • Fixed an issue with unresponsive UART that occurs when getting asynchronous connection events while the module is in command mode sending commands.
  • When a smartphone with random private addressing which has already paired and bonded initiates a new pairing and bonding event after deleting the previous bonding information then a new entry is created in the RN4870/71 PDL and previous bonding information on the RN4870/71 will be stale. In this case the user is expected to delete the stale bonding information on RN4870/71. To avoid this, the fix replaces the previous bonding material with the new bonding material.
  • Fixed an issue with NA and IA command where the total advertisement data size was limited to 30 bytes instead of 31 bytes.
  • Fixed issue with list service table commands LS and LC when the service table is large.