We want replace product target IC from nRF51822 to nRF52832, What need to do for mobile APP?

Dear:
We have product using nRF51822 with BLE to UART bridge between an app on the phone and the UART interface on the nRF51822 device.
that include control command and OTA function between device and mobile app


We evaluate nRF52832 as a replacement target IC. 

Does the mobile app need to be changed? Can the existing app be used?

Parents
  • Hi,

    The existing mobile app for your nRF51822-based product should generally work with an nRF52832-based replacement, especially if you're using Nordic's standard BLE UART service. However, there are a few considerations:
    1. BLE UART Service: If your current app uses Nordic's UART service, it should be compatible with nRF52832. The Nordic UART Service example is available for nRF52 series devices, including nRF52832 Nordic Q&A: UART and BLE.
    2. OTA (Over-The-Air) Updates: For OTA functionality, nRF52832 supports Device Firmware Update (DFU) over BLE. If your current app uses Nordic's DFU service, it should work with nRF52832 as well. Nordic provides the nRF Device Firmware Update mobile app for this purpose, which supports nRF52 series devices.
    3. Bluetooth Version: The nRF52832 supports Bluetooth 5.4, which is newer than what nRF51822 supports nRF52832 Product Page. Your existing app should still work, but you may want to update it to take advantage of new Bluetooth 5 features if desired.
    4. SDK Compatibility: If you're using Nordic's SDKs, note that the nRF52832 is supported in newer SDK versions. You may need to update your device firmware to a compatible SDK version, which could potentially require app updates if there are significant API changes.
    In conclusion, while your existing app should generally work with an nRF52832-based device, it's recommended to test thoroughly and potentially update the app to take full advantage of the nRF52832's capabilities. If you're using standard Nordic services and recent SDK versions, the transition should be relatively smooth.
    Best regards,
    Charlie
Reply
  • Hi,

    The existing mobile app for your nRF51822-based product should generally work with an nRF52832-based replacement, especially if you're using Nordic's standard BLE UART service. However, there are a few considerations:
    1. BLE UART Service: If your current app uses Nordic's UART service, it should be compatible with nRF52832. The Nordic UART Service example is available for nRF52 series devices, including nRF52832 Nordic Q&A: UART and BLE.
    2. OTA (Over-The-Air) Updates: For OTA functionality, nRF52832 supports Device Firmware Update (DFU) over BLE. If your current app uses Nordic's DFU service, it should work with nRF52832 as well. Nordic provides the nRF Device Firmware Update mobile app for this purpose, which supports nRF52 series devices.
    3. Bluetooth Version: The nRF52832 supports Bluetooth 5.4, which is newer than what nRF51822 supports nRF52832 Product Page. Your existing app should still work, but you may want to update it to take advantage of new Bluetooth 5 features if desired.
    4. SDK Compatibility: If you're using Nordic's SDKs, note that the nRF52832 is supported in newer SDK versions. You may need to update your device firmware to a compatible SDK version, which could potentially require app updates if there are significant API changes.
    In conclusion, while your existing app should generally work with an nRF52832-based device, it's recommended to test thoroughly and potentially update the app to take full advantage of the nRF52832's capabilities. If you're using standard Nordic services and recent SDK versions, the transition should be relatively smooth.
    Best regards,
    Charlie
Children
No Data
Related