RTOS: Infinite loop in check the RAMINIT_DONE bit to be set when DCAN Raminit

jaye,

Whats the use case ? The reason the code gets stuck in DCAN_RAM init is because the clocks to the module would not be enabled. We do not claim DCAN tested with vision SDK + Linux. One suggestion is to enable clock to DCAN in the uboot and the try. You can also add enabling clocks as part of the DCAN init code by calling PM lib APIs.

regards
yashwant

Hi Yashwant,

Thanks for reply.

My DCAN driver is operate independently.  The code is migrated from kernel 3.14.49.

When I comment the code check the RAMINIT_DONE bit, the registers of DCAN are readable and writable, not blocked.

I will check the clock, and reply later.

regards

Jaye

Hi,
I enable the DCAN clock domain and the issue is resolved. But when I transmit CAN message, it is bus off. Is there any other need to be changed?

regards,
Jaye