Installer v1.0.3 upgraded TF-A to v2.9. Installer v1.0.2 still uses TF-A v2.4.
Edit:
OKD really started after folks used Installer v1.0.3.
4 Likes
If you are on v1.0.3, then you may get OKD eventually. It would be advisable to roll BL2 back to the version in 1.0.2.
1 Like
Oh ok. Thank you for that info.
Thanks for the link but all my RT3200's (3 of them) are in FIP-in-UBI layout based on v1.1.0 installer.
Two of them still boot (I think, haven't tried turning them ON for many days now). Third one is in complete OKD (even freezer trick doesn't work) which will require recovery using UART or USB-TTL cable.
All 3 devices are in a different country and the people using it are not tech savvy. I can, using VNC connect to Windows or Linux laptop, try to flash correct TF-A on the 2 RT3200's that are still booting.
Scrubbing only relocates a physical erase block if there are 4 bitflips (out of 4 total correctable at this ECC strength). As that's a bit late I've lowered it to 75% which means now relocation will happen at 3 bitflips.
However a single flipped bit is enough to cause OKD... So rewriting is safer in case the next boot still relies on the old buggy bl2.
5 Likes
Thanks.
I get:
v2.4(release):OpenWrt v2021-05-08-d2c75b21-1 (mt7622-snand-1ddr)
v2.4(release):OpenWrt v2021-05-08-d2c75b21-1 (mt7622-snand-1ddr)
v2.4(release):OpenWrt v2021-05-08-d2c75b21-1 (mt7622-snand-1ddr)
v2.4(release):OpenWrt v2021-05-08-d2c75b21-1 (mt7622-snand-1ddr)
How does this translate to installer v1.0.2/1.0.3/1.1.0/1.1.1/1.1.2/...?
And can I safely upgrade from 23.05.3 stable to 23.05.4 stable?
You are on TF-A v2.4 which is all that matters at this point. You can safely upgrade within 23.x stable train, but NOT to snapshot or future 24.x.
@all newcomers - Please read the recent posts at least
3 Likes
That version of TF-A was used in multiple versions of the UBI installer, so we would need more info to know exactly which one. However, as @peca89 says, that version of TF-A is OKD safe, so OKD should not affect you.
For you, moving to 23.05.4 stable release is also safe.
I have to thank @daniel for the efforts and time to fix OKD!
And @NullDev for the path to downgrade the TF-A.
Now I can use the RT 3200 again.
2 Likes
thanks for all of the efforts to fix the OKD!
I have created a Github Gist with instructions that I created from this post and successfully followed to fix the OKD on three E8450s via SSH. Perhaps this will help someone: https://gist.github.com/abmcmillan/9771991da9d4422ccd61fb76eaba236f
I am happy to have survived the OKD without having to ever do serial recovery on my devices. Thanks to all who fixed this!
8 Likes
Thank you for the details. Do you mind sharing your opinion about running the openwrt snapshot on your 3 devices ? Is it stable enough?
I have been using recent snapshots with no issues. Iphones seem to not like my ax wifi6 settings but I doubt its a firmware issue.
1 Like
Thanks a lot for summarizing and making it easier for users to escape from OKD before it happens.
Once little detail: Also TF-A v2.10 is affected by OKD before version v2024.01.17~bacca82a-3 (ie. v2024.01.17~bacca82a-2 and v2024.01.17~bacca82a-1 are affected as well).
3 Likes
Are you running at 80MHz or 160MHz? I've been running my RT3200 at 80Mhz (latest 23.05-SNAPSHOT), and I'm getting good performance on a MBP '21 Apple silicon (can't test on an iPhone).
IIRC, 160MHz seems to cause performance issues.
Hope it helps 
1 Like
I've been running main snapshot for years and have found it to be as stable as "Stable" on my devices, including an RT3200. Probability of bugs in main snapshot is higher, but bugs get fixed in snapshot much faster than the interval between stable point releases on those occasions when a stable point release has a bug or two in it. On balance, I have been very satisfied with main snapshot stability and performance.
I sysupgraded my RT3200 to current main snapshot last night (r27140-ccc06f6716), including installing the kmod-mtd-rw package, and followed the instructions above in this thread to write the current snapshot preloader.bin. It rebooted fine, is running as stable as always and now OKD risk free thanks to the persistence and tenacity of several contributors in this thread.
5 Likes
- I am using wpa3. Frequent disconects/reconnects. Moved them to 2.4ghz seems fine now.
I have it on 160MHz and zero problems with it connecting it to my laptop with the AX210 card. But I use WPA2 because I can't make 802.11r work with WPA3 on both RT3200 and my WDR4300 AP. With WPA2, I can roam to one AP to the other and it seamlessly changes to the stronger SSID.
With WPA3 and applying every guide I've read, the client disconnects and then connects to the other AP only when the signal is unusable. I'm sticking with WPA2 beacuse of this.
I too have just updated my (2) RT-3200 and (1)E8450 using the detailed instructions within
https://gist.github.com/abmcmillan/9771991da9d4422ccd61fb76eaba236f#file-okd_fix_instructions-md
and all three responded to the fix as advertised.
My three were/are running on SNAPSHOT r27143-0b7d99147b for the fix.
root@e8450:~# grep "(release)" /dev/mtd0ro
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7622-snand-ubi-1ddr)
root@e8450:~#
Thanks is not enough. May I just say BRAVO! BRAVO! to the community effort.
One question...
The way I read it I don't need to have kmod-mtd-rw on board any more after the fix is that correct?
5 Likes
Correct. You only needed it once to update bl2. It should never be needed again (unless we discover yet another crazy bootloader bug, but let's just hope that won't happen...)
1 Like
Users with the last "good" UBI-Installer v1.0.2 are fine to just install the v1.1.3 without anything additional?