Last updated: 2018-10-05T19:44:59-07:00
Device Support Status Report
This device is end-user ready. Wired and wireless works, most LEDs work, buttons work, and factory image installation works. Testing has shown the system to be very stable, even under load. However, there are a few issues -- see below.
LEDE Project leaders previously rejected all of my patches and I don't see any situation where it's possible to get them merged so I gave up trying. If someone else wants to take my work and move on with it, you are welcome to do so.
I try to update my patches and pre-built images within a week or two of new releases. Watch this thread for future updates and releases.
Current Known Issues
802.11/wireless activity LEDs don't work. The ath10k driver needs to get fixed. Multiple other devices are also waiting on this. I have seen some progress on this issue in other threads and I think there may be patches to fix this floating around.
The "LED on/off" button can't be made to work because we currently can't shut off the ethernet switch port LEDs. This may be fixed in the future if I am able to support it. The button currently does nothing, but it is configured in the DTS so you can write a script to use it if you want to.
We can't install OpenWRT/LEDE via the OEM web interface yet because the install will revert after next reboot due to the Safe Upgrade/redundant partition system. However, there is a recovery loader in u-boot which is easier to use anyway, so we can and should install our image that way instead.
You can download my builds and patches here:
The minimal builds have a basic bare-bone package set. You have roughly 45MB of free space on the overlay to work with. No LuCi web interface or anything else. Install the packages you want with opkg.
Luci builds are like the minimal builds, but with luci-ssl added to provide a web interface.
I previously published big builds loaded with many packages built-in, but I no longer do that. There is plenty of space on this device to install packages anyway.
The latest builds are based off the OpenWRT v18.06.1 release. The patch set for this build is v13.
Recovery and Installation Instructions
Relatively speaking, installing OpenWRT/LEDE on this device is very safe and it's easy to restore the OEM image if you want to go back.
This device offers three methods for installing images: The uboot http Recovery Loader, the OEM http upgrade tool, and console uboot tftp.
Most users should use the uboot http Recovery Loader because it's easy and safe to use.
DO NOT use the OEM web/http upgrade page at this time. While the OEM upgrade tool will accept and install the OpenWRT/LEDE image, we don't yet support TRENDnet's "Fail Safe"/safeupgrade dual boot system, which means that the device will revert to the old OEM image on the next reboot.
Finally, you can install images via serial console uboot and tftp.
uboot http Recovery Loader
Connect an ethernet cable from your PC/switch/whatever to any one of the ethernet jacks on the router.
Manually configure your computer with an IP on the 192.168.0.0/24 network. The router does not offer DHCP services in this mode.
Press and HOLD down the RESET button on power-up for four seconds. Then release the reset button. NOTE: My testing shows the recovery system will not load if no ethernet cable is plugged in during boot.
The recovery page is at http://192.168.0.1/
The page should say "TRENDnet Recovery Mode" in blue text at the top and there is a "Choose File" button and "Upload" button.
If installing OpenWRT/LEDE, then upload the factory image file.
If you want to go back to the OEM image, use an OEM firmware file, such as "TEW827DRU_FW100B11.bin".
While the file is uploading, the Internet LED will blink. You can watch progress on the serial console too. Beware the progress/percent animation on the https loader page is fake/placebo.
That's it. OpenWRT/LEDE should be up and running within 30 seconds of uploading the file. The OEM image takes about two minutes and boots very slowly.
OEM http upgrade tool
DO NOT use the OEM http upgrade tool at this time. While our factory image file conforms to the OEM requirements to be accepted and installed, we don't yet support TRENDnet's "Fail Safe"/safeupgrade redundant partition boot loader scheme. The result is that the device will successfully boot into OpenWRT/LEDE after the first reboot, but upon the second reboot it will revert to the old OEM system.
I plan to work on supporting the OEM http upgrade tool and the redundant partition system in the future, but I have not gotten around to it yet.
Console uboot tftp
The serial console on this device is fairly easy to access. A 3.3v/TTL serial port can be found in the corner next to the USB ports. You will need to soldier in header pins. Disassembling the chassis is not difficult.
JP1 = Rx
JP2 = Tx
JP3 = Ground
baud = 115200
uboot gives a 2-second "Hit any key to stop autoboot" prompt, so that's easy to break. No special key combo required.
This device uses a FIT archive file, which includes an installer script, a bootconfig image, and the UBI (kernel+rootfs). All we really need to do is tftp the factory image into memory and execute the script embedded within it.
setenv ipaddr 192.168.0.1 setenv serverip 192.168.0.2 setenv netmask 255.255.255.0 tftpboot 0x42000000 openwrt-ipq806x-trendnet_tew827dru-squashfs-factory.bin setenv imgaddr 0x42000000 source 0x42000000:script reset
JTAG recovery is something I want to do some day. It may be possible to recover from JTAG by booting from RAM or programming the NAND flash on this device. I've already experimented with this but I've not yet figured everything out.
Expand the NAND partitions, or otherwise fully use the NAND flash space. The default "rootfs" partition is 64MB in size, but there is 108MB of completely-unused space on the NAND flash, outside of smem/mtd partitions. There is also an additional 64MB of space used by the redundant rootfs_1 partition. It may eventually be possible to have a rootfs file-system of 228MB in size.
Custom u-boot. This depends upon being able to safely recover. We would need either TRENDnet's broken "Fail Safe" system to be fixed, or JTAG recovery. Otherwise the risk of permanently breaking the device is too great.
Boot from USB. This is not possible right now because the OEM u-boot wasn't built with the right modules, but it is possible. This depends upon building a custom u-boot.
Old Development Forum Thread
In May of 2018 the old OpenWRT forum died due to negligent administration. Previously, this is where I had kept a running log of changes and updates for this device, but I am no longer able to update anything on the old forum thread.
This new thread replaces and supersedes any information on the old forum, but you can still read the old thread for background information for how I ported the device, previous issues, and additional technical information.
The old forum thread can be read here:
The original (now potentially invalid) URL to the old forum was: