Hard fault error

Anjalipurushothaman — Wed, 06 Sep 2023 19:43:03 GMT

Have contacted NXP representative. They have advised to put this issue here in this forum for this error,
Answer from NXP representative for the Hard fault error:

"A prelim hypothesis this hard fault seems to be part of the application going into a hard fault because an invalid access to a memory address, Before any conclusion can be made, need further info especially if modifications to the code were done. How (steps / procedure) you produce this fault?

Please update in your thread in NXP community, we have engineers working there."

I haven't made any changes to the code other than the syntax errors which popped up (missing semicolon,..).

Please find the below project example used and steps followed.

Development board- s32k3x8evb-Q289

IDE - s32DS for s32 platform

Debugger Used - PE Micro Debugger

Example project from s32k3xx (Port Example - Siul2_Port_Ip_S32K358) (mentioned in the description that supported board as x32k3x8cvb-q289)

*File -New -project from example - port example-finish

*From the Project explorer window, selected the project name - Right click- configuration tool-Under Drivers added Mcu, Port, Dio.

*Click on Update code

*Build Project

*Under Debug configuration-Selected the devices - Debug.

To build and run the example application, generated configurations needed at the Configuration Tool menu then clicked on the desired configuration tool (Pins, Cocks, or Peripherals). Made the desired changes then clicked on the Update Code button. and then select the configuration to be built and finally debug the project.

These are the steps followed, Please go through and let me know if anything wrong in these.

We are posting the issues here, as advised by the NXP representative, in order to have them resolved.

Re: Hard fault error

Robin_Shen — Fri, 08 Sep 2023 08:47:11 GMT

Did you checked the OsifEnableUserModeSupport? Have you tried latest RTD version?

Best Regards,
Robin

topic Hard fault error in S32 Design Studio

Hard fault error

Re: Hard fault error