Hi,
I am using Error inject Module to inject double-bit to SRAM_L,and many strange bugs have occurred:
1:When I inject double-bit error to SRAML,sometimes it cannot trigger double-bit error but single-bit error and enters single fault handler!And reset is useless it just keeps going into single fault handler.The solution is to restart the computer or inject the single-bit error to SRAML again after injecting double-bit error to SRAML:
``
Hi @n00b123,
Can you modify the example below so that you can reproduce the issue with it and share it here?
https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K14x-SRAM-ECC-Injection/ta-p/1129181
Thanks,
Daniel
Yeah, I have modified the code from your example but I do not use your link files and startup code instead of Project Hello World of S32DS(SRAM_ECC.zip), I inject the double-bit and single-bit error to SRAML at the same time, but this cannot reproduce the issue.Instead when I port the code to my project,the issue will be reprodeced,sometimes the bug is Injecting double-bit error but trigers single fault ISR or Injecting double-bit error trigers double fault ISR normally but injecting single-bit error cannot triger single fault ISR ,I have made my ECC injecting code identical to the example so I doubt that is the different link files or startup code cause the issue,see attachments(MyprojectsLinkerFilesAndStartupCode.zip)
I believe I address that in the description of the example:
The default S32 Design Studio start_up file copies the vector table to the SRAM_L region.
To be able to inject ECC errors in this SRAM region and call the interrupts,
the copying is disabled by __flash_vector_table__ symbol declared in the start_up.h file and defined in the S32K144_64_flash linker file.
Regards,
Daniel