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

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

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

1,807件の閲覧回数
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?

ラベル(3)
0 件の賞賛
返信
6 返答(返信)

1,780件の閲覧回数
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 件の賞賛
返信

1,763件の閲覧回数
Fukuda
Contributor I

Hi, Edwin.

It happens in every project.

Best Regard.

0 件の賞賛
返信

1,684件の閲覧回数
Fukuda
Contributor I

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

 

Hi, @Edwin.

It happens in every project.

Best Regard.

 
0 件の賞賛
返信

1,613件の閲覧回数
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 件の賞賛
返信

1,591件の閲覧回数
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 件の賞賛
返信

1,389件の閲覧回数
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 件の賞賛
返信