Bug#864562: No ethernet link on Olimex A20-Olinuxino Micro Rev. J, possibly PHY driver problem
On Fri, Jul 28, 2017 at 10:39:01PM +0200, Jean-Louis MOUNIER wrote:
> Hello Karsten,
>
> thank you for your investigations and sorry for the delay : I have many
> lives...
>
> here is the test result :
>
> U-Boot 2016.11+dfsg1-4 (Mar 27 2017 - 18:39:51 +0000) Allwinner Technology
>
> CPU: Allwinner A20 (SUN7I)
> Model: Olimex A20-Olinuxino Micro
> I2C: ready
> DRAM: 1 GiB
> MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
> *** Warning - bad CRC, using default environment
>
> Setting up a 1024x768 vga console (overscan 0x0)
> In: serial
> Out: vga
> Err: vga
> SCSI: SATA link 0 timeout.
> AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode
> flags: ncq stag pm led clo only pmp pio slum part ccc apst
> Net: eth0: ethernet@01c50000
> starting USB...
> USB0: USB EHCI 1.00
> USB1: USB OHCI 1.0
> USB2: USB EHCI 1.00
> USB3: USB OHCI 1.0
> scanning bus 0 for devices... 1 USB Device(s) found
> scanning bus 2 for devices... 1 USB Device(s) found
> Hit any key to stop autoboot: 0
> =>
> =>
> => gpio clear PA17
> gpio: pin PA17 (gpio 17) value is 0
> => dhcp
> Speed: 100, full duplex
> BOOTP broadcast 1
> BOOTP broadcast 2
> BOOTP broadcast 3
> DHCP client bound to address 192.168.11.80 (1028 ms)
> *** Warning: no boot file name; using 'C0A80B50.img'
> Using ethernet@01c50000 device
> TFTP from server 0.0.0.0; our IP address is 192.168.11.80; sending through
> gateway 192.168.11.254
> Filename 'C0A80B50.img'.
> Load address: 0x42000000
> Loading: *
> TFTP error: 'File not found' (1)
> Not retrying...
> =>
>
> As you can see, the gpio command make a change ! For information, the
> 192.168.11.80 network address and the gateway address are valid for my home
> network. The DHCP request did work fine !
Good, so we are on the right track. Could you also try booting
Linux directly after running the "gpio clear PA17" in u-boot and
check whether the on-board ethernet works in this case? To boot
linux from the u-boot command prompt, just enter the command
"run bootcmd".
This would show us whether the kernel explicitly sets PA17
somewhere or whether it just uses the state in which u-boot has
left the GPIO pin. If the latter, modifying u-boot should probably
be sufficient, otherwise we would need to patch both u-boot and
the kernel.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: