S32K3xx Sensorless Example build wasnt complete

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32K3xx Sensorless Example build wasnt complete

Jump to solution
160 Views
yr1205
Contributor I

Hi,

I was trying to build the example "PMSM Sensorless Field-Oriented Control with Motor Control Blockset™ S32CT" from Simulink into the S32K344. I was able to finish the building process without any Error. The Simulink notified that the build was successful and it was working fine. Then I tried reflashing the same example later, the build was successful, however the blue LED was not turning on.

So, I tried other examples, and still the same issue persists. I am wondering where it went wrong.

Regards,

yr1205

0 Kudos
Reply
1 Solution
95 Views
stefanvlad
NXP Employee
NXP Employee

Hi @yr1205 ,

 

What version of the MBDT for S32K3 toolbox are you using?

I do recommend you install the latest NXP Model-Based Design Toolbox for S32K3 version 1.7.0 - Product Release Announcement - NXP Communit...

 

Second , what board are you using? 

If you are using the MCSPTE1AK344 kit, i recommend you follow the Getting started guide

 

Third, you are using the s32k344_mcb_sensorless_s32ct.mdl ? 

 

If the Blue LED doesn't turn On, there might be a problem with the GD3000 board , not fully inserted into the S32K344-T172 board.

To fix this, you need to press on the GD3000 headers to get better contact into S32K344-T172 board.

 

Best regards,

Stefan V.

View solution in original post

0 Kudos
Reply
1 Reply
96 Views
stefanvlad
NXP Employee
NXP Employee

Hi @yr1205 ,

 

What version of the MBDT for S32K3 toolbox are you using?

I do recommend you install the latest NXP Model-Based Design Toolbox for S32K3 version 1.7.0 - Product Release Announcement - NXP Communit...

 

Second , what board are you using? 

If you are using the MCSPTE1AK344 kit, i recommend you follow the Getting started guide

 

Third, you are using the s32k344_mcb_sensorless_s32ct.mdl ? 

 

If the Blue LED doesn't turn On, there might be a problem with the GD3000 board , not fully inserted into the S32K344-T172 board.

To fix this, you need to press on the GD3000 headers to get better contact into S32K344-T172 board.

 

Best regards,

Stefan V.

0 Kudos
Reply