Hi Dear Daniel,
when i follow the course of lesson 9 to cancel the diagnostic ：eTimer and GPO like this
the matlab is abnormal termination . I have added the text of abnormal termination.
Can you help me solve the problems.
Can you share the model you are using and let us know what toolbox version you are using? This way I can see if the issue is within our toolbox in the etimer_mpc574x_config.mex64 or some Simulink issue and open a ticket to MathWorks.
I was referring to what version of our (NXP) toolbox. Can you run the following command in the MATLAB terminal and share the output with us?
I suspect some setup issue and for that I'll have to replicate yours to come up with a solution. Thank you for understanding.
I'm sorry to bother you, is there a solution for this problem?
I run the course again for the demo given by the course , found that system began to collapse until i use the Function-Call subsystem.
There is nothing wrong with using the routines from before lesson 5.
Please check if there's a link between the use of subsystem and system collapse ?
When I use demo"PMSM_ClosedLoop_mpc5744p", system collapse occured.
thank you very much for reproducing the issue.
I have reset the path as you mentioned in error during build （hall sensors）MBD for MPC5744P ,but it seems not work.
There is something wrong with my computer system.
Thanks again for the answer to this question.
Sorry for the late reply - I found that you are using the 3.1.0 version of our release - I answered on the topic you opened on this issue. Briefly - I can not seem to be able to reproduce this issue you are having; please try my recommendations and let us know if that did the trick.
Hi Dear Daniel,
Thanks for the excellent video first. I encountered a @Mahd Khalid. When I try to implement "EventBased_ReadHallSesnor". I get the error "Can not detect the board information" on FreeMaster. Specifically, when I add eTimer0 channel2 into the diagram. I start running into trouble.
In the picture, if I remove the portion circled by the green circle. I am good.
Thanks for your help!
When using the EventBased_ReadHallSesnor file I get the same error "Can not detect the board information" on FreeMaster
I don't get this error in the ReadHallSensor file.
I have already applied the hotfix
Do I need to use CAN instead of UART?
Switching to CAN is only required when your will use the MOTORGD to spin the motor because only then the TX1 will interfere with GD_RST_B pin that is supposed to be hold to 1 during pre-driver initialization and normal operation.
In this case i think there is a different issue. Perhaps and error in the model - like FreeMASTER configuration.
Hope this helps!
i have a question to the eTimer module.
What value gives the STS Register? Is there a possibility to get the counting value of the eTimer like in the toolbox of the s32k144? To get a time stamp or to measure the time between two edges?
The STS output maps over the Channel n Status Register (ETIMER_CHn_STS)
Each flag description can be found in the Reference Manual at page 1092.
To count between 2 edges you can:
#1: use the eTimer_capture block
#2: Or, you can use the STS to trigger some subsystem to count for.
#3: Or, you can use the eTimer ISR trigger output to start a SW counter (as i did in the Lecture 10) assuming there is no HW support for such capture event.
Hope this helps!
Have you tried to use and it and you got wrong results ? or do you have issues to configure the eTimer_config Block compared with the functionalities exposed in the Reference Manual ?