topic Re: s32k-HOW TO HARDFAULT in S32K

s32k-HOW TO HARDFAULT

jack-joker — Mon, 21 Oct 2024 01:25:57 GMT

Hello, after I configured the Mcal generated by EB to the compiler, a hardfauld error occurred during the run, and I found the SPI_INIT, but I couldn't solve it.
Thank you

Re: s32k-HOW TO HARDFAULT

VaneB — Mon, 21 Oct 2024 17:49:13 GMT

Hi @jack-joker

Could you please provide more information such as the settings you made and the implementation? Also, bedug further in Spi_Init() function to find out which line is stucked and causing this issue.

BR, VaneB

Re: s32k-HOW TO HARDFAULT

jack-joker — Tue, 22 Oct 2024 00:13:38 GMT

thank you for your report By search for that. It’s (Base>FCR=LPSPI_FCR_TXWATER((uint32)LPSPI_IP_FIFO_SIZE_U8-(uint32)2u);).it this line which casing to hard fault@VaneB

Thank you

Jack-joker

Re: s32k-HOW TO HARDFAULT

VaneB — Tue, 22 Oct 2024 17:19:54 GMT

Hi @jack-joker

Could you please provide more information such as the configurations you made?

Re: s32k-HOW TO HARDFAULT

jack-joker — Wed, 23 Oct 2024 05:29:51 GMT

that is all about my configure about SPI1

thank you!

Re: s32k-HOW TO HARDFAULT

VaneB — Thu, 24 Oct 2024 18:51:21 GMT

Hi @jack-joker

I have a question. Which S32K derivative are you using? Also, in the SpiPhyUnitClockRef the name of the SPI clock source configuration seems to be "SPI1", but you are configuring the LPSPI0, could you confirm if the clock configuration is the one corresponding to the SPI instance? The discrepancy in the name confused me.

Re: s32k-HOW TO HARDFAULT

jack-joker — Fri, 25 Oct 2024 09:35:51 GMT

I commented these three lines of code and it worked

This is the configuration to which one is associated

Thank you！

Re: s32k-HOW TO HARDFAULT

VaneB — Fri, 25 Oct 2024 20:32:53 GMT

Hi @jack-joker

There is no relation between these 3 lines of code; the first one enables the SPI to work in debug mode, the second one configures some main fields of the SPI and the last one corresponds to the transmit FIFO watermark.

Previously, you said that the hard faul was caused at Base>FCR=LPSPI_FCR_TXWATER((uint32)LPSPI_IP_FIFO_SIZE_U8-(uint32)2u), but with the current information but could you please verify if the fault is not caused by the the configurations set in the second line of code?

Re: s32k-HOW TO HARDFAULT

jack-joker — Sun, 27 Oct 2024 10:26:41 GMT

@VaneBI'm able to determine which line is the result of one of these three lines of code, and I'll have to verify it tomorrow

Tank you!