Friday, May 25th 2018, 3:03am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Date of registration: Mar 20th 2017

Posts: 7

Location: Poland

1

Wednesday, February 14th 2018, 11:15am

[SOLVED] STM32F411RE - Timeout while checking target RAM

Hi,

I'm trying to flash STM32F411RE using J-Track for ARM Cortex-M, it seems that the flasher connects fine to the device but when I try to erase or loadbin the "Timeout while checking target RAM" error occurs. Is there something with my flashing process, please?


Log from JLinkExe is attached below.

----- Update -----

And we were able to flash this uC using ST-Link flasher.


---------------------

Kind Regards,
Krzysztof


"

$ JLinkExe -device STM32F411RE -speed 4000 -if SWD
SEGGER J-Link Commander V6.20d (Compiled Sep 29 2017 16:44:27)
DLL version V6.20d, compiled Sep 29 2017 16:44:18

Connecting to J-Link via USB...O.K.
Firmware: J-Trace PRO V1 Cortex-M compiled Dec 1 2017 14:41:37
Hardware version: V1.00
S/N: 751000106
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 192.168.0.2
Emulator has RAWTRACE capability
VTref = 3.305V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "STM32F411RE" selected.


Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Found SW-DP with ID 0x2BA01477
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: 0x24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
J-Link>erase
Erasing device (STM32F411RE)...

****** Error: Timeout while checking target RAM, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x21000000)!
Failed to prepare for programming.
Failed to execute RAMCode for RAM check!
ERROR: Erase returned with error code -1."

This post has been edited 1 times, last edit by "krzysztof.rosinski" (Feb 14th 2018, 12:05pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,054

2

Wednesday, February 14th 2018, 4:09pm

Hello,

Thank you for your inquiry.
Such an issue is not known to us.
You seem to be using an older J-Link software version.
Could you update to the latest version and check if the behaviour improves?
Additionally, could you try to reset the target after a connect int J-Link commander before calling loadbin. Does that make a difference?

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Date of registration: Mar 20th 2017

Posts: 7

Location: Poland

3

Thursday, February 15th 2018, 9:17am

Hello Nino,

This looks exactly the same with the newest J-Link (V6.30c) and reset before erase / loadbin.

Regards,
Krzysztof


Quoted

$ JLinkExe -device STM32F411RE -speed 4000 -if SWD
SEGGER J-Link Commander V6.30c (Compiled Feb 9 2018 17:21:42)
DLL version V6.30c, compiled Feb 9 2018 17:21:32

Connecting to J-Link via USB...O.K.
Firmware: J-Trace PRO V1 Cortex-M compiled Feb 2 2018 18:26:42
Hardware version: V1.00
S/N: 751000106
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
IP-Addr: 192.168.0.2
Emulator has RAWTRACE capability
VTref = 3.303V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Device "STM32F411RE" selected.


Connecting to target via SWD
Found SW-DP with ID 0x2BA01477
Found SW-DP with ID 0x2BA01477
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: 0x24770011)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
ROMTbl[0][0]: E000E000, CID: B105E00D, PID: 000BB00C SCS-M7
ROMTbl[0][1]: E0001000, CID: B105E00D, PID: 003BB002 DWT
ROMTbl[0][2]: E0002000, CID: B105E00D, PID: 002BB003 FPB
ROMTbl[0][3]: E0000000, CID: B105E00D, PID: 003BB001 ITM
ROMTbl[0][4]: E0040000, CID: B105900D, PID: 000BB9A1 TPIU
ROMTbl[0][5]: E0041000, CID: B105900D, PID: 000BB925 ETM
Cortex-M4 identified.
J-Link>r
Reset delay: 0 ms
Reset type NORMAL: Resets core & peripherals via SYSRESETREQ & VECTRESET bit.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
J-Link>erase
Erasing device (STM32F411RE)...

****** Error: Timeout while checking target RAM, RAMCode did not respond in time. (PC = 0x00000000, CPSR = 0x00000000, LR = 0x21000003)!
Failed to prepare for programming.
Failed to execute RAMCode for RAM check!
ERROR: Erase returned with error code -1.

This post has been edited 1 times, last edit by "krzysztof.rosinski" (Feb 15th 2018, 9:18am)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,054

4

Thursday, February 15th 2018, 9:53am

Hello Krzysztof,

Thank you for providing the log.
We tried to replicate your setup with a NUCLEO-F411RE board and a J-Trace PRO as debug probe and everything is working as expected. See attachment.
Are you using custom hardware or an eval board?

Best regards,
Nino
SEGGER - Nino has attached the following image:
  • Capture.PNG
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Date of registration: Mar 20th 2017

Posts: 7

Location: Poland

5

Thursday, February 15th 2018, 5:23pm

Hello Nino,

We have tried the same flasher with a NUCLEO-F411RE too and everything seems to work fine but on our custom board we can't program uC. We use 4 pins SWD (VCC, GND, CLK, IO). Do you have any idea why this works fine with ST-Link but we can't use J-Trace?

Kind regards,
Krzysztof

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,054

6

Friday, February 16th 2018, 2:47pm

Hello Krzysztof,

Try connecting the reset pin as well to J-Link.
Generally it is recommended to connect the reset Pin to J-Link to have a fallback if software reset is not enough on the used target device.
If it still does not work compare the eval board schematic with your custom board schematic and see if there are any other differences.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


Date of registration: Mar 20th 2017

Posts: 7

Location: Poland

7

Wednesday, February 21st 2018, 5:46pm

Thank you Nino for your help.

It turned out that we had a capacitor missing on pin 30 PB11/VCAP1, once we added this capacitor J-Link works as expected.

Kind regards,
Krzysztof

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 1,054

8

Monday, February 26th 2018, 9:17am

Hello Krzysztof,

Great to hear that you are up and running.

We will consider this case as closed now.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/