maybe someone can upload a firmware with a modified config.linux, and someone with 2 of these routers can try it on their spare one.....
lol well unless you want to brick your router with a buggy build, you should compile and debug it first. I think that's what that Jtag thing does, gives a demo runtime of the compiled FW before actually installing it onto the router. I, of course, am completely talking outta my ass right now but i think i'm on the right track.
As soon as you guys are ready, I am willing to test the firmware on my router. I bought three of these things because it was such a good deal.
Someone recommended putting dd-wrt on the router so I could use it for more things. I then realized that I could use one as a client bridge for my modded xbox in a different room that doesn't have ethernet ran.
When someone is ready with some firmware, include the exact instructions on what to do,because I have no experience with dd-wrt or any of the components used to install it. Although, I do have a basic understanding of networking and turning regular routers into access points.
As soon as you guys are ready, I am willing to test the firmware on my router. I bought three of these things because it was such a good deal.
Someone recommended putting dd-wrt on the router so I could use it for more things. I then realized that I could use one as a client bridge for my modded xbox in a different room that doesn't have ethernet ran.
When someone is ready with some firmware, include the exact instructions on what to do,because I have no experience with dd-wrt or any of the components used to install it. Although, I do have a basic understanding of networking and turning regular routers into access points.
You won't really help out by bricking your router. If you sincerely want to help, donate one of your "extra" routers to any on this thread who know what they are doing. This will greatly speed things up.
As soon as you guys are ready, I am willing to test the firmware on my router. I bought three of these things because it was such a good deal.
Someone recommended putting dd-wrt on the router so I could use it for more things. I then realized that I could use one as a client bridge for my modded xbox in a different room that doesn't have ethernet ran.
When someone is ready with some firmware, include the exact instructions on what to do,because I have no experience with dd-wrt or any of the components used to install it. Although, I do have a basic understanding of networking and turning regular routers into access points.
maybe someone can upload a firmware with a modified config.linux, and someone with 2 of these routers can try it on their spare one.....
lol well unless you want to brick your router with a buggy build, you should compile and debug it first. I think that's what that Jtag thing does, gives a demo runtime of the compiled FW before actually installing it onto the router. I, of course, am completely talking outta my ass right now but i think i'm on the right track.
i don't know jack about linux. But I really doubt setting ONE item in config.linux to "=y" will brick a router..... esp the usb items
speaking of linux, i'm having a hell of a time getting this shhtt installed on virtualpc/box.
this is pissing me off. tried compiling on my Athlon II x4 in 64bit fedora 12.
i woulda thought Fedora 12 would have everything.
I extract everything in their proper folders:
I have 2 main folders after extraction-
/opt/toolchains/SW
/opt/toolchains/westell_msw2
and then i get this error:
Quote:
[root@FED12 SW]# make PROFILE=A90-750115
making all for A90-750115
make -C /opt/toolchains/SW/targets/A90-750115 all
make[1]: Entering directory `/opt/toolchains/SW/targets/A90-750115'
echo "A90-750115" > /opt/toolchains/SW/.PROFILE
***** Configuring Linux kernel *****
cp -f /opt/toolchains/SW/targets/A90-750115/config.linux /opt/toolchains/SW/targets/A90-750115/objects/.config
yes "" | make -C /opt/toolchains/SW/linux/linux-2.6.8.1 O=/opt/toolchains/SW/targets/A90-750115/objects oldconfig > /dev/null
/bin/sh: gcc: command not found
make[4]: *** [scripts/basic/fixdep] Error 127
make[3]: *** [scripts_basic] Error 2
make[2]: *** [oldconfig] Error 2
make[1]: *** [/opt/toolchains/SW/targets/A90-750115/objects/.config] Error 2
make[1]: Leaving directory `/opt/toolchains/SW/targets/A90-750115'
make: *** [all] Error 2
[root@FED12 SW]#
so i installed gcc, and i still get another compiling error, not to mention the crapload of warnings.
looks like I won't ever figure out what tools I need for this.
how about you guys compile the default firmware, and load it into the router, and see if anything changes?
if nothing changes, that means the firmware is good.
Posted: Tue Feb 23, 2010 16:34 Post subject: Broadcom SOC bcm6358
I haven't seen this in any post so far. Here is the Broadcom product brief in pdf format.
I hope it is useful. With all the Westell 7501's out there, there's definitely a need for "undisabled" firmware. Unfortunately, I don't know how to write code and I haven't used Linux very often.
the CPU is BCM6359 not is BCM6358.
Not sure the BCM6359 is same as BCM6358 , or not.
I got one document says BCM6359 is lite BCM6358 version. _________________
Posted: Tue Feb 23, 2010 17:58 Post subject: bcm 6358 vs 5359
[quote="cgigate"]the CPU is BCM6359 not is BCM6358.
Not sure the BCM6359 is same as BCM6358 , or not.
I got one document says BCM6359 is lite BCM6358 version.[/quote]
Not to wear this out, but I can't find the place where I saw the difference explained. It was an "incremental" difference-like 16MB ram instead of 32MB or a revision of CPU speed (lower of course) to save $.50 in cost.
This is the best list of BCM chipset family trees I've found so far:
BCM6358 ADSL2+
BCM6358GW ADSL2+ 11n WLAN Gateway
BCM6358VW2 ADSL2+ 11g WLAN USB Gateway
CANT-3 ADSL2+ 11g WLAN 3G Femto USB Gateway
CANT-G ADSL2+ 11g WLAN VoIP USB Gateway
CANT-H ADSL2+ 11g WLAN VoIP DECT USB Gateway
CANT-J ADSL2+ 11n WLAN Gateway
CANT-O ADSL2+ 11n WLAN USB Gateway
CANT-S ADSL2+ 11n WLAN VoIP USB Gateway
CANT-T ADSL2+ 11n WLAN VoIP DECT USB Gateway
CANT-W ADSL2+ 11g WLAN VoIP USB Gateway
CANT-Y ADSL2+ 11g WLAN VoIP USB Gateway
CANT-Z ADSL2+ 11g WLAN VoIP DECT USB Gateway
DANT-D ADSL2+ 11g WLAN VoIP USB Gateway
BCM6358 VDSL2
VDNT-C VDSL2 Residential Gateway
VDNT-D(0) VDSL2 11g WLAN VoIP USB Gateway
VDNT-D(1) VDSL2 11g WLAN VoIP USB Gateway
As you can see from some of the pictures in the forum, even though it has 6359 silkscreened on the outside, it reports as a 6358 when queried. In my experience, if the chip says it's a '58, treat it like a '58.
from the OpenWrt.org site, I found it is also used in:
Neuf Box 4
Inventel Livebox
D-Link DSL-2650U
D-Link DSL-2740B
Pirelli Alice Gate VoIP 2 Plus Wi-Fi AGPF-S0
And according to the Linux-Mips.org:
Cable modem series includes BCM33xx SoCs, these SoCs are internally not different from the BCM63xx SoCs (except the CPU speed I'm guessing)
I just hope someone can make sense out of all this. Lots of info but not enough knowledge on my part.
the information got from Jtag.
because the jtag app not BCM6359 in database, then shows BCM6358 instead of real BCM6359.
actually, the device is well neat designed _________________
Last edited by cgigate on Tue Feb 23, 2010 23:59; edited 1 time in total
I have no problem testing one of these since I have quite a few. I bought 6 for $42 shipped and have already sold two for $70. If one bricks, I'll easily get over it.
Built serial cable for it. it works fine. I got in reboot info, it shows 8M flash and 32M RAM
it looks and sounds a great router, if figure out to load dd-wrt
It looks impossible to TFTP way to flash the rom, the boot-up process could not be stopped
Looks like you're on the right track there, I compiled with Debian 64-bit Lenny without a problem.. however I think you just have a PATH problem, try this:
this is pissing me off. tried compiling on my Athlon II x4 in 64bit fedora 12.
i woulda thought Fedora 12 would have everything.
I extract everything in their proper folders:
I have 2 main folders after extraction-
/opt/toolchains/SW
/opt/toolchains/westell_msw2
and then i get this error:
Quote:
[root@FED12 SW]# make PROFILE=A90-750115
making all for A90-750115
make -C /opt/toolchains/SW/targets/A90-750115 all
make[1]: Entering directory `/opt/toolchains/SW/targets/A90-750115'
echo "A90-750115" > /opt/toolchains/SW/.PROFILE
***** Configuring Linux kernel *****
cp -f /opt/toolchains/SW/targets/A90-750115/config.linux /opt/toolchains/SW/targets/A90-750115/objects/.config
yes "" | make -C /opt/toolchains/SW/linux/linux-2.6.8.1 O=/opt/toolchains/SW/targets/A90-750115/objects oldconfig > /dev/null
/bin/sh: gcc: command not found
make[4]: *** [scripts/basic/fixdep] Error 127
make[3]: *** [scripts_basic] Error 2
make[2]: *** [oldconfig] Error 2
make[1]: *** [/opt/toolchains/SW/targets/A90-750115/objects/.config] Error 2
make[1]: Leaving directory `/opt/toolchains/SW/targets/A90-750115'
make: *** [all] Error 2
[root@FED12 SW]#
so i installed gcc, and i still get another compiling error, not to mention the crapload of warnings.
looks like I won't ever figure out what tools I need for this.
how about you guys compile the default firmware, and load it into the router, and see if anything changes?
if nothing changes, that means the firmware is good.