This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can bad inicialization of flash damage chip

Hi I probably have done multiple or bad inicialization of flash memory in code and my MiniBeacon (www.alibaba.com/.../Nordic-bluetooth-nRF51822-logo-customizable-minibeacon_60408141084.html) doesn't work now. It was debugging by nRF51 DK. I see debugger nRF51 DK in nRF Studio and in Keil, but chip of custom board doesn't see anyone.

  1. Can bad inicialization of flash damage chip ?
  2. Can I recover it somehow ?

UPDATE 30.3.2017: I figured out somehow, but this issue occurs again. Log: *

--------------------------------------------------------------------------------
C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin\nrfjprog.exe --recover --log
nrfjprog verion 9.3.1
--------------------------------------------------------------------------------
FUNCTION: open_dll.
FUNCTION: open_dll.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: enum_emu_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_with_snr.
FUNCTION: connect_to_emu_without_snr.
FUNCTION: enum_emu_snr.
Device "NRF51822_XXAA" selected.
FUNCTION: recover.
FUNCTION: recover.
Communication timed out: Requested 20 bytes, received 0 bytes !
Could not read hardware status!
JLinkARM.dll Connect returned error -257.
JLinkARM.dll Connect returned error -257.
Debugger tries to select target interface SWD.
This interface is not supported by the connected emulator.
Selection will be ignored by the DLL.
JLinkARM.dll Connect returned error -257.
Debugger tries to select target interface SWD.
This interface is not supported by the connected emulator.
Selection will be ignored by the DLL.
JLinkARM.dll Connect returned error -257.
Debugger tries to select target interface SWD.
This interface is not supported by the connected emulator.
Selection will be ignored by the DLL

*.

Parents Reply Children
No Data
Related