J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

awneil — Wed, 25 Apr 2018 11:27:18 GMT

[quote userid="17188" url="~/f/nordic-q-a/33649/j-link-the-firmware-of-the-connected-j-link-does-not-support-the-following-memory-access-read-0x02000004/129200"]nrfgo studio is kinda deprecated, 2 years since it was updated or something, so that's the reason it's pulling an old version. nRF connect for desktop is the cool kid now: www.nordicsemi.com/.../nRF-Connect-for-desktop[/quote]

But nRF Connect doesn't provide this funcitonality!

I'll take that to a separate topic:

devzone.nordicsemi.com/.../what-to-use-in-place-of-nrfgo-studio

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

awneil — Fri, 20 Apr 2018 22:23:34 GMT

I was following the instructions in the SDK v15.0.0 "Getting Started". It gave no indication that nRFgo Studio was deprecated.

In fact, in "Compiling and running a first example" it specifically directs to use nRFgo Studio!

😡

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

Daniel Wang — Fri, 20 Apr 2018 22:11:50 GMT

nrfgo studio is kinda deprecated, 2 years since it was updated or something, so that's the reason it's pulling an old version. nRF connect for desktop is the cool kid now: www.nordicsemi.com/.../nRF-Connect-for-desktop

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

awneil — Fri, 20 Apr 2018 21:59:21 GMT

C:\Users\xxx>nrfjprog  -v
nrfjprog version: 8.5.0
JLinkARM.dll version: 6.14h

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

awneil — Fri, 20 Apr 2018 21:54:20 GMT

Like I said - I just downloaded the latest of everything from the Nordic site!

The command-line tools were installed automatically when I ran the nRFgo Studio installer:

So why would that be pulling-in an old version?

How do I check the version of command-line tools?

Yes, the DK is old - new hardware is on its way ...

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

Daniel Wang — Fri, 20 Apr 2018 21:38:40 GMT

Are you using an old command-line-tools installer?

Download the newest here, it comes bundled with Jlink v6.20i:

https://www.nordicsemi.com/eng/nordic/Products/nRF51822/nRF5x-Command-Line-Tools-Win32/33444

Side note: your pca10040 0.9.0 uses engineering B nRF52832 IC... so you might want to upgrade

RE: J-Link: "The firmware of the connected J-Link does not support the following memory access: Read @ 0x02000004

awneil — Fri, 20 Apr 2018 21:37:02 GMT

[quote userid="6462" url="~/f/nordic-q-a/33649/j-link-the-firmware-of-the-connected-j-link-does-not-support-the-following-memory-access-read-0x02000004"]So everything should be "latest" and "up-to-date"[/quote]

Ha!

How Naive!

The nRF Command-line Tools installer has installed a really old Segger JLink software!

😡

In fact, we can see that it's waaaay older than anything I have before:

If I restore the the version which Keil had before - v6.30h - it works fine (after doing a JLink FW update):

Load "C:\\Users ... examples\\peripheral\\blinky\\pca10040\\blank\\arm5_no_packs\\_build\\nrf52832_xxaa.axf"
* JLink Info: Updating firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
* JLink Info: Replacing firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 2 2017 12:22:13
* JLink Info: Waiting for new firmware to boot
* JLink Info: New firmware booted successfully
Set JLink Project File to "C:\Users\awn\Antronics\Client_Work\Fractal\nRF-SDK\15-0-0\examples\peripheral\blinky\pca10040\blank\arm5_no_packs\JLinkSettings.ini"
* JLink Info: Device "NRF52832_XXAA" selected.

JLink info:
------------
DLL: V6.30h, compiled Mar 16 2018 18:02:51
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
Hardware: V1.00
S/N : 682645609

* JLink Info: Found SW-DP with ID 0x2BA01477
* JLink Info: Found SW-DP with ID 0x2BA01477
* JLink Info: Scanning AP map to find all available APs
* JLink Info: AP[2]: Stopped AP scan as end of AP map has been reached
* JLink Info: AP[0]: AHB-AP (IDR: 0x24770011)
* JLink Info: AP[1]: JTAG-AP (IDR: 0x02880000)
* JLink Info: Iterating through AP map to find AHB-AP to use
* JLink Info: AP[0]: Core found
* JLink Info: AP[0]: AHB-AP ROM base: 0xE00FF000
* JLink Info: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
* JLink Info: Found Cortex-M4 r0p1, Little endian.
* JLink Info: FPUnit: 6 code (BP) slots and 2 literal slots
* JLink Info: CoreSight components:
* JLink Info: ROMTbl[0] @ E00FF000
* JLink Info: ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
* JLink Info: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
* JLink Info: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
* JLink Info: ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
* JLink Info: ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
* JLink Info: ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
ROMTableAddr = 0xE00FF000
* JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
* JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.

Target info:
------------
Device: nRF52832_xxAA
VTarget = 3.300V
State of Pins:
TCK: 0, TDI: 1, TDO: 1, TMS: 1, TRES: 1, TRST: 1
Hardware-Breakpoints: 6
Software-Breakpoints: 8192
Watchpoints: 4
JTAG speed: 1000 kHz

Erase Done.
Programming Done.
Verify OK.
* JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
* JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
Application running ...
Flash Load finished at 22:26:08