The 5356 cpu is a 4716 with radio and lan switch integrated, same as Asus RT-N10 so Eko's build for RT-N10 should theoretically work.
What is most interesting is a serial boot log, Netgear usually have one or more reserved partitions in the flash and with 4Mb flash that may not give enough room for Eko's RT-N10 K26 build.
The CFE for the router was included in the GPL code. _________________ Kernel panic: Aiee, killing interrupt handler!
Not sure if my jtag is working. My Xilinix cable (P-Port) shares the same pins as the tjtag pinout. I do get a ID.
There is a 25L3205 on the bottom of the board.
Anyone know what CPU ID I should be getting?
Your cable may be ok, force instruction length to 32 with the switch /instrlen:32 and see if you can get a proper cpu id.
It should read 0x1535617F. _________________ Kernel panic: Aiee, killing interrupt handler!
I see what the problem is, No Target Vcc to the jtag programmer ;(. Easy fix, will try your sugestions.
I'll also try to get the boot info off the serial header. I have a max232 on a card that I can plug into the header.
Ok, So I got the Jtag working and I get the correct CPUID, however I can't get the CFE. All I get is zeros.
Now here is the serial console:
(I edited the MAC to XX-XX-XX)
Decompressing...done
Decompressing...done
CFE for WNR1000v3 version: 3.0.5
Build Date: Thu Nov 5 20:19:02 CST 2009
Boot partition size = 131072(0x20000)
Found a 4MB ST compatible serial flash
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet ContDecompressing...done
CFE for WNR1000v3 version: 3.0.5
Build Date: Thu Nov 5 20:19:02 CST 2009
Boot partition size = 131072(0x20000)
Found a 4MB ST compatible serial flash
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.10.56.46
Device eth0: hwaddr C0-3F-0E-XX-XX-XX, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
CPU ProcId is: 0x00019749, options: 0x000021cd
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 60k freed
Reading board data...
WSC UUID: 0xd85ece1252fe810439835ed0c9fe189c
convert_wlan_params_for_bssid: configure BSSID 2
convert_wlan_params_for_bssid: configure BSSID 3
convert_wlan_params_for_bssid: configure BSSID 4
Using /lib/modules/2.4.20/kernel/drivers/net/emf/emf.o
Using /lib/modules/2.4.20/kernel/drivers/net/igs/igs.o
Using /lib/modules/2.4.20/kernel/drivers/net/et/et.o
Using /lib/modules/2.4.20/kernel/drivers/net/wl/wl.o
Hit enter to continue...WARNING: console log level set to 1
waitpid: No child processes
waitpid: No child processes
killall: upnp: no process killed
UPnP daemon is ready to run
killall: wps_monitor: no process killed
killall: wps_ap: no process killed
killall: wps_enr: no process killed
Reading board data...
WSC UUID: 0xd85ece1252fe810439835ed0c9fe189c
Using /lib/modules/2.4.20/kernel/net/ipv4/acos_nat/acos_nat.o
info, udhcp server (v0.9. started
error, unable to parse 'option wins '
error, unable to parse 'option domain '
[a]the file size is 4294967295
POT integrity check OK.
IOCTL_AG_REGION_SET: English
Start DHCP client daemon
info, udhcp client (v0.9. started
vlan1: No such process
Hit enter to continue...Hit enter to continue...Info: No FWPT default policies.
Using /lib/modules/2.4.20/kernel/net/ipv4/multissidcontrol/MultiSsidControl.o
Ok, So I got the Jtag working and I get the correct CPUID, however I can't get the CFE. All I get is zeros.
You'll have to pm Tornado and ask him for a pre-release of the next tjtag version, these new cpu's needs special jtag handling.
Your serlog shows the additional flash partitions that are common for Netgear routers, I have never seen an original wholeflash from them but assume that ML1 and ML2 are language files. I have no idea what T_Meter1, T_Meter2 and POT are..
dd-wrt overwrites all of them except for the board_data partition which has to the preserved, it contains MAC addresses, radio calibration parameters and so on.
It is therefore important that the router gets full dd-wrt support, ie can be identified by dd-wrt so that the board_data partition is kept.
You can, after doing a jtag wholeflash backup, load a generic K26 small mini build for test but you'll have to write it via jtag since there is no tftp or gui .chk file for this router.
The hardware is identical to the Asus RT-N10, it is after all a SOC (SystemOnaChip) cpu with only 2 external components, the ram and the flash ic's.
What differs between them is the reserved flash partitions and the CFE routines for loading a file via tftp (header differences).
Both of these routers suffers from poor radio performance with their original firmwares and also when dd-wrt is loaded.
It is a matter of the radio driver for single stream 802.11N, there will hopefully soon be a better driver available from Broadcom.
Good luck! _________________ Kernel panic: Aiee, killing interrupt handler!
These have been out for quite a while now. In lieu of waiting for DDWRT support, you should at least do like I did over in this previous thread for the WGR614v10 last month and crossflash it to a WNR1000v3:
WGR614v10 and WNR1000v3 have the EXACT same underlying hardware (same FCC ID and everything...look at the docs and you'll see both routers on all the photos). The *only* difference is in the firmware. WGR614v10 fw limits you to b/g while the WNR1000v3 fw allows full b/g/n of the BCM5356 chipset. That's also why you see the CFE on the WGR614v10 report itself as a WNR1000v3 lol.
Only N device I have is my 360's N adapter and it reports itself as being connected at N speed but the platform doesn't really allow for a true test. No reason it shouldn't though as outlined above.
Posted: Sun Apr 11, 2010 14:50 Post subject: WGR614v10
Hi,
I just got one of these and would love to run it in bridge mode, like a gaming adapter. To be precise, I would like to use it to connect a TV that has an ethernet port to my wireless network.
As I am a complete novice with dd-wrt, I have no idea where to start. I spent hours reading on the wiki and the hardware support database, and the forums, and so on and am still not much the wiser.
Concretely:
1) By cross-flashing to WNR1000v3, do you mean download Netgear's firmware for that one and try to upload it with the WGR614v10's own web gui?
2) Where do I start if I want to flash it with dd-wrt? I seem to be unable to figure out where to download what from.
Posted: Tue Mar 08, 2011 18:20 Post subject: WNR1000v3 Bricks
Alright, I know this thread is old, but it seemed the most relevant. I have 3 WNR1000v3's. One is bricked. One won't allow any access to it because I omitted a parenthesis in an if statement in the firewall.c file (netgears open source firmware), and the third one one won't allow access either (started flashing new firmware to it willy-nilly and it apparently didn't like it). TFTP is not working for any of them. Any luck with tjtag, or do I need to donate them as test subjects? The CFE should be good on the last 2. I'm not so sure about the 1st one though.
I have this router and was hoping it would work but the stock firmware (both the one that came on it and the latest from Netgear) both reject the dd-wrt.v24_mini-wgr614v8-L.chk file
If anyone knows how to get bridge mode (to make a WAP bridge) with stock firmware that would be great. (not as good as dd-wrt though!)
with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
