[Arm-netbook] eoma68-a20 ethernet testing

[luke.leighton]

On Wed, Sep 4, 2013 at 10:56 PM, joem <joem at martindale-electric.co.uk> wrote:
>
> Actually Mr Luke, you have a bug in your documentation.

 yippeee.  it's a wiki - could you please edit and correct it?

> Where it says
>   ./usb-boot ../u-boot-sunxi/spl/u-boot-spl.bin ../u-boot/u-boot.bin
>
> it should read
>   ./usb-boot ../u-boot-sunxi/spl/u-boot-spl.bin ../u-boot-sunxi/u-boot.bin

 ahhh that'll do it.  errr.... actually i find that doesn't work
either, _but_ hey...


>
>
> After correcting for that, I get:
>
>   # That is the EOMA. To check it is working, do this:
>
>   cd sunxi-tools
>   sudo ./usb-boot ../u-boot-sunxi/spl/u-boot-spl.bin ../u-boot-sunxi/u-boot.bin
>
>   # ordinarily sudo is not needed in above line, it seems USB on Ubuntu 12.04 is broken.

 ... it's not - you need to be in the right group and/or set up udev
rules to get an account added _to_ that group...

libusb is basically direct access from userspace to USB devices, and
as such needs to be restricted, otherwise the average user could try
to cat a file directly to a USB hard drive for example and corrupt it,
cause it to crash etc. etc.

>   # note ./usb-boot takes two parameters, both of which were previously compiled
>   # and sitting in u-boot-sunxi directory.
>   # The messages I get when ./usb-boot runs are these:
>
> fel write 0x2000 ../u-boot-sunxi/spl/u-boot-spl.bin
> fel exe 0x2000
> fel write 0x4a000000 ../u-boot-sunxi/u-boot.bin
> fel write 0x41000000 ./bin/ramboot.scr
> fel exe 0x4a000000
>
>   # and on the minicom window, I get these messages:
>
> U-Boot SPL 2013.10-rc1-08247-gd787d30 (Sep 04 2013 - 10:03:46)
> Board: EOMA68_A20_FEL
> DRAM: 1024 MiB
> CPU: 960000000Hz, AXI/AHB/APB: 3/2/2
>
> U-Boot 2013.10-rc1-08247-gd787d30 (Sep 04 2013 - 10:03:46) Allwinner Technology
>
> CPU:   Allwinner A20 (SUN7I)
> Board: EOMA68_A20_FEL
> I2C:   ready
> DRAM:  1 GiB
> MMC:   SUNXI SD/MMC: 0
> Card did not respond to voltage select!
> MMC init failed
> Using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Net:   emac
> Hit any key to stop autoboot:  0
> ## Executing script at 41000000
>
> ## Checking Image at 4c000000 ...
> Unknown image format!
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> Card did not respond to voltage select!
> ** Bad device mmc 0 **
> sun7i#
>
>
> ----
>
> Is that about right to do next steps?

 yyup.  at the point where "Net: emac" was displayed, you should have
*immediately* got a link light.  if not, check the hardware.  repeat
until success.  _then_ run those setenv commands and the ping.

l.