Closed PeterBowman closed 2 years ago
I'm not planning on working on this anytime soon, but I'm definitely convinced that we'll drop the proprietary PCAN drivers in favor of SocketCAN: https://github.com/roboticslab-uc3m/yarp-devices/issues/251. So, WONTFIX I guess.
ASIBOT has undergone a major SO upgrade from old Debian 6.0 ("squeeze") to Debian 8.0 ("jessie"), see https://github.com/roboticslab-uc3m/questions-and-answers/issues/20. Everything went fine but the ability to read/write via CAN. Perhaps this is linked to the fact that I installed old HiCO.CAN kernel drivers first, checked that they worked, and then tried the Peak CAN ones. It seems that initial communication succeeds within a CAN-based application (e.g. oneCanBusOneWrapper), but it is not capable of performing CAN transfers afterwards.
I traced this error down to kernel log messages and found an obscure "irq 9: nobody cared (try booting with the "irqpoll" option)". I reached out to PEAK support and obtained no answer. I'm pasting here the same kernel log excerpts shared with support, plus this SO link: https://stackoverflow.com/q/13861282.