LEDE Table of Hardware: Available firmware files vs. dataentries

Are we sure that every device for which a firmware file is available at https://downloads.lede-project.org/snapshots/targets/ is present in the ToH?

To check this, I created https://lede-project.org/toh/views/fwfiles_vs_dataentries, where all firmware files available at https://downloads.lede-project.org/snapshots/targets/ are listed vs. the dataentries which contain links to those firmware files.

You can help to improve the dataquality of the ToH by visiting https://lede-project.org/toh/views/fwfiles_vs_dataentries and https://lede-project.org/toh/views/toh_fwdownload2, and either updating the dataentries or creating new ones, if appropriate.

Since this is a big bunch of work, I really need the help of the community for this task.

Thanks for your support! :slight_smile:

Are *vmlinux.bin (10) + *vmlinux.elf (13) + *vmlinux.lzma (3) flashable firmware images?
Are *initramfs-uImage.bin (33) + *initramfs-kernel.bin (104) *initramfs.bin (11) *initramfs.elf (8) *-uImage (86) *-zimage (52) flashable firmware images?

Reason for asking: I want to clean up the list and remove everything that does not require a dataentry, in order to make this a valuable list for identifying missing dataentries.

@tmomas This is brilliant! What a good way to test the import process.

I looked at the dataentry's for routers that I know about, and note the following. Except for the trailing "" (see below), I see no reason to change anything in the import process.


  • Links to firmware (factory & sysupgrade) on the dataentry page seem OK.
  • OEM Firmware link points to .de page


  • OEM Firmware link points to .de page
  • Links to the four variations of firmware look OK. (WNDR3800, WNDR3800ch) and (factory, sysupgrade) each on their own dataentry pages.
  • Dataentry page for WNDR3800_CH doesn't have links to OEM page or wikidevi page.

Archer C7v2:

  • There are a zillion (well, 6) images because of TP-Link's (stupid) FCC change to "prevent" upgrades.
  • il...factory
  • il...sysupgrade
  • factory-eu
  • factory-us
  • factory-(no country) <- has link from dataentry page
  • sysupgrade <- has link from dataentry page
  • We will probably have to add a Comment to the dataentry (manually) that describes how to find the right factory image. Or say "Check the Device Page" in the comment
  • The OEM Firmware has a trailing "" that breaks the link - removing it gave a good URL. (Original OpenWrt page had "http://www.tp-link.com/en/download/Archer-C7_V2.html#Firmware")

Thanks again for all this good work!

How about "See devicepage for other international firmware versions."?

BTW: The import is finished. ToH is live now.
I'm currently checking available fwfiles, add them to dataentries or create new dataentries.
Sadly, oftentimes there's not much hardware information available -> Still work to be done later, to fill in the missing information.

Or 'See Device Page for regional (US, EU, International) versions."?


Yeah, that'll always be a problem. I'm pretty sure dataentry and device pages get filled in for routers that are actually well-supported. The others will just languish (and hopefully) be easy to distinguish from the more popular ones.

I improved the page a bit and added filter capabilities: https://lede-project.org/toh/views/fwfiles_vs_dataentries_searchtable

  • Searching for a firmware file with root in it's name? -> type root
  • Searching for all legacy firmware files? -> type legacy
  • Searching for all asus firmware files? -> type asus
  • Searching for all ipq806x files? -> type ipq

Works only for single querys, i.e. not for "asus bcm53", but it is fast and simple.
I like it!

Further improvement: Links to dataentries + devicepages added

Could this be an alternative way (a quick one!) to find firmware files and installation instructions?