• State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 74 subscribers
  • Views 2232 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288513
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Programming nRF52 SoCs with nRF5340 DK

Shaun Brentnall

Hi, I want to eventually be able to programme a custom built chip with an nRF52833 SoC on board, but first I thought I would try with a nordic Thingy:52. 

My setup is as follows:

Computer (Windows with nRF connect v3.11.0) <---> nRF5340 DK <---JTag---> Nordic Thingy:52

I can programme the nRF5340 DK via the nRF connect visual studio IDE, but I am not sure how to be able to connect to the nordic thingy_52 in order to be able to programme that device directly. On the 'connected devices' section in visual studio I cannot see the nordic thingy:52 appear, only the nRF5340 DK appears. 

Do I need to do something else in order to connect to the thingy to programme it? Or is the JTag physical connection sufficient?

Thank you for your help!

  • 0

    Hello, 

    Computer (Windows with nRF connect v3.11.0) <---> nRF5340 DK <---JTag---> Nordic Thingy:52

    This sounds correct. To what port have you connected the JTAG debug probe? You should be able to automatically program the Thingy:52 if connected to P19, see Debug Output in the nRF5340DK documentation. Make sure that the device is powered.

    Are you using the Programmer app in nRF Connect for Dekstop 3.11.0 ? If so, choose the nRF5340DK and the device name from Thingy:52 should be visible in the left hand side. Here I've used the nRF9160DK to program the Thingy:52 with a zephyr.hex.

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    Hi Øyvind, thank you for your reply.

    Yes, it was a connection between P19 and and the 10 pin port on the thingy:52. 

    I was trying toolchain manager actually. But I tried with the Programmer app as you said, and it does detect that there is a device there but it still can't write to it. When I try to it returns a "JLINKARM_DLL_ERROR". I tried updating Segger JLink (from V7.58b to V7.64d), but I still get an error "Unsupported device. The device could not be recognised as neither JLink device nor Nordic USB device."


  • 0 in reply to Shaun Brentnall

    What version of the nRF5340DK and the Thingy:52 do you have? Both should be visible on the stickers.

    The right hand side does show Unknown. Is the Thingy:52 powered on? 

  • 0 in reply to Øyvind

    Yeah, the Thingy:52 is on, I made sure to check that. Though it wouldn't have surprised me. 

    nRF5340 devkit version: 1.0.0
    Thingy:52 version: 1.1.2

    Could there be some compatibility issue?

  • 0 in reply to Shaun Brentnall

    In the programmer app, the nRF5340DK should show as a DK. I finally found my kit and tested:

    What happens if you issue command nrfjprog --ids in cmd? Are you able to program the device using nrfjprog?

Related
Terms of service