Requesting 23.05 for Linksys Audi (EA3500)? The EA3500 Audi variant seems to have disappeared from the firmware list? Last firmware available was 19.07.9? But EA3500 (non-audi) still supported. The generic EA3500 non-audi image does not work, will not boot.
This?
https://firmware-selector.openwrt.org/?version=23.05.5&target=kirkwood%2Fgeneric&id=linksys_ea3500
No that is the 'non-audi' image. It will not load on the 'audi' EA3500 router, as I noted in my original post. If you look at the 19.07 release you will see there are 2 variants for EA3500, audi and non-audi variants.
For example...
https://firmware-selector.openwrt.org/?version=19.07.10&target=kirkwood%2Fgeneric&id=linksys_audi
It is same thing.
Sorry but they are not the same, the generic EA3500 is REPORTED AS INCOMPATIBLE when loaded, and does not flash correctly even with an override done. The only image that works on the 'audi' EA3500 hardware is the EXPLICITLY labelled LINKSYS AUDI EA3500, the firmware selector STOPS listing the linksys audi EA35000 at 19.07. Until 19.07 there were TWO separate images, now there is only the NON AUDI image from 21.x until 23.05. So again, how do I request that the AUDI variant of the EA3500 be supported AGAIN as it once was? The current non-audi EA3500 does NOT WORK on the audi specific EA3500 hardware.
What's odd is that the 19.07 version you reference does indeed say Audi, but it's not like there's a non-Audi version.
Meanwhile, the device info page mentions that Audi is the codename, but makes no other distinctions.
https://openwrt.org/toh/linksys/ea3500?s[]=linksys&s[]=ea3500&s[]=audi
With that in mind, I'm not sure why it won't flash to a more recent version.
Let's start with an n+1 jump... try downloading the sysupgrade image from here:
https://firmware-selector.openwrt.org/?version=21.02.7&target=kirkwood%2Fgeneric&id=linksys_ea3500
And then attempt to upgrade (do not keep settings, but don't force). If it presents an error, please grab a screenshot so we can see it. We might also try to do this on the command line to see if we can get more info about it.
Where? Info page says ir is same.
When you load the flash files... .The firmware updater says literally the image not compatible... moreover the image does not work... so it is not compatible.
What file(s) are you using (the exact filename and where it came from, please), and into what are you loading it?
Can you provide output (screenshots are okay here)?
Sure... What do you want a snapshot of? The warning/issue screen before you can force the image to load? A snapshot of the router model information as well?
Pictures of the sticker on the device and then whatever you see as you attempt to run the upgrade... warning messages, etc.
And of course, tell us which exact file you are using.
Here the screen prints are...
Example of generic firmware for GENERIC NOT AUDI EA3500 THAT FAILS...
Example of last existing firmware for AUDI EA3500 That works...
Device Information...
Incremental Image Update From Audi Firmware To Audi Firmware...
Note MISSING LINKSYS AUDI UPDATE AFTER 19.07.*...
Failing Firmware Update When Attempting To Use "LINKSYS EA3500 GENERIC"
So... as you can clearly see... there are EA3500 GENERIC and EA3500 AUDI variants of the EA3500.... And... NO firmware has been generated for the AUDI fariant of the hardware for a VERY LONG TIME... This SHOULD NOT have been dropped, because someone thought GENERIC = AUDI.
As I previously explained, there is only one version of the EA3500... the code name for it is "Audi" and the earlier firmware included that in the filename, but it is not required... did you happen to notice that there is only one EA3500 entry in 19.07, and only one EA3500 entry in 21.02? There was never a "special Audi" version vs some "generic" version.... there's only one revision of this device.
Meanwhile...
You sound very agitated. Please calm down -- screaming (all caps) is not necessary. As I explained, your interpretation of the file naming is incorrect.
Maybe it will help if I explain why you're getting that error...
- Your device, when running 19.07, uses
swconfigto manage the switch chip inside the device (this is what handles the Ethernet ports) - Starting with 21.02, OpenWrt began the transition to DSA (Distributed Switch Architecture), beginning with the Kirkwood target (including your device) as well as a few others.
- DSA represents a major under-the-hood change in the way that the switch is handled.
- This was a 'breaking change' in that the previous configuration methods became invalid, requiring entirely new syntax. Keeping the old syntax would result in a soft-bricked device. (recoverable, but annoying)
- To be clear, "breaking change" does not mean it will break your device; it just "breaks" backwards compatibility of the config and methods used to address the things that have changed.
- The release notes even mention that a scary error message may appear, although what you have there is different (I suspect you are trying to use the wrong image file)
- If you look back at the forum posts around this time, there were lots of people worried about the same message.... it was (and still is) safe to force the upgrade.
Moving on... there is little-to-no risk because your device is a dual-partition system, so it's really hard to brick it. But that said, I can assure you that it is safe to force the upgrade as long as you use the correct file. Since you're currently on 19.07:
- download the 21.02.7 release
- be sure to use the sysupgrade file.
- uncheck "keep settings..."
- Then, go ahead and force the upgrade.
Yes, I have been using OpenWRT for years, I know about the dual firmware image feature, I am not worried about breaking the router. What is at issue is I have tried the 21.x series firmware (generic) and effectively bricks the firmware bank that attempts the load, on the audi hardware.
I have never retain the previous configuration, I always select erase before flashing. Retaining the configuration is of course a mine field of issues, so have never relied on it.
Why is there 2 completely different firmware references in the firmware selector if they are the same? At the 19.07 level.... AND... their two separate BINARY files in the repository?
Why is it that 4 of the 5 EA3500 I have, have completely different physical design, yes I opened them, and confirmed this... the physical hardware is different, since there are actually 3 different revisions of the EA3500 router, this is documented on the Linksys web site as v1, v2, v3 hardware. Unfortunately I only have 1 audi variant so any validation testing across devices is not possible.
Why is it that 4 use the generic image just fine. But the Audi variant rejects the generic image. This is not a case of insufficient resources (storage or memory) for the new image as far as I can tell.
I updated all 5 using the generic image from 19.07 to 23.05 and 4 worked, 1 bricked. It is the only the audi variant that bricked. Of the 4 that worked they vary between v1 to v3 of the hardware differences as noted above.
If what you said is true 21.02.07 would have worked. It failed. I attempted the kernel variant of 21.02.07, assuming that was your intention that I start there.
As for all caps....I don't agree that caps are screaming.... I want to make sure the text is recognized as IMPORTANT... all caps is a new era mindset that those of us that come from the mainframe and mini systems all we used is CAPS, because this all that was supported for years. But I digress. You take the CAPS anyway you want.
What is frustrating is the fact that I have had to do the long rest of the audi hardware over and over, had to use serial console access at least one, because the firmware image above 19.07 is consistently failing to load.
I explicitly unchecked the keep settings option and of course selected the force flash option.
As I type this note, the router is again doing that fast-blinking of the power indicator LED that is typical of a failed flash attempt. It has been at least 15 minutes since I attempted the flash. Once I reset the router yet again, I can load 19.07.10 just fine... that is labelled "Linksys Audi". But I am 0 for 11 or so now for any version of the generic image in the audi hardware.
Oh, I don't believe this is memory consistency issue, i..e bad programmable memory bank, given I can flash any version of 19.07 several times, thus using both banks in turn without issue.
Looking at the 21.02.07 image...
Model Linksys EA3500
Platform kirkwood/generic
Version 21.02.7 (r16847-f8282da11e)
Looking at the 19.0.7.10 image...
Model Linksys EA3500 (Audi)
Platform kirkwood/generic
Version 19.07.10 (r11427-9ce6aa9d8d)
Is there a reason that there is no kernel image for 19.0.7.10? But is for 21.02.07? I can try the factory image at 21.02.07, but the documentation suggests you load kernel before factory.
Kernel - Linux kernel with minimal file system. Useful for first installation or recovery.
Factory - Use a Factory image to flash a router with OpenWrt for the first time. You normally do this via the web interface of the original firmware.
The qualification between Kernel and Factory is a bit confusing... First installation versus first time? Maybe the definitions should be qualified a bit more? Such as kernel is expected to be use to test suspect hardware or do recovery? But factory is expected to used on known supported hardware?
Since you did not qualify, I used kernel, it failed, are you going to next suggest I try factory?
No. I specifically said use the sysupgrade image.
Unfortunately, the unit is now officially bricked. The sysupgrade 21.02.7 flash failed again, as in the past, I was careful to uncheck keep settings, force the upgrade, etc. I have tried a soft reset, as well as the 30-30-30 reset. The 30-30-30 reset always worked in the past.
I connected to the serial interface, have done this many times before on both this router and the others I have, but try as I might, I get nothing from the boot loader on this specific router. This router would not accept any image but 19* series, when it was working I updated from 19.07.7, .8, .9 and even .10. But never anything higher. But that issue is moot now that the router is apparently officially bricked.
The router acts like it resets, boots, fast blinking, to slow blinking to solid on. Any connected ethernet port at L2 level (i.e. link hardware state) shows connection and traffic... but never get any IP address, not even 192.168.1.1 default, and given it appears the boot loader failed, this effect appears to be at an end.
Pulled out the multivolt meter and watched the levels... nothing from transmit pin on the serial interface. First time I have seen a router not switch banks like this... but since I cannot get the serial console... I cannot force the flash to a specific bank to validate if one of the banks has failed?