topic MPC5604B interrupts in University Programs

MPC5604B interrupts

catalinvasile — Thu, 13 Feb 2014 14:20:53 GMT

It's been some time since the 2 threads I've found here, related to MPC5604B interrupts, have been issued.

Has anyone successfully used interrupts one this MCU ? If so, how? Can you provide some sample code?

Re: MPC5604B interrupts

FlavioStiffan — Tue, 20 May 2014 12:55:35 GMT

michaelgoudey would you have any clue about this one?

Thanks

Re: MPC5604B interrupts

FlavioStiffan — Tue, 20 May 2014 13:19:59 GMT

murraystewart-b04629 maybe you have a clue about this.

Thanks

Re: MPC5604B interrupts

michaelgoudey — Tue, 20 May 2014 21:51:56 GMT

Flavio,

The original question is pretty old so I wonder if Catalin has already found sample code for interrupts on MPC5604B. If the topic is still open, though, I'd probably first look at the Qorivva cookbook reference code. There are both HW and SW vector mode examples included with the document, also known as AN2865. Here are the links to the PDF and the ZIP file with examples.

http://cache.freescale.com/files/32bit/doc/app_note/AN2865.pdf

http://www.freescale.com/webapp/sps/download/license.jsp?colCode=AN2865SW&location=null&Parent_nodeId=&Parent_pageType=

If the format of this code is different than desired then there are examples included with CodeWarrior for MCU. For example, CW MCU v10.5 includes examples for MPC5604P where the interrupt controller functions in the same fashion as MPC5604B. Look under the following path within CodeWarrior:

<CodeWarrior>/MCU/CodeWarrior_Examples/Qorivva_Examples

MPC5604P_INTC-HW-VLE

MPC5604P_INTC-SW-VLE

There are also examples included with the StarterTRAK development kit, such as TRK-MPC5606B, which may be suitable. I haven't looked over those to confirm interrupts are used in each kit's example code.

Regards,

Michael Goudey

Re: MPC5604B interrupts

catalinvasilef — Wed, 14 Jan 2015 12:19:52 GMT

The cookbook and the samples were the problem. The MPC5604B came in 2 revisions, and it seems that the hardware addresses on the bus have some differences.

The car shipped with a revision, but with code support for another, as in the used header with define constants for I/Os was for the other revision.

So for some I/Os worked perfectly since they were mapped the same, but other, like the interrupts registers, were mapped at a different addresses.

I accidentally found out when someone provided other example code for using other I/Os by using interrupts.