Error: Flash Download failed - "Cortex-M4" at keil uvision5

[MAS_JP]

Hello support Team,An unclear point came out when driving nRF52810 with Keil uVision5.
I have a soft device(S112) write error. Can you help me with the following information?

Chip:nRF52810
Module:EBSLCNZWW (Taiyo Yuden)
SDK:Keil uvision5
Nordic SDK:ver14.2.0
File:C:\Nordic Semiconductor\nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral\ble_app_uart\pca10040e\s112\arm5_no_packs\ble_app_uart_pca10040e_s112.uvprojx

■Console log
Load "..\\..\\..\\..\\..\\..\\components\\softdevice\\s112\\hex\\s112_nrf52810_5.1.0_softdevice.hex"
Set JLink Project File to "C:\Nordic Semiconductor\nRF5_SDK_14.2.0_17b948a\examples\ble_peripheral\ble_app_uart\pca10040e\s112\arm5_no_packs\JLinkSettings.ini"
* JLink Info: Device "NRF52810_XXAA" selected.
 
JLink info:
------------
DLL: V6.52e, compiled Oct 16 2019 12:16:54
Firmware: J-Link Lite-Cortex-M V9 compiled May 17 2019 09:50:01
Hardware: V9.00
S/N : 519002337
Feature(s) : GDB
 
* JLink Info: InitTarget() start
* JLink Info: InitTarget() end
* 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: 000BB000 SCS
* JLink Info: ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
* JLink Info: ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTableAddr = 0xE00FF000
* JLink Info: Reset: Halt core after reset via DEMCR.VC_CORERESET.
* JLink Info: Reset: Reset device via AIRCR.SYSRESETREQ.
 
Target info:
------------
Device: nRF52810_xxAA
VTarget = 3.228V
State of Pins:
TCK: 0, TDI: 1, TDO: 1, TMS: 1, TRES: 1, TRST: 255
Hardware-Breakpoints: 6
Software-Breakpoints: 8192
Watchpoints:          4
JTAG speed: 4000 kHz
 
Erase Failed!
Error: Flash Download failed  -  "Cortex-M4"
Flash Load finished at 00:00:58

[Vidar Berg]

The "UART start" message will be printed out over the serial port, so you need to set up a serial client on your PC to see it. 

MAS_JP said:

I went to "Select UART⇒Connect from CONNECT button to Nordic_UART(Default Device Name),
but I don't know what to do after that.

Please refer to the "Testing" section in the example doc for more detailed instructions if you haven't done it already. The buttons are programmable. Click edit to add a button and a text string to be sent when the button is pressed. The text strings should be displayed in the serial client after its sent from the phone.  

  

[MAS_JP]

Thank you for introducing the materials.
I proceeded with the procedure of "Testing", but "UART Start!" is not displayed in No.4.

Steps 5 and 6 can be connected without problems.
Nos. 7 and 8 will generate an error even if you set a character string and press the button.
Is it a problem on the terminal emulator side?

■Treminal emulator
Tera Term ver4.99
(Set as No.2 in "Testing")

■nRF Toolbox Show Log
10:02:31.139 Connecting to:Nordic_UART...
10:04:31.140 centralManager.connect(peripheral, options:nil)
10:04:34.996 UART RX Characteristic not found

[Vidar Berg]

Surprised that you get this error "UART RX Characteristic not found". Are you using the original ble_app_uart example without any changes to the service initialization? And are you testing with iOS or Android?

[MAS_JP]

The contents of SDK(ver14.2.0) are not changed and the original ble_app_uart example is written as it is.
Testing is done on iOS.

iOS version : 12.0.1.
nRF Toolbox version : 4.5.1

[Vidar Berg]

Your iPhone may have cached Services from previous connections with the same device. The caching enables it to skip the time-consuming service discovery on every re-connect. But it can be a problem during development when you want to try different services/apps on the same board which use the same BT address. Try to clear the cache by enabling and disabling Flight mode on your phone. Then re-connect and see if you get the same error. You may also use the nRF connect app on iOS to see the actual services.

  

[MAS_JP]

Thank you for your reply.

I tried to delete the cache in flight mode, but I got the same error.