JLinkExe missing during flash build (nrf52840_dongle) about opensk HOT 12 CLOSED

Looking more closely, I see that the upstream Tock docs do cover the docs part somewhat. If it is only possible to use the J-Link EDU with the full development board, and not the USB stick version, or what combinations might work, covering that in the README would also be helpful for users who don't have a lot of JTAG experience.

Do you already have Jlink installed?
If not then install from this .deb
Jlink Linux 64

from opensk.

@conashin if you had an error like
FileNotFoundError: [Errno 2] No such file or directory: 'JLinkExe': 'JLinkExe'
Then yes, but make sure you're downloading the right one for your platform.
JLink Download Page

from opensk.

Looking more closely, I see that the upstream Tock docs do cover the docs part somewhat. If it is only possible to use the J-Link EDU with the full development board, and not the USB stick version, or what combinations might work, covering that in the README would also be helpful for users who don't have a lot of JTAG experience. 😳

from opensk.

So, do we need any other things when flashing nrf52840 dongle?

from opensk.

Looking more closely, I see that the upstream Tock docs do cover the docs part somewhat. If it is only possible to use the J-Link EDU with the full development board, and not the USB stick version, or what combinations might work, covering that in the README would also be helpful for users who don't have a lot of JTAG experience.

Do you already have Jlink installed?
If not then install from this .deb
Jlink Linux 64

Can I install a jlink flasher?
https://www.segger.com/downloads/flasher/JLink_Linux_x86_64.deb

from opensk.

@SuperDeron System pop-up this window when I was trying to flash it.

Does it need something else with hardware?

from opensk.

According to the very first line in the dialog window, your JLink probe is not detected: "No emulators connected via USB"

from opensk.

I deployed OpenSK to a nrf52840-DK using OpenOCD rather than JLinkExe. To do so, I needed an up-to-date version of OpenOCD (newer than my distro packages), and I made tweaks to tockloader, tock, and OpenSK's deploy.sh.

I'll work on upstreaming (less hacky versions of) the changes I've made. Upstreaming will take some time, as I expect to make changes serially across three repositories. I'll open a separate issue for OpenOCD support when I've made enough progress to put together a coherent issue title/body.

from opensk.

Thanks Johnathan! Be aware that I'm currently almost done rewriting the deploy.sh script in python3. This should give us more flexibility and portability (python3 is already a dependency for tockloader anyway).

Let's coordinate so that I'm not adding more work to merge your contributions.

from opensk.

Thanks Johnathan! Be aware that I'm currently almost done rewriting the deploy.sh script in python3. This should give us more flexibility and portability (python3 is already a dependency for tockloader anyway).

Let's coordinate so that I'm not adding more work to merge your contributions.

I opened #35 to track/coordinate this effort. I don't expect it to collide with your deploy.sh changes. I added a flag to tockloader (tock/tockloader#52) then tweaked deploy.sh and tock so that I could pass the flags through.

from opensk.

PR #40 now checks for JLinkExe.

Thanks to Johnathan and the community, it seems that we're going to be able to support different flashing methods, including using the pre-flashed Nordic bootloader. Covering how to setup the JTAG probes on everyone's environment is in my opinion out of scope for this project.

from opensk.

Yep, works just as intended - thanks for this!

For the upcoming native Nordic bootloader work - is that tracking under #35 ? Which issue(s) should I follow to track that? (I ask here so that other people with this interest can find the thread)

from opensk.