Thanks Jon, I have cleared my sdcard and setup tftp/nfs etc.

The exercise has shown I have a uboot/hardware problem in that the network
is not working

If I build uboot using "cubieboard2" .... I don't even get a "link up"

If I build uboot using "A20-OLinuXino_MICRO"  ... I at least get link
up...but I can't ping not can I tftp

Then I tried setting "cubietruck"
BR2_TARGET_UBOOT_BOARDNAME="Cubietruck"


and bingo.....network started working and I can at least load my kernel and
dtb blob.....unfortunately I don't see anything after "Starting kernel.... "
 but at least I know which board to select when compiling uboot.





U-Boot 2014.04 (Jun 24 2014 - 23:03:23) Allwinner Technology

CPU:   Allwinner A20 (SUN7I)
Board: Cubietruck
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.1c50000
Hit any key to stop autoboot:  0
sun7i# tftp 0x46000000 uImage
Speed: 100, full duplex
Using dwmac.1c50000 device
TFTP from server 192.100.1.10; our IP address is 192.100.1.19
Filename 'uImage'.
Load address: 0x46000000
Loading: #################################################################
         #################################################################
         ################################################
         3.7 MiB/s
done
Bytes transferred = 2607919 (27cb2f hex)
sun7i# tftp 0x49000000 sun7i-a20-cubietruck.dtb
Speed: 100, full duplex
Using dwmac.1c50000 device
TFTP from server 192.100.1.10; our IP address is 192.100.1.19
Filename 'sun7i-a20-cubietruck.dtb'.
Load address: 0x49000000
Loading: ##
         2.9 MiB/s
done
Bytes transferred = 21639 (5487 hex)
sun7i# bootm 0x46000000 - 0x49000000
## Booting kernel from Legacy Image at 46000000 ...
   Image Name:   Linux-3.16.0-rc2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2607855 Bytes = 2.5 MiB
   Load Address: 46000000
   Entry Point:  46000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 49000000
   Booting using the fdt blob at 0x49000000
   XIP Kernel Image ... OK
   Using Device Tree in place at 49000000, end 49008486

Starting kernel ...










On Mon, Jun 23, 2014 at 9:58 PM, jonsm...@gmail.com <jonsm...@gmail.com>
wrote:

> Enable early printk in the kernel debug section on menu config. Then
> add it to the command line from uboot.
>
> Kernel command line: console=ttyS0,115200 loglevel=9 earlyprintk
> root=/dev/nfs ip=192.168.1.51:192.168.1.254:192.168.1.254:255
> .255.255.0:truck::off
> nfsroot=192.168.1.50:/export/work/root rootwait
>
> For development I use tftp in uboot to load the kernel and then nfs
> mount the root file system. SD in target only has uboot on it.
>
>
> sun7i# printenv
> baudrate=115200
> boot_ram=saved_stdout=$stdout;setenv stdout nc;if iminfo 0x41000000;
> then true; setenv stdout $saved_stdout; source 0x41000000;else setenv
> stdout $saved_stdout;fi
> bootargs=console=ttyS0,115200 loglevel=9 earlyprintk root=/dev/nfs
> ip=dhcp root=192.168.1.50:/work2/root
> bootdelay=2
> bootenv=uEnv.txt
> bootm_size=0x10000000
> bootscr=boot.scr
> ce=run nbe; run nbb; run nbr
> ch=run nbl; run nbb; run nbr
> console=ttyS0,115200
> device=mmc
> ethact=dwmac.1c50000
> ethaddr=70:71:bc:b8:ab:ee
> fdt_high=ffffffff
> fileaddr=49000000
> filesize=5e1a
> ipaddr=192.168.1.51
> kernel=uImage
> loadbootenv=fatload $device $partition $scriptaddr ${bootenv} ||
> ext2load $device $partition $scriptaddr boot/${bootenv} || ext2load
> $device $partition $scriptaddr ${bootenv}
> loadbootscr=fatload $device $partition $scriptaddr ${bootscr} ||
> ext2load $device $partition $scriptaddr boot/${bootscr} ||ext2load
> $device $partition $scriptaddr ${bootscr}
> loadkernel=if bootpath=/boot/ && ext2load $device $partition
> 0x43000000 ${bootpath}${script} && ext2load $device $partition
> 0x48000000 ${bootpath}${kernel};then true; elif bootpath=/ && fatload
> $device $partition 0x43000000 ${script} && fatload $device $partition
> 0x48000000 ${kernel};then true; elif bootpath=/ && ext2load $device
> $partition 0x43000000 ${bootpath}${script} && ext2load $device
> $partition 0x48000000 ${bootpath}${kernel};then true; else false;fi
> loglevel=8
> nbb=setenv bootargs console=ttyS0,115200 loglevel=9 earlyprintk
> root=/dev/nfs ip=192.168.1.51:192.168.1.254:192.168.1.254:255
> .255.255.0:truck::off
> nfsroot=192.168.1.50:/export/work/root rootwait
> nbe=tftp 0x46000000 /var/lib/tftpboot/eImage && tftp 0x49000000
> /var/lib/tftpboot/e.dtb && setenv fdt_high ffffffff
> nbl=tftp 0x46000000 /var/lib/tftpboot/uImage && tftp 0x49000000
> /var/lib/tftpboot/ct.dtb && setenv fdt_high ffffffff
> nbr=bootm 0x46000000 - 0x49000000
> panicarg=panic=10
> partition=0:1
> script=script.bin
> scriptaddr=0x44000000
> serverip=192.168.1.50
> setargs=if test -z \\"$root\\"; then if test \\"$bootpath\\" =
> "/boot/"; then root="/dev/mmcblk0p1 rootwait"; else
> root="/dev/mmcblk0p2 rootwait"; fi; fi; setenv bootargs
> console=${console} root=${root} loglevel=${loglevel} ${panicarg}
> ${extraargs}
> stderr=serial
> stdin=serial
> stdout=serial
>
>
>
> On Mon, Jun 23, 2014 at 4:28 PM, bruce bushby <bruce.bus...@gmail.com>
> wrote:
> > Hi Axel
> >
> > How did you fix your console problem?  I have the same issue:
> >
> > This config says starting kernel....and then nothing
> > setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
> panic=10
> > ${extra}
> > fatload mmc 0 0x46000000 uImage
> > fatload mmc 0 0x49000000 sun7i-a20-olinuxino-micro.dtb
> > env set fdt_high ffffffff
> > bootm 0x46000000 - 0x49000000
> >
> >
> > This config boots and I can login:
> > setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait
> panic=10
> > ${extra}
> > fatload mmc 0 0x43000000 script.bin
> > fatload mmc 0 0x48000000 uImage
> > bootm 0x48000000
> >
> >
> > But I feel that I should be using the dtb file rather then script.bin ?
> ....
> > bit confused
> >
> > My kernel is built with:
> > [bruce@core buildroot]$ grep tty configs/olimex_a20-som_defconfig
> > BR2_TARGET_GENERIC_GETTY_PORT="ttyS0"
> > [bruce@core buildroot]$
> >
> >
> >
> > Any tips would be much appreciated!
> >
> > Thanks
> >
> >
> >
> >
> > On Sunday, 17 November 2013 01:24:59 UTC, Axel Theilmann wrote:
> >>
> >>
> >> moin,
> >>
> >> > i'm trying to boot the mainline kernel on an A20-olinuxino micro,
> >> > following
> >>
> >> nevermind..it's working now. someone on #linux-sunxi was able to help
> me.
> >>
> >> it was just a console problem, the kernel seems to work fine...
> >>
> >>
> >> tty, axel
> >>
> >>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "linux-sunxi" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to linux-sunxi+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> Jon Smirl
> jonsm...@gmail.com
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "linux-sunxi" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/linux-sunxi/5mQHoyAjvJE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> linux-sunxi+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to