On 06/21/2012 12:43 PM, Rafał Miłecki wrote:
> 2012/6/21 Hauke Mehrtens <ha...@hauke-m.de>:
>> You could try top boot a ramdisk from a tftp server from within CFE:
>> boot -tftp -elf 192.168.1.220:/brcm47xx/openwrt-brcm47xx-vmlinux.elf
>> here 192.168.1.220 is the IP address where the tftp server is running
>> and brcm47xx/openwrt-brcm47xx-vmlinux.elf is the patch on the tftp
>> server where the image can be found. To generate a ramdisk image select
>> "Target Images" --> "ramdisk" and in ramdisk menu "Compression" to lzma.
> 
> 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! :)
The core ids for some cores on this SoC are different from the ids used
on all other chips, see include/hndsoc.h.

#define CC_4706_CORE_ID         0x500           /* chipcommon core */
#define SOCRAM_4706_CORE_ID     0x50e           /* internal memory core */
#define GMAC_COMMON_4706_CORE_ID        0x5dc           /* Gigabit MAC core */
#define GMAC_4706_CORE_ID       0x52d           /* Gigabit MAC core */

> Why booting elf from tftp allowed to me finally see anything? Any
> explanation to that maybe?

I do not know, it could be that it boots the system somehow different or
you did something wrong while flashing.

Hauke
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to