APM32F103VC MINI and J-Link

RRRR

I created a small application (led blinking) and tried to download it to the board (JLink_V794i) without success.
The debugger (SEGGER J-Link) from eclipse does not work and J-Link (command line) says ‘Writing target memory failed.’.
The board is brand new (I’ve just received it) and I tried the same configuration on both Linux and Windows 10.
The application is based on the ‘APM32F10x_SDK_V1.8\Examples\GPIO\GPIO_Toggle’ example (I only changed the linker script to match the MCU on my board).

Memory is not write-protected, I checked.

Any ideas?

Pravin

RRRR please try as below video

RRRR

As I said in my post, I tried to use SEGGER J-Link with the board, not the Geehy CMSIS-DAP debugger. According to SEGGER (https://wiki.segger.com/Geehy_APM32) it should work. But it doesn’t.

Pravin

RRRR what is error found can you please explain. and share connection diagram between boards and j-link .also need external power supply when you burn the code..

RRRR

First of all, thank you for trying to help ! I appreciate !
I followed this tutorial:
The board is APM32F103VC so the external power can only be an USB connection (to the PC).
Using J-Link (command line) I can erase the chip but that’s all I can do. I tried both SWD and JTag connections but to no avail.

Here is the J-Link session (if it helps):

Please specify device / core. <Default>: APM32F103VC
Type ‘?’ for selection dialog
Device>APM32F103VC
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>j
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device “APM32F103VC” selected.
Connecting to target via JTAG
InitTarget() start
Check if Flash is read protected.
InitTarget() end - Took 3.11ms
TotalIRLen = 9, IRPrint = 0×0011
JTAG chain detection found 2 devices:
#0 Id: 0×4BA00477, IRLen: 04, CoreSight JTAG-DP
#1 Id: 0×06414B47, IRLen: 05, APM32 Boundary Scan
DPv0 detected
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0×24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0×412FC231. Implementer code: 0×41 (ARM)
Found Cortex-M3 r2p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB000 SCS
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 003BB923 TPIU-Lite
[0][5]: E0041000 CID B105900D PID 003BB924 ETM-M3
Memory zones:
Zone: “Default” Description: Default access mode
Cortex-M3 identified.
J-Link>LoadFile C:\Users\XXXXX\eclipse-workspace\APM32F103VC_MINI_1\Debug\APM32F103VC_MINI_1.elf
‘loadfile’: Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading file [C:\Users\XXXXX\eclipse-workspace\APM32F103VC_MINI_1\Debug\APM32F103VC_MINI_1.elf]…
Writing target memory failed.

J-Link>

Pravin

RRRR Can you identify the mcu and jlink on pc?

RRRR

Sorry, I do not understand your question. What do you mean by ‘identify’?
I attached the J-Link session. The only identification that I can see is <Cortex-M3 identified.>.

Pravin kumar

Check if that help—connect the NRST of MCU with RST pin of Jlink.
1. Lower down the interface speed— 4000kHz->1000kHz/500kHz
2. Use J-Flash instead of J-Link Commander, check if connection is successful, check if unsecure is successful.
3. What board did you use? Our mini board or own PCBA?
4. Shorten the wires between the port of Jlink and MCU’s SWD/JTAG ingterface. Or just change other wires

David

Can you upload your elf file so that we can try to reproduce your problem?

RRRR

Board is the original APM32F103VC MINI (https://www.soselectronic.com/ro/products/geehy/apm32f103vc-mini-board-388085).
I tried both J-Link and J-Flash.
To build the project I used gcc_APM32F10xxC.ld and startup_apm32f10x_hd.S from the official APM32F10x_SDK_V1.8.

Attached the debug - elf file.

apm32f103vc-mini-1.bin

71kB

David

RRRR
I tried burning the elf file and found a similar error, so I suspect that there may be a problem with your project. Can you send me the first phase of the project for testing? My email is as follows: david.liu@geehysemi.com.

If you are using an Eclipse project, I have the following suggestions:
Replacing the chip model without APM32F103VC requires two changes,

RRRR

Thank you, David !
You were absolutely right (screenshot 2) .
While adjusting the GPIO_Toggle example I completely forgot to change the *.ld file in the linker settings (-T).
It’s working now.