RE: Error while identifying cortex-M core

Stian Røed Hafskjold — Tue, 14 Oct 2014 10:26:50 GMT

There is a program called Configurator in the J-link software pack. You try a firmware update/replace of the J-link in there.

RE: Error while identifying cortex-M core

Stian Røed Hafskjold — Mon, 13 Oct 2014 13:29:55 GMT

Sound to me like it's a hardware problem. Are you sure the USB-cable is good? Try to replace that.

RE: Error while identifying cortex-M core

pramithkv — Wed, 08 Oct 2014 12:58:48 GMT

i had tried that too

am having two nRF51822 EK boards and this problem is only with one of them. the same gets connected sometimes and can be programmed and shows these problems ..........................................................................................................................

i cannot discover services using master control panel //log message im getting in master contrpl panel [18:22:14.8] Loading... [18:22:15.3] Device address: 0xDBF0B072D957 [18:22:15.3] Master emulator firmware version: mefw_nrf51822_0.9.0.10022 [18:22:15.6] Ready [18:22:15.8] SERVER: Server has started [18:23:41.1] Device discovery started [18:23:49.1] Device discovery stopped [18:23:53.2] GetDeviceInfo() [18:23:53.6] ---------------------------- [18:23:53.6] Connected to device [18:23:53.6] Role: 0 [18:23:53.6] PeerAddressType: 1 [18:23:53.6] PeerAddress (MSB): D29464A294AC [18:23:53.6] Connection Interval: 20.0ms [18:23:53.6] Connection Latency: 0 [18:23:53.6] Supervision Timeout: 3000ms [18:23:53.6] Clock Accuracy: (1) [18:23:53.6] ---------------------------- [18:23:53.6] Connected to address: D29464A294AC [18:23:53.6] Starting a Read Information Request on the whole remote DB [18:23:53.6] Lost connection to device. Reason: BTLE_CONN_FAILED_TO_BE_ESTABLISHED [18:23:53.6] Discovering all attribute UUIDs [18:23:53.6] Lost connection before service discovery was complete [18:23:53.7] SERVER: Received packet <HciEvent: eventCode=0x0A> - <HciEvent: eventCode=0x0A> [18:23:53.7] SERVER: Received Link Loss ......................................................................................................................... 2.m not able to run debug mode in kiel //command window output while debugging [10/7/2014 5:32:27 PM] pramith kv: Running with Code Size Limit: 32K Set JLink Project File to "C:\Keil_v5\ARM\Device\Nordic\nrf51822\Board\pca10001\s110\ble_app_hrs\arm\JLinkSettings.ini"* JLink Info: Device "NRF51822_XXAA" selected (257 KB flash, 16 KB RAM).

JLink info:

DLL: V4.90e, compiled Sep 8 2014 18:46:31 Firmware: J-Link OB-SAM3U128 V1 compiled Aug 22 2014 17:25:44 Hardware: V1.00 S/N : 480204190

JLink Info: Found SWD-DP with ID 0x0BB11477
JLink Info: Found Cortex-M0 r0p0, Little endian.
JLink Info: FPUnit: 4 code (BP) slots and 0 literal slots ROMTableAddr = 0xE00FF003

Target info:

Device: nRF51822_xxAA VTarget = 3.300V State of Pins: TCK: 0, TDI: 0, TDO: 1, TMS: 1, TRES: 1, TRST: 1 Hardware-Breakpoints: 4 Software-Breakpoints: 8192 Watchpoints: 2 JTAG speed: 2000 kHz

Load "C:\Keil_v5\ARM\Device\Nordic\nrf51822\Board\pca10001\s110\ble_app_hrs\arm\_build\ble_app_hrs.axf"

*** Restricted Version with 32768 Byte Code Size Limit *** Currently used: 24536 Bytes (74%)

**JLink Warning: CPU could not be halted ***JLink Error: Can not read register 15 (R15) while CPU is running ***JLink Error: Can not read register 16 (XPSR) while CPU is running ***JLink Error: Can not read register 0 (R0) while CPU is running ***JLink Error: Can not read register 1 (R1) while CPU is running ***JLink Error: Can not read register 2 (R2) while CPU is running ***JLink Error: Can not read register 3 (R3) while CPU is running ***JLink Error: Can not read register 4 (R4) while CPU is running ***JLink Error: Can not read register 5 (R5) while CPU is running ***JLink Error: Can not read register 6 (R6) while CPU is running ***JLink Error: Can not read register 7 (R7) while CPU is running ***JLink Error: Can not read register 8 (R8) while CPU is running ***JLink Error: Can not read register 9 (R9) while CPU is running ***JLink Error: Can not read register 10 (R10) while CPU is running ***JLink Error: Can not read register 11 (R11) while CPU is running ***JLink Error: Can not read register 12 (R12) while CPU is running ***JLink Error: Can not read register 13 (R13) while CPU is running ***JLink Error: Can not read register 14 (R14) while CPU is running ***JLink Error: Can not read register 15 (R15) while CPU is running ***JLink Error: Can not read register 16 (XPSR) while CPU is running ***JLink Error: Can not read register 17 (MSP) while CPU is running ***JLink Error: Can not read register 18 (PSP) while CPU is running ***JLink Error: Can not read register 20 (CFBP) while CPU is running

RE: Error while identifying cortex-M core

Stian Røed Hafskjold — Wed, 08 Oct 2014 12:18:38 GMT

Try to uninstall the J-link drivers in Device Manager (under USB controllers), unplug the board and plug it back in.

RE: Error while identifying cortex-M core

pramithkv — Tue, 07 Oct 2014 12:04:02 GMT

still problem remains after doing recover alsoo

RE: Error while identifying cortex-M core

pramithkv — Tue, 07 Oct 2014 10:11:32 GMT

im using nRFgo Studio v1.17

RE: Error while identifying cortex-M core

Petter Myhre — Tue, 07 Oct 2014 10:08:58 GMT

I haven't seen that error before. Could you try to update to the latest nRFgo Studio and nRF51-Tools? Found here.

Does it work with nrfjprog? Run a cmd.exe and try nrfjprog --recover. Select the Segger serial number that corresponds to your kit.