On Mon, 3 Nov 2014, Robert P. J. Day wrote:
> apologies for being repetitive but i'm still trying to figure out how to
> reflash my d-link dir-810L with an openwrt image, and i'm willing to buy
> someone a virtual beer or 12 if they can give me the solution. (i'm well
> aware that the wireless will almost certainly not be functional -- that's
> ok, i just want to boot to openwrt, and i'll worry about the wireless
> from there.)
>
> as an initial test, i downloaded the latest *official* firmware image
> from d-link, and that reflashed just fine, so i know reflashing is possible.
> at that point, i grabbed the "dir-810l" image from here:
>
> http://downloads.openwrt.org/barrier_breaker/14.07/ramips/mt7620a/
>
> and tried the same thing, and i got an error dialog starting with:
>
> "The uploaded firmware file may not be correct ..."
>
> i suspect more than a few people have seen that dialog -- in the end,
> no reflashing was done, so i'm assuming there's something in that
> openwrt image that the d-link firmware doesn't like.
>
> reading the openwrt dir-810L page here:
>
> http://wiki.openwrt.org/toh/d-link/dir-810l
>
> it would appear that my other option is to slap together a USB-TTL cable,
> and upgrade using TFTP, is that the correct solution? has anyone done
> this and can verify that the upgrade both *can't* be done through the GUI,
> but *can* be done over the serial port via TFTP? i'd really like to
> get an openwrt image onto this board ASAP. thanks.
there is one other thing i can add in case someone sees an issue
i'm missing. i'm trying to figure out what sort of test the d-link is
running so that its own official firmware passes the test, but the
openwrt bin image fails.
here's an examination of the official firmware:
$ file D*bin
DIR810LA1_FW102B22.bin: u-boot legacy uImage, Linux Kernel Image,
Linux/MIPS, OS Kernel Image (lzma), 6057805 bytes, Mon Jul 7 06:15:05
2014, Load Address: 0x80000000, Entry Point: 0x8000C2D0, Header CRC:
0x8D5ABC60, Data CRC: 0x87ECB287
$
so it's clearly a u-boot legacy image, there's an embedded
description string, etc, etc and so on and so on. and here's the same
info for the openwrt image:
$ file openwrt-ramips-mt7620a-dir-810l-squashfs-sysupgrade.bin
openwrt-ramips-mt7620a-dir-810l-squashfs-sysupgrade.bin: u-boot legacy
uImage, MIPS OpenWrt Linux-3.10.49, Linux/MIPS, OS Kernel Image
(lzma), 1128601 bytes, Wed Oct 1 10:42:30 2014, Load Address:
0x80000000, Entry Point: 0x80000000, Header CRC: 0x912E84E5, Data CRC:
0x77AF9BF4
$
again, a u-boot legacy image, different embedded string, but entry
point same as load address, could that be something that the d-link
router is testing? i'm just trying to figure out what about the
openwrt image is unpalatable to the router. i'm more than happy to
"hexdump" or "dd" to hack the openwrt image to make it acceptable, if
someone knows what i should be hacking.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
openwrt-users mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-users
