You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After building an image with these changes the 256MB Variant of the WE3526 would work.
To reproduce the problem on 256MB Variant I tried building the image with reg = <0x0 0x1c000000>, <0x20000000 0x4000000>; (which is basically no change). I would get stuck in the soft brick.
I discovered this solution because of this commit 310f851
The problems with the 256MB Variant may be because of #2220 where memory auto-detection for mt7621 is not reading the 256MB correctly. Might be worth investigating.
StarWhiz:
This was solved by changing /openwrt/target/linux/ramips/dts/ZBT-WE3526.dts
line #14 from
reg = <0x0 0x1c000000>, <0x20000000 0x4000000>;
to
reg = <0x0 0x10000000>;
After building an image with these changes the 256MB Variant of the WE3526 would work.
To reproduce the problem on 256MB Variant I tried building the image with reg = <0x0 0x1c000000>, <0x20000000 0x4000000>; (which is basically no change). I would get stuck in the soft brick.
I discovered this solution because of this commit 310f851
The problems with the 256MB Variant may be because of #2220 where memory auto-detection for mt7621 is not reading the 256MB correctly. Might be worth investigating.
Reference Post From When I Had the Problem: https://forum.openwrt.org/t/zbt-we3526-soft-bricks-everytime-256mb-ram-variant/61913/2
Fixing this will solve soft bricks for WE3526 256MB Routers.
The text was updated successfully, but these errors were encountered: