Hello,
I can see in the Sbc_Fs26_HLD example that there is an option in the Spi component (MCAL) to set a CS pin, which allows manual control over the CS pin
But I'm not clear where that option is if I don't want to use a MCAL layer.
So, not working according to a AUTOSAR framework.
In the same type of example but in the version Sbc_fs26_example_IP , which is not according to AUTOSAR standard, I don't have that option.
Where is SPI CS as GPIO pin control, option in the non autosar example?
Thank you.
Hi @Djuric
The pin should be configured only as a GPIO, not as an SPI pin. For example, instead of defining it like this in the Pins Tool:
It should be configured as follows:
Then, control the state of the pin using the API Siul2_Dio_Ip_WritePin().
Thanks for the answer.
How do I configure the CS pin in the S32DS tool to be a GPIO, when it is reserved for a Lpspi peripheral. There is a definition collision. One pin cannot be defined in two different components Lpspi and SIUL. Can you send me a screenshot of where this is exactly set up. I read the documentation, this chapter refers to settings in the AUTOSAR context.
Hi @Djuric
Unlike the SPI driver (MCAL), the LPSPI driver (IP) does not provide an explicit option to indicate whether the CS will be managed via GPIO or by the HW engine. For the IP driver, handling CS through GPIO must be implemented in code, and in ConfigTool you need to configure the desired pin as a GPIO.
Additionally, please note that a low CLK pulse occurs when using the first workaround for ERR050456, which involves resetting the LPSPI module. If you select the second workaround, this low pulse will not appear.
For more details about how to enable the second workaround, refer to Section 3.6.8 of the User Manual for S32K3_S32M27x SPI Driver.
BR, VaneB