CAN timeout - imx6 Crashes

Technical Support
, ,
1

Hello Team,

Colibri iMX6DL 512MB V1.1A
Carrier board - custom
Linux BSP 2.7

We are using a imx6DL512 Colibri to run a GUI based on GTKmm and a firmware running on K66 .

From the SoM we trigger a run for “selftest” that triggers a complete selftest of all the components and peripherals on the Firmware.
When we continuously do the Selt test, I notice that the imx6 Completely hangs (Application GUI and Terminal of imx6, network ). This happens sporadically after 50 Selftests and gives a CAN timeout.

I would like to know if there are any open issues or fixes made in this regard with this particular BSPs or updated in further versions.

Thanks in advance

Regards,
Viveknath

2

Hi @viveknaththulasi and welcome to the Toradex Community!

We don’t know about a specific hang issue regarding the Bsp 2.7.
Could you share your self-tests scripts?
Could you try to reproduce this issue also on of the Toradex Boards?

Best regards,
Jaski

3

Hi @jaski.tx

Thanks a lot for your response.

Info Update: BSP version I mentioned was wrong.
BSP 2.7.6
Kernel 4.1.44

Okay.
Through the selftest script, we only send a CAN message to the firmware to trigger start of Selftest and the trigger is sent Periodically.

We tried to update the kernel and BSP to the latest ( BSP 5.0 Kernel ) and CAN Timeout error did not occur and we are able to run around 500 Selftest without hanging/ display freeze.

Can you suggest us some commands through which i can enable more debug information ?

Or to access the terminal / Serial connection when the tests stop?

We have already tried monitoring while the tests are running with Jounalctl and dmesg, but would like to have more debug messages before or access when the application and SoM completely hangs?

Best Regards,
Viveknath

4

Hi @viveknaththulasi

So you are using a LTS release.

We tried to update the kernel and BSP to the latest ( BSP 5.0 Kernel ) and CAN Timeout error did not occur and we are able to run around 500 Selftest without hanging/ display freeze.

Would this be an option for you to update to the newest kernel?

Can you suggest us some commands through which I can enable more debug information ?

You can simply set up the log level to a higher value in the kernel config.
Do you have access to the serial console? If yes, then you should be able to see the error there.

Best regards,
Jaski