• State Not Answered
  • Replies 4 replies
  • Subscribers 87 subscribers
  • Views 511 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 272593
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NrfConnect on iPhone does not allow to upgrade with confirmed firmware

sebsko

During the release, we got 2 files with firmware, with and without confirmed in the name.

I want to upgrade my device with the nRF Connect application and confirmed firmware. When I try to use the android application, it works perfectly, the device is upgraded and reports a new version.

When I want to do the same with iPhone the application closes immediately after "Start". I use the same device, the same firmware file, but after click "Start" the application closes.

It's really important because most of our customers have iPhones/iOS.

.

Parents
  • 0

    Hi,

    I have not been able to reproduce this. I tested with the smp svr sample from NCS 1.6, and renamed the upgrade image to "app_update_confirmed.bin". With that, update using iOS 16.6 and nRF Connect for Mobile 2.4.12 the upgrade was successful as expected.

    Can you explain in more detail exactly how to reproduce the issue you are seeing?

  • 0 in reply to Einar Thorsrud

    As far as I know from hardware people, the released version contains 2 bin files: with and without confirmed in the name. When I use confirmed FW on iPhone it closes the application, the same file on Android works ok. I think it's not about to rename the image to "confirmed.bin", both files have probably different content.

    What I know from hardware people when they build/release the firmware it is "confirmation Firmware". They said it's a common format of files.

  • 0 in reply to sebsko

    Hi,

    It was just my too quick assumption that you used the nRF Connect SDK, I see that was not specified. I have now tried to reproduce using the nRF5 SDK and rename the upgrade images to contain "confirmed", but still no success preproducing. Please provide detailed instructions on how to preproduce this issue (exactly how do you generate the upgrade images, exactly what are they named (as you write that is important) for which bootloader version, which nRF Connect for Mobile version do you use).

Reply
  • 0 in reply to sebsko

    Hi,

    It was just my too quick assumption that you used the nRF Connect SDK, I see that was not specified. I have now tried to reproduce using the nRF5 SDK and rename the upgrade images to contain "confirmed", but still no success preproducing. Please provide detailed instructions on how to preproduce this issue (exactly how do you generate the upgrade images, exactly what are they named (as you write that is important) for which bootloader version, which nRF Connect for Mobile version do you use).

Children
Related
Terms of service