Potential firmware / driver issue #175
Comments
|
What's the output of |
|
Not sure what you mean by "configuring your CAN" interface.
Duh ... There is a TX error with 1 for transmitted (bottom right in the "table") ? |
I see the same error value of "1" for my candlelight adapter, as well as for another USB CAN adapter. Don't know where this comes from. However the rest looks fine. Now configure |
What do you mean exactly ? Right now each of them are (in the garage) connected to one separate Emerson R48-3000e Rectifier. Do you want me to connect the can0 and can1 adapter between themselves in a "loop" (can0 CAN_H goes to can1 CAN_H, can0 CAN_L goes to can1 CAN_L) ? I don't think I'll have time to go into the garage and reassembly everything before the weekend :(. |
OK
Exactly make a small CAN bus with |
|
Who knows what version of candlelight those are running - we added the git commit hash to the iConfiguration string in april 2021. I don't know if the other forks followed suit... |
|
Not sure if that helps, but I got three status LED indicators and they all seem to be constantly ON.
But yes, I could try with a more recent version. It's just very weird that it worked in the beginning (possibly with an older version of Debian / Linux Kernel). |
|
Looks like these. Can you see which STM32 these are using? |
|
This was the listing: https://www.aliexpress.com/item/1005004972158302.html?spm=a2g0o.order_list.order_list_main.5.38c71802xenhek I tried asking the seller if they are using STM32 and which one if so ... |
|
Have a look at the µC, it's the chip with the legs on all 4 sides. |
|
Yeah I thought so. The square one LFQP or something like that ... |
|
Well the dfu-util output at least seems to match what an stm32 would show. just try |
|
Not sure, the second -U fails, and now there are 2 devices (well total is 3, but I only tried to update 1 - I have 2 CanAble Pro plugged in): |
|
Disconnect the other and try |
|
Well then I have to try during the weekend. It's in the garage so ... |
|
Should I just reboot now to "free it" for now ? |
ah, well you can play with dfu-util options to help it select the proper interface by device path (not sure why your attempt with |
|
The attempt with -S worked the first time. But then 2 devices got created with the same FFFFFFFEFFFF serial number: Whereas the untouched CanAble Pro adapter still has its previous serial number: |
|
yes, the first time causes the stm32 to enter native DFU mode which exposes two interfaces, alt=0 and alt=1, and I see now they have the same FFFEFFF serial which doesn't help to disambiguate which one to use. You want the "internal flash" to grab the firmware. |
|
OK quick try in the garage today. Removed power supply (AC adapter) from USB Hub. Now it's passive. Unplugged & replugged in the CanAble Pro Adapter. Launched my script. Set the rectifier to 56V. Works like a charm. So I don't know if the Powered USB hub is the root cause of the problem, but NO amount of rebooting the Raspberry Pi would fix the issue. |
I'm quite sure the boards use STM32F072C8T6 µCs. |
I'm using some CanAble Pro adapters I bought off AliExpress and I could communicate with the devices connected to them initially.
Since then, not sure if related to upgrading Debian Bullseye to Debian Bookworm, Firmware BUG / incompatibility, or what else, my program using python-can says it sent the CAN message correctly, yet nothing appears in
ifconfigand the device does not react at all.candumpdoesn't log anything either.Is there a way to check the current version of the firmware ? I'm not even sure these are STM32 microcontroller based ...
dfu-util
dmesg can
dmesg usb
ifconfig shows packet counter stuck at zero
lsusb
It's like the CAN device is properly recognized but it's doing absolutely nothing ...
The text was updated successfully, but these errors were encountered: