SK-AM62P-LP: AM62P Android AOSP — CAN interface not working

Sreerag E

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

Hi Team,

I am working on the TI AM62P EVK using the TI Android 16 SDK.

After enabling main_mcan1 in the device tree (DTS), the interface appears successfully as can0. I can change its bitrate and bring the interface UP using standard ip link commands without errors.

However, I am completely unable to send or receive data. When running the built-in Android Automotive CAN HAL utilities (canhalsend / canhaldump), it fails with the following error:

Bus can0 is not available

Could you please provide the exact steps, configurations, or patch required to resolve this issue in the Android 16 SDK environment so that the Automotive CAN HAL can recognize and communicate over can0?

Thank you!

console:/ # ip link set can0 down                                              
console:/ # ip link set can0 type can bitrate 100000                           
console:/ # ip link set can0 up                                                
console:/ # console:/ # ifconfig can0                                                  
can0      Link encap:UNSPEC    Driver m_can_platform
          UP RUNNING NOARP  MTU:16  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:10 
          RX bytes:0 TX bytes:0 
          Interrupt:179  
console:/ # 
console:/ # canhaldump can0                                                    
Bus can0 is not available
console:/ # 
console:/ # canhalsend can0 123#DEADBEEF                                   
Bus can0 is not available

1 day ago

0 Vishal Mahaveer 1 day ago

TI__Mastermind 33970 points

Hi Sreerag,

The TI SDK only provides the base build support to get to the Automotive UI of AAOS configuration.
We don't enable additional servives/features needed for other HALs of AAOS.

The CAN HAL service is not part of the SDK and may be the reason for this error.

Regards,
Vishal

0 Vishal Mahaveer 1 day ago in reply to Vishal Mahaveer

TI__Mastermind 33970 points

Hi Sreerag,

I can suggest some theoretical changes to try, but this is out of scope of what the Android SDK supports.
If the theoretical changes don't work, I don't have any other suggestions for this topic.

/cfs-file/__key/communityserver-discussions-components-files/791/0001_2D00_Experimental_2D00_CAN_2D00_changes.patch

Regards,
Vishal

0 Sreerag E 18 hours ago in reply to Vishal Mahaveer

Prodigy 40 points

Hi Vishal,

Thank you for the update for the CAN HAL. I will apply these changes to my setup and test the HAL layer.

In parallel, I manually added the native SocketCAN utility cansend directly to the system to isolate the issue. When executing it on the board, the network socket creation fails with a protocol registration error:

console:/ # cansend can0 123#DEADBEEF
socket: Address family not supported by protocol

Since this protocol layer error blocks both cansend and the CAN HAL from working, is there a standard solution, configuration flag, or an additional kernel patch required to enable the SocketCAN architecture (AF_CAN) on this platform?

Regards,

Sreerag

0 Vishal Mahaveer 16 hours ago in reply to Sreerag E

TI__Mastermind 33970 points

Hi Sreerag,

Could you open a separate ticket for CAN specific Kernel question, so a CAN expert can answer that question.

Regards,
Vishal

Processors

Processors forum

SK-AM62P-LP: AM62P Android AOSP — CAN interface not working