Openwrt booting problems
littlebilly
downloaded from
http://sites.google.com/site/bifferboard/Home/factory-firmware/openwrt-rdc-jffs2-64k-bifferboard.img?attredirects=0&d=1
everything is running well, BB boots like this!
00100000 loaded from
flash.
Booting Linux
with:
Linux version 2.6.32.20 (biff@fonzi) (gcc version 4.1.2) #5 Mon Feb 7
23:21:40 1
KERNEL supported cpus:
......
When flashing my BB with firmware build as described in Readme on
https://github.com/bifferos/openwrt
I get
BIFFBOOT>
boot
Booting...
00100000 loaded from
flash.
Booting Linux with:
and nothing more (stopped)
What I did do in detail was:
Download with
git clone git://github.com/bifferos/openwrt.git
$ cp bifferboard_example_config .config
$ make package/symlinks
$ make
make was running without any problems, than I flashed the firmware
found in
bin/rdc/openwrt-rdc-jffs2-64k-bifferboard.img
to the board.
the booting settings are ok. ( like those when flashing the original
Factory firmware)
Whats going wrong?
Billy
littlebilly
I got it running!
While the
original Factory Firmware prebuild is running with
cmndline: empty
eg
* BIFFBOOT>
showconfig
Configuration
values:
bootsource: on-board
flash
console:
enabled
nic:
enabled
boottype: Linux 2.6 parameter
block
loadaddress:
0x00400000
cmndline:
kernelmax: 0x0010
The BB with firmware build as described in Readme on
https://github.com/bifferos/openwrt
needs cmndline: cmndline: console=uart,io,0x3f8
rootfstype=squashfs,jffs2
eg
BIFFBOOT>
showconfig
Configuration
values:
bootsource: on-board
flash
console:
enabled
nic:
enabled
boottype: Linux 2.6 parameter
block
loadaddress:
0x00400000
cmndline: console=uart,io,0x3f8
rootfstype=squashfs,jffs2
kernelmax: 0x0010
Might be interesting for other newbees too.
My problem was, that in some documents it's mentioned that cmndline
should be blank for openwrt.
I guess the experts now why?
Nevertheless I learned a lot.
Billy
nicolas le falher
If you compile a trunk version for your bifferboard, cmdline is embedded.
You can see it with "make kernel_menuconfig" :
Processor type and features --->
[*] Built-in kernel command line
(console=uart,io,0x3f8 rootfstype=squashfs,jffs2) Built-in kernel command string
Here is a trunk version, on git version, option is not selected.
2011/4/10 littlebilly <vultur...@googlemail.com>:
> --
> To unsubscribe send email to bifferboard...@googlegroups.com
>
--
Nicolas Le Falher.
G. Geyer mobil
biff...@yahoo.co.uk
On Apr 10, 7:17 pm, nicolas le falher <n.lefal...@gmail.com> wrote:
> Cause on git, cmdline is not embedded, so bifboot pass it to kernel :).
If one single RDC-based device has a broken bootloader, then all RDC
ports are forced to embed the kernel command-line, even if the device
has a 'working' bootloader. I suspect with some work you could hack
the build system to support different command-line setup for different
RDC ports, but it would take someone cleverer than me to figure it
out, and there is probably no way the developers would accept my
patch.
This was one of the many reasons for creating the Git fork.
regards,
Biff.
Andrew Scheller
It's all documented (kind of) on the wiki...
http://sites.google.com/site/bifferboard/Home/openwrt-git
Lurch
Antonio Cansado
I've just started playing with my BB. It came preloaded with Openwrt
working ok.
Now I'm trying to reflash it with Openwrt from the GIT repo, though
with no luck.
I have followed instructions from Git's README -> copied the example
config (cp bifferboard_example_config .config), and then flashed the
device.
When I bootup BB, it gets stuck in the "Booting Linux with: ".
Using the Serial cable I went into biffboot and checked that the
cmdline is empty.
After seeing this thread, I recompiled the kernel adding:
[*] Built-in kernel command line
(console=uart,io,0x3f8 rootfstype=squashfs,jffs2) Built-in kernel
command string
is empty and BB fails to boot.
The BB is still working if I flash it with the factory firmware from
https://sites.google.com/site/bifferboard/Home/factory-firmware. This
firmware also reports cmdline as empty in showconfig, though BB boots
ok.
What am I missing? Any help will be greatly appreciated.
Regards,
Antonio
Andrew Scheller
> with no luck.
> I have followed instructions from Git's README -> copied the example
> config (cp bifferboard_example_config .config), and then flashed the
> device.
I assume you ran "make" as well? ;)
> After seeing this thread, I recompiled the kernel adding:
> Processor type and features --->
> [*] Built-in kernel command line
> (console=uart,io,0x3f8 rootfstype=squashfs,jffs2) Built-in kernel
> command string
Hmmm, dunno why that didn't work.
> Though when I reflash it again, showconfig still signals that cmdline
> is empty and BB fails to boot.
Biffboot runs *before* the kernel, and so the cmdline that showconfig
displays has no knowledge of what's been compiled into the kernel.
To check what cmdline the kernel actually used, after Linux has booted type:
cat /proc/cmdline
> The BB is still working if I flash it with the factory firmware from
> https://sites.google.com/site/bifferboard/Home/factory-firmware. This
> firmware also reports cmdline as empty in showconfig, though BB boots
> ok.
>
> What am I missing? Any help will be greatly appreciated.
I think the confusion is because
http://sites.google.com/site/bifferboard/Home/factory-firmware
has the command-line compiled into the kernel (and so the biffboot
cmdline should be blank), whereas
http://sites.google.com/site/bifferboard/Home/openwrt-git
actually reads the cmdline from biffboot (and so the compiled-in
cmdline should be blank).
(IIRC factory-firmware is an older version of openwrt-git, from before
Biff added "Kernel command-line is supplied by the bootloader, not
embedded")
And as explained above, the compiled-in cmdline and the
biffboot-supplied cmdline are two separate things.
After changing the biffboot cmdline with the serial console, don't
forget to save changes too.
Lurch
Antonio Cansado
I finally got it running. It seams I messed up with something during
compilation 'cause I did the whole process again and it was ok.
Thanks again!
PS:
BB is quite a nice device, though I'll probably need a faster one. It
achieved ~30 Mbps in iperf and I was aiming ~60Mbps.
On Jun 5, 6:31 am, Andrew Scheller <ya...@loowis.durge.org> wrote:
> > Now I'm trying to reflash it with Openwrt from the GIT repo, though
> > with no luck.
> > I have followed instructions from Git's README -> copied the example
> > config (cp bifferboard_example_config .config), and then flashed the
> > device.
>
> I assume you ran "make" as well? ;)
>
> > After seeing this thread, I recompiled the kernel adding:
> > Processor type and features --->
> > [*] Built-in kernel command line
> > (console=uart,io,0x3f8 rootfstype=squashfs,jffs2) Built-in kernel
> > command string
>
> Hmmm, dunno why that didn't work.
>
> > Though when I reflash it again, showconfig still signals that cmdline
> > is empty and BB fails to boot.
>
> Biffboot runs *before* the kernel, and so the cmdline that showconfig
> displays has no knowledge of what's been compiled into the kernel.
> To check what cmdline the kernel actually used, after Linux has booted type:
> cat /proc/cmdline
>
> > The BB is still working if I flash it with the factory firmware from
> >https://sites.google.com/site/bifferboard/Home/factory-firmware. This
> > firmware also reports cmdline as empty in showconfig, though BB boots
> > ok.
>
> > What am I missing? Any help will be greatly appreciated.
>