Part Number: AM3352
Tool/software: Linux
Why are canconfig and libsocketcan.so.2 missing from the Processor SDK 4.3 rootfs image?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Yes, all of them sequentially for the last three years. Currently, with SDK 4.03 I had to copy canconfig and libsocketcan.so.2.2.1 (and symlink the latter to libsocketcan.so.2) from SDK 4.01.
It appears to me that either some policy had changed and there is some other tool to configure CAN from userspace, or these tools have dropped out of the distribution due to a build bug or something.
I just need a rational explanation for the reason, to know how to address this issue in the future.
Thanks
Hi Schuyler,
Indeed, the ip utility can be used instead of canconfig to configure the CAN interface, and libsocketcan is only used by canconfig.
The CAN operation by our application software relies entirely on socket (AF_CAN) communication, so these two are not necessary.
I believe this approach resolves my issue regardles on whether libsocketcan will remain or not in the filesystem.
Thanks,
Peter