Re: Dropped CAN-Frames
Posted: Wed 24. Jun 2015, 09:28
Hello,
Moreover, to summarize and in order to be sure that I understood everything correctly with your 3.19 Kernel: whatever the driver you're using (pcan or peak-usb), your application does not receive all the frames that have been sent. Sometimes, you detect some hw overrun errors, sometimes not. Right?
I'd like to do a last test: could you rebuild the pcan driver but with "make NET=NO". Doing this, you will build a "chardev" pcan driver that won't be compatible with the socket-CAN layer. *BUT* Id' like to do some tests with this pcan and our test applications. Thus,
From this point, you have loaded pcan. Launch the receivetest application please, like this:
Then, start your application that loads the CAN bus. Do what you are used to (aka resizing windows). Stop the transmitting application, then the "receivetest" application (^C). This last one displays the number of frames it has received. Could you please compare this number with the number of CAN frames your (writing) application has written? You could also give us a screen copy of this result...
Regards,
Stéphane.
Hum... I admit I don't understand what your wrote above, about some "asm stuff" that may have changed. I would be very astonished if this prevented from building our pcan driver. We first have to check this against this new Kernel asap.Unfortunately, they changed the asm stuff in the recent 4.1 kernel, so I was only able to test this on my Ubuntu running the 3.19.
Moreover, to summarize and in order to be sure that I understood everything correctly with your 3.19 Kernel: whatever the driver you're using (pcan or peak-usb), your application does not receive all the frames that have been sent. Sometimes, you detect some hw overrun errors, sometimes not. Right?
I'd like to do a last test: could you rebuild the pcan driver but with "make NET=NO". Doing this, you will build a "chardev" pcan driver that won't be compatible with the socket-CAN layer. *BUT* Id' like to do some tests with this pcan and our test applications. Thus,
Code: Select all
% cd peak-linux-driver-x.y
% make -C driver NET=NO
% make -C lib
% make -C test
% sudo rmmod pcan
% sudo insmod driver/pcan.ko
Code: Select all
% test/receivetest -f=/dev/pcan32 -b=0x11c
Regards,
Stéphane.