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.

SK-AM62P-LP: How to enable MCAN interface in Android SDK 10.0.1

Part Number: SK-AM62P-LP
Other Parts Discussed in Thread: AM62P

Tool/software:

Hello,

I am using SK-AM62P-LP with Android SDK 10.0.1. I have referred to below link for MCAN however it does not work and I could not find a link for Android automotive SDK.

software-dl.ti.com/.../How_to_test_MCAN_on_AM62x.html


From what I understand from above link, dtbo overlay is needed. I have used tried as below but still I could not find a can0 interface when using ifconfig command. Kindly share steps (or) any document for enabling CAN-FD in android.

  • I tried the steps mentioned in below link but still there was some issue loading m_can.ko. So finally I downgraded to Android 14(SDK 10.0) and removed all protected symbols from the list and now I am able to see can0 & can1 interfaces.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1408639/sk-am62p-lp-enable-can-interface-on-android

    Planning to check physical connections today but I am yet to locate pin diagram and config for starter kit.

    Below link to download design files does not work!
    www.ti.com/.../SPRR487

  • With below link, dtbo issue is resolved and I am able to see 4 can interfaces can0..3.
    software-dl.ti.com/.../Application_Notes_dtbo_support.html

    I sent packets via J1 (3 pin) and it is received in can3.

  • Strange! but it seems there is no vehical hal (or AIDL) listening to CAN interfaces. As far as I see there is no TI implementation of vehicle hal.

    $ ps -ef | grep -i vehicle
    vehicle_network 202    1 0 07:37:43 ?     00:00:00 android.hardware.automotive.vehicle@V1-default-service
    vehicle_network 335    1 0 07:37:46 ?     00:00:00 android.hardware.automotive.can-service
    vehicle_network 379    1 0 07:37:47 ?     00:00:00 android.hardware.automotive.ivn@V1-default-service
    vehicle_network 382    1 0 07:37:47 ?     00:00:00 android.hardware.automotive.remoteaccess@V1-default-service

    am62p:/ # logcat --pid=335
    --------- beginning of main
    01-01 00:00:13.566   335   335 V CanController: Starting up...
    01-01 00:00:13.570   335   335 V CanController: Started successfully!
    ^C
    130|am62p:/ # logcat--pid=202
    --------- beginning of main
    01-01 00:00:10.349   202   202 I VehicleService: Starting thread pool...
    01-01 00:00:10.356   202   202 I FakeVehicleHardware: loading properties from /vendor/etc/automotive/vhalconfig/
    01-01 00:00:10.362   202   202 I FakeVehicleHardware: loading properties from /vendor/etc/automotive/vhalconfig//VendorClusterTestProperties.json
    01-01 00:00:10.365   202   202 I FakeVehicleHardware: loading properties from /vendor/etc/automotive/vhalconfig//TestProperties.json
    01-01 00:00:10.371   202   202 I FakeVehicleHardware: loading properties from /vendor/etc/automotive/vhalconfig//DefaultProperties.json
    01-01 00:00:10.481   202   202 I VehicleService: Registering as service...
    01-01 00:00:10.497   202   202 I VehicleService: Vehicle Service Ready
    01-01 00:00:10.545   202   214 E FakeVehicleHardware: failed to get value, error: value has not been set yet: NOT_AVAILABLE, code: 3
    01-01 00:00:10.547   202   214 E FakeVehicleHardware: failed to get value, error: value has not been set yet: NOT_AVAILABLE, code: 3