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.

Linux/AM3352: CAN support in latest SDK

Part Number: AM3352

Tool/software: Linux

Why are canconfig and libsocketcan.so.2 missing from the Processor SDK 4.3 rootfs image?

  • Hi,

    I am away from the office at the moment so I can't see what may be the problem. Were you using a previous Linux SDK? If so which version?

    Best Regards,
    Schuyler
  • 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,

    Actually these components look to have been missing since the 04.02.00.09 release. I will research with the SDK build team to find out the reason.

    Best Regards,
    Schuyler
  • Hi Schuyler,

    I am looking forward to a reliable information about the availability of these components in future SDK releases.

    Thanks,

    Peter

  • Hi Peter,
    It looks like canconfig and libsocketcan were dropped from the builds when switching CAN utils packages to enable support for CAN-FD on another device. The loss of canconfig was not detected as an issue due to the ip command is used to configure the interface in the SDK testing scripts. Since the ip command can be used to configure the interface the canconfig command will be probably be deprecated, we will need to update the online documentation to reflect this.

    I am still discussing with the file system maintainer about libsocketcan if this can be added back in. This lib was most likely lost when canconfig was removed as it was probably the only dependency for the library.

    Best Regards,
    Schuyler
  • 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