WLAN: known issues and how to help - uptime test - more results
Philip Rhoades
phil at pricom.com.au
Tue Feb 10 02:38:24 CET 2009
Werner,
Werner Almesberger wrote:
> Philip Rhoades wrote:
>> Still using:
>>
>> wlan-trial-20090206.jffs2
>
> If you could give your regular rootfs a try with my kernel, that
> would be great. What I'm interested in now is to confirm if the
> communication breakdown is caused by the assertion.
OK, will do.
> For debugging why my rootfs doesn't work for you, could you
> please send the output of printenv from u-boot ?
boot_menu_timeout=60
bootargs_base=rootfstype=jffs2 root=/dev/mtdblock6
console=ttySAC2,115200 console=tty0 loglevel=4 regular_boot
bootdelay=5
menu_1=Boot from microSD (FAT+ext2): setenv bootargs ${bootargs_base}
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
menu_4=Set console to USB: setenv stdin usbtty; setenv stdout usbtty;
setenv stderr usbtty
menu_5=Set console to serial: setenv stdin serial; setenv stdout serial;
setenv stderr serial
menu_6=Reboot: reset
menu_8=Power off: neo1973 power-off
sd_image_name=uImage.bin
usbtty=cdc_acm
mtdids=nor0=physmap-flash,nand0=neo1973-nand
pcb_rev=0x000
pcf50633_int1=0x80
pcf50633_int2=0x02
mtdparts=mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(u-boot),0x00040000(u-boot_env),0x00800000(kernel),0x000a0000(splash),0x00040000(factory),0x0f6a0000(rootfs)
partition=nor0,0
mtddevnum=0
mtddevname=nor
stdin=usbtty
stdout=usbtty
stderr=usbtty
bootcmd=setenv bootargs ${bootargs_base} ${mtdparts}; nand read.e
0x32000000 kernel 0x300000; bootm 0x32000000
Environment size: 1093/262140 bytes
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil at pricom.com.au
More information about the devel
mailing list