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

Fail to update modem

I'm trying to update the modem on Thingy:91 using nRF Connect Programmer v3.6.0

I get these errors

18:50:16.131
Application data folder: /home/tmh/.config/nrfconnect/pc-nrfconnect-programmer
18:50:16.338
Using nrfjprog library 10.9.0, pc-nrfjprog-js 1.7.3
18:50:17.134
Error while probing devices: Error occured when get serial numbers. Errorcode: CouldNotCallFunction (0x9) Lowlevel error: INVALID_OPERATION (fffffffe)
18:50:42.133
Modem DFU starts to write...
18:50:42.133
Writing /home/tmh/src/thingy_0923/mfwnrf9160121.zip to device
18:50:42.554
MCUboot DFU failed. Please make sure that the device is in MCUboot mode and try again.

I tried to update the

thingy91_ltem_dfu_2020-09-23_b6ad40d0.bin

and

thingy91_nrf52_usb_uart_bridge_dfu_2020-09-23_b6ad40d0.bin

using mcumgr but that does not help

I also tried

thingy91_nrf52_usb_uart_bridge_2020-10-30_5522ca2b.bin

but it never completes uploading.

I have tried using both Linux (OpenSUSE 15.2) and Windows 10

Parents
  • Hi,

    When using the Programmer application in nRF Connect for Desktop, you should use the .hex files, not the .bin files.

    What hardware version of the Thingy:91 do you have? Have you updated the firmware on it before, or is it a new device?

    Did you hold the (big) button when you powered on the Thingy to set it in bootloader mode?

    Also. remember that you have to hold the small button when setting the nRF52840 in bootloader mode.

    If you did all the above correctly, could you try to update the nRF52840 to the newest connectivity_bridge version using mcumgr from you Linux computer?

    To do so, you can follow this guide: Update Thingy:91 firmware with mcumgr.

    Remembder that when using mcumgr, you must use the .bin files.

    Best regards,

    Didrik

  • As the procedure describes that I have to update the modem, first I never tried .hex nor .bin files using nRF Connect for Desktop.

    I tried just now, but got the same error message as above.

    There are a few things that are unclear in the mcumgr guide. I assume that "thingy91_nrf52*" files are for nRF52840 and I have to push SW4 during start-up. How about the dip-switch, should it be in nRF91 or nRF52 position?

  • torhans said:
    How about the dip-switch, should it be in nRF91 or nRF52 position?

     That does not matter when doing DFU.

    The switch controls the routing of the 10-pin header used when programming the Thingy:91 with a programmer.

     

    torhans said:
    I assume that "thingy91_nrf52*" files are for nRF52840

     Yes.

     

    torhans said:
    I have to push SW4 during start-up

     Yes, when updating the 52. FOr the 91, you must use SW3 (the "big" button)

Reply
  • torhans said:
    How about the dip-switch, should it be in nRF91 or nRF52 position?

     That does not matter when doing DFU.

    The switch controls the routing of the 10-pin header used when programming the Thingy:91 with a programmer.

     

    torhans said:
    I assume that "thingy91_nrf52*" files are for nRF52840

     Yes.

     

    torhans said:
    I have to push SW4 during start-up

     Yes, when updating the 52. FOr the 91, you must use SW3 (the "big" button)

Children
  • I have updated the connectivity_bridge, but still I receive the same error message.

  • Hi, and please accept my sincere appology for the late reply.

    I have been trying to figure out what the issue could be, but have unfortuately not been able to find a good soultion yet.

    First, could you make sure that you are using the newest versions of nRF Connect for Desktop (3.6.1), and the Programmer application (1.4.8).

    Also, some other customers who have reported problems were able to solve them by using WIndows 10, so let's stick to that for now.

    If you are using the newest versions, does that help?

    Secondly, just to be sure:

    When you are putting the nRF9160 in MCUBoot mode, are you powering the Thingy off with the power switch, and holding SW3 (the "main" button in the middle of the PCB) while powering the Thingy on?

    Does the Thingy appear in the device manager?

    Does it appear as a storage device?

    Are you able to update the application on the nRF9160?

    Do you have any external programmers you can use, such as an nRF9160DK?

  • Updating to 3.6.1/1.4.8 seems to make to work, I was able to update modem firmware on Windows 10.

    I was not able to update on Linux.

    usb 8-5: USB disconnect, device number 9
    usb 8-5: new full-speed USB device number 10 using ohci-pci
    usb 8-5: New USB device found, idVendor=1915, idProduct=9100, bcdDevice= 2.04
    usb 8-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 8-5: Product: Thingy:91 UART
    usb 8-5: Manufacturer: Nordic Semiconductor
    usb 8-5: SerialNumber: THINGY91_f1b4097f4864
    cdc_acm 8-5:1.0: ttyACM0: USB ACM device
    usb-storage 8-5:1.2: USB Mass Storage device detected
    scsi host6: usb-storage 8-5:1.2
    cdc_acm 8-5:1.3: ttyACM1: USB ACM device
    scsi 6:0:0:0: Direct-Access     ZEPHYR   ZEPHYR USB DISK  0.01 PQ: 0 ANSI: 0 CCS
    sd 6:0:0:0: Attached scsi generic sg4 type 0
    sd 6:0:0:0: [sdd] 32 512-byte logical blocks: (16.4 kB/16.0 KiB)
    sd 6:0:0:0: [sdd] Write Protect is off
    sd 6:0:0:0: [sdd] Mode Sense: 03 00 00 00
    sd 6:0:0:0: [sdd] No Caching mode page found
    sd 6:0:0:0: [sdd] Assuming drive cache: write through
    sdd:
    sd 6:0:0:0: [sdd] Attached SCSI removable disk

  • Great to hear that you got it to work on Windows!

    We will continue working on making the process easier, and figuring out why it does not work as it should on Linux.

Related