On 06/22/2012 02:10 PM, Rafał Miłecki wrote: > 2012/6/22 Rafał Miłecki <zaj...@gmail.com>: >> 2012/6/21 Rafał Miłecki <zaj...@gmail.com>: >>> YOU'RE GREAT GUYS >>> >>> boot -tftp -elf 192.168.1.2" :/openwrt-brcm47xx-vmlinux.elf >>> Loader:elf Filesys:tftp Dev:eth0 >>> File:192.168.1.2:/openwrt-brcm47xx-vmlinux.elf Options:(null) >>> Loading: 0x80001000/4400228 0x80433464/118060 Entry at 0x80247370 >>> Closing network. >>> Starting program at 0x80247370 >>> [ 0.000000] Linux version 3.3.8 (za...@linux-bxwm.site) (gcc >>> version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #5 Thu >>> Jun 21 12:00:17 CEST 2012 >>> [ 0.000000] bootconsole [early0] enabled >>> [ 0.000000] CPU revision is: 00019749 (MIPS 74Kc) >>> [ 0.000000] bcm47xx: using bcma bus >>> [ 0.000000] bcma: Found chip with id 0x5300, rev 0x01 and package 0x00 >>> [ 0.000000] bcma: Failed to scan for common core: -29 >>> [ 0.000000] Kernel panic - not syncing: Failed to initialize BCMA >>> bus (err -1) >>> >>> Now the rest sounds trivial to fix! :) >>> >>> >>> Why booting elf from tftp allowed to me finally see anything? Any >>> explanation to that maybe? >> >> OK, I've fixed booting to reach some sane state. I've been working >> using tftp and elf all the time. Finally my boot log (using tftp + >> elf) looks like you can see in attached log. >> >> So after reaching this stage I've switched from generating ramdisk to >> generating squashfs. Installed my openwrt-wndr4500-squashfs.chk and... >> again, nothing. I can't see anything after "Starting program at >> 0x80001000". > > Hauke: does serial console logging works for you on any BCMA board? > > In brcm47xx/setup.c I can see some serial related code in > bcm47xx_register_ssb. We don't have anything like that in > bcm47xx_register_bcma. Can this cause a problem for me?
This code is used if the default serial port is on a different tty and it is used for some old devices or just one. I had never problems with serial console on my bcma based devices (bcm4716 and BCM5357). I think you stored the image on the wrong flash chip. From the boot log of the original firmware it looks like it has a 2MB serial flash and a 128MB NAND flash. One has the partition named linux and the other a partition named kernel with round about the same size. You could look into the source code provided by Netgear for your device and find out how the booting works with the original firmware and how the original firmware image is structured. Hauke _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
