Linux 6.5 Mainline kernel driver (NetDev): PCAN-USB Pro FD lost channel-id assignment after reconnect

[M.Heidemann]

Hello Tom,

The test machine has the following specs:

- mainboard: Asus WS X299
- x299 chipset
- intel i5 7640X
- ASM (AsMedia) USB 3.0 controllers

i have an idea as to what is going on, can you share the serial number of your PCAN-USB FD with us?

I think, as you had the same results on a different system, that this might be down to firmware or
a fault with the device itself. Let us investigate.

Best Regards

Marvin

[TomyYamy]

Hi Marvin,

I have tried an additional trial with Windows and PCAN-View. Please see attached screen shot.

I can set ID as well as Ubuntu trial. But the other side is fixed with 0-FFFFFFFFh.

It is new for me. Perhaps does it mean PCAN-USB Pro FD can apply ID only one side channel and anther channel is fixed FFFFFFFF even though it is settable in Ubuntu?

Thanks,
Tom

[M.Heidemann]

Hello Tomy,

I appreciate the effort to this on Windows, however
this handled differently in Linux.

With the Linux driver each individual channel can have its own id,
on Windows this is not implemented. Windows only uses a general
device id, so this is not the reason for what you were seeing.

Your firmware is also up to date, so that excludes another possibility.

I'd check another PC entirely, with any recent Linux.

If that goes nowhere, it would seem that the device itself is having an issue.

[rsbtech]

@marvin: This user's experience has been my experience also. I'm on linux (raspberry pi 4b). What I found was that:
1. I am able to rename both channels on the previous firmware version of the PCAN-USB Pro FD (serial number of device is 17xxx).
2. But not on the latest, i can only rename the first bus. The second bus always shows up as 0xFFFFFFFF. (serial number of device is 26xxx).
3. My recommendation for the future would be to re-enable this feature where the EEPROM for the second bus can also be flashed.
4. That said, it's worth adding here that the udev code with the /bin/peak_usb_device_namer works, as long as the EEPROM value can be set of course.
5. Also, for implementing a workaround, I wanted to use the device ID. But this is not possible as this as the PCAN-USB Pro FD does not have a device ID that is unique to it in Linux. So all PCAN-USB Pro FD devices are indistinguishable from each other to Linux.

I should add here that one of your coworkers (when I emailed Peak in April) has recommended me to install the driver of PCAN-USB Pro FD on a raspberry pi as that has a tool called pcan-settings tool that can also be used for setting the EEPROM value. I believe this was the old method used before ethtool (speaking from memory when I was experimenting with this 5 months ago so could be wrong on this, I've not worked on it since but I need it to work now haha). I've not tried this method yet, and if it's not too painful I might try it soon. Overall, I love Peak tools but using udev to set the mapping has been a painful task with incomplete result. I'll post more updates here in the next few days. Thank you for your support.

[M.Heidemann]

Hello Tom,

Can you provide us with the following:

Output for:

Code: Select all

dmesg

Code: Select all

uname -a

?


Thank you!

Best Regards

Marvin