DAVE™ Forum Discussions

[#1]

Hello
I like to try a very simple example with the latest DAVE and the CAN App.
I have instantiated the CAN App which results in the following App hierarchy
CAN_NODE_0
GLOBAL_CAN0
CLOCK_XMC4_0
main() is emtpty. Only DAVE_Init(); is called.
Debugging the example results in a endless loop within xmc_can.c function XMC_CAN_Enable()
It looks like CAN does not have a module clock and is not enabled and the controller stays in the following loop.

while (obj->CLC & CAN_CLC_DISS_Msk)
{
/*Do nothing*/
};

I managed already CAN communication with DAVE4.0 and the XMClib only.
What is missing in the simple CAN App example? Any hint for me?

Regards
Heinz

[#2]

Hi Heinz,

This line of code is to wait until the CAN module is available. If your main is empty, I am not sure if the last piece of code executed.

In each DAVE v4 APP, there is a USAGE section in the APP Help documentation. For the CAN_NODE APP, the example is for CAN communication in loopback mode. Can you try it out to see if this is working on your setup?

Regards,
Daryl