PEAK-System Forum

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 ...

OK, meanwhile I can send and receive messages but ran into other problems that seems driver related.

If I run "pcanfdtst tx <path/to/dev>" it starts sendingrandom messages as expected but at some some the messages are no longer sent over the CAN bus and the transmit buffer fills up to its maximum ...

I found the problem for that issue. I misconfiguered the external bus interface to use 16-Bit wide accesses, now with8-bit wide accesses I can load the kernel module and get a character device for CAN.

But I ran into another issue.To reproduce this I did the following:
- load the kernel module ...

I know this is old but I still have some trouble with the driver.

Since last time I'm using v8.10.2 which fixed some of the issues I had (cross compile and larger range for isa addresses).
I still had to add a patch because I want to use the sja1000 as memory-mapped device but my controller does ...

IPEH-002054

To port an application to a newer embedded Linux system. I have to use your driver as I still need chardev.

During cross compilation I found out that I had to comment out CC=gcc in the make files of driver, lib and test as well as adding export CC=$(CROSS_COMPILE)gcc to the main Makefile. With this ...