I can't write to the FRDM-MCXC242 Flash using MCUXpresso IDE

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

I can't write to the FRDM-MCXC242 Flash using MCUXpresso IDE

1,806 Views
Fukuda
Contributor I

Hello, I'm Fukuda.

I am using FRDM-MCXC242 and MCUXpresso IDE v24.12.148.
When I use the GUI Flash Tool in MCUXpresso IDE, no errors occur.
Also, when I press the Start debugging project button, no errors occur and I move to the debug screen.
However, random values ​​are written to the vectors where the initial stack pointer and reset handler addresses should be written.
Even if I erase the flash or write a suitable demo project, the values ​​remain the same and do not change.
When I dumped the axf file, the vector addresses were set to the correct values.
What could be the possible causes?

Labels (3)
0 Kudos
Reply
6 Replies

1,779 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @Fukuda,

Do you see this issue happening with any project, including the example projects we provide in the SDK, or only with a specific custom application?

BR,
Edwin.

0 Kudos
Reply

1,762 Views
Fukuda
Contributor I

Hi, Edwin.

It happens in every project.

Best Regard.

0 Kudos
Reply

1,683 Views
Fukuda
Contributor I

Sorry, I forgot to mention it, so I'll repost it.

 

Hi, @Edwin.

It happens in every project.

Best Regard.

 
0 Kudos
Reply

1,612 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @Fukuda,

Thanks for the clarifications. Could you share screenshots of the issue? Where do you see the random values and where on the dumped axf do you see the correct ones?

BR,
Edwin.

0 Kudos
Reply

1,590 Views
Fukuda
Contributor I

Hi @EdwinHz 

The first image is a screenshot of MCUXpresso, and the bottom right shows a memory dump starting from address 0.
The second image is a dump of the axf file, with the initial stack stored at address 0 and the handler addresses stored from address 4 onwards.

Best Regard.

0 Kudos
Reply

1,388 Views
EdwinHz
NXP TechSupport
NXP TechSupport

Hi @Fukuda,

I haven't been able to replicate this issue. When I try it, I get the same values for 0x00000000 on both the memory window and the .axf dissasembly:

EdwinHz_0-1745951847941.png

EdwinHz_1-1745951863342.png

You mention this discrepancy occurs in every project, but does it also occur on different workspaces? Please try creating a new workspace and downloading the image files from there. Also, try doing the mass erase using a different debugger if possible (like a J-Link debugger).

BR,
Edwin.

0 Kudos
Reply