Unable to flash using eclipse

RE: Unable to flash using eclipse

Xavier — Fri, 09 Aug 2019 14:42:54 GMT

Hi, after two weeks I have found the problem.. it was my jlink edu mini. I tried using my coworker Jlink and it worked.

RE: Unable to flash using eclipse

Xavier — Fri, 09 Aug 2019 14:06:06 GMT

Hi, thanks for the input

I can flash using nrfjprog and it does work as intended. I tried using -noir instead of -ir but it still did not flash the new image and the debugger stopped at a random address

Here's the output in eclipse

SEGGER J-Link GDB Server V6.44e Command Line Version

JLinkARM.dll V6.44e (DLL compiled Apr  5 2019 16:15:03)

Command line: -if swd -device nRF52832_xxAA -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -noir -localhostonly 1 -singlerun -strict -timeout 0
-----GDB Server start settings-----
GDBInit file:                  none
GDB Server Listening port:     2331
SWO raw output listening port: 2332
Terminal I/O port:             2333
Accept remote connection:      localhost only
Generate logfile:              off
Verify download:               off
Init regs on start:            off
Silent mode:                   off
Single run mode:               on
Target connection timeout:     0 ms
------J-Link related settings------
J-Link Host interface:         USB
J-Link script:                 none
J-Link settings file:          none
------Target related settings------
Target device:                 nRF52832_xxAA
Target interface:              SWD
Target interface speed:        1000kHz
Target endian:                 little

Connecting to J-Link...
J-Link is connected.
Firmware: J-Link EDU Mini V1 compiled Jul 10 2019 16:32:48
Hardware: V1.00
S/N: 801011244
Feature(s): FlashBP, GDB
Checking target voltage...
Target voltage: 2.25 V
Listening on TCP/IP port 2331
Connecting to target...Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
Reading all registers
Read 4 bytes @ address 0x00029F86 (Data = 0x0F10F01E)
Received monitor command: speed 1000
Target interface speed set to 1000 kHz
Received monitor command: clrbp
Received monitor command: reset
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x000008E8)
Received monitor command: regs
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000, R13= 20000400, MSP= 20000400, PSP= 00000000
R14(LR) = FFFFFFFF, R15(PC) = 000008E8
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x000008E8 (Data = 0x47184B06)
Received monitor command: speed auto
Select auto target interface speed (2000 kHz)
Received monitor command: flash breakpoints 1
Flash breakpoints enabled
Received monitor command: semihosting enable
Semi-hosting enabled (Handle on BKPT)
Received monitor command: semihosting IOClient 1
Semihosting I/O set to TELNET Client
Read 4 bytes @ address 0x000008E8 (Data = 0x47184B06)
Downloading 4096 bytes @ address 0x00026000
Downloading 4096 bytes @ address 0x00027000
Downloading 4096 bytes @ address 0x00028000
Downloading 4096 bytes @ address 0x00029000
Downloading 4096 bytes @ address 0x0002A000
Downloading 4096 bytes @ address 0x0002B000
Downloading 4096 bytes @ address 0x0002C000
Downloading 4096 bytes @ address 0x0002D000
Downloading 4096 bytes @ address 0x0002E000
Downloading 4096 bytes @ address 0x0002F000
Downloading 4096 bytes @ address 0x00030000
Downloading 4096 bytes @ address 0x00031000
Downloading 4096 bytes @ address 0x00032000
Downloading 4096 bytes @ address 0x00033000
Downloading 4096 bytes @ address 0x00034000
Downloading 4096 bytes @ address 0x00035000
Downloading 4096 bytes @ address 0x00036000
Downloading 4096 bytes @ address 0x00037000
Downloading 4096 bytes @ address 0x00038000
Downloading 4096 bytes @ address 0x00039000
Downloading 4096 bytes @ address 0x0003A000
Downloading 4096 bytes @ address 0x0003B000
Downloading 4096 bytes @ address 0x0003C000
Downloading 4096 bytes @ address 0x0003D000
Downloading 4096 bytes @ address 0x0003E000
Downloading 4096 bytes @ address 0x0003F000
Downloading 272 bytes @ address 0x00040000
Downloading 24 bytes @ address 0x00040110
Downloading 104 bytes @ address 0x00040128
Downloading 168 bytes @ address 0x00040190
Downloading 24 bytes @ address 0x00040238
Downloading 16 bytes @ address 0x00040250
Downloading 16 bytes @ address 0x00040260
Downloading 8 bytes @ address 0x00040270
Downloading 8 bytes @ address 0x00040278
Downloading 200 bytes @ address 0x00040280
Downloading 84 bytes @ address 0x00040348
Downloading 20 bytes @ address 0x0004039C
ERROR: Verification of RAMCode failed @ address 0x20000000.
Write: 0xA801BE00 F0009900
Read: 0x00013C00 F0001000
Failed to prepare for programming.
Failed to download RAMCode!
Writing register (PC = 0x   262d0)
Read 4 bytes @ address 0x000262D0 (Data = 0x00060004)
Read 2 bytes @ address 0x000359C8 (Data = 0xE7E0)
Read 2 bytes @ address 0x000359C8 (Data = 0xE7E0)
Read 2 bytes @ address 0x000359C4 (Data = 0xF072)
Read 2 bytes @ address 0x0003A06A (Data = 0x0300)
Read 2 bytes @ address 0x0003A4E0 (Data = 0x0000)
Received monitor command: clrbp
Received monitor command: reset
WARNING: T-bit of XPSR is 0 but should be 1. Changed to 1.
Resetting target
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x000008C0)
Read 2 bytes @ address 0x000359C8 (Data = 0xF7E0)
Read 2 bytes @ address 0x000359C8 (Data = 0xF7E0)
Read 2 bytes @ address 0x000359C4 (Data = 0xF072)
Received monitor command: regs
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000
R12= 00000000, R13= 00000000, MSP= 00000000, PSP= 00000000
R14(LR) = FFFFFFFE, R15(PC) = 000008C0
XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000
CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00
Reading all registers
Read 4 bytes @ address 0x000008C0 (Data = 0xF0003E10)
Setting breakpoint @ address 0x000359C4, Size = 2, BPHandle = 0x0001
Starting target CPU...
Debugger requested to halt target...
WARNING: T-bit of XPSR is 0 but should be 1. Changed to 1.
...Target halted (PC = 0x00031770)
Reading all registers
Read 4 bytes @ address 0x00031770 (Data = 0x4420C00C)
Removing breakpoint @ address 0x000359C4, Size = 2
Starting target CPU...

RE: Unable to flash using eclipse

Simonr — Fri, 09 Aug 2019 10:37:51 GMT

Hi Xavier

Does it work programming your application with nrfjprog or does it only fail when you use Eclpse? Could you try using -noir and not -ir in your command line? The debugger should not have to initialize the register on the nRF5 device.

Best regards,

Simon

RE: Unable to flash using eclipse

Xavier — Thu, 08 Aug 2019 14:49:32 GMT

Hi Simon,
Yes I am still having trouble and I cannot flash. My build and toolchain path are set correctly since I can build, I just cannot flash. I tried fully reinstalling eclipse to an older version (oxygen) and redoing all the configs but it still does not work.

RE: Unable to flash using eclipse

Simonr — Thu, 08 Aug 2019 12:46:39 GMT

Hi Xavier

Are you still having trouble? Could it be that your configure environment has changed? Please check that the paths to your Build and Toolchain are set correctly, and if not, add these paths where you have them installed. Also, enter Run/Debug, click on SEGGER J-Link, and make sure that it's pointing to your latest version of the SEGGER software. You can see our development with GCC and Eclipse guide for more detailed steps.

A side note. Have there been any updates to Eclipse lately that might have caused this? Are you able to flash any of the standard SDK examples using Eclipse?

Best regards,

Simon

RE: Unable to flash using eclipse

Mojo — Wed, 07 Aug 2019 21:06:09 GMT

Well, in that case, no ideas. I use Eclipse full time but with openOCD and a CMSIS-DAP JTAG. Never has this issue. Check to see if you are using the same version of jlink driver for both eclipse and nrfjprog. May be eclipse could point to the wrong version.

RE: Unable to flash using eclipse

Turbo J — Wed, 07 Aug 2019 18:55:37 GMT

Also disable semihosting. You can use Segger RTT instead.

Final tip: Start the GUI version of the JLinkGDBServer manually outside eclipse. Works better when using the RTT Viewer, as this can share the debug connection ("existing session").

RE: Unable to flash using eclipse

Xavier — Wed, 07 Aug 2019 18:44:15 GMT

Sorry, I was confused, it is not a devkit actually, it's a custom board with only the nrf52 chip on it so I need the external jlink to programm it. So there isn't multiple jlink connected. I have fixed my answer, sorry about that. I still cannot flash to the device using eclipse and debug ( though nrfGo and by command line works as mentioned)

RE: Unable to flash using eclipse

Mojo — Wed, 07 Aug 2019 18:26:34 GMT

ah! ha! There you go. You have 2 Jlink connected. It must have picked up the DevKit instead of your. There is a Jlink built onto the DevKit. You need to select the correct one by giving the serial number as parameter in the debug config. Otherwise it will pick first found.

RE: Unable to flash using eclipse

Xavier — Wed, 07 Aug 2019 18:09:21 GMT

I have only one jlink and one ̶D̶e̶v̶k̶i̶t̶ custom board connected on the PC. I tried a fresh install of my IDE and recloning the repo but I can't seem to make it work. It's such a frustrating issue though.

RE: Unable to flash using eclipse

Mojo — Wed, 07 Aug 2019 17:41:19 GMT

It is odd indeed. By any chance, there is one more jlink connected to the same pc ? Or a DevKit along with your board ? Or that you are using the DevKit to flash your board but instead it flashes the DevKit ? The log said verify success which means flashing works.

RE: Unable to flash using eclipse

Xavier — Wed, 07 Aug 2019 17:37:23 GMT

I tried erasing all and re flashing the soft device multiple time. And if an app is already on the device, it will restart de device and relaunch the old app instead of the updated one. I find this issue very odd

RE: Unable to flash using eclipse

Xavier — Wed, 07 Aug 2019 17:36:06 GMT

That would actually make sense since I am using a cheap USB splitter. Although, I can flash using the command nrfjprog or with nrfGo Studio. And I don't see why it would stop working since I was developing this way.But I stopped using the usb splitter but it still does not work and the voltage is still around 2.3V

RE: Unable to flash using eclipse

Mojo — Wed, 07 Aug 2019 17:01:38 GMT

The log said it flashed correctly. It is more likely your firmware crashed on start before reaching main. One possible reason is because Softdevice was not present. Reflash softdevice see if it helps.

RE: Unable to flash using eclipse

Turbo J — Wed, 07 Aug 2019 16:56:06 GMT

> Target voltage: 2.28 V

That is not a lot. You might simply be running out of power.

How do you power the chip?