S32K1xx Autosar 4.2 MCAL RTM_104 SPI module Configuration error

[ou_gangxun]

When I use S32K1xx Autosar 4.2 MCAL RTM_104 to configure the SPI module of s32k148, I create a new SBC property under [SpiExternalDevice], and its [SpiSlaveMode] property is set to "false".

The relevant controller configuration is the main mode:

SpiPhyUnit/SpiPhyUnit1/SpiPhyUnitMode = SPI_ MASTER。

However, the tool reports an error pointing to

SpiExternalDevice/SBC/SpiSlaveMode

Original report:

Invalid value for node "/AUTOSAR/TOP-LEVEL-PACKAGES/Spi/ELEMENTS/Spi/SpiDriver/SpiExternalDevice/SPI_ DEV_ FS4500/SpiSlaveMode": External Device mode is different with assigned HW mode.

However, the code can be generated and the function can run normally.

Question:

Is this a defect in S32K1x MCAL 421 RTM_104?

Will it be fixed in a later upgrade?

[hungnguyenphi]

Hello ou_gangxun,

I believe that you are choosing the wrong "SpiExternalDevic/SpiHwUnit " for the SPI_ DEV_ FS4500.

From my point of view, it should be CSIB1(refer to SpiPhyUnit_2) instead of CSIB0(refer to SpiPhyUnit_1) in your case. Could you please help to change it.

Best regards,

Hung.

[ou_gangxun]

hallo, Hung.

thank you for your reply.

I checked the configuration you described and found no errors.

But your suggestion gave me inspiration.

1. I try to create a SpiPhyUnit_0 in SpiPhyUnit that will not be used. The mode is configured as a slave device.
2. Then a strange phenomenon occurred: the same error occurred in SPI_DEV_SOC.
3. I guess EB tresos may have problems with the index logic of CSIBx in SpiExternalDevice/SpiHwUnit, so I made the following changes
   SPI_DEV_SOC/SpiHwUnit = CSIB1
   SPI_DEV_FS4500/SpiHwUnit = CSIB2
   The error disappeared.
4. It seems that CSIBx seems to refer to the selection list of SpiPhyUnit/SpiPhyUnitMapping instead of the configuration list of SpiPhyUnit.
5. To be safe, I ordered Index and SpiPhyUnitMapping in the SpiPhyUnit configuration list:
   Index0 SPI0
   Index1 SPI1
   Index2 SPI2

This situation is contrary to the description of SpiExternalDevice/SpiHwUnit. Also ask the tool development team to check this issue.

Best regards,

ou_gangxun

[hungnguyenphi · Accepted solution]

Hello ou_gangxun,

Yes, you are right. It seems that we have an issue in the MCAL package S32K1x MCAL 421 RTM_104.

I am asking MCAL team for checking this case.

Best regards,

Hung.