The D-Link DIR-685 is some kind of high-profile product from D-Link, it is labelled a Xtreme N Storage Router whatever that means. It is based solely around the Gemini platform, and ARMv4 Faraday silicon design. It has the following features:

• Router: WAN+4 LAN
• 2x USB ports
• Wireless card (this is by default a Ralink RT2880F mini PCI iNIC card currently NOT supported by Linux in any way)
• Mini SATA drive bay
• Small video screen (!)

Currently using this device with OpenWrt requires UART access.

This is preliminary flashing instructions since network is not working out of the box and you need UART access to set up networking on the device. Do not install OpenWrt unless you are planning to experiment.

• Plug the DIR-685 into your computer ethernet using one of the LAN ports on the back. Set your computer to obtain network from DHCP.
• Turn on the router. The router should boot and assign an IP number to your computer. Check what IP you get: I got 192.168.0.100.
• Check that you can contact the router: ping 192.168.0.1
• Start a browser and browse to 192.168.0.1
• Log in as “Admin”, blank password by default.
• Select “Tools” from the top row pane
• Select “Firmware on the left pane
• Select “Browse” in the “FIRWMARE UPGRADE” box
• Select the openwrt-gemini-dlink_dir-685-squashfs-factory.bin file from the OpenWrt build or from another trusted source
• Hit “Upload”
• The router says “The F/W is updating…” also in the little display.
• Next thing that happens is that OpenWrt boots the kernel from flash.
• Note that INSTALLATION IS NOT FINISHED YET if you just reboot the router here, it will be bricked.
• Wait for the following text on the console (this can take a few minutes):

      jffs2_build_filesystem(): erasing all blocks after the end marker...
      jffs2: notice: (1645) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan).

This means the flash is set up and ready to be used.

Now OpenWrt is installed on your router, and you can proceed to basic configuration.

Using this method, new installs are downloaded using TFTP, see the generic OpenWrt TFTP instructions.

The firmware can be reflashed from the RedBoot derivative “Boot Menu” that comes up if you have a serial console and hammer Ctrl+C during startup like this:

• Select “Y: Upgrade Kernel” by pressing “Y” (this “kernel image” contains all of OpenWrt including root filesystem)
• Select TFTP or serial download (see elsewhere for how that works) Download the openwrt-gemini-dlink_dir-685-squashfs-factory.bin file using TFTP, you need to rename it because the boot loader cannot handle this long filename. I just name it openwrt
• The boot loader will erase and flash the image looking something like this:

  Erase flash (0x30040000): Size=32768000 ........
  Program flash (0x30040000): Size=6750212 ........

• This takes a while. When this ends, reboot to start the new firmware and it should come up.
• Note that INSTALLATION IS NOT FINISHED YET if you just reboot the router here, it will be bricked.
• Wait for the following text on the console (this can take a few minutes):

      jffs2_build_filesystem(): erasing all blocks after the end marker...
      jffs2: notice: (1645) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan).

This means the flash is set up and ready to be used.

Now OpenWrt is installed on your router, and you can proceed to basic configuration.

Upload the openwrt-gemini-dlink_dir-685-squashfs-sysupgrade.bin image to the routers /tmp directory. If your networking is set up properly it should be just something like:

  scp openwrt-gemini-dlink_dir-685-squashfs-sysupgrade.bin root@192.168.1.2:/tmp

Then issue sysupgrade:

  sysupgrade /tmp/openwrt-gemini-dlink_dir-685-squashfs-sysupgrade.bin

The DIR-685 will flash the firmware upgrade and reboot.

There is no need to wait for the JFFS2 to initialize when upgrading the firmware: this is just needed on factory installs.

We haven't yet figured out how to bring the network online properly with the DSA network switches. The following interactive commands will bring it online as 169.254.1.2 on the local link (assuming the host is statically configured on the local link as 169.254.1.1):

  ifconfig eth0 169.254.1.2 netmask 255.255.255.0 up
  ifconfig br-lan 169.254.1.2 netmask 255.255.255.0 up
  ping 169.254.1.1

If you slot in a hard disk in the device this can be pretty easily partitioned, formatted and used for storage, e.g. for using the router as a NAS device. With a completely blank disk the procedure is something like this:

• Log in to NAS or use the console if you have one.
• fdisk /dev/sda press n, ENTER, ENTER, ENTER, ENTER, w to create /dev/sda1
• mkfs.ext4 /dev/sda1
• Use the ''block'' tool to set up the partion for mounting:
• block detect | uci import fstab
• uci set fstab.@mount[-1].enabled='1'
• uci commit fstab
• Reboot
• When the device comes up df should show you /dev/sda1 mounted as /mnt/sda1

The same procedure can be used for a USB disk, just augment the above. If you have both an internal harddrive and a USB disk attached, the internal harddrive will be /dev/sda and the USB disk will be /dev/sdb.

A basic configuration as OpenWrt NAS is very simple and straight forward. The following assumes that you have some kind of hard drive or other large storage mounted on /mnt/samba.

chown -R nobody /mnt/sda1
chgrp -R nogroup /mnt/sda1

Edit /etc/config/samba to contain something like this:

config samba
    option 'name'                   'DIR-685'
    option 'workgroup'              'WORKGROUP'
    option 'description'            'DIR-685'
    option 'homes'                  '0'
    option 'interface'              'lan'

config sambashare
    option 'name'                   'files'
    option 'path'                   '/mnt/sda1'
    option 'guest_ok'               'yes'
    option 'create_mask'            '0700'
    option 'dir_mask'               '0700'
    option 'read_only'              'no'

Reboot and you can browse to the IP number (etc) of your NAS, use the files share and upload and download files that will appear in /mnt/sda1, of course you can set up whatever partition etc you like.

• A Ilitek ILI9322 display controller for 320RGBx240 connected to a panel with the label LM918A01-1A SY-B4-091116-E0199 connected to the main PCB with a flat cable (we know this is driven by a ILI9322 from the boot messages)
• A touch input module PCB with a Cypress Semiconductor CY8C214 MCU, with a LED connected to it (the WPS flashing LED), connected to the main PCB with a flat cable
• A Sunon Maglev GM0502PFV2-8GN 0.4W fan connected to the main PCB, software controlled
• A soldered (!) Alpha Networks WMP-N08 Mini-PCI RaLink RT2880F-based wireless network card, inside the shield box is a RT2850L antenna driver. The Linux driver is named “ralink_RT2880_iNIC” and is version v1.1.8.3 in the source drop but it doesn't contain the source code.
• Main PCB:
  • A blue LED indicating power on
  • A Spansion S29GL256 256 Mbit (32MB) CFI NOR-flash memory
  • A Hynix HY5DU121622DTP-D43 512 Mbit (64MB) SDRAM classed at 200MHz
  • A Bothhand GST5009 LF 1000 Base-T magnetic module (galvanic isolator) facing the WAN port
  • A RealTek RTL8366RB switch using GPIO for control
  • Two LFE9407 Delta LFE9407 LAN Filters (also galvanic isolators) facing the four LAN ports
  • A TI SN54LVC14A schmitt-trigger array
  • Inside the shield box:
    • The Storlink SL3516 SoC ASIC
    • RealTek RTL8366SR ethernet PHY/switch
    • Another Hynix HY5DU121622DTP-D43 of 64MB SDRAM so in total we have 128MB SDRAM
    • An LXC16373 latch array

For background and generic information see the generic serial console documentation.

The J3 header on the top in the front picture is the serial port connector. This is the pin assignment:

 o o o _ o
 | | |   |
 | | |   RX
 | | VCC
 | GND
 TX

Once the UART is properly connected open (in this case) /dev/ttyUSB0 in your serial console (terminal) program and set it to 19200 baud, no hardware flow control (obviously, do you see any CTS or DTS leads) 8 bits, 1 stop bit.

How to add tags