[Solved] WRT3200ACM wont accept firmware

Installing and Using OpenWrt
28

https://cdn.corifeus.com/openwrt/SNAPSHOT/targets/mvebu/generic/insomnia-latest-mwlwifi-openwrt-snapshot-insomnia-mvebu-linksys-wrt3200acm-squashfs-factory.img

https://cdn.corifeus.com/openwrt/SNAPSHOT/targets/mvebu/generic/insomnia-latest-mwlwifi-openwrt-snapshot-insomnia-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin

29

@RandomReaper Do you have a SHA256SUM for the factory image?

30

imo, the best way to get a winbond build for the recent rango units is to add the patch to a current clone of master, not to build a ~5 week old(4.9) staging tree YMMV.

31

I am new at this patching thing. I am trying to get LEDE 17.01.4 working on my new WRT3200ACM. Do you know where I can find a clone for this specific version?

32

Sorry, no, I just run master as it is stable enough for my purposes. If push comes to shove, there are images off the Stuff link on my avatar.

33

Thanks! Will look into it.

34

Here are the images I've built form https://git.openwrt.org/openwrt/staging/kaloz.git
, commit 7ae59a2f288ba1cef23b20e1d36e199e8c646245

openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin

sha256

1d0b208cbf4845a0a6e95d65daa9f72e2001802f4499393d871186075dc54f21  openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
e415531f268ebcc2e8e5dac3b687f9b9c5f1ca95104e10799bf4b69bfe80ed8c  openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin

md5

e62398c625198fbd0cb428a220f0815b  openwrt-mvebu-linksys-wrt3200acm-squashfs-factory.img
9879eef008969a99c70f8e8910dab348  openwrt-mvebu-linksys-wrt3200acm-squashfs-sysupgrade.bin
35

@tmomas / @hnyman Any chance the WRT3200ACM 17.01.4 stable image could be updated with kaloz's
3 patches?

36

Pushed to master; and a/the next stable is in the works, to which things will be cherry-picked.

37

Right, but that doesn't affect any 17.01.4 Stable images, hence why I asked for the the Stable images for the WRT3200ACM to be updated.

Does Kaloz's patches change anything other than allowing for the WinBond chip to be recognized and partitioned accordingly?

  • If not, there doesn't seem to be a reason to not regenerate the two Stable images for the WRT3200ACM with those patches applied.
    • These patches are a bit different than most other patches, as without them, the firmware cannot be installed to WRT3200ACM's with WinBond NAND flash because the ROM isn't recognized.
38

Because it takes effort, and the next stable is in the works.

Edit: I'm not about to waste my time enumerating all the blatant flaws with this. I will point out what your keen observational skills apparently have overlooked; note the monikers from the linked ML as the ones responsible for the buildbots, try barking up that tree. Nice numbers though, what part of your anatomy did you pull those from.

39

Does it need to be done manually? Yes. Does it take significant time? No.

Perhaps it's believed this is more complex than it really is?

  1. Copy patches to the appropriate directory, ensure kernel makefile has the same 4.4.92 kernel set, then issue make... takes all of 3min to issue and verify, ~15min to build.

  2. Copy the two newly generated images to web server... takes all of 2min

  3. Update sha256 hashes for the images... takes all of 30s to copy and paste.
  • Time required:
    • User: ~5min
    • Total: ~20min
40

What's weird is I can't install DD-WRT on my WRT3200ACM but not LEDE. I want my damn cake and piece_of_cake!

41

If your device has the newer WinBond NAND, you'll either need to compile your image using kaloz's patches mentioned above, or you can try @david502's build, but I haven't followed his changelog and do not know if his images have the required WinBond patches

42

I wish I knew how to compile images. I just started learning about third party firmwares for routers. But I'm going to do more research.

43

Start here:
https://openwrt.org/docs/guide-developer/build-system/start

After that, go on with this:

In case of further questions, see https://forum.openwrt.org/c/devel

Ask questions about building LEDE firmware. Ask for advice about adding a new device to LEDE, getting help compiling LEDE, using ImageBuilder, or creating custom configurations.

44

If the issue is the flash change;

  • use a master snapshot, it has the patch
  • for stable, add the patch your build (see above)
  • the patch should find its way into the next stable(hopefully this month), so wait
  • use an available image that includes patch, including any recent master image (there are images to be had from the link found on my avatar
45

You can utilize this script to automate the entire build process on Ubuntu (can be installed into a VM using VirtualBox, if not using a Windows edition that has Hyper-V included [Windows 10 Pro only, Windows 8 Pro, etc.]).

  • The only manual part, besides selecting the OS version and OpenWrt version, is making selections in MenuConfig
    • If selecting anything other than the OpenWrt 18.xx version, you will need to manually add kaloz's patches.

    • I realized the other day I forgot to add code to prevent keystrokes from being recognized as option selections, so until you reach the OpenWrt branch selection of the script, ensure you don't press any keys [other than to select the OS version] while the terminal window is active... if you do, the script will fail - exit successfully, but fail.

  • Since you've never compiled OpenWrt before, it's likely best you stay out of the libraries selection in MenuConfig.
46

not sharing those files anymore, since the 18.06 release has this bug fixed

47

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.