This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

OTA update using nRF Android Toolbox Application getting failed

When I enable the OTA AT Command on the nRF52832 module and click on the DFU option available on the nRF toolbox Android Application, selected the OTA Package which shows the complete package as Invalid. The same package is getting OK response using the nRF iOS Application. 

NOTE: If I rename the OTA package as "filename_DTM".zip the package shows OK. But If I take it with the default name it shows as invalid file. But the same file name is showing OK on iOS nRF Application

Attached is the screenshot of the setup. Kindly share your thoughts/comments for the same.

Parents Reply Children
  • Hi Hung, 

    My Default Name of the OTA Package is "BM+S42_Central_ATEX_V3_12_0002_FWupdate_OTA.zip" for which the package shows as Invalid File. But If I change the name to "BM+S42_Central_ATEX_V3_12_0002_FWupdate_OTA_DTM.zip" or “SBS4604_V3.12.0002_with_DTM.zip” both the things are working fine. I do not see any limitations to the naming conventions for the OTA related to chipset. Looks like the Android App is not allowing the package with the default names. But with other nRF52832 OTA package, I could able to succeed with the default names without any modifications. 

  • Please try to remove the '+' in the file name and check if it works ? I tried here with "BM+S42_Central_ATEX_V3_12_0002_FWupdate_OTA_DTM.zip"  and nRF COnnect still said that it's Invalid file. 
    But if I tried with "BMS42_Central_ATEX_V3_12_0002_FWupdate_OTA.zip" or "BMS42_Central_ATEX_V3_12_0002_FWupdate_OTA_DTM.zip" it worked 

Related