OpenWrt Forum Archive

Topic: Dir-601 B1

The content of this topic has been archived between 3 Feb 2018 and 1 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

First off, I really appreciate everyone that is involved in regards to make OpenWRT work on the B1 version of this router.
I have very simple questions respectfully, please.
I have downloaded all of the following .bin files that Mr. Jalopicus posted on google drive (Thank You Sir!).
Which one of the following should I install from the DLink web interface?
openwrt-ar71xx-generic-dir-601-b1-squashfs-factory-NA
openwrt-ar71xx-generic-dir-601-b1-squashfs-factory
openwrt-ar71xx-generic-dir-601-b1-squashfs-sysupgrade

The only main function that I need, is the ability to use the router as a wireless repeater bridge, so I can extend the reach of my wireless workstations, to my main WAP.
From some of the videos on YouTube that I see, it looks like OpenWRT has that functionality, like DD-WRT does.
If someone could please answer those questions, it would make the upcoming holiday truly bright. :-)
Thank You, Happy Holidays! - Happy Tom :-)

(Last edited by HappyTom on 21 Dec 2013, 20:49)

Jalopicus wrote:

Here's a build I compiled last night for my DIR-601 B1.  I have pretty simple needs so it's basically the default config plus Luci, QOS, and UPNP.

I was able to flash with the D-Link web interface and then got right in via Luci with no problem.  I set everything up and haven't had any issues yet except that the status page claims that the router is a TEW-712BR (it isn't).

Hostname    OpenWrt
Model    TRENDnet TEW-712BR
Firmware Version    OpenWrt Barrier Breaker r38971 / LuCI Trunk (svn-r9934)
Kernel Version    3.10.18

Not sure what to make of this, but no adverse effects so far.

So, I got the sources downloaded and even the base configuration for the DIR-601 B1 to compile correctly and work when flashed, but I can't figure out what I can safely remove in order to get Luci to fit. I also need OpenVPN and the tun module installed, and that's it.

Do you happen to know what packages you omitted, or got the .config file you created that you can share with us?

I can get openvpn to compile in w/o Luci, and not having the web interface isn't a dealbreaker, but I would prefer to have it. Any help is appreciated.

Thanks!

HappyTom wrote:

First off, I really appreciate everyone that is involved in regards to make OpenWRT work on the B1 version of this router.
I have very simple questions respectfully, please.
I have downloaded all of the following .bin files that Mr. Jalopicus posted on google drive (Thank You Sir!).
Which one of the following should I install from the DLink web interface?
openwrt-ar71xx-generic-dir-601-b1-squashfs-factory-NA
openwrt-ar71xx-generic-dir-601-b1-squashfs-factory
openwrt-ar71xx-generic-dir-601-b1-squashfs-sysupgrade

The only main function that I need, is the ability to use the router as a wireless repeater bridge, so I can extend the reach of my wireless workstations, to my main WAP.
From some of the videos on YouTube that I see, it looks like OpenWRT has that functionality, like DD-WRT does.
If someone could please answer those questions, it would make the upcoming holiday truly bright. :-)
Thank You, Happy Holidays! - Happy Tom :-)

I too am a normal DD-WRT user, but I am new to OpenWRT. However, that said, I used the openwrt-ar71xx-generic-dir-601-b1-squashfs-factory-NA image when I tried it and it works. I am not sure what the difference is between them.

knightcrusader wrote:

I too am a normal DD-WRT user, but I am new to OpenWRT. However, that said, I used the openwrt-ar71xx-generic-dir-601-b1-squashfs-factory-NA image when I tried it and it works. I am not sure what the difference is between them.

Thank You knightcrusader, I will try image, when I get the unit. Does that firmware enable the router in regards to "wireless repeater bridge" mode? I think Open WRT calls it "Routed Client Mode".. at least what I see here in the link below,
this is my goal.. to have the 601 relay the wireless signal as a repeater to the main AP in my house:
http://wiki.openwrt.org/doc/howto/clientmode

Thank You for your help, and I really wish you and everyone else here.. a great upcoming holiday!
Happy Tom :-)

(Last edited by HappyTom on 24 Dec 2013, 20:11)

antiflag1980 wrote:

Thanks Jalopicus! I will try this and report back when I get a chance.  As far as the model thing, I've been using one of the Luci builds that was posted in this thread for 6 months now and it's been working great, but this is what it reports:

Model    TRENDnet TEW-712BR
Firmware Version     OpenWrt Barrier Breaker r36935 / LuCI Trunk (svn-r9842)
Kernel Version    3.8.13

So I don't think the wrong model reporting makes any difference.

I guess I forgot to report back, build works great, thanks!

https://drive.google.com/folderview?id= … sp=sharing

(Last edited by antiflag1980 on 14 Mar 2014, 00:23)

WARNING WARNING WARNING

Okay I had to get an account to even post this.

After enough goofing around trying to find out some information on this router (DLink 601B1), this is the site that keeps coming up in online seaches and I have tried to read and work through this mess of a thread for a while now.

There have been links to various binary's and NO CLEAR confirmation that any particular one IS THE GOTO binary to flash this router with! Besides unsuccessful uploads (even reported as being unsuccessful here) there are even binaries with NONSTANDARD log ins and passwords. And then no courtesy of the posters here to even report what passwords they used in their builds.

There is no doubt that I am not the only one that has one of these routers and was looking for some open source firmware for it. The confusion (and lack of manufacture clarity on which version is in the box until you open it - re:version A1 or B1) has waisted enough of my time trying to find something that works. As well as time trying to understand the confusion of a thread like this. Some binaries load but are still useless. Posters that asked for some basics got completely skipped over while the group want to talk about serial connections and usb support. (oh wow ... dah!) 

The manufacture was able to have a web GUI by default on this router, yet all of the tweakers here don't seem to have enough space to build that into their flashes. And beyond that, the use of none standard log ins and passwords seems like a simple oopsie. (too bad they didn't spend the time to clarify that when they posted a link to their personal favorite)

telnet is closed ... ssh works ... maybe (if you can guess the password) ... GUI .. naw ... what network does it boot too? (you guess)

All in all, I am very dissappointed in both the faking in believing open wrt had a simple solution for this router and the lack of clarification of much by the posters on this thread here. I don't see how much of what is written here is of much use to the unregistered visitors. I guess you gotta be in the click of open wrt experts to understand (and guess what passwords they use).

If you aren't an open wrt EXPERT, I would leave this router alone in stock form.

Someone please clean up this thread with some clarifications ... or the only thing I can say isi good luck to newbies. Your are pretty much on you own. (enjoy reading the manual for openwrt - i am sure it is a good read - but i don't feel like it myself)

I will not become a fan of openwrt, that is for sure. After this experience.

I just managed to upgrade to the latest trunk build from http://downloads.openwrt.org/snapshots/ … grade.bin. I used sysupgrade to come from a previous build on this thread. I did lose luci since it's not included, and the simple "opkg install" method to install doesn't work as /overlay doesn't have enough space. Not really a big deal, especially as you can preserve your configs and everything networking wise will still work.

Again. Someone pops by, posts some info about a ghost and doesn't say much.

The link is broken. I know what file is being refered to here.

It's great that you claim to have managed to do something. But sharing the how - would show us.

This is still a broken thread with no real flash.

notgood wrote:

This is still a broken thread with no real flash.


have some grease

(Last edited by squeakywheel on 29 Mar 2014, 20:02)

Hello guys.

Im happy I finally could install the firmware in my device. Nonethless, I would like to now how I can build a vpn service into de OpenWrt.

The specific problem Im having, is that It seems I dont have enough space. I try to remove certain packages, but It happens that even more space is taken after removing such packages... I dont know what to do to regain more space in my device.

Can anyone help, please???

btw, what's the best vpn package I can get t install; i would like to get the more automated, graphical one to use with ipvanish... any ideas?

(Last edited by goniak on 30 Mar 2014, 08:48)

--- BLAH BEGINS ---

Hi, I just picked up a free DIR-601 B1 the other day and promptly A) flashed it with openwrt (courtesy of jay0lee) then promptly bricked it while trying to install a trunk version from the router's CLI. At least I think that's when I bricked it, I got a flash error, can't remember what it said...anyhow, I have a serial port, and using a cp2102 could at least read the boot message which shows u-boot which freezes on Bad Magic Number with accompanying command prompt. Fine, bootloader seems intact.

Unfortunately the router is not accepting any commands. To add to my incompetent string of Keystone Cops type antics, I had previously "modded" the cp2102 by removing the Rx LED in order to accommodate a 1.8v shifter circuit to use with a kijiji purchased dead kindle ( which I would like to smash into little bits but I got it for my mother so I am waiting for a replacement board...). So anyhow, I figure that is causing my present woes. Add to that I just fried the cp2102 by crossing the GND and data lines...FTDI board in the mail!

--- BLAH ENDS ---

So,

Q1: Has anyone managed to send commands via the serial console?

I am hoping that I haven't fried the router's RX port, just the cp2102.

Q2: Does anyone know of a target specific debrick ( ie the proper hex addresses in the flashing process, etc...still studying the docs )

I'm kind of surprised there hasn't been more info put out on these routers, I guess it's not as popular as the other revs/models?

Thanks!

(Last edited by lobonse on 7 Apr 2014, 18:01)

Update: Just tested one data line without the other connected and I got the u-boot process.

uvray313 said: "The front pad is TX, the middle ground, and the rear (next to the square pad) is RX."

This is incorrect, the TX is definitely next to the square pad, and so far the other line isn't accepting CLI. So the actual pinout I have now is:

[] O O O = NULL - TX - GND - ?

The ? pin shows a full 3.3v, TX shows around 2.7v after boot. I am using an UNO as the USB-TTL converter with some 10k resistors. Voltage on the UNO's TX is 3.2v or so, UNO RX reads the bootup just fine. Anyone concur/have any ideas?

Thanks!

(Last edited by lobonse on 7 Apr 2014, 19:17)

On study of a closeup image of the serial pads I noticed that the two traces which go fairly directly to the UART_SIN and UART_SOUT pins on the ar9331 are connected to these pads->  [] O O O = "trace - trace -  GND - BIG trace" ie power ( which gels with my previous measurement of 3.3v on the pad - it might also explain why the cp2102 got hot enough to burn my fingers! Mmm, ozone).

DIR-601 B1 serial pads

This image shows my old configuration. Notice the wide trace on the board leading to the red wire, which is now on the square [] pad. The green wire is definitely TX and black is definitely GND.

DIR-601 B1 Red wire changed

Red wire changed to square pad.

It's hard to see the full trace ends as the white labelling covers a lot of it, but when I zoom in on the square pad, the trace is quite noticeable.

DIR-601 B1 serial pinout?

It appears that R174 on the right is a pull-down( or is it pull-up? ) resistor that is part of a voltage divider circuit (4k on R173, 3k on R174). How this helps me is unknown.

So from what I see the pads are now

[] O O O = RX - TX - GND - Vcc

Sadly, RX still doesn't do anything. I tried a loopback test on the arduino rx/tx - before the pads - working fine. So I figure that assuming the RX line is not fried, either the router doesn't like the arduino signal, or the trace isn't touching the pad. I really studied the RX and TX traces all the way from the chip to the pads, there can be no mistake there. I suppose other possibilities might include the RX line is deactivated in code or there is no write access? I will have to wait now for the FTDI to arrive from China to confirm RX isn't working, unless some intrepid explorer grabs the ball...

I also tried (sudo) minicom, gtkterm, putty and miniterm.py, with RTS/CTS XON/XOFF NONE etc etc etc...

See you in a month!

(Last edited by lobonse on 21 Mar 2018, 13:36)

Success! I can now pass commands vial serial console. The 3.3V FTDI board was the ticket, although I imagine that any 3.3V USB to serial board would do. I can now confirm that for the DIR601 B1 the UART serial console pads are:

[] O O O = RX - TX - GND - Vcc

I am guessing the reason why people have abandoned this router ( other than it's old I guess ) is that there seems to be limited access to file transfer via U-boot commands:

fake   - fake
?       - alias for 'help'
boot    - boot default, i.e., run 'bootcmd'
bootd   - boot default, i.e., run 'bootcmd'
bootm   - boot application image from memory
cp      - memory copy
erase   - erase FLASH memory
eth_soft_led    - start the ethernet software led control
help    - print online help
httpboot- entering the backup mode.
md      - memory display
mm      - memory modify (auto-incrementing)
mtest   - simple RAM test
mw      - memory write (fill)
nm      - memory modify (constant address)
ping    - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
progmac - Set ethernet MAC addresses
reset   - Perform RESET of the CPU
run     - run commands in an environment variable
setenv  - set environment variables
tftpboot- boot image via network using TFTP protocol
version - print monitor version

There are no 'load' commands, only tftp seems to be available. Unfortunately, that is not working, even though the tftp server (host pc) is working, and eth1 (host pc, set up to 192.168.0.100) is apparently pinging fine from the router.

According to the wiki page http://wiki.openwrt.org/toh/d-link/dir-600:

"Loading an image via tftp may not work, arp replies do not seem to make it though the switch, these commands use y-modem instead."

However there is no loady option in the menu above.

I've also noticed that the Trendnet  TEW-712BR has a physical board and a U-boot setup that is quite close to this router. The RAM addresses are identical from what I see, but I know nothing about the proper "offsets" I guess they are called. Anyhow, that is moot at this point.

So, I've hit another wall. Anyone know whether there is a solution?

(Last edited by lobonse on 7 May 2014, 20:40)

Ok, so it turns out that I had to simply allow the ip address from the firewall. Awesome! Transferring files over serial works! I set up atftpd for the file server on the pc and used tftp from the router. Now I have to figure out all the hex addresses, what to "erase" etc.

(Last edited by lobonse on 7 May 2014, 09:57)

Right, so I've figured out the size of Jay0lee's dir-601b1.bin in hex, namely 0x390054 (3735636 bytes). So now I guess that I am left with the address. Using this as the example ( NOT CORRECT FOR THIS ROUTER DO NOT USE! ):

tftpboot 0x81000000 firm.bin
erase 0xbf020000 +0x7c0000
cp.b 0x81000000 0xbf020000 0x7c0000
bootm 0xbf020000

I assume I would replace 0x7c0000 ( I also assume this is what's called the offset? ) with 0x390054?
Also, where could I find the starting address?

If I type:

printenv bootcmd

I get bootcmd=bootm 0x9f070000. When I bricked the device I was trying to copy over a trunk image which was waaay too big, thus I suppose overwriting the existing image. If this address variable is what was left from that original openwrt image, would that be where I start erase?

I'm beginning to think nobody reads this thread tongue

(Last edited by lobonse on 7 May 2014, 20:36)

I just tried this:

tftpboot 0x80000000 dir-601b1.trx
erase 0x9f070000 +0x390034

I got this:

Bytes transferred = 3735604 (390034 hex)
ar7240> erase 0x9f070000 +0x390034
Error: end address (0x9f400033) not in flash!
Bad address format

Apparently printenv bootcmd isn't showing me the correct flash address...

lobonse wrote:

I just tried this:


Bytes transferred = 3735604 (390034 hex)
ar7240> erase 0x9f070000 +0x390034
Error: end address (0x9f400033) not in flash!
Bad address format

I think you need to trim the header.
see https://forum.openwrt.org/viewtopic.php … 66#p189566

(Last edited by squeakywheel on 8 May 2014, 00:40)

Yep, I had seen that one and thought after seeing the hex head output decided on trying bs=32 instead of 84. Thanks! I was about to try 0xbf070000 instead.

BusyBox v1.19.4 (2013-06-04 17:25:04 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
|       |.-----.-----.-----.|  |  |  |.----.|  |_
|   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
|_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
-----------------------------------------------------
BARRIER BREAKER (Bleeding Edge, r36848)
-----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
-----------------------------------------------------

SUCCESS!! Serial recovery is finished!

So, to recap I:

1) soldered a serial console on the board and used an FTDI USB to TTL converter ( 3.3V ) to connect to it

   [] O O O = RX - TX - GND - Vcc

Using sudo minicom -s or some other serial communications program, set up to 115200 baud, 8n1, hardware/software controls off, ttyUSB0 plug in router, watch boot up, hit key when prompted and from command prompt:

ar7240>

type printenv

You should see ipaddr=192.168.0.1 and serverip=192.168.0.100

Once you have ifconfig set up (step 5) and atftpd set up (step 6) tftpboot will do the rest from the router prompt.

2) used jay0lee's build here ( thank you btw ): https://googledrive.com/host/0B0YvUuHHn … -601b1.bin

3) converted the file to dir-601b1.trx (I am now guessing that the file is trimmed to the correct size for the flash space, therefore for this router it needs to be 390000 hex, or 3735522 bytes exactly.) and trimmed the header from the file as per here: https://forum.openwrt.org/viewtopic.php … 66#p189566
   
   dd bs=84 skip=1 if=dir-601b1.bin of=dir-601b1.trx

4) connected an ethernet cable from a router lan port to laptop ( I used an ethernet to usb converter since my ethernet port is borked )

5) set up a static ip address for laptop ethernet which gels with the default address for u-boot ( ifconfig eth0 192.168.0.100 up )

6) from u-boot console ping 192.168.0.100 ( should say 'host 192.168.0.100 is alive' )

7) set up atftpd ( or some other ftp daemon ) on laptop, making the directory /tftpboot and place dir-601b1.trx in it

**********************************************************************
******* WARNING: I assume the next step can brick your router if used carelessly *******
******* The values of 0x80000000 and 0x9f070000 are always the same for this *******
******* router, but 0x390000 is file size in hex, be sure your file is the right size!! *******
**********************************************************************

8) used the following commands on the router's u-boot console to download dir-601b1.trx, erase the flash, burn image and reboot:

   tftpboot 0x80000000 dir-601b1.trx
   erase 0x9f070000 +0x390000
   cp.b 0x80000000 0x9f070000 0x390000
   bootm 0x9f070000

The value of 0x390000 is the hexadecimal value of the filesize in bytes.

That's it.

I think next I will try making and uploading images. What the heck, I know how to unbork it now...

PS I got the POS kindle working too! Ma loves it.

PPS I also have to say that I am quite noob at this and still managed to find all of the pertinent information in this and other threads on this forum. I for one am very grateful for all the work done by others to get me this far. Great job folks.

(Last edited by lobonse on 24 May 2014, 19:36)

Interesting note, I had mentioned the similarity to the Trendnet  TEW-712BR...

root@OpenWrt:/# cat /proc/cpuinfo
system type             : Atheros AR9330 rev 1
machine                 : TRENDnet TEW-712BR

I'm back! Squeak squeak squeak! ( Not Squonk, that's blasphemy )

I compiled an image, sysupgraded and I've configured the router as wireless AP and bridge to internet router. What a pain, one thing I will happily complain about is networking configuration. I also tried to install packages from the internet, nano and luci, both of which succeeded. I don't know if that is smart.

Yes, I got luci working from packages, along with these errors:

Collected errors:
* verify_pkg_installable: Only have 12kb available on filesystem /overlay, pkg luci-app-firewall needs 57
* opkg_install_cmd: Cannot install package luci.

Memory:

root@OpenWrt:~# free
             total         used         free       shared      buffers
Mem:         29044        21940         7104            0         1688
-/+ buffers:              20252         8792
Swap:            0            0            0

root@OpenWrt:~# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  896.0K    820.0K     76.0K  92% /
/dev/root                 1.8M      1.8M         0 100% /rom
tmpfs                    14.2M    916.0K     13.3M   6% /tmp
/dev/mtdblock8          896.0K    820.0K     76.0K  92% /overlay
overlayfs:/overlay      896.0K    820.0K     76.0K  92% /
tmpfs                   512.0K         0    512.0K   0% /dev


However, the luci interface is working.

UPDATE: I removed luci and associated packages, since I couldn't even save a text file!

After removal:

root@OpenWrt:/tmp# free
             total         used         free       shared      buffers
Mem:         29044        20912         8132            0         1688
-/+ buffers:              19224         9820
Swap:            0            0            0

root@OpenWrt:/tmp# df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  896.0K    340.0K    556.0K  38% /
/dev/root                 1.8M      1.8M         0 100% /rom
tmpfs                    14.2M      1.1M     13.1M   8% /tmp
/dev/mtdblock8          896.0K    340.0K    556.0K  38% /overlay
overlayfs:/overlay      896.0K    340.0K    556.0K  38% /
tmpfs                   512.0K         0    512.0K   0% /dev

I also got an md5sum mismatch from another opkg download, so I've set up a local repository for my own compiled packages.
Lesson learned!

(Last edited by lobonse on 10 May 2014, 00:05)

I bought four of these off Amazon, thinking they would be hardware version A1. I tinkered around a little and finally found a use for them, as Dumb AP's!

Using the D-Link failsafe firmware recovery method, install this build:

http://downloads.openwrt.org/snapshots/ … ory-NA.bin

Once you see it reboot (at about 43% complete in the web UI upgrade counter) set your NIC back to DHCP and wait for an IP address.

This build of OpenWRT has no web UI, so using telnet in putty, connect to 192.168.1.1 and set a password with the passwd command. This will enable ssh access.

Next, use vi to edit /etc/config/wireless and delete the line that reads, "option disabled 1"

If your regular LAN also uses the 192.168.1.1 subnet, then edit /etc/config/network and change the static IP to something else. (for example, my router is 192.168.1.1 and my DHCP assigned addresses start at .100, so I set this unit to .99)

Run /etc/init.d.network reload and wireless will now be enabled. Plug in the WAN port to your LAN and the B1 device is now functioning as a full wireless router, with internet access.

From here, use this tutorial to set up the Dumb AP:

http://wiki.openwrt.org/doc/recipes/dumbap

For the network config, follow the subsection titled "For devices with switch and dedicated WAN, e.g. WNDR3700, WR1043ND v1"

**HOWEVER** don't set 'option proto' to dhcp, leave it as the static IP you set earlier. This will allow you to connect via SSH later to make wifi changes as needed. Follow the rest of the guide as written.

Once completed and the device restarted, you will have a working WAP that passes through DHCP from your main router.

To connect to the device later to make changes, unplug the WAN port and direct connect a PC to it. Manually set an IP on the PC to something other than what you assigned to the DIR-601. Set the subnet mask to 255.255.25.0 and the gateway to the IP of the DIR-601. Then you should be able to connect to the DIR-601 with ssh as root with the password set in the first step.

I have converted all 4 of mine and they are working great as cheap WAP's.

@corey.maddocks
Could you publish your \etc\config\network and \etc\config\wireless?  I have a lot of difficulties to reproduce the same setup.

Thanks in advance

Hi again, something new to add today, I got USB working! At first I was getting "unable to initialize libusb: -99" when I ran lsusb ( from usbutils package )

Now I get, with cheapo usb hub and thumb drive:

root@OpenWrt:~# lsusb
Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive

root@OpenWrt:~# dmesg
[   38.690000] usb 1-1.1: new high-speed USB device number 4 using ehci-platform
[   38.830000] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[   38.830000] scsi1 : usb-storage 1-1.1:1.0
[   39.840000] scsi 1:0:0:0: Direct-Access     LUXL     - V GOLD         1100 PQ: 0 ANSI: 0 CCS
[   39.850000] sd 1:0:0:0: [sda] 3962880 512-byte logical blocks: (2.02 GB/1.88 GiB)
[   39.860000] sd 1:0:0:0: [sda] Write Protect is off
[   39.860000] sd 1:0:0:0: [sda] Mode Sense: 43 00 00 00
[   39.860000] sd 1:0:0:0: [sda] No Caching mode page found
[   39.870000] sd 1:0:0:0: [sda] Assuming drive cache: write through
[   39.880000] sd 1:0:0:0: [sda] No Caching mode page found
[   39.880000] sd 1:0:0:0: [sda] Assuming drive cache: write through
[   39.890000]  sda: sda1
[   39.900000] sd 1:0:0:0: [sda] No Caching mode page found
[   39.910000] sd 1:0:0:0: [sda] Assuming drive cache: write through
[   39.910000] sd 1:0:0:0: [sda] Attached SCSI removable disk

Here's what worked for me:

SOFTWARE SIDE

1. Set up 'make menuconfig' with the usual usb suspects: kmod-usb-core, kmod-usb-storage, kmod-usb2, kmod-fs-ext4 (match fs type), block-mount, kmod-scsi-core, usbutils

2. Run make

If make finished with no errors,

3. Go to /build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/linux-***KERNELVERSION***/arch/mips/ath79/ (where ***KERNELVERSION*** = the present kernel version) and edit this file:

mach-tew-712br.c

After the line #include "dev-m25p80.h"

add

#include "dev-usb.h"

After the line  ath79_register_eth(0);

add

ath79_register_usb();

4. In the same directory, also edit this file:

Kconfig

Add

select ATH79_DEV_USB

after editing the section looks like this:

config ATH79_MACH_TEW_712BR
    bool "TRENDnet TEW-712BR support"
    select SOC_AR933X
    select ATH79_DEV_ETH
    select ATH79_DEV_GPIO_BUTTONS
    select ATH79_DEV_LEDS_GPIO
    select ATH79_DEV_M25P80
    select ATH79_DEV_USB
    select ATH79_DEV_WMAC
    select ATH79_NVRAM

then run make again. Use the sysupgrade version ( openwrt-ar71xx-generic-dir-601-b1-squashfs-sysupgrade.bin ) if installing openwrt from a working openwrt install.

HARDWARE SIDE

http://img198.imageshack.us/img198/6154 … nv4png.jpg

Using the above picture for reference, I also used a 100uF 16v capacitor across the power and gnd connections. I used two 10k resistors to gnd ( standard is 15k apparently ), one on each data line. I don't think it really matters, and the resistors might not even be necessary. The external 5v power supply is unnecessary in this case, just pull 5v off of the wide bus near the power adapter. The hardest part of the whole thing for me was bridging the two tiny, empty resistor pads on each data line (R211, R212). I lifted one pad and destroyed another. Just scraping the trace further down and soldering to that was fine. The Squonk reverse engineered WR703N (ar9331-based) page showed them to be 0R or zero ohms, so just a piece of wire on each line will do.

https://i.imgur.com/kHhP6R0.jpg

Now using extroot:

http://wiki.openwrt.org/doc/howto/extroot

and a usb thumb drive I can install everything! Not bad for zero dollars.

That's it, that's all, I'm done and outta here.

Cheers!

(Last edited by lobonse on 21 Mar 2018, 13:45)

Here's the final product:
https://i.imgur.com/sZsOVwR.jpg

https://i.imgur.com/BDyBtqn.jpg

Yes, the wires on the capacitor are the wrong colors, the electrons don't seem to mind though.

https://i.imgur.com/tyJGizq.jpg

They call me the mangler. I never knew I could use such cuss words. The two white wires toward the top are completely unnecessary if you can manage to bridge the two gaps with tiny pieces of wire or 0R resistors ( or probably 22 ohm resistors, etc )

https://i.imgur.com/BpOpVYP.jpg

Comments welcome.

(Last edited by lobonse on 21 Mar 2018, 13:50)