I've worked a little with the wl520gu, which has the same processor as the v2. The loading problem for me was the cfe api. The entry point passed by the cfe isn't correct and I haven't been able to guess one that works. The various gpl sources aren't much help, as none I could find use the api. It may even be that the api doesn't exist in this cfe as it's stripped of much of it's earlier functionality. Maybe somebody more experienced than me will disassemble the 520gu or v2 cfe and figure out what's going on. It seems to only be used for debugging to get console output early in the boot process.
So, I just disconnected the api with this patch. Now it boots.
diff --git a/arch/mips/bcm47xx/prom.c b/arch/mips/bcm47xx/prom.c
index 079e33d..30287f6 100644
--- a/arch/mips/bcm47xx/prom.c
+++ b/arch/mips/bcm47xx/prom.c
@@ -146,9 +146,9 @@ static __init void prom_init_mem(void)
void __init prom_init(void)
{
- prom_init_cfe();
- prom_init_console();
- prom_init_cmdline();
+// prom_init_cfe();
+// prom_init_console();
+// prom_init_cmdline();
prom_init_mem();
}
diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
index c6a063b..b748dd3 100644
--- a/arch/mips/kernel/setup.c
+++ b/arch/mips/kernel/setup.c
@@ -557,12 +557,14 @@ void __init setup_arch(char **cmdline_p)
prom_init();
#ifdef CONFIG_EARLY_PRINTK
+#if 0
{
extern void setup_early_printk(void);
setup_early_printk();
}
#endif
+#endif
cpu_report();
check_bugs_early();
The other problem is the radio. It has a lp phy, where lp is probably "low power". Both the 520gu and the v2 have rf amps on them, so lp seems reasonable. Anyway, the word from the bcm43xx-dev experts is that it isn't supported yet.
I put a patch on the openwrt-devel list that gets the usb2 part of the usb working. It hasn't been merged yet.
I'd really recommend getting a serial console. I'm using a um232r usb interface from ftdi. Find them at www.ftdichip.com. It's available from several distributors for about $20. It's so early in the development that a report of "won't boot" without any console output probably won't get a lot of replies.