S32 SDKのトピックRe: EEP Partitioning causing exception or Hardfault during Init after flashing

EEP Partitioning causing exception or Hardfault during Init after flashing

SAnjal — Wed, 05 Jun 2024 10:30:42 GMT

I have developed a custom SW for S32K118, in which I have to store Data to NVM, for this I have used FlexRAM. When I flashed App on the MCU and run, I observe that MCU stuck at exception handler. After debugging the SW I have seen that, while FlexRAM partition is in progress its going to exception from the condition "while(0 == ((FTFC->FSTAT & FTFC_FSTAT_CCIF_MASK) >> FTFC_FSTAT_CCIF_SHIFT))" is being checked,

Note: also the watchdog is enabled before the partitioning with timeout of 32mSec and refresh is performed every 10mSec. The FlexRAM activity is performed in periodic task of 10mSec for partitioning/Reading/Writing. Also MCU reset is performed after EEP partition as per the requirement.

Re: EEP Partitioning causing exception or Hardfault during Init after flashing

lukaszadrapa — Fri, 07 Jun 2024 15:45:28 GMT

Hi @SAnjal

The partition command must be executed from RAM memory. You need to ensure that the flash is not accessed during partitioning (disabled interrupts, callback function in RAM...):

And be aware of other restrictions related to flash, emulated eeprom and CSEc:

Regards,

Lukas

Re: EEP Partitioning causing exception or Hardfault during Init after flashing

SAnjal — Wed, 19 Jun 2024 10:34:58 GMT

We have take care to run Partitioning command from RAM but, still facing this issue. As per observation,

PC is not jumping to RAM to execute the Program Partitioning command.

Note: As per current implementation we have optimized our code to level 01, does this might be creating the issue. If yes, then what care should we take for FlexRAM partitioning.

Re: EEP Partitioning causing exception or Hardfault during Init after flashing

lukaszadrapa — Mon, 24 Jun 2024 08:04:09 GMT

How do you force the function to RAM?