| Revision | Version Supported | Download latest stable version | Model Specific Notes |
|---|---|---|---|
| C1/C2 | 10.03 & newer | 15.05.1 | Full support, eth/wireless/leds/buttons ok |
| D1-D4 | 14.07 & newer | 15.05.1 | Full support, eth/wireless/leds/buttons ok. Workarounds for d3; Forum; Connection resets |
| D5 | Lede 17.01 & newer | 17.01.4 LEDE Project (Based on OpenWrt) | |
| E1-E5 | 10.03 & newer | E1-E3 15.05.1 или E4-E5 15.05.1 | (Works with DIR-600 rev. A1 firmware)*, LEDs should work since R29973, support for E4 merged with DIR-600 A1 in R29976 |
| H1/H2 | 12.09 & newer | 15.05.1 | Working as of R36213 |
| I1 | 15.05.1 | 15.05.1 | See Forum |
| I3 | 15.05.1 | 15.05.1 | See Forum |
* You might have to change the magic number at the end of the OpenWrt firmware to the one used by the stock DIR-615 firmware to get it to upload.
| Revision | Model Specific Notes |
|---|---|
| A1? | |
| B2 | Ubicom & SPI Flash with 2 MB only |
| D5 | Use LEDE project firmware |
| F1, F2 | SPI Flash with 2 MB only |
| J1 | Realtek RTL8196C & SPI Flash with 2 MB only |
| T1 | Realtek RTL8196E & SPI Flash with 2 MB only |
| Revisions | CPU | Ram | Flash | Network | Gigabit | USB | Serial | JTag |
|---|---|---|---|---|---|---|---|---|
| A1 | Marvell | 32MB | 8MB | 4x1 | No | No | Yes | Yes |
| B2 | Ubicom | 8MB | 2MB | 4x1 | No | No | Yes | Yes |
| C1, C2 | Atheros | 32MB | 4MB | 4x1 | No | Yes* | Yes | No |
| D1 - D5 | Ralink | 32MB | 4MB | 4x1 | No | No | Yes | No |
| E1, E2 | Atheros | 32MB | 4MB | 4x1 | No | Yes* | Yes | Yes |
| E3,E4,E5 | Atheros | 32MB | 4MB | 4x1 | No | Yes* | Yes | Yes |
| F1, F2 | Realtek | 16MB | 2MB | 4x1 | No | No | Yes | Yes |
| G1 | Ralink | 32MB | 8MB | 4x1 | No | No | Yes | ? |
| H1, H2 | Ralink | 32MB | 4MB | 4x1 | No | No | Yes | Yes |
| I1 - I3 | Atheros | 32MB | 4MB | 4x1 | No | Yes* | Yes | Yes |
| J1 | Realtek | 16MB | 2MB | 4x1 | No | No | Yes | Yes |
| K1 | Broadcom | 32MB | 4MB | 4x1 | No | No | No | Yes |
| K2 | Broadcom | 32MB | 4MB | 4x1 | No | Yes | Yes | ? |
| M1 | Realtek | 32MB | 4MB | 4x1 | No | No | No | Yes |
| M2 | Realtek | 32MB | 4MB | 4x1 | No | No | No | Yes |
| N1 | Realtek | 32MB | 4MB | 4x1 | No | ? | Yes | No |
| Q2 | Realtek | 32MB | 4MB | 4x1 | No | No | Yes | Yes |
| T1 | Realtek | 8MB | 2MB | 4x1 | No | ? | ? | ? |
*Hardware and software modifications required
Installation is fairly straight forward for this router, you will need to access the D-Link recovery console with the steps below.
openwrt-ar71xx-dir-615-c1-squashfs-factory.bin).
The firmware update system doesn't support the HTTP header Expect: 100-continue, which is used in POST requests by most modern browsers. If the browser sends this header, it will wait for the server to send a provisional response with status 100 Continue before sending the file contents. This feature was added in HTTP/1.1 to allow servers to reject uploads without needing to upload the file first. The router's built-in HTTP server claims to support HTTP/1.1, but it never sends the 100 Continue response so the browser waits forever or eventually times out.
Internet Explorer 6,7,8 on Windows, Firefox 13 Portable Edition on Windows 7, Google Chrome 49 on Windows 7 are known to work.
On GNU/Linux, Firefox 13.0.1 has happened to work. Problems have been reported with newer versions and most other browsers.
There seems to be some compatibility issues with the firmware update system network stack and at least Linux 3.5.3 and curl 7.27.0. Even forcing curl down to HTTP/1.0 resulted in a hang. One known working configuration is NetBSD 5.1.2 with curl 7.26.0. Downgrading curl to 7.26 on fresh version of GNU/Linux doesn't solve the issue.
Alternatively, to upload an image you might try to use the curl command-line HTTP client like so:
curl -0vF files=@openwrt-ar71xx-dir-615-c1-squashfs-factory.bin http://192.168.0.1/cgi/index
Same actions(C1 and C2 have same hardware and openwrt image), but to upload openwrt image in recovery mode, you must to edit C1 openwrt image by hex editor.
Just add 30 31 before lastest not zero values:
D1, D2 and D4 works now fully out of box.
Wireless Repeater function dos not work! however Client mode works fine. (Maybe attached another router on the LAN ports for WiFi woth another subnet????)
Installaion/Flashing Guide for D2 (Chaos Calmer 15.05.1) may work on D1-D4
Works with the latest Chaos Calmer 15.05.1 (2015) build.
D4
: D4 build instructions |
Updated D4 install instructions (AArc2) are here: https://forum.openwrt.org/viewtopic.php?id=35184
: The DIR-825 has a better description: installation. |
As of R36213 this router no longer needs a custom build. The following only applies to older revisions.
Requires at minimum a customized /etc/config/network. If you have a working network with DHCP server you can put the following in your /etc/config/network (you have to edit via serial connection for the first time or have a custom build with the modified /etc/config/network):
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config interface 'lan'
option ifname 'eth0'
option hostname 'DIR-615_H1'
option proto 'dhcp'
Now you should be able to telnet to DIR-615_H1
This documentation refers to current trunk of 03.04.2013. Instead of using the above procedure, you can build the image following the next steps. It will create a working image with dhcp on wan and fixed ip 192.168.0.1 on lan.
- Download current trunk. I've downloaded it from git mirror:
git clone git://nbd.name/openwrt.git- Add the file "target/linux/ramips/rt305x/profiles/d-link.mk" with content (ref:DIR-615 H1 current sources):
#
# Copyright (C) 2012 OpenWrt.org
#
# This is free software, licensed under the GNU General Public License v2.
# See /LICENSE for more information.
#
define Profile/DIR615H1
NAME:=DIR-615 H1
PACKAGES:=\
kmod-usb-core kmod-usb-ohci \
kmod-usb2 kmod-ledtrig-usbdev \
usb-modeswitch usb-modeswitch-data \
kmod-usb-serial-option
endef
define Profile/DIR615H1/Description
Package set for DIR-615 H1
endef
$(eval $(call Profile,DIR615H1))
- edit file "target/linux/ramips/base-files.mk", remove the line :
rm -f $(1)/etc/config/network- Edit the file "package/base-files/files/etc/config/network" with the settings you want. For example:
# Copyright (C) 2006 OpenWrt.org
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config interface 'lan'
option ifname 'eth0.1'
option type 'bridge'
option proto 'static'
option ipaddr '192.168.0.1'
option netmask '255.255.255.0'
config interface 'wan'
option ifname 'eth0.2'
option hostname 'DIR-615-H1'
option proto 'dhcp'
config switch
option name rt305x
option reset 1
option enable_vlan 1
config switch_vlan
option device rt305x
option vlan 1
option ports '0 1 2 3 6t'
config switch_vlan
option device rt305x
option vlan 2
option ports '4 6t'
- In case you have already build something make a dirclean
make dirclean- Configure the image:
make menuconfig
Target System (Ralink RT288x/RT3xxx) Subtarget (RT305x based boards) Target Profile (DIR-615 H1)- Build the image:
make -j 5
Revisions D1 to D4, H1 as well as I1 are pretty much unbrickable as they have a built-in firmware recovery mode. Revision D5 does not have built in recovery.
To access, simply hold down the reset button while powering on the router. The power LED should blink orange. Set your computer with a static IP in the 192.168.0.x range, and open 192.168.0.1 in a web browser. Recovery mode loads up within a few seconds, but doesn't respond to pings. If the power LED is blinking orange the above page should be accessible.
You will need to flash either a stock firmware image or Openwrt-factory image, *not* a sysupgrade image.
Since this part is identical for all devices, see Basic configuration.
→wireless.overview This router requires the packages kmod-ath9k and wpad-mini.
Numbers 0-3 are Ports 1-4 as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don't be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth0.0, vlan1 = eth0.1 and so on.
| Port | Switch port |
|---|---|
| Internet (WAN) | 4 |
| LAN 1 | 3 |
| LAN 2 | 2 |
| LAN 3 | 1 |
| LAN 4 | 0 |
add revisions
| Architecture: ? |
| Bootloader: ? |
| System-On-Chip: Ubicom IP5090U |
| CPU Speed: ? |
| Flash-Chip: Spansion S25FL016 |
| Flash size: 2 MiB (2Mx8) |
| RAM-Chip: PoinTec PT460816HG / Mira P2S28D40CTP |
| RAM size: 8 MiB (2x4Mx16) |
| Wireless: AR5008 2.4ghz b/g/n |
| Ethernet: Marvell 88E6060 |
| USB: 1x header on PCB, unpopulated |
| Serial: Yes |
| JTAG: Yes |
| Architecture: MIPS |
| Bootloader: U-Boot |
| System-On-Chip: Atheros AR9130 |
| CPU Speed: 400 Mhz |
| Flash-Chip: W25x32vf1g |
| Flash size: 4 MiB |
| RAM-Chip: Winbond W9425G6EH-5 |
| RAM size: 32 MiB (4M x 4 x 16bit) |
| Wireless: AR9102 802.11n Radio |
| Ethernet: AR8216 6-port switch |
| USB: 1x right-angle receptacle footprint on PCB, unpopulated |
| Serial: Yes |
| JTAG: Yes |
| Circuit: Dir615C1 |
| Architecture: MIPS |
| Bootloader: U-Boot |
| System-On-Chip: Ralink RT3052F Rev 2 on D1/D2, Rev 3 on D3/D4 |
| CPU Speed: 384 Mhz |
| Flash-Chip: MX29LV320DBTI-70G |
| Flash size: 4 MiB |
| RAM-Chip: 2 x w9812g6ih |
| RAM size: 32 MiB (2 x 2M x 4 x 16bit) |
| Wireless: SoC integrated |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: No |
| Architecture: MIPS |
| Bootloader: Unknown |
| System-On-Chip: Ralink RT3352F |
| CPU Speed: 400 Mhz |
| Flash-Chip: ESMT F25l32PA |
| Flash size: 4 MiB |
| RAM-Chip: ESMT M14D2561616A |
| RAM size: 32 MiB (4M x 4 x 16bit) |
| Wireless: SoC integrated |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: No |
| Architecture: MIPS |
| Bootloader: U-Boot |
| System-On-Chip: Atheros AR7240 |
| CPU Speed: 400 Mhz |
| Flash-Chip: mx25l3205 |
| Flash size: 4 MiB |
| RAM-Chip: W9425G6EH |
| RAM size: 32 MiB (4M x 4 x 16bit) |
| Wireless: AR9283 802.11n Radio |
| Ethernet: - (cpu direct) |
| USB: 1x right-angle receptacle footprint on PCB, unpopulated |
| Serial: Yes |
| JTAG: Yes |
| Architecture: MIPS |
| Bootloader: U-Boot |
| System-On-Chip: Atheros AR7240 |
| CPU Speed: 400 Mhz |
| Flash-Chip: MX25L3205 |
| Flash size: 4 MiB |
| RAM-Chip: A3S56D40ETP |
| RAM size: 32 MiB (4M x 4 x 16bit) |
| Wireless: AR9287 802.11n Radio |
| Ethernet: - (cpu direct) |
| USB: 1x right-angle receptacle footprint on PCB, unpopulated |
| Serial: Yes |
| JTAG: Yes |
| Architecture: MIPS |
| Bootloader: U-Boot |
| System-On-Chip: Ralink RT3052F |
| CPU Speed: 384 Mhz |
| Flash-Chip: MX29LV640ETBI-70G |
| Flash size: 8 MiB |
| RAM-Chip: 2x w9812g6ih |
| RAM size: 32 MiB (2 x 2M x 4 x 16bit) |
| Wireless: SoC integrated |
| Ethernet: SoC integrated |
| USB: Unknown |
| Serial: Yes |
| JTAG: Unknown |
| Architecture: Mips24kc |
| Bootloader: U-Boot |
| System-On-Chip: Ralink RT3352 |
| CPU Speed: 400 Mhz |
| Flash-Chip: mx25l3205d |
| Flash size: 4 MiB |
| RAM-Chip: 2 x ESMT M12L128168A 166 MHz |
| RAM size: 32 MiB (2 x 2M x 16bit x 4 banks) |
| Wireless: SoC integrated |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: Yes |
| Architecture: Mips24kc |
| Bootloader: U-Boot |
| System-On-Chip: Atheros AR9341 rev 1.1 |
| CPU Speed: 535 Mhz |
| Flash-Chip: mx25l3206d |
| Flash size: 4 MiB |
| RAM-Chip: 1 x W9425g6JH-5 |
| RAM size: 32 MiB (2 x 2M x 16bit x 4 banks) |
| Wireless: SoC integrated |
| Ethernet: SoC integrated |
| USB: 1x right-angle receptacle footprint on PCB, unpopulated |
| Serial: Yes |
| JTAG: Yes |
| Architecture: RLX4181 |
| Bootloader: ? |
| System-On-Chip: Realtek RTL8196C |
| CPU Speed: ? |
| Flash-Chip: Winbond 25Q16BVSIG |
| Flash size: 2MB |
| RAM-Chip: Winbond W9812G6JH-6 |
| RAM size: 16 MiB (2M x 16bit x 4 banks) |
| Wireless: Realtek RTL8192CE |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: Yes |
| Architecture: MIPS 74K V4.9 |
| Bootloader: CFE |
| System-On-Chip: Broadcom BCM5357C0 |
| CPU Speed: 300 Mhz |
| Flash-Chip: Macronix MX25L3206EMI-12G |
| Flash size: 4MB |
| RAM-Chip: 1 x W9425g6JH-5 |
| RAM size: 32 MiB (2M x 16bit x 4 banks) |
| Wireless: Broadcom BCM5357C0 |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: No |
PCB has "1DIR620C1.A1G" and "1DIR615K2.A1G" check-boxes (neither was ticked on mine DIR-615).
| Architecture: ? |
| Bootloader: ? |
| System-On-Chip: ? |
| CPU Speed: ? |
| Flash-Chip: Macronix MX25L3206EMI-12G |
| Flash size: 4MB |
| RAM-Chip: 1 x W9425g6JH-5 |
| RAM size: 32 MiB (2M x 16bit x 4 banks) |
| Wireless: ? |
| Ethernet: SoC integrated |
| USB: P7 (unpopulated micro-USB) |
| Serial: JP1 (unpopulated header - UART) |
| JTAG: ? |
| Architecture: RLX4181 |
| Bootloader: ? |
| System-On-Chip: Realtek RTL8196C |
| CPU Speed: ? |
| Flash-Chip: Winbond 25Q32BVSIG |
| Flash size: 4MB |
| RAM-Chip: Winbond W9825G6JH-6 |
| RAM size: 32 MiB (4M x 16bit x 4 banks) |
| Wireless: Realtek RTL8192CE |
| Ethernet: SoC integrated |
| USB: No |
| Serial: ? |
| JTAG: Yes |
| Architecture: ? |
| Bootloader: ? |
| System-On-Chip: Realtek RTL8196C |
| CPU Speed: ? |
| Flash-Chip: Winbond 25Q32BVSIG |
| Flash size: 4 MB |
| RAM-Chip: 1 x Winbond W9825G6JH-6 |
| RAM size: 32 MiB (4M x 16bit x 4 banks) |
| Wireless: Realtek RTL8192CE |
| Ethernet: SoC integrated |
| USB: No |
| Serial: No |
| JTAG: Yes (12 Pin) |
| Architecture: RLX5821 |
| Bootloader: ? |
| System-On-Chip: Realtek RTL8196D |
| CPU Speed: ? |
| Flash-Chip: 25L3206E |
| Flash size: 4MB |
| RAM-Chip: ESMT M13S2561616A-5T |
| RAM size: 32 MiB (4M x 16bit x 4 banks) |
| Wireless: Realtek RTL8192ER |
| Ethernet: SoC integrated |
| USB: ? |
| Serial: Yes |
| JTAG: No |
| Architecture: ? |
| Bootloader: ? |
| System-On-Chip: Realtek RTL8196E |
| CPU Speed: ? |
| Flash-Chip: MX25L3206E |
| Flash size: 4 MB |
| RAM-Chip: winbond W9825G6JH-6 |
| RAM size: 32 MB (4 M x 4 banks x 16 bits sdram) |
| Wireless: Realtek RTL8192ER |
| Ethernet: SoC integrated |
| USB: No |
| Serial: Yes |
| JTAG: Yes |
More info, please!
| Revision | Photos page | Comment |
|---|---|---|
| C1/C2 | dir-615/c1-photos/start | This is rev.C2 device photo, but board rev C1! |
| D1 | dir-615/d1-photos/start | Mira DDR memory chips (instead of Winbond) |
| D2 | dir-615/d2-photos/start | Wireless, cpu are unshielded |
| D3 | dir-615/d3-photos/start | Wireless, cpu are unshielded, revD3E |
| D4 | dir-615/d4-photos/start | Wireless, cpu are unshielded |
| E3/E4/E5 | dir-615/e4-photos/start | Wireless, cpu and memory are unshielded on this photo |
| F1/F2 | dir-615/f1-photos/start | This is rev.F1/F2 device photo |
| H1 | dir-615/h1-photos/start | Shield removed |
| H2 | dir-615/h2-photos/start | As-is |
| K1 | OpenWrt forum | Wireless, cpu and memory are unshielded on this photo |
| M1 | dir-615.rev.m1.jpg | As-is |
| Q2 | photo | As-is |
Note: This will void your warranty!
| Pin1 | TX |
| Pin2 | GND |
| Pin3 | 3.3V |
| Pin4 | RX |
D2 Serial port settings: Speed:57600, Data bits:8, Stop bits:2, Parity: none, Flow control: none
Warning: above picture very likely wrong, i.e. TX and RX swapped. Table below is correct for E3, i.e. Pin3 is RX and Pin9 is TX.
| Pin1 | 3.3V |
| Pin2 | 3.3V |
| Pin3 | RX |
| Pin9 | TX |
| Pin11 | GND |
| Pin12 | GND |
Remember to use 12V ↔ 3.3V serial port converter or you might break the router serial pins by overvoltage.
COM port settings: Speed:115200, Data bits:8, Stop bits:1, Parity:none, Flow control:none
| Pin1 | 3.3V |
| Pin2 | RXD |
| Pin3 | TXD |
| Pin4 | GND |
| Pin1 | 3.3V |
| Pin2 | GND |
| Pin3 | TXD |
| Pin4 | RXD |
Serial port settings: Speed:57600, Data bits:8, Stop bits:2, Parity: none, Flow control: none
| Pin1 | 3.3V |
| Pin2 | TXD |
| Pin3 | GND |
| Pin4 | RXD |
COM port settings: Speed:115200, Data bits:8, Stop bits:1, Parity:none, Flow control:none
Remember to use 12V ↔ 3.3V serial port converter or you might break the router serial pins by overvoltage.
Looks like C1/C2 JTAG lines connected to testpoints tp5-tp8. Pinout is unknown.
Adding JTAG to C1 not easy as some other revisions but should be possible:
E1/E2/E3/E4 has standard MIPS EJTAG JTAG 14-pin header pinout (pic is from E4)
I1 has same footprint and apparently pinout as E1-E4 but still not fully verified.
See port.jtag for more JTAG details.
| HW Revision | Instruction | Discussion |
|---|---|---|
| C1/C2 | RevC1 USB mod | D-Link DIR-615 HW rev C1 USB |
| E1-E4 | RevEx USB mod | Dlink DIR-615 Revision E1 |
All C1/C2, E1-E4 and I1 share the same empty footprints and hole in plastic case (except for sticker) for adding cleanly USB support.
22-ohm resistors are for impedance matching of the characteristic impedance of the transmission line in the case of high-speed USB for signal integrity at 480Mbps. The single-ended impedance of the line is in theory 45 ohms but the transceiver has an output impedance too that is added to the 22-ohm resistor. For full-speed (12Mbps) or low-speed (1.5Mbps) communication, these resistors are not mandatory. For reasons like not having the required 0603 22-ohm surface mount resistors or skill required to solder them and if you plan on using only full-speed and low-speed USB devices, you might decide to replace these resistors with pieces of wire-wrap wire, which are easier to solder than 0603 resistors.
For high-speed, full-speed and low-speed USB, a host has to provide 15k pull-down resistors on D+ and D- lines. E1-E4 and I1 revisions have 0603 footprints for these pull-down resistors. C1/C2 revisions do not have footprints for these pull-down resistors. If you do not have 0603 resistors, the skill required to solder them or not the footprints for soldering, you may want instead use through-hole resistors soldered on the bottom side of the USB receptacle footprint.
Since the DIR-615 uses a +5 V power supply (from 1 A to 2.5 A according to the revision), one can use it as is to power the USB device. Although this is not good practice. USB hosts have normally some protection from excessive current drawn by the device. This protection shuts down the VBUS supply when a given current threshold is reached.
Revision C1
U4 fooprint is for a dual USB high-side power switch partnumber G526-1 or G526-2 by Global Mixed-mode Technology Inc. Datasheet links: long one single page. These parts are obsolete. Good luck finding them. A pinout compatible and mostly similar in terms of electrical characteristics is MIC2076A-2YM.
A list of possibly matching USB type A vertical right-angle receptacles (verify footprint with datasheet and measurements on board before ordering):
Example to extract info from the first link in the list:
Manufacturer: amphenol-fci
Manufacturer Part Number: 73725-0110BLF
The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/8=32MiByte) 400MHz chip Zentel A3S56D40FTP. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. One of the ways to get them is to have a look at DDR SO-DIMM (because SO-DIMM modules are shipped with x16 chips). Since there are no 64Mbit x 16bit DDR1 Chips available → no 128 MB mod!
The most easy approach is to seek for a 4-chip DDR 256 MB module. These all have x16 chips too. Chips only on one side (not to be confused with double-sided 256 MB modules with 4 chips on each side) and only 4 of them - that's the best chance to get some. They represent a small percent among usual 8-chip modules but this is equalized with the amount and "cheap as dirt" price of such DDR 256 MB modules.
Working chips:
Additional list that may work:
| Type | ID Code | Vendor | ||
|---|---|---|---|---|
| DDR | 32Mx16 | DDR 400 TSOP Pb Free | HY5DU121622DTP-D43-C | Hynix |
| DDR | 32Mx16 | DDR 400 TSOP Pb Free | H5DU5162ETR-E3C | Hynix |
| DDR | 32Mx16 | DDR 400 Pb Free | K4H511638G-LCCC | Samsung |
| DDR | 32Mx16 | DDR 400 | A3S12D40ETP-G5 | Zentel |
| DDR | 32Mx16 | DDR 400 | NT5DS32M16BS-5T | Nanya |
| DDR | 32Mx16 | DDR 400 PB Free | P3S12D40ETP-GUTT | Mira |
| DDR | 32Mx16 | DDR 333 CL2.5 TSOP | MT46V32M16TG-6T:F | Micron |
| DDR | 32Mx16 | DDR 333 CL2.5 TSOP | MT46V32M16P-6T:F | Micron |
| DDR | 32Mx16 | DDR 333 PB Free TSOP | HYB25D512160CE-6 | Qimonda |
| DDR | 32Mx16 | DDR 333 PB Free TSOP | HYB25D512160CEL-6 | Qimonda |
| DDR | 32Mx16 | DDR 333 PB Free TSOP | HYB25D512160DE-6 | Qimonda |
By default router able to see all 64MB.
Used only next chips:
W25Q128FVSSIG
MX25L12835FM2I
S25FL128P
Uboot and Kernel patches for 16MB Flash External Link
Take some GPIOs which are connected to LEDs or switches, 3.3V and GND from the JTAG header and use the mmc-over-gpio kernel module. The kmod-leds-gpio and kmod-input-gpio-keys-polled kernel modules have to be unloaded before. The blue WPS LED will show when the SD-Card is being accessed and the power LEDs will flicker while data is being transfered.
| GPIO # | Original use | SD signal | SD pin |
|---|---|---|---|
| 0 | WPS button | MISO | 7 |
| 7 | Power LED amber | MOSI | 2 |
| 9 | Power LED green | SCK | 5 |
| 14 | WPS LED blue | /SS | 1 |
| +3.3V | +3.3V | 4 | |
| GND | GND | 3 | |
| GND | GND | 6 |
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.
NOTE: The root file system in failsafe mode is the SquashFS partition which is always readonly. To switch to the writable root file system (JFFS2) run mount_root command and make your changes.
passwduci get network.lan.ipaddropkg upgrade or filled up the flash by installingmtd -r erase rootfs_dataWhen you are done with failsafe mode - power cycle the router and let it boot normally.
See also:
The D-Link DIR-615 has two buttons. They are WPS and RESET. The WPS button has its own blue led.
The buttons can be used with hotplug events. E. g. wifitoggle.
| BUTTON | Event |
|---|---|
| RESET | reset |
| WPS | wps |
How to configure LEDs in general, see the LED section in the Wiki.
Rev C: The DIR-615c2 has 1 blue, 3 green and 2 orange controlled LEDs:
| LED name | LED symbol | Internal name |
|---|---|---|
| Power (green) | Power | dir-615c1:green:status |
| Power (orange) | Power | dir615c1:orange:status |
| WPS (blue) | Refresh | dir-615c1:blue:wps |
| Wan (green) | Globe | dir-615c1:green:wan |
| Wan (orange) | Globe | dir-615c1:orange:wan |
| Wlan (green) | Waves | dir-615c1:green:wlan |
Rev H1: The same LED configuration applies to Rev H1.
Revision C2 has 6 free (non-used) GPIO ports. To use them you should do some solder work. Please train you solder skills on broken motherboards before trying to do this on working hardware.
| GPIO # | Notation | Location |
|---|---|---|
| 0 | R127 | unpopulated resistor pad near LED21, pcb bottom left corner |
| 2 | R2 | unpopulated resistor pad to the left of the CPU |
| 7 | R203 | unpopulated resistor pad near LED20 near gpio0 |
| 8 | tp5 | testpoint on the bottom side of pcb near cpu |
| 9 | tp6 | testpoint on the bottom side of pcb near cpu |
| 11 | tp7 | testpoint on the bottom side of pcb near cpu |
There is also one free GPIO5 used by dir-615c1:green:wancpu led interface. This led interface is useless so we can just desolder r218 (located between q7 transistor and led10), remove led definition from mach-dir-615-c1.c recompile/reflash kernel and use GPIO5 as we want.
To activate GPIO interface you should export it using command 'echo N > /sys/class/gpio/export' (N is a GPIO number). Then you can use /sys/class/gpio/GPION interface to control GPIO (set/get direction, value, etc). Also you can use i2c_gpio_custom/w1_gpio_custom kernel modules for 1wire/i2c protocols over gpio to connect devices/sensors/actuators to your router.