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 <[email protected]> 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 [email protected].
> For more options, visit https://groups.google.com/d/optout.
--
Jon Smirl
[email protected]
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
