Re: Testing CAN on Allwinner A20 / Banana Pi

[Patrick Menschel <menschel.p@posteo.de>]

[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]

Thanks for the advice,

in my case the sunxi_defconfig already had the driver selected, so no
change necessary.
Apparently only the device tree information is missing in the mainline
kernel. If that were to change, it would work out of the box if a
transceiver is added.

At the moment I can send and recv from both C and Python3.

Regards,
Patrick


Am 21.03.2016 um 10:27 schrieb gianluca:
> On 03/19/2016 01:33 PM, Marc Kleine-Budde wrote:
>>>
>>> Compiling to dtb and back to dts now resolves to
>>>
>>>         can@01c2bc00 {
>>>             compatible = "allwinner,sun4i-a10-can";
>>>             reg = <0x1c2bc00 0x400>;
>>>             interrupts = <0x0 0x1a 0x4>;
>>>             clocks = <0x31 0x4>;
>>>             status = "okay";
>>>             pinctrl-names = "default";
>>>             pinctrl-0 = <0x32>;
>>>         };
>>>
>>> That does look plausible from my perspective.
>>>
>>> Unfortunately I'm still missing /dev/can0 and have no clue why.
>>
>> CAN devices are network devices and will not show up in "/dev". Have a
>> look at:
>>
>>      ifconfig -a
>>
>>> If your Bpi works with legacy u-boot, I would try that next.
> 
> It is not enough having the can-core controller in dtsi only. The kernel
> has to be compiled with a network/can/socketcan enabled and the specific
> SoC can controller enabled in the same subarch structure.
> i.e.: you will need to have:
> 
> in sunxi_defconfig:
> 
> CONFIG_CAN=y
> CONFIG_CAN_SUN4I=y
> 
> Just my $0.2...
> 
> Hope this helps!


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3709 bytes --]