: Please check the template_device — orca 2011/03/11 13:26 |
| WIP |
Wilibox WBD-111
Small board (81x91mm) with minipci module.
Supported Versions
| Version/Model | Launch Date | S/N | OpenWrt Version Supported | Model Specific Notes |
|---|---|---|---|---|
| v1 | ? | - | trunk | - |
| v1 Teltonika RUT104 | ? | - | r29967 | contains a Option GTM-382 GSM/3G Modem and a WLM54G Wireless LAN MiniPCI Adapter |
| v2 | ? | - | trunk | - |
Hardware Highlights
| CPU | Ram | Flash | Network | USB | Serial | JTag |
|---|---|---|---|---|---|---|
| StorLink ARM920@300MHz | 32MiB | 8MiB | 1 | Yes | Yes | ? |
Installation
This device works with gemini images. If you would like to use USB ports you should recompile yourself following th OpenWRT howto and customize the kernel as described here
Flash Layout
OEM easy installation
This section deals with how you install OpenWrt from a device freshly opened. Plus the steps required such as reset to factory defaults if the device has already been configured
Note: Reset router to factory defaults if it has been previously configured.
- Upload .bin file to router
- Wait for it to reboot
- Telnet to 192.168.1.1 and set a root password, or browse to http://192.168.1.1 if LuCI is installed.
OEM installation using the TFTP method
- Set your PC's IP to 192.168.1.254
- Open a TFTP server and place in his root the image with this name: fwupdate.bin
- Power-on your WBD-111 holding reset button
- Wait about a minute per megabyte (default image 3-4minutes)
If you have attached a serial interface, be aware that the speed of the serial Port ist switched to 9600N81 on kernel boot. This only happens for kernel boot's directly after flashing the router via TFTP (very likely a uboot bug).
Upgrading OpenWrt
SYSUPGRADE DOESN'T WORK ON GEMINI PLATFORM → generic.sysupgrade
If you have already installed OpenWrt and like to reflash for e.g. upgrading to a new OpenWrt version you CANNOT upgrade using the mtd command line tool. You should bask to the original firmware then "upgrade" with the new image.
LuCI Web Upgrade Process
Not possible.
Terminal Upgrade Process
Manual Update using mtd works, you have to write the kernel image and the squashfs image in two steps:
Upload the kernel Image an the squashfs image:
$ scp bin/gemini/openwrt-gemini-wbd111-zImage bin/gemini/openwrt-gemini-squashfs.img 192.168.1.1:/tmp
Write the Kernel Image
root@OpenWrt:/# mtd write /tmp/openwrt-gemini-wbd111-zImage kernel
Write the SquashFs Image and reboot
root@OpenWrt:/# mtd write /tmp/openwrt-gemini-squashfs.img rootfs
You will most likely loose your config, since the rootfs_data will most likely overwritten
Basic configuration
→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.
Specific Configuration
Interfaces
The default network configuration is:
| Interface Name | Description | Default configuration |
|---|---|---|
| br-lan | LAN & WiFi | 192.168.1.1/24 |
| eth0 | LAN port | None |
| wlan0 | WiFi | Disabled |
Failsafe mode
If you forgot your password, broken one of the startup scripts, firewalled yourself or corrupted the JFFS2 partition, you can get back in by using OpenWrt's failsafe mode.
Boot into failsafe mode
NOT TESTED
- Unplug the router's power cord.
- Connect the router's LAN1 port directly to your PC.
- Configure your PC with a static IP address between 192.168.1.2 and 192.168.1.254. E. g. 192.168.1.2 (gateway and DNS is not required).
- Plug the power on and wait for the DMZ LED to light up.
- While the DMZ LED is on immediately press any button (Reset and Secure Easy Setup will work) a few times .
- If done right the DMZ LED will quickly flash 3 times every second.
- You should be able to telnet to the router at 192.168.1.1 now (no username and password)
What to do in failsafe mode?
NOTE: The root file system in failsafe mode is the SquashFS partition mounted in readonly mode. To switch to the normal writable root file system run mount_root and make any changes. Run mount_root now.
- Forgot/lost your password and you like to set a new one
passwd
- Forgot the routers IP address
uci get network.lan.ipaddr
- You accidentally run 'ipkg upgrade' or filled up the flash by installing to big packages (clean the JFFS2 partition and start over)
mtd -r erase rootfs_data If you are done with failsafe mode power cycle the router and boot in normal mode.
Hardware
Info
| Architecture: ARM |
| Vendor: StorLink |
| Bootloader: RedBoot |
| System-On-Chip: ? |
| CPU/Speed 300MHz ARM920 CPU |
| Flash-Chip: ? |
| Flash size: 8192 KiB |
| RAM: 32 MiB |
| Wireless: Not included |
| Ethernet: 1*100MBit |
| USB: Yes 1 x 2.0 |
| Serial: Yes |
| JTAG: ? |
More infos here
Photos
These are some photos of a mdex RUT 104, with a hardware modification for a serial console
Front:
Left to right:
- Reset Micro Switch behind the plastic casing
- Green GSM LED
- 100 MBit LAN Port
- Green LAN LED
- SIM Card Slot
- Green Power LED
- Power Connector, 3.9mm outer diameter, 1.1mm inner diameter. Polarity does not matter, the board has a bridge rectifier build in the power input
Back:
Left to Right:
- WLAN Main
- GSM Main
- Hardware modification: 2,5mm TRS connector for a 3.3 Volt serial console
- GSM AUX or GPS Antenna (depending on the GSM module settings)
- WLAN AUX
Opening the case
Note: This will void your warranty!
- To remove the cover you should simlpy unscrew the 4 screws!
Main PCB
Frontside
Backside
Serial
→ port.serial general information about the serial port, serial port cable, etc.
How to connect to the Serial Port of this specific device:
The Serial connection can soldereded to J4, the connector on the top of the PCB photo's.
| Pin | colour | What |
|---|---|---|
| A1 | white | UART TX |
| A3 | grey | Ground |
| B1 | yellow | UART RX |
JTAG
→ port.jtag general information about the JTAG port, JTAG cable, etc.
As far as known, the platform has not JTAG interface.
Debugging
Bootloader Mods
- you could read about bootloader in general
Hardware mods
- as a beginner, you really should inform yourself about soldering in general and then obtain some practical experience!
Notes
Enable USB
- prepare your kernel (this step is uncommon, but it's indispensable for wbd-111):
make kernel_menuconfig
In this step you should include the right usb drivers:
**Device Drivers --->** **USB support --->** Mark as "built in" (*) **Support for Host-side USB** Mark as "built in" (*) **EHCI HCD (USB 2.0) support** esc-esc esc-esc... save!
To check if you have selected the correct driver after flashing image
dmesg | grep -i ehci-fotg2xx
should return
ehci-fotg2xx ehci-fotg2xx.0: Found Faraday OTG 2XX controller (base = 0x68000000) ehci-fotg2xx ehci-fotg2xx.0: FOTG2XX EHCI Host Controller ehci-fotg2xx ehci-fotg2xx.0: new USB bus registered, assigned bus number 1 ehci-fotg2xx ehci-fotg2xx.0: irq 10, io mem 0x68000000 ehci-fotg2xx ehci-fotg2xx.0: USB 0.0 started, EHCI 1.00, overcurrent ignored ehci-fotg2xx ehci-fotg2xx.0: role detected: Host, ehci-fotg2xx ehci-fotg2xx.0: A-Device ehci-fotg2xx ehci-fotg2xx.0: role detected: Host, ehci-fotg2xx ehci-fotg2xx.0: A-Device usb 1-1: new high speed USB device using ehci-fotg2xx and address 2
Teltonika RUT-104
Enable hso (3g modem) support
- Select hso module in make_menuconfig:
**Kernel modules --->** **USB Support --->** Mark as "built in" (*) **kmod-usb-net** Mark as "built in" (*) **kmod-usb-net-hso** Mark as "built in" (*) **kmod-usb-serial** Mark as "built in" (*) **kmod-usb-serial-option** esc-esc esc-esc... save!
- Select PCCARD Bus support in make kernel_menuconfig:
**Bus support --->** Mark as "built in" (*) **PCI support** Mark as "built in" (*) **PCCard (PCMCIA/CardBus) support --->** **PCCard (PCMCIA/CardBus) support --->** Mark as "built in" (*) **32-bit CardBus support** esc-esc esc-esc... save!
Add built-in hso comgt support
- Download and apply the patch to openwrt sources attached in this ticket.
Tags
toh/wiligear/wbd-111.txt · Last modified: 2012/07/31 16:09 by lairsdragon

: Please check the 


