• State Not Answered
  • Replies 7 replies
  • Subscribers 63 subscribers
  • Views 702 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 289753
Options

Can't upload code to PCA10095 (nRF5340-DK) via Segger Embedded Studio

Jamal

Hi,

I have started learning nRF5340 recently and have got the development kit as well.

I compiled first example of "peripheral_uart" but I am not able to program the board. It gives error while programming. You can see the errors i get in the images.

ALSO, is it possible that i can compile the hex file and upload it via J Flash Lite software to both cores at the same time?? Or via nRF Connect Programmer etc?

One more thing i want to add is that i am using nRF5340-PDK. Not the DK. And the nRF Connect Programmer does not detect my DK at all.

Any assistance on this matter will be appreciated.

Thank you.

  • 0

    Hi,

    Which nRF Connect SDK version are you using? Could it be that you are seeing this issue? Note that the PDK is deprecated and cannot be used with any recent releases (the latest version with support for the PDK was 1.4.99-dev1). So I strongly recommend that you use a DK instead so that you can work with later SDK releases (the latest is 1.9.1 and 2.0.0 is right around the corner).

    Einar

  • 0 in reply to Einar Thorsrud

    Hi,

    The nrf Connect for Desktop version i am using is 3.11.0

    But the problem is that i am not able to erase or program both cores from J Flash Lite as well.

    What J Flash Lite has to do with version of nRF Connect?

    Also the DK connects to the PC properly and I can see it in the SES Target Connection Properties.

    Check this image.

  • 0 in reply to Jamal

    Hi,

    Jamal said:
    The nrf Connect for Desktop version i am using is 3.11.0

    I see. However, I was wondering about the nRF Connect SDK version? This is mostly related to the point about the PDK not being supported in newer revisions so if you want to use this with a newer SDK version (which would be for all use cases except playing with old stuff for fun), then that is an important point.

    Jamal said:
    But the problem is that i am not able to erase or program both cores from J Flash Lite as well.

    I see. It looks like the debugger cannot communicate with the target IC, perhaps because of HW reasons. Did you obtain the PDK from someone else? Could it be that they have cut SB40? If so, the nRF5340 will not be powered unless you short the nRF Current measurement port.

  • 0 in reply to Einar Thorsrud

    Hi, 

    I made a little progress on the problem and want to let you know the situation.

    I installed the nrf connect and sdk on my older laptop and following is the stuff which i am either able to do or not able to. 

    WHAT I CAN DO:

    1- I  can erase both cores individually via J Flash Lite (after selecting both cores differently via device selection)

    2- I can program "peripheral_uart" project only if i select nRF5340_cpunet as board. (using Target->Download zehpyr.elf)

    3- On J Flash Lite, i am able to download merged.hex if i select nRF5340_APP from device selection. But it does not work.

    WHAT I CAN'T DO:

    1- I can not program "peripheral_uart" project if i select nRF5340_cpuapp_ns as board (using Target->Download merged.hex)

    2- On J Flash Lite, i am not able to download any hex file if i select nRF540_NET from device selection menu.

    Please let me know if you get any idea from all these details. 

    On SES, it seems like there could be a step to selecct which core I want to program or the SES and DK programmer does that automatically?

    Thank you.

  • 0 in reply to Jamal

    Please let me know which nRF Connect SDK version are you using? If you are using >= 1.5.0, then most samples will not work due to HW changes in the IC and it not being supported. The PDK is no longer supported and you should use a DK instead.

Related

core_v2_widget.Hide()