Guide: Running the NXP SW32K358_HVBMS-RD_IntProj_S32DS Example

[AchrafOukheir]

Guide: Running the NXP SW32K358_HVBMS-RD_IntProj_S32DS Example

 

Introduction

The NXP SW32K358_HVBMS-RD_IntProj_S32DS example provides a reference for developing a high-voltage battery management system (BMS) using the S32 Design Studio (S32DS). our journey involved overcoming challenges, collaborating with the NXP team, and making critical corrections. Let’s capture that spirit in our guide.
 

Prerequisites

• Ensure you have downloaded the SW32K358_HVBMS-RD_IntProj_S32DS_0.8.1_D2408 example from NXP’s website.
   
• Note: This guide is for the NXP SW32K358_HVBMS-RD_IntProj_S32DS_0.8.1_D2408 example, which is not yet a stable version. Some issues were encountered and resolved  to successfully run this example.
   
• After downloading the SW32K358_HVBMS-RD_IntProj_S32DS_0.8.1_D2408 example from NXP, our team faced several issues and errors. It seems that some corrections were made from version 0.8.0 to version 0.8.1, but issues still remained. Here are the steps we took to fix them before running the example:

Step 1: MCAL Code Generation

1. Open S32DS and open the project based on the downloaded example.
2. Generate the MCAL code for your specific hardware configuration.

Step 2: Addressing the First Error

1. After building the project, you encountered an error related to BMS_Common.
    
2. After following the MCAL code generation steps, an error occurred while building the project

 To fix this, we updated the bms_common component by choosing the correct driver.

• Screenshot:
• 

Step 3: Fixing Communication with Freemaster

1. There was an issue with FreeMASTER communication after investigating. We had to change the baud rate to establish communication with FreeMASTER
    
2. Adjust the baud rate settings to ensure proper communication.
   
    

Step 4: Freemaster GUI and Application Execution

1. Open the Freemaster GUI.
2. Run the application to verify correct behavior.
• Screenshots:

Conclusion

After resolving the issues mentioned above through our investigations and exchanges with the NXP team, we were finally able to run the application correctly. We hope that NXP will develop a well-documented and stable version 1.0.0 of this example, incorporating the corrections and improvements we have identified.