MSPM0L1228: RAMcode did not respond during flashing

Jan Bender

Part Number: MSPM0L1228
Other Parts Discussed in Thread: SEGGER, MSPM0L2228, UNIFLASH

Tool/software:

Hello,

We have designed the new MSPM0L1220 QFN32 on our PCB. Unfortunately, we have not been able to flash or delete the controller since then. The connection to the controller was established. We use the Segger J-link Pro as a programmer.
The error message is: Timeout while preparing target, RAMCode did not respond in time! Faild to perform RAMCode-sided Prepare() .
We were able to flash the MSPM0L2228 dermoboard with the Segger without any problems.
We have already checked the signals and checked the SWD circuitry. the only diference to the MSPMOL2228 demo board, Vcore is not connected.
We would be very pleased to receive quick feedback from you.

best regards Jan Bender

10 months ago

0 Luke Ledbetter 10 months ago

TI__Mastermind 25620 points

Hi Jan,

VCORE is needed to operate the device. Please populate the VCORE with a 0.47uF capacitor.

Regards,
Luke

+1 Jan Bender 10 months ago in reply to Luke Ledbetter

Prodigy 15 points

Hello,
after we soldered the capacitor to Vcore, we were able to flash successfully about 5 times. But now the µC can no longer be connected.

0 Luke Ledbetter 10 months ago in reply to Jan Bender

TI__Mastermind 25620 points

Hi Jan,

What is the error you're getting?

Regards,
Luke

0 Jan Bender 10 months ago in reply to Luke Ledbetter

Prodigy 15 points

Hello Luke,
sorry for my late reply. We carried out a few more tests and built new PCBs to verify the error.
We get the following error messages.

- Segger: Failed to connect. Could not establish a connection to target.

- UniFlash: Error connecting to target. DAP Connection Error. This could be caused by device having gone to low power mode. Try forcing an external reset.....

- UniFlash: Error connecting to the target: (Error -614 @ 0x0) thetarget indicates there is an error condition from a previous SWD regquest.

best regards Jan

0 Luke Ledbetter 10 months ago in reply to Jan Bender

TI__Mastermind 25620 points

Hi Jan,

Since the program is able to connect on the launchpad, I am still suspicious of your board. Are you able to send me a schematic? (If you want to you can go through your TI FAE as well).

Regards,
Luke

0 Jan Bender 10 months ago in reply to Luke Ledbetter

Prodigy 15 points

Hello Luke. I can send you a circuit diagram. Do you have an email address for me? best regards jan

0 Jan Bender 10 months ago in reply to Luke Ledbetter

Prodigy 15 points

Hello Luke,

Does the BSL PA18 pin have to be in a defined state during the false? in the EVAL board it is placed against GND.
ROSC is in our schematic to not connected, could that be a cause?

best regards Jan

0 Luke Ledbetter 10 months ago in reply to Jan Bender

TI__Mastermind 25620 points

Hi Jan,

My email is l-ledbetter@ti.com

BSL is the default BSL invoke pin, so if you have a high-signal then the device would enter BSL mode on device startup. Pulling to down is recommended to prevent this. Optionally, you can disable the BSL-invoke pin or move it to a different pin in the NON-MAIN configuration.

Regards,
Luke

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0L1228: RAMcode did not respond during flashing