Hi NXP team,
We are using S32 design studio v3.5.
From the secure NXP website, we obtained the BCC_S32K144_Monitoring_Diagnostics example code.
Since we are utilizing the S32K344 EVB-Q172 board in this case, we modified the low level peripheral drivers of example code to translate the example code to the S32K344. Now the code is compiling without any errors.
However, the following error message appears and we are not receiving any data on SPI communication:
"BCC_STATUS_COM_CRC".
Could you please help me to address this problem?
Thanks and regards,
Hareesh
Hi @Hareesh,
Just to confirm, was the project working properly before porting? Did you migrate the example from S32DS for ARM to S32DS 3.5 manually? There were some issues migrating to S32DS3.5 so 3.4 was recommended as in this community post: Solved: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platfo...
Please confirm if the pin-mux is correctly configured, the peripheral is initialized, and that the SPI module follows this configuration:
Master mode, 48 bits/frame, MSB first, clock polarity: active high, clock phase:
capture on the 2nd edge, active low chip selects, clock frequency: up to 4 MHz
Best regards,
Julián
Hi @Julián_AragónM ,
Just to confirm, was the project working properly before porting? Did you migrate the example from S32DS for ARM to S32DS 3.5 manually? There were some issues migrating to S32DS3.5 so 3.4 was recommended as in this community post: Solved: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platfo...
Yes, the project was migrated successfully and the configuration files are generated properly in S32DS v3.4.
1. After migration, we connected a S32K144 EVK board with FRDM33771CSPEVB board. However we are not getting any data on the SPI communication with the example code itself (BCC_S32K144_Monitoring_Diagnostics).
2. We also ported the example code to support S32K344 MCU by changing the low level peripheral drivers of S32K144 MCU. But we are not getting any data on SPI communication.
In both the cases, we getting the following error "BCC_STATUS_COM_CRC " while initializing the BCC device.
Best regards.
Hareesh
Hi @Hareesh,
If this error is present even when testing with the S32K144EVB, then this may be an issue with importing. Could you test the project in S32DS for Arm v2.2? Also, could you measure with a logic analyzer the signals to confirm the data is being correctly transmitted?
Best regards,
Julián
This application note provides the main differences between the S32K1 and the S32K3 family, and their general considerations when migrating from S32K1 to.