Sitecom WLR-2100 V2
- Manufacturer pages: information and support
Supported Versions
This device is not supported in the official OpenWrt builds. Experimental builds are available (see below).
Hardware Highlights
* Possible with modifications.
Hardware
Info
Architecture | MIPS 74Kc |
---|---|
Vendor | Sitecom |
bootloader | U-Boot |
System-On-Chip | Atheros AR1321 (Atheros AR1321-AL1A PCK898.00B 1138) |
CPU/Speed | 500 MHz |
Flash | 4 MiB (cFeon Q32B-104HIP AJM291A4 1244LMA) |
RAM | 32 MiB (Hynix 236A H5DU2562GTR-E3C NWJM0330AHE) |
Wireless | Atheros AR1321 (integrated) |
Ethernet | Atheros AR1321 (integrated) |
USB | No (available with modification) |
Serial | Yes (available with modification) |
JTAG | No (available with modification) |
According to WikiDevi, the Atheros AR1321 seems identical to the AR9341.
Opening the case
Note: This will void your warranty!
- Remove the four screws at the bottom of the device in each corner
- Remove the fifth screw located under the sticker
LED
Description | Position | Color | GPIO | PCB Name | Mode |
---|---|---|---|---|---|
Power | 1 | Amber | GPIO15 | LED8 | Active low |
WiFi | 2 (top) | Blue | GPIO13 | LED1 | Active low |
WPS | 2 (bottom) | White | GPIO12 | LED9 | Active low |
WAN | 3 | Blue | GPIO18 | LED7 | Active low |
LAN1 (4*) | 4 | Blue | GPIO19 | LED3 | Active low |
LAN2 (3*) | 5 | Blue | GPIO20 | LED4 | Active low |
LAN3 (2*) | 6 | Blue | GPIO21 | LED5 | Active low |
LAN4 (1*) | 7 | Blue | GPIO22 | LED6 | Active low |
* LAN port numbers are reversed in OpenWrt.
The position is numbered from left to right when front facing the router.
Buttons
Description | GPIO | PCB Name | Mode |
---|---|---|---|
OPS (WPS) | GPIO16 | SW3 | Active low |
Seconds | Mode |
---|---|
2 | OPS mode |
10 | Reset |
15 | Factory default |
Serial
Serial console is available on the J4 connector. No pin header is available, so you might want to solder a pin header on the PCB. Remove the solder from the holes, preferable with desoldering techniques such as litze wire. If not possible, use a 0.8 mm drill.
Do not connect Vcc. Only connect GND, TxD and TxR.
Serial communication might not be reliable. Oddly, it works well in boot command line mode. This needs more investigation.
Setting | Value |
---|---|
Baudrate | 115200 |
Data Bits | 8 |
Stop Bits | 1 |
Parity | None |
Handshake | None |
Pin | Description | Notes |
---|---|---|
1 | Vcc | 3.3V, NC, marked with arrow |
2 | GND | |
3 | TxD | |
4 | RxD |
USB and JTAG
According to the datasheet, the AR9341 supports USB 2.0 and JTAG. The USB data pins do not have soldering pads on the PCB. However, the pins are directly accessible on the chip, so an USB mod can be easily made with some soldering skills. The supplied experimental images are compiled with USB kernel modules. JTAG is available on the GPIO ports, but this is not tested yet.
Photos
Description | Photo |
---|---|
PCB top view | Photo externally hosted on OneDrive |
Serial front view | External photo hosted on OneDrive |
Serial back view | Photo externally hosted on OneDrive |
Software (OEM)
OEM Bootlog
Officially, only one version of the firmware is available for the WLR-2100 V2. However, some routers may be shipped with another older version of the firmware. The bootlog is based on the official firmware provided by Sitecom.
U-Boot 1.0.1 (Mar 14 2012 - 16:09:18) U-boot AP123 DRAM: sri Wasp 1.1 wasp_ddr_initial_config(280): Wasp (16bit) ddr1 init Tap value selected = 0xf [0x0 - 0x1f] 32 MB Top of RAM usable for U-Boot at: 82000000 Reserving 235k for U-Boot at: 81fc4000 Reserving 192k for malloc() at: 81f94000 Reserving 44 Bytes for Board Info at: 81f93fd4 Reserving 36 Bytes for Global Data at: 81f93fb0 Reserving 128k for boot params() at: 81f73fb0 Stack Pointer at: 81f73f98 Now running in RAM - U-Boot at: 81fc4000 id read 0x1c15 venid=1c,devid=15 Unknown flash device Flash: 4 MB *** Warning *** : PCIe WLAN Module not found !!! In: serial Out: serial Err: serial Please choose the operation: 1: Load system code to SDRAM via TFTP. 3: Boot system code via Flash (default). 4: Entr boot command line interface. 3: System Boot system code via Flash. ## Booting image at 9f040000 ... Image Name: Linux Kernel Image Created: 2013-07-01 6:10:50 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1355370 Bytes = 1.3 MB Load Address: 80002000 Entry Point: 80006110 Verifying Checksum at 0x9f040040 ...OK Uncompressing Kernel Image ... OK No initrd ## Transferring control to Linux (at address 80006110) ... ## Giving linux memsize in bytes, 33554432 Starting kernel ... Booting Atheros AR934x init started: BusyBox v1.7.5 (2013-07-01 14:07:05 CST) starting pid 672, tty '/dev/console': '/sbin/config_init' mknod: /dev/ttyS0: File exists mknod: /dev/ttyS1: File exists Config Init version: 1.0.2.2 date: 2013/07/01 Tue Jan 1 00:00:00 UTC 2013 mount: can't find /sys in /etc/fstab or /etc/mtab ln: /lib/./modules: File exists starting pid 724, tty '/dev/ttyS0': '/sbin/config_term' ************************************************************************ * WLR-2100_3100 * ************************************************************************ KernelApp/Ramdisk Ver:1.0.2.2 Date:2013/07/01 password:
The password lin17 can be used to login into the shell.
OEM Flash Layout
The bootargs report a different MTD layout compared to what is actually loaded by the kernel. Seems to be some left over code due to source recycling (NVRAM on Atheros)?
bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs,jffs2 init=/sbin/init mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),2752k(rootfs),896k(uImage),64k(NVRAM),64k(ART)
# cat /proc/mtd dev: size erasesize name mtd0: 00400000 00010000 "ALL" mtd1: 00030000 00010000 "Bootloader" mtd2: 00010000 00010000 "Config" mtd3: 00340000 00010000 "Kernel" mtd4: 001f0000 00010000 "apps" mtd5: 00010000 00010000 "manufacture" mtd6: 00010000 00010000 "backup" mtd7: 00050000 00010000 "storage" mtd8: 00010000 00010000 "caldata"
# cat /proc/partitions major minor #blocks name 31 0 4096 mtdblock0 31 1 192 mtdblock1 31 2 64 mtdblock2 31 3 3328 mtdblock3 31 4 1984 mtdblock4 31 5 64 mtdblock5 31 6 64 mtdblock6 31 7 320 mtdblock7 31 8 64 mtdblock8
# cat /proc/mounts rootfs / rootfs rw 0 0 /proc /proc proc rw,relatime 0 0 /dev/mtdblock7 /storage jffs2 rw,relatime 0 0 /dev/mtdblock4 /apps squashfs ro,relatime 0 0
Layer 0 | Layer 1 | Layer 2 |
---|---|---|
ALL mtd0 4096 | Bootloader mtd1 192 | |
Config mtd2 64 | ||
Kernel mtd3 3328 | vmlinux 1344 | |
app mtd4 1984 | ||
manufacture mtd5 64 | ||
backup mtd6 64 | ||
storage mtd7 320 | ||
caldata mtd8 64 |
Binaries and Patches
This in an experimantal build of OpenWrt. Use this firmware at own risk.
Downloads
Version | Date | Type | Notes | Download |
---|---|---|---|---|
0.1 | 07-12-2016 | Initramfs | Build with default packages + USB + LUCI | Firmware externally hosted on OneDrive |
0.1 | 07-12-2016 | Patch | Not a quilt patch file | Patch file externally hosted on OneDrive |
Changelog
Version 0.1 - First experimental build for OpenWrt on WLR-2100 V2. - Based on OpenWrt trunk (9d64efa1a23f31847f4a9bef9f3474a9cf3fadb3). - The white OPS led serves as status led. - OPS button needs configuration, does not work out of the box. - Not intended for flashing.
Installation
Currently, loading the firmware via TFTP is the only possible way of running OpenWrt on the WLR-2100 V2. Permanent flashing will be available soon. Grab the Precompiled binaries, or apply the patch and build your own firmware with the OpenWrt Buildroot.
Build with Buildroot
This part can be skipped if you want to use the precompiled binaries. Prior knowledge is required to build your own firmware. Please check out the documentation for more information on installing and using the OpenWrt Buildroot.
- Install the OpenWrt Buildroot.
- Apply the patch file to your OpenWrt buildroot (this modifies your OpenWrt source code, quilt patches will be available soon).
- Configure your buildroot. A target profile for the WLR-2100 V2 should be available after applying the patch. For now, create a ramdisk to run OpenWrt on the WLR-2100 V2. Flashable images will be available soon.
- Build your OpenWrt firmware.
Loading Firmware
Currently, no flashable images are available. However, you are able to load the OpenWrt firmware via serial and TFTP.
- Create a TFTP server to serve the firmware file as 'ap.bin'.
- Assign the static IP address 192.168.1.101 to the server and make sure the server is accessible for the router.
- Connect the WLR-2100 V2 via serial, and load up a console to see the output.
- During boot, keep tapping '1' to load system code to the SDRAM via TFTP.
- OpenWrt should now boot!
For now, please report bugs on the forum thread. Maybe some day the device profile will be added to the OpenWrt master branch.