Adapting MCSPTR2AK396 reference firmware (AMMCLIB/FreeMASTER) for custom hardware with high-side sen

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Adapting MCSPTR2AK396 reference firmware (AMMCLIB/FreeMASTER) for custom hardware with high-side sen

59 次查看
Esakki
Contributor II
Hello NXP Community,

I am currently developing a motor control application using the S32K396 MCU and testing it via FreeMASTER / AMMCLIB. As a starting point, I am using the reference firmware provided for the MCSPTR2AK396 evaluation kit.

However, my custom hardware design differs significantly from the reference EVK board in three main areas:

  1. Current Sensing Topology:

    • EVK Board: Low-side current sensing.
    • Custom Design: High-side current sensing.
  2. Gate Driver Configuration:

    • EVK Board: Single pre-driver (GD3000 / MC33937 type).
    • Custom Design: Three separate, independent gate drivers (one dedicated driver per phase) with direct active-high control inputs.
  3. PWM Polarity:

    • EVK Board: High-side PWM inputs are active-low (inverted).
    • Custom Design: High-side PWM inputs are active-high (non-inverted).
Because of these hardware discrepancies, running the original MCSPTR2AK396 firmware out-of-the-box results in faults and incorrect phase behavior.

Could you please advise on the best approach or provide a checklist for modifying the S32K396 initialization, PWM/eMIOS configuration, ADC trigger timings, and AMMCLIB software layers to successfully migrate from the EVK design to my custom architecture?

Any guidance, code snippets, or configuration pointers would be greatly appreciated.

Thank you!

Regards,
Esakki
0 项奖励
回复
1 回复

8 次查看
PetrS
NXP TechSupport
NXP TechSupport

Hi,

The changes you described (high-side current sensing, different gate driver architecture, PWM polarity changes, and the associated motor-control software adaptations) represent a significant shift from the MCSPTR2AK396 reference design and require substantial modifications to the reference solution.

Due to the project-specific nature and complexity of this work, we are unable to provide a complete migration guide through the standard support channel.

For dedicated assistance with adapting the reference software to your custom hardware, please consider engaging NXP Professional Engineering Services:

NXP Engineering Services

Best regards,
Petr

0 项奖励
回复