• State Verified Answer
  • Replies 8 replies
  • Subscribers 69 subscribers
  • Views 1913 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 235714
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bootloader: file specified not a valid hex file

Cy

The example bootloader hex files within SDK 15.3 will load on the development board and seems to provide connection through nRF toolbox on a iphone 7 but will not load on custom hardware. The custom boards are fairly mature and have had good success with other applications. The development has been through the armgcc and therefore utilizes the command line tools. The specific command to program the both the development board and my custom hardware was:   nrfjprog --reset --program sd_s132_bootloader_buttonless_with_setting_page_dfu_secure_ble_debug_without_bonds.hex --family NRF52 --sectoranduicrerase which was suggested from the online SDK 15.3 examples documentation. 

When trying to program custom boards through the development board the command line tools suggest that the hex file is not valid as the data is either in or out of the valid area. Any help would be appreciated.

  • 0

    Hello,

    How do you perform the DFU? Command line tools or the nRF Toolbox app?

    If it is command line tools, how do you generate the image that you use for the DFU update? Can you copy-paste all the commands you use? If you use nRF Toolbox, what file do you use to perform the update?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    I can not DFU as the bootloader will not program onto the nRF52832 of the custom board. But it is my intention to utilize the nrfutil.exe to create a zip and will try to upload to my iphone performing DFU through nRFtoolbox. 

    Again, the custom hardware which is fairly mature and stable with other applications will not be programmed through development board and command line tools. However the development will and I can connect to the bootloader through nRFtoolbox. 

  • 0 in reply to Cy
    Cy said:
    Again, the custom hardware which is fairly mature and stable with other applications will not be programmed through development board and command line tools. However the development will and I can connect to the bootloader through nRFtoolbox. 

     

    I suggest you have a look at the DFU getting started guide.
    If you try to follow the guide (on your custom board) where is it that your behavior differs from the guide?

    Are you able to flash anything at all through command line tools (or an IDE)? Just regular programming?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hey Edvin,

    It is so nice of you to have an interest in my problem. Yes, I have looked at the DFU getting started guide many of the post I have looked at suggest this link, that is a good suggestion!!!! 

  • 0 in reply to Cy

    Hello,

    No problem.

    I am a bit confused to what you are actually doing. You speak of .hex files and DFU. Is it the .hex file of the bootloader that you are not able to program to the nRF, or have you created a .zip application image that you are not able to update over DFU?

    BR,

    Edvin

Related