debug thingy:91 using nrf9160 DK

Hi Nordic,

I would like to understand the philosophy behind the nRF9160 DK acting as a debugger.  I recover my thinky:91 connecting the 10 pin flat cable from thingy:91 to a  nrf52840 DK, updating the firmware in the nRF52840 SoC. Then installing the Connectivity bridge firmware file.  After that I was able to install the asset tacker application, by using an nRF9160 DK in the thingy:91.    Since I have both, the thingy and the nrf9160 DK board ,  connected to  my computer,  which one should I select when I download the application to the thingy91 (thingy91 or nRF9160DK acting as debugger connected to thingy91) ?....

Many thanks in advance..

Parents
  • Hi,

     

     Since I have both, the thingy and the nrf9160 DK board ,  connected to  my computer,  which one should I select when I download the application to the thingy91 (thingy91 or nRF9160DK acting as debugger connected to thingy91) ?....

    If you program the thingy:91 via. the nRF9160-DK, you should select the nRF9160-DK.

     

    If you open the thingy:91 instead, it assumes that you are to update using the mcuboot bootloader instead, which is not what you currently want to do.

     

    Kind regards,

    Håkon

Reply
  • Hi,

     

     Since I have both, the thingy and the nrf9160 DK board ,  connected to  my computer,  which one should I select when I download the application to the thingy91 (thingy91 or nRF9160DK acting as debugger connected to thingy91) ?....

    If you program the thingy:91 via. the nRF9160-DK, you should select the nRF9160-DK.

     

    If you open the thingy:91 instead, it assumes that you are to update using the mcuboot bootloader instead, which is not what you currently want to do.

     

    Kind regards,

    Håkon

Children
No Data
Related