Devkit MPC5744P and MotorGD config problems

[haoxue1027]

Hello，marius
Sorry to trouble you beacuse community site is" Site Undergoing Maintenance".
Now I want to use the Devkit MPC5744P (rev E)and MotorGD to produce the PWM singal on the side of mosfet.
But I failed.
In the simulink demo, the config is recommended as belowing.

haoxue1027_0-1598921302555.png

But I found that it seemed some errors here.
I cannot find the cs=PG5.
I checked  the MotorGD pin set and Devkit MPC5744P (rev E) pin set：

haoxue1027_1-1598921344897.png

haoxue1027_2-1598921354836.png

It is different from the recommend config in the simulink demo。
I am so confused about it.
Can you help me solve it？
Thank you very much。
best regards。

hao

[mariuslucianand · Accepted solution]

Hello @haoxue1027,

I think there is a typo in the project description. If you have a look on the LPSPI config block, it actually uses the PC5 as clock.

mariuslucianand_0-1598948579296.png

Hope this helps,

Marius

[haoxue1027]

Hello，marius.

Thank you for replying.

MotorGD is ok when the clock is configrated PC5.

In addition, When I use an oscilloscope to measure the signals of these two PHA_HSG and the PHA_LSG signal, the signal is shown in the figure below，the deadtime is 15us.

haoxue1027_0-1598961593176.png

But deadtime is set to SPI_Data = 0x81 in the fet pre-driver and set to 100ns in the PWM config block.

I want to know how to decrese the deadtime in the hardware?

best regards

hao

[adriantudor]

Hi @haoxue1027,

In the project description is an error regarding to pins recommended to be used with Rev. E.

The problem with the deadtime is due to incorrect settings of the CS pin. The deadtime of the GD3000 circuit is set with the CS pin set in the TPP Config block. In the SPI block please use other CS pin (any unused pin in the project) or you can not use CS at all. The CS pin set in TPP Config will do the job of the traditional cs pin of SPI block and this will also set the deadtime, but you don't have to set any CS in the SPI block.

I see that you want to set 100ns for deadtime. There will be some inaccuracy of the deadtime PWM outputs. The reason is that the deadtime is dependent on the internal clock of GD3000 ic and the payload of functions who set deadtime at the config step, but anyway it should be much lower than 15us.

Best regards,

Adrian

[haoxue1027]

Hello,Adrian

Thank you very much for your replying.

I used the TPP config ,but the GD3000 did not work.

SO I used the stateflow to implement the sequence.

I will try to set the config as your advices again.

best regards

hao

[mariuslucianand]

Hello @haoxue1027 ,

@adriantudor can help you with the information requested.

Regards,

Marius