topic Re: when Pflash mapping the ram ，pflash loss the init data in S32K

when Pflash mapping the ram ，pflash loss the init data

Wan — Thu, 26 Jun 2025 07:01:31 GMT

Hello NXP engineer

I find the program . please help me

Chipes : S32K310 S33DS3.6.1 RTD :4.0.0

when I use the “ int_calflash AT > int_calram”code mapping the pflash datat to ram, I find the pflash Initdata is all 0xFF. but i init the pflash the data.

Re: when Pflash mapping the ram ，pflash loss the init data

VaneB — Fri, 27 Jun 2025 20:21:36 GMT

Hi @Wan

Based on your description, it seems you are trying to map initialized data from Flash to RAM.

Please note that 0xFF typically indicates unprogrammed flash memory. This suggests that the data might not have been correctly placed in the .int_calflash section, or that this section was not included in the linker script or the generated S-record/binary file.

To help with this, I recommend reviewing the following resources:

HOWTO: Run a routine from RAM in S32 Design Studio: explains how to modify the linker file to define code allocation regions.

S32K312_C40_Ip_SRAM_RTD_500_DS35: demonstrates how to place functions in SRAM.

If I have misunderstood, please feel free to let me know.

BR, VaneB

Re: when Pflash mapping the ram ，pflash loss the init data

Wan — Mon, 30 Jun 2025 05:51:28 GMT

hello VaneB ：

I had saw the "HOWTO: Run a routine from RAM in S32 Design Studio"

but not thorough slove my question, this page is my image question ,please help my check.

I want the operation space of Flashdata to be within the RAM area I have specified.

Re: when Pflash mapping the ram ，pflash loss the init data

Wan — Mon, 30 Jun 2025 14:07:41 GMT

Re: when Pflash mapping the ram ，pflash loss the init data

VaneB — Mon, 30 Jun 2025 20:25:54 GMT

Hi @Wan

It is important to understand that the linker script only defines memory regions and assigns variables or sections to those regions. It instructs the compiler and loader where data should reside in memory (e.g., Flash, RAM), but it does not perform any actual copying of data from Flash to RAM at runtime.

The responsibility for copying initialized data from Flash to RAM lies with the startup code or, in some cases, a dedicated initialization function. If you are depending on certain data to be available in RAM at runtime, it is essential to verify that your startup or initialization code is explicitly handling this copy process.