MSPM0L1306: innacessible device after programming random data in flash

Tomas Lehotsky

Part Number: MSPM0L1306

Hi,

I have met with a problem during developing the read/program/erase algo for MSPM0Lx devices. I have developed the first revision of my algorithms on experimental samples of XMS0Lx. For the XMS0Lx I program completely random data to the whole flash from adress 0x0. After power cycling( power-down and power-up the device(or reset)), I can succesfull read or verify programmed flash.

When I do the same with the regular MSPM0Lx devices(program random data to the flash from address 0x0) I can't access the device. I am not able to access the DHCSR register(in purpose of halting CPU) because I obtain an fault acknowledge(on SWD interface) when I try to do this. So what is the reason fort this behaviour? How should I halt the core and read the flash via SWD?

Thank you!

Best regards,

Tomas

over 1 year ago

0 Luke Ledbetter over 1 year ago

TI__Mastermind 21390 points

Hi Tomas,

Are you able to connect to the target configuration and connect to the DAP core? If you're programming random data there could be an interrupt, a hardfault, or something else blocking the debug state. Connecting to the core should let you view the device memory without having to run the code.

Regards,

Luke

0 Tomas Lehotsky over 1 year ago in reply to Luke Ledbetter

Intellectual 995 points

Hi Luke,

the CCS is not able to connect to the target:

I have feeling that I have the same problem as in this post https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1180256/lp-mspm0l1306-flash-programming-cause-soc-ahb-bus-to-be-inaccessible

Do you have any idea how should I connect to the device and verify programmed data?

The only workaroud at this time is to run the BSL mass erase over UART and erase the device...but this is not the solution.

Thank you!

0 Luke Ledbetter over 1 year ago in reply to Tomas Lehotsky

TI__Mastermind 21390 points

Hi Tomas,

Can you load in the gpio_toggle_output.c example, then check the memory? If this works can you then debug the example you are working on and step through, see if you are getting into a hardfault. With the flash memory if you program into the wrong space it can cause unexpected results, which is what I am expecting is happening here. 0x0 is generally the start of the application code if you aren't partitioning the code you could be overwriting the application code.

Regards,

Luke

0 Tomas Lehotsky over 1 year ago in reply to Luke Ledbetter

Intellectual 995 points

Hi Luke,

I am not able to load mentioned project(gpio_toggle_output.c) to the device.When I try to debug this project and try to connect to the target, I obtain an error: Error connecting to the target:

(Error -6305) PRSC module failed to write to a router register.
(Emulation package 9.11.0.00128)

As I wrote before, it seems that random data from address 0x0 cause that device is not accesible. Can you tell me, what is the reason why is the device not accesible?

Regards,

Tomas

0 Luke Ledbetter over 1 year ago in reply to Tomas Lehotsky

TI__Mastermind 21390 points

Hi Tomas,

Historically the PRSC module failed to write to a router register has to do with power on ARM devices. Here is an E2E post that will help provide context to this error.

I believe our first step should be relieving the PRSC error. Were you able to successfully program the device previously? Looking at this post history it isn't clear if you had a successful program. I would double check the wire connections to make sure they are reliable. Scope the power to see if there are any excessive drops.

Also a general precaution, since you are using the production version of the device make sure you are using CCS 12.3+ and MSPM0SDK 1.0+.

Regards,

Luke

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0L1306: innacessible device after programming random data in flash