Hi,
I was wondering if the changeset supporting for WD N600 could be tweaked to support this nearly identical router.
http://wiki.openwrt.org/toh/wd/n600
http://wiki.openwrt.org/toh/wd/n750
I uploaded the OpenWRT firmware for WD n600, but it did not work. Specifically I flashed:
http://downloads.openwrt.org/snapshots/ … actory.bin
The ethernet lights were off. The wifi LED was blinking initially, and then became stable within a minute. But no wifi SSID was visible.

I also tweaked the chageset at https://dev.openwrt.org/changeset/38076 and built an image. With that, even the WIFI led was not blinking. Specifically, I changed the board id in the last part of the diff from wrgnd16_wd_db600 to wrgnd13_wd_db600. So, the new line was:
$(eval $(call SingleProfile,Seama,64k,MYNETN600,mynet-n600,MYNET-N600,ttyS0,115200,$$(mynet_n600_mtdlayout),wrgnd13_wd_db600,1310720,16187392))

I got the board id from http://wikidevi.com/wiki/Western_Digital_My_Net_N750
I also noticed that the output of cat /proc/mtd on that page looks different from the mtdlayout in the above changeset.
The changeset says
mynet_n600_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,1280k(kernel),14592k(rootfs),64k(radiocfg)ro,15872k@0x70000(firmware)

But the page above says:
# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 0099d000 00010000 "rootfs"
mtd1: 00f80000 00010000 "upgrade"
mtd2: 00010000 00010000 "devdata"
mtd3: 00010000 00010000 "devconf"
mtd4: 00010000 00010000 "radiocfg"
mtd5: 01000000 00010000 "flash"
mtd6: 00040000 00010000 "bootloader"
mtd7: 00010000 00010000 "bdcfg"
mtd8: 00010000 00010000 "devrev1"
mtd9: 00010000 00010000 "devrev2"
mtd10: 00020000 00010000 "devrev3"

Any guidance would be appreciated. Thanks

(Last edited by abhishek.anand.iitg on 23 Oct 2013, 19:06)

Hi,

It seems there is some interest in this router:
http://article.gmane.org/gmane.comp.emb … evel/20900
http://article.gmane.org/gmane.comp.emb … evel/20910

It seems like pretty decent hardware.
Unfortunately where I live (in europe) these are still pretty expensive so I won't buy it at the moment to play with it a bit...

(Last edited by jaceq on 23 Oct 2013, 18:26)

I have

$(eval $(call SingleProfile,Seama,64k,MYNETN750,mynet-n750,MYNETN750,ttyS0,115200,$$(mynet_n600_mtdlayout),wrgnd13_wd_av,1310720,16187392))

according to git. The good news is that the n600 layout is correct enough that we don't fry the bootloader or radio calibration. The bad news is that new firmware runs only once after flashing; I suspect the firstboot code which creates the overlay filesystem overwrites the seama partition headers. But I am not sure.

Anyway, I believe the hardware of this device seems most similar to the DIR-825-C1. There is no direct connection between eth0 and any particular jack; that's all handled by VLANs in the switch programming. It's possible the wireless code already works without without change, but I am not very interested in the device until the wired ethernet works.

There's a 3.3v serial header soldered in, identical to the N600. You'll need a "security" Torx screwdriver bit to take out the screws the...correct way.

Thanks jaceq and nop.
This router is surprisingly cheap for it's h/w specs.
I managed to connect to the router w/ stock firmware via telnet.
(somehow, telnet was not working in the latest stock firmware and I had to play a little with the GPL source)
My cat /proc/mtd results differ from that in the wiki at http://wikidevi.com/wiki/Western_Digital_My_Net_N750

# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 0094c000 00010000 "rootfs"
mtd1: 00f80000 00010000 "upgrade"
mtd2: 00010000 00010000 "devdata"
mtd3: 00010000 00010000 "devconf"
mtd4: 00010000 00010000 "radiocfg"
mtd5: 01000000 00010000 "flash"
mtd6: 00040000 00010000 "bootloader"
mtd7: 00010000 00010000 "bdcfg"
mtd8: 00010000 00010000 "devrev1"
mtd9: 00010000 00010000 "devrev2"
mtd10: 00020000 00010000 "devrev3"

In particular, the size of rootfs is different.
This weekend, I might trying buidling OpenWrt with this layout

Hi abishek,

I would love to try to play with that router, will keep searching for cheap one in my area
I have TTL console converter and 'security' torxes so access to console wouldn't be a problem.

Anyway keep posting results / progress, I will try to answer questions if I will be able to.

(Last edited by jaceq on 24 Oct 2013, 08:48)

I think I almost understand how to convert the output of cat /proc/mtd to the mtd_layout definition in Makefile(like the following):

mynet_n600_mtdlayout=mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,64k(devdata)ro,64k(devconf)ro,1280k(kernel),14592k(rootfs),64k(radiocfg)ro,15872k@0x70000(firmware)

I dont understand why some entries have "ro" after the parenthesis, but other's dont.
How do I figure out where to put "ro"?

Also, the last entry "firmware" is different as it has an additional "@0x70000". Where do I get that number from?

Also, has someone written a script/small program to convert the output of cat /proc/mtd to the layout line in Makefile?
It's kinda tedious and error-prone to do it manually.

Thanks. BTW jaceq, where do you live?

(Last edited by abhishek.anand.iitg on 26 Oct 2013, 21:46)

Hi,

ro flag marks partition as read only obviously. You should have ro everywhere where you don't need modifications from OpenWRT level (or it's unsafe). Basically above is correct, I think it would also be possible to have kernel partition with 'ro' since sysupgrade writes to 'firmware' partition which is overlay over kernel and rootffs.
I see there is some progress about this router on mailing list, I will ask guy there to write here too.

ps. I live in Europe

Thanks. I joined that mailing list.

Patches posted to mailing list, please test if you can:

http://patchwork.openwrt.org/patch/4570/
http://patchwork.openwrt.org/patch/4573/
http://patchwork.openwrt.org/patch/4571/
http://patchwork.openwrt.org/patch/4572/

(Last edited by Heffer on 13 Dec 2013, 14:44)

It worked great . Thanks lot!
Both(2.4 ghz and 5 ghz) wifi interfaces are working.
The ethernet is working too.

One extremely minor issue is that wifi leds dont blink.
I can share the build image if anyone wants(and if it is legal).

Sharing images is completely legal if you built it directly from the OpenWRT git sources (because everyone then knows where to get the source). If you did modifications you would need to publish those in source code format as well.

Can you please check if your ethernet comes up in gigabit or just 10Mbit/s half-dulpex (either check using swconfig dev switch0 show or check on the connected device using (for example) ethtool)?

I'm having the problem that most of the time the ethernet only comes up at 10Mbit/s.

I've sent a set of new patches after the initial support for the N750 was added to trunk yesterday.
These should fix any negotiation issues on the switch:

http://patchwork.openwrt.org/patch/4611/
http://patchwork.openwrt.org/patch/4609/
http://patchwork.openwrt.org/patch/4610/
http://patchwork.openwrt.org/patch/4612/

Thanks. I updated http://wiki.openwrt.org/toh/wd/n750 accordingly.

I tried flashing OpenWRT to my Western Digital MY NET N750 (Model E2F with stock firmware 1.04.16 via Windows 8.1) today using the instructions posted on OpenWRT under "Installing OpenWRT" (http://wiki.openwrt.org/toh/wd/n750)  to no avail. 

I tried several times and also on two separate N750 routers (I have two of the same model:  one in router mode and one in AP mode).  After following the steps, especially resetting the router, and attempting to upload the .bin file, the N750 generates a "Firmware Upload File," "Invalid image file...." message.

Note:  I did not quite understand step 2 or "Configure your computers [sic] IP address to 192.168.1.10...."  However, after surfing the 'net for guidance, I think that I figured it out and changed my the IPV 4 TCP/IPv4 adapter settings to the address provided in the step.  I was unable to connect to the router via the LAN port without making the IPV 4 change, but could with the change made.  Thus, I think that I successfully followed step 2.

Note too:  I successfully flashed updated stock firmware to both of my N750 routers and I also unlocked/rooted/flashed custom RUUs to my HTC One V and now Nexus 5.  So it's not like I am a complete flashing noob (at least an end user noob).  It's been my experience that steps are always left out of procedures and I almost always need to view many sites, and cobble together a complete set of procedures, but I just couldn't find any other sites to expand on the OpenWRT installation steps.

Please advise and thank you.

(Last edited by ludoviclalo on 23 Dec 2013, 02:41)

For windows, the following link explains the process with pictures:
http://wdc.custhelp.com/app/answers/detail/a_id/9618/
In step 10, provide the file you download from http://downloads.openwrt.org/snapshots/ … actory.bin

Thank you for replying so quickly and replying too!  I was able to successfully flash following the WD link guidance.

No problems flashing my N750 per wiki. Just wondering is there any way to get the orange LEDs working on the rear? On my unit they are lit until OpenWRT boots, then its just the single green LED per port. I've been reading that swconfig is the go-to place for changing LEDs attached to switches, but there's no LED parameter listed in:

 swconfig dev ag71xx-mdio.0 help

I have a different issue, I assigned IP to eth0 and I think I should have assigned to eth0.1. I cannot ssh to router at all. It is at present in bridge mode, I can access internet via lan port and other lan port of router is connected to my main router. WAN port has no access or does not work. After flash I was unable to get Internet to get luci to install and led to this thread and current state. I think at present router has no ip and I am dangling. I scanned IPs on subnet and none of the IP works.
I could not find link for serial access details. I am used to some page where some information is listed with little change but here I may have to solder and then access. I can solder and create cable and access but not sure where on this board I will attach and what are the pin configurations. I too need some tools for accessing console because I am not sure if native Win 7 provides such tools. There used to be HyperTerminal but don't see it any more. I do have MAC, Linux box in addition to windows machines.

The LED configuration is set in the board support file (https://dev.openwrt.org/browser/trunk/t … net-n750.c).

The current configuration is set to the default of the AR9344 SoC:

static struct ar8327_led_cfg mynet_n750_ar8327_led_cfg = {
    .led_ctrl0 = 0xcc35cc35,
    .led_ctrl1 = 0xca35ca35,
    .led_ctrl2 = 0xc935c935,
    .led_ctrl3 = 0x03ffff00,
    .open_drain = false,
};

The meaning of this for the My Net N750 is:
Green LED: Lights up when there is a Gigabit connection. Blinks on gigabit RX/TX with a frequency of 4Hz.
Orange LED: Lights up when there is a 100M connection. Blinks on 100M RX/TX with a frequency of 4Hz.

Thanks! That makes sense, I only had Gigabit gear in arms reach when I was testing. For curiosity's sake is there a public manual / method to deciphering the 32-bit config strings on the AR8327 or was it derived from using a source drop from a similar platform (e.g. TP-LINK WR1043ND) and seeing if it worked?

It's in the AR8327N datasheet. It's not public but can be found if looked for hard enough (like #2 result on Google search for "AR8327N datasheet"). If you come across one you will find the explanation on p.37.

(Last edited by Heffer on 28 Dec 2013, 17:10)

Just chiming in to thank Heffer & co. for their work getting this router supported by OpenWRT, and in the nighly builds. Everything seems to work perfectly, and BB from last night flashed straight on, no issues. This seems like a solid 450Mbps N router with the stock firmware gone.

Does OpenWRT enable this device to do Wireless Bridging?
I believe the stock firmware is only capable of Wired

Yes. I have been using it as a bridge successfully on 5 GHz with 450 Mbit/s.

Are USB ports and SAMBA/Windows sharing supported on OpenWRT?  If yes can someone link me to a guide please?  Also can i install the gargoyle UI or am i restricted to the LUCI thing?