No, I mean I use PCAN Explorer to verify but our program always send CAN messages to have expected lengths depending on CAN-ID.
For example in the attached picture the message with CAN-ID 1E0h was received with different data lengths and data. Our program on the linux side does not do this. Also the heartbeat send every second as CAN-ID 760h was received as CAN-ID 761h.
As this does not happen with the older embedded device we are going to replace this is either some hardware issues I have to pinpoint or something in the driver went wrong and a bit got flipped/overwritten at some point.
Issues with Linux driver
Re: Issues with Linux driver
- Attachments
-
- PCan missformed receive.png (82.01 KiB) Viewed 2899 times
-
- Sales & Support
- Posts: 1083
- Joined: Fri 20. Sep 2019, 13:31
Re: Issues with Linux driver
Yes, this looks like a hardware/driver issue.
Furthermore:
If the tx fifo does not seem to be read by the driver it's because it doesn't receive any Tx interrupts from the hw anymore. Often it's because of a bus state that is no more ACTIVE.
The fact that restarting the application resolves this is a strong indication.
You may also wanna check for phyical issue (wrong baudrate, wrong termination, etc)
Best Regards
Marvin
Furthermore:
If the tx fifo does not seem to be read by the driver it's because it doesn't receive any Tx interrupts from the hw anymore. Often it's because of a bus state that is no more ACTIVE.
The fact that restarting the application resolves this is a strong indication.
You may also wanna check for phyical issue (wrong baudrate, wrong termination, etc)
Best Regards
Marvin
---
Marvin Heidemann
PEAK-Support Team
Marvin Heidemann
PEAK-Support Team