[LEDE-DEV] Issues on brcm47xx, Buildbot config
p.wassi at gmx.at
p.wassi at gmx.at
Sat Jun 4 07:17:06 PDT 2016
Related to my last post to the list "brcm47xx legacy broken in trunk?"
I'm not sure whether "legacy broken in trunk" is the right terminology.
When I started to dig into the problem, I cloned the repo and built the
image myself. It worked immediately.
To confirm my findings, I downloaded today's current trunk again. These images
still DO NOT BOOT on WRT54G(L).
The only settings I change in "make menuconfig" for the new image:
-) Target System = Broadcom BCM47xx/53xx (MIPS)
-) Subtarget = Legacy (BMIPS3300)
A built image with these settings works perfectly fine:
> Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
> Loading: .. 3800 bytes read
> Entry at 0x80001000
> Closing network.
> Starting program at 0x80001000
> [ 0.000000] Linux version 4.1.20 (openwrt at debian-compiler) (gcc version 5.3.0 (LEDE GCC 5.3.0 r482) ) #4 Sat Jun 4 10:01:44 UTC 2016
> [ 0.000000] CPU0 revision is: 00029008 (Broadcom BMIPS3300)
> [ 0.000000] bcm47xx: Using ssb bus
> [ 0.000000] ssb: Found chip with id 0x5352, rev 0x00 and package 0x02
> [ 0.000000] ssb: Sonics Silicon Backplane found at address 0x18000000
> (...)
So I assume, some configuration the buildbot is using, makes the images
unusable for WRT54G(L)
Best regards,
P.Wassi
More information about the Lede-dev
mailing list