On Fri, Aug 5, 2011 at 9:47 PM, Marco Antonio Mauro <marcu...@gmail.com> wrote: > Hi > > I have a Sitecom WL-341 and would like to know what was needed to run > OpenWRT on it. > > It's Ralink based, with a RT3052F ASIC, has 4MB flash and 16MB ram > (upgradable to 32 or more, has space and components to accommodate > another TSOPII-54 (SDR?) SDRAM chip which pads are left not > populated), USB (only data lines as it misses the 5V voltage regulator > but I think it can be used with a powered USB hub) and a single > pushbutton labelled WPS. > > Onboard components are: > > CPU: Ralink RT3052F (covered by glued on heatsink) running at 384MHz > RAM: 1x EtronTech EM639165TS-6C 16MB, 1x free TSOPII-54 "slot" > FLASH: 1x Macronix MX29LV320 4MB on bottom side > > 4xLAN and 1xWAN 100Mbps > > 1 button only > > Has a custom u-boot bootloader that is very buggy (TFTP reflash > doesn't work, flashes at 0x50000 and then tries to boot an image at > 0x40000) but if the single button the unit has is pressed briefly > during boot the unit will use the same protocol as the Linksys NSLU2 > that correctly flashes a complete image of the flash except for the > bootloader and the NVRAM > First 4 blocks of the flash contain the bootloader and nvram, last 64k > block is unuseable as it contains the eRcOmM signature required by the > bootloader (that starts the NSLU2-protocol reflash if it doesn't find > that signature) for a grand total of 3.7Mb available for kernel and > rootfs (but probably can be used with an external rootfs via USB) > > A firmware image can be found here: > > http://www.sitecom.com/download/4232/WL-341v3_v1012.img > > The file is a ZIP with a 512byte header, can be unzipped to have the > complete firmware image (including bootloader) IP1006RRv2_16.bin that > can also be used to reflash via NSLU2-protocol. > > The source code for the device is here: > > http://www.sitecom.com/documents/WL-341_GPL.tgz > > I didn't test it to see if it compiles to a working image or not though. > > I can post pictures of the board and a bootlog taken via the serial > port if needed. > > Thanks in advance :)
I worked on the device and after patching a number of things I built with current svn buildroot and my patches a sysupgrade working image that I then manually modified to get the windows nslu2 update application to reflash the device. I made the wiki page for the device with the status of the port and some information: http://wiki.openwrt.org/toh/sitecom/wl-341 I am now facing 3 problems and I need help: 1. The device has 6 unlabeled leds: 5 blue/amber and 1 blue but in the manufacturer provided source code there is no mention of the GPIOs used. How can I test it manually from openwrt so that at least I can provide the user the ability to use those from within the web interface? 2. The device boots successfully but I cannot enable the wifi access point. In the system log there is an error. You can see the log here: http://wiki.openwrt.org/toh/sitecom/wl-341#notes I personally think it's a not enough RAM problem, but the device tells me there is over 5MB of ram available at boot time so I'm a bit puzzled. 3. To generate an image that can be flashed directly using the windows update application it must satisfy some costraints: it must contain the bootloader that is already on the device even though it won't be flashed (256kb), then the kernel uImage at 0x40000, then the rootfs and enough padding to get to 4MiB. The last 16bytes contain a magic (eRcOmM) that must be there at every boot else the router will go in recovery mode. I patched the partition table to avoid using the last flash block in all cases thereby protecting the signature, but I can't seem to figure out how to make the buildroot generate a valid flashable factory image. Basically I need the buildroot to concatenate: 4 blocks from a file; uImage and rootfs padded to 0x3ffff0 bytes, and then; 0x10 bytes that contain some parameters for the upgrade application and the eRcOmM magic. I'd like help on how to do those steps. Once I fix those problems (at least the wifi and the factory image ones) I'll prepare and submit a patch here. Thanks again. -- Marcus905 GPG pubkey: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x1FC0ECC932FE5FAC _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
