Problem with CAN interface when using eTimer

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

Problem with CAN interface when using eTimer

Jump to solution
1,484 Views
rafael_barbosa
Contributor IV

Hello,

I am using the MBD toolbox 3.0.0 and the target micro-controller is MPC5744P. For the problem that I bring here, I am also using the PMIC 35FS6500.

My target is to use the etimer0 as a counter to measure the time between two interruptions and exchange CAN data in parallel.

I can send and receive CAN messages in the attached example when I delete (or comment out) the eTimer related blocks:

pastedImage_1.png

However when I include these eTimer related blocks in the model, the can messages does not works anymore in the target microcontroller.

Why is it happening?

mariuslucianandrei

I am using Canoe 11.0 from vector to exchange messages with the target microcontroller.

Kind Regards, Rafael

0 Kudos
1 Solution
1,379 Views
rafael_barbosa
Contributor IV

Hello constantinrazvan.chivu‌,

After the installation of the new version v3.2.0 this issue was solved.

The clock configuration updating 

pastedImage_1.png

on the new toolbox version fixed the issue.

Kind Regards, Rafael

View solution in original post

0 Kudos
6 Replies
1,379 Views
rafael_barbosa
Contributor IV

Hello constantinrazvan.chivu‌ and mariuslucianandrei‌,

Do you have some updating regarding this topic?

Kind Regards, Rafael

0 Kudos
1,379 Views
constantinrazva
NXP Employee
NXP Employee

Hello rafael.barbosa@chassisbrakes.com ,

Unfortunately due to our current workload it is hard to check this issue, given that it is in a version this old. Can you please check if you replicate this issue in the latest version? If the answer would be yes, we could give you a solution quicker for the v3.2.0 (than the v3.0.0).

Kind regards,

Razvan.

0 Kudos
1,380 Views
rafael_barbosa
Contributor IV

Hello constantinrazvan.chivu‌,

After the installation of the new version v3.2.0 this issue was solved.

The clock configuration updating 

pastedImage_1.png

on the new toolbox version fixed the issue.

Kind Regards, Rafael

0 Kudos
1,379 Views
constantinrazva
NXP Employee
NXP Employee

Hello rafael.barbosa@chassisbrakes.com ,

Thank you for confirming this!

Kind regards,

Razvan.

0 Kudos
1,379 Views
constantinrazva
NXP Employee
NXP Employee

Hello rafael.barbosa@chassisbrakes.com ,

First of all consider installing our latest version of MPC toolbox (https://community.nxp.com/docs/DOC-346265 ) - the support for earlier versions will be limited.

Regarding your issue, I have a few questions: are you using a shared pin between eTimer and CAN? If yes, that would be a problem with our consistency check, as it should have warned you. Next, do you know if the application is still working after adding the eTimer blocks? Do you have a blinking LED or something to let you know? Or if you have put the executable in the debugger and saw the application is running normally.

Kind regards,

Razvan.

0 Kudos
1,379 Views
rafael_barbosa
Contributor IV

Hello constantinrazvan.chivu‌,

Indeed I am considering to update the toolbox for the version 3.2.0. It will be performed as soon as I reach the next project baseline. Thank you for point it out.

No shared pins between the modules:

PMIC pins for SPI: PTC7, PTC6, PTC5 and PTF3

CAN1 pins: PTA15, PTA14, PTD3 and PTD4

eTimer pin: PTC14

After adding the eTimer blocks the application runs. I am using the debugger (PE Micro).

I am intrigued what is going on.

Kind Regards, Rafael

0 Kudos