Programming of thingy:53?

Hi,

Recently I have got the thingy:53 and I was quite exited and started to learn nRF connect SDK. Soon when I tried to program the kit I realized that it needs some external JTAG programmer.. Which I do not have...So I looked for options and one of them is that it can be programmed via nRF4053 DK.

The 4053DK is smart enough to detect that something is there on the 10-pin connector which can be programmed.! Am I right?

For the thingy:53 I also looked at schematic where I also made it conform that it has no usb to ttl converter or similar on it.?

One more possibility is via nRF ble applications but which is pretty limited I think to rebuilt application only. Am I right?

Parents Reply Children
  • I was working on the firmware update part and found that I can actually update the firmware but MCUboot needs to be enabled in kconfig.

    The question for me is that weather is it possible to load a binary build by other platforms than nRF connect SDK using nRF connect Programmer?

    I know it would be difficult but there might be possibility. One thing is that currently there is manifest.json file in the zip archive which could be an issue.?

    There are some fields which one may not know..like the following code has load_address etc.

    {
        "format-version": 0,
        "time": 1646868676,
        "files": [
            {
                "type": "application",
                "board": "thingy53_nrf5340_cpuapp",
                "soc": "nRF5340_CPUAPP_QKAA",
                "load_address": 66048,
                "image_index": "0",
                "slot_index_primary": "1",
                "slot_index_secondary": "2",
                "version_MCUBOOT": "1.0.0+0",
                "size": 235052,
                "file": "app_update.bin",
                "modtime": 1646868675
            },
            {
                "type": "application",
                "board": "thingy53_nrf5340_cpunet",
                "soc": "nRF5340_CPUNET_QKAA",
                "image_index": "1",
                "slot_index_primary": "3",
                "slot_index_secondary": "4",
                "load_address": 16812032,
                "version": "1",
                "size": 171348,
                "file": "net_core_app_update.bin",
                "modtime": 1646868626
            }
        ],
        "name": "light",
        "firmware": {
            "zephyr": {
                "revision": "8d7aa9fc1c06eea0ad021934f68879246b8aef26"
            },
            "nrf": {
                "revision": "126fad0e2e5cbe5b965a45efc6a5e31f40d6020c"
            }
        }
    }

    Also, is it possible to update just application core of the nRF5340?

  • Okey I have tried to flash the application using mcuboot but seems that it may not be working. I have changed the led pin to 38,39,40 one by one to see if it is blinking but there seems no change?

    developer.nordicsemi.com/.../readme-mynewt.html

  • Hello,

    While programming or flashing via USB you need to make the Thingy53 in the bootloader mode. And also, are you enabling the "Enable MCUboot" tab in the nRF programmer App?

    ujur007 said:
    I have some files in .hex and some in .img files which needs to be uploaded to the Thingy and I realized they are not being uploaded.

    Yes you can upload the .hex file via nRF programmer. For eg:if you check the precompiled Application firmware for the thingy53 you can find some hex file under homekit_weather_station sample. Try flashing this hex file and see the change.

    Kind Regards,

    Abhijith

  • Hi,

    Thanks for reply. Actually the nRF connect programmer works and I have tried to flash recompiled binaries and it works. but what I am trying is that uploading the .img file generated by apache mynewt build system. That seems not working as mentioned in the previous link.

    The code upload but I do not see led blinking. That make me thing weather the flash worked? 

Related