HLK-7621 doesn't reboot after update to 21.02.0

Anubis · September 8, 2021, 2:12pm

After updating (Previous Kernel 19.7) the system to fix an impernitent freezing bug to 21.02.0 r16279-5cc0535800 I had another problem.
The system does not accept reboot. If the reboot command is typed it freezes and has to remove the power and reconnect again.
It is all configured but even with the system in default the bug happens. Restart web skin (luci) doesn't work either, it freezes.

HLK-7621 (Mt-7621At)

log putty(uart) after "root@OpenWrt-1:/# reboot" .

BusyBox v1.33.1 (2021-08-31 22:20:08 UTC) built-in shell (ash)



  _______                     ________        __

 |       |.-----.-----.-----.|  |  |  |.----.|  |_

 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|

 |_______||   __|_____|__|__||________||__|  |____|

          |__| W I R E L E S S   F R E E D O M

 -----------------------------------------------------

 OpenWrt 21.02.0, r16279-5cc0535800

 -----------------------------------------------------

root@OpenWrt-1:/# reboot
root@OpenWrt-1:/# [   63.437535] br-lan: port 4(lan4) entered disabled state
[   63.448104] br-lan: port 3(lan3) entered disabled state
[   63.458733] br-lan: port 2(lan2) entered disabled state
[   63.469336] br-lan: port 1(lan1) entered disabled state
[   63.488367] device lan1 left promiscuous mode
[   63.497413] br-lan: port 1(lan1) entered disabled state
[   63.528097] mt7530 mdio-bus:1f lan1: Link is Down
[   63.541233] device lan2 left promiscuous mode
[   63.550256] br-lan: port 2(lan2) entered disabled state
[   63.583022] mt7530 mdio-bus:1f lan2: Link is Down
[   63.596085] device lan3 left promiscuous mode
[   63.605045] br-lan: port 3(lan3) entered disabled state
[   63.630864] mt7530 mdio-bus:1f lan3: Link is Down
[   63.643910] device lan4 left promiscuous mode
[   63.652879] br-lan: port 4(lan4) entered disabled state
[   63.678833] mt7530 mdio-bus:1f lan4: Link is Down
[   64.001502] mtk_soc_eth 1e100000.ethernet eth0: Link is Down
[   64.020815] mt7530 mdio-bus:1f wan: Link is Down
[   68.000374] reboot: Restarting system

--------freezing-----------

psherman · September 8, 2021, 2:26pm

How did you update the kernel? Did you attempt to do it using opkg upgrade?

Upgrading packages (via the CLI opkg upgrade command or the LuCI Upgrade... button) can result in major problems. It is generally highly discouraged, unless you know what you are doing or if there is specific instruction to do so.

Anubis · September 8, 2021, 2:34pm

I updated by (uboot) - to perform a clean install. Strange that this is the only problem. Update link - https://downloads.openwrt.org/releases/21.02.0/targets/ramips/mt7621/openwrt-21.02.0-ramips-mt7621-mediatek_ap-mt7621a-v60-squashfs-sysupgrade.bin

psherman · September 8, 2021, 5:12pm

so this was a fresh install of 20.0.2.0 with no further upgrades? Did you retain settings from a previous install, or is this also reset/default?

Anubis · September 8, 2021, 7:31pm

Even on standard. I didn't import the configuration... clean installation.

Borromini · September 8, 2021, 7:43pm

I think the reset is done by triggering a certain GPIO?

I'm not finding your device in the 21.02 tree, and what you're using looks more or less like a generic MT7621 image?

Anubis · September 8, 2021, 8:15pm

It even turns off the leds and turns them on again, but it doesn't show anything on the UART terminal (usb) after the reboot. This is the only problem. It is already set up and working normally. But I can't use auto restart in crontab.
Yes and somewhat generic. A development platform. HLK-7621 Chipset MT-7621AT.
If it is turned off and on the power starts normally.

Product link - https://www.hlktech.com/en/Product/Details/51

Borromini · September 8, 2021, 8:18pm

Compare the DTS of the 19.07 and the 21.02 image. Reset GPIO should still be the same, normally.

Is your uptime reset e.g.? If you're saying it's seemingly resetting the LEDs...

Borromini · September 11, 2021, 6:49am

@Anubis I bumped into this PR:

github.com/openwrt/openwrt

ramips: fix reboot for remaining 32 MB boards

openwrt:master ← mpratt14:ramips-reboot

opened 02:48AM - 11 Sep 21 UTC

mpratt14

+45 -7

The following devices have a Winbond W25Q256FV flash chip, which does not have …the RESET pin enabled by default, and otherwise would require setting a bit in a status register. Before moving to Linux 5.4, we had the patch: 0053-mtd-spi-nor-add-w25q256-3b-mode-switch.patch which kept specific flash chips with explicit 3-byte and 4-byte address modes to stay in 3-byte address mode while idle (after an erase or write) by using a custom flag SPI_NOR_4B_READ_OP that was part of the patch. this was obsoleted by the patch: 481-mtd-spi-nor-rework-broken-flash-reset-support.patch which uses the newer upstream flag SNOR_F_BROKEN_RESET for devices with a flash chip that cannot be hardware reset with RESET pin and therefore must be left in 3-byte address mode when idle. The new patch requires that the DTS of affected devices have the property "broken-flash-reset", which was not yet added for most of them. This commit adds the property for remaining affected devices in ramips target, specifically because of the flash chip model. However, it is possible that there are other devices where the flash chip uses an explicit 4-byte address mode and the RESET pin is not connected to the SOC on the board, and those DTS would also need this property. Ref: 22d982ea0033 ("ramips: add support for switching between 3-byte and 4-byte addressing") Ref: dfa521f12953 ("generic: spi-nor: rework broken-flash-reset") Signed-off-by: Michael Pratt <mcpratt@pm.me>

While it's not for MT7621 but for MT7628, maybe something similar is happening with your device? Can you check which flash chip you have?

Anubis · September 11, 2021, 9:36am

25Q256JVEQ - I didn't find his datasheet. BGA
It can be .They look similar.

gmtandi · September 13, 2021, 2:46am

Following. this problem is ocurring with me too... This is not BGA flash memory, it is only a WSON8 package, just like a dip8 32mbit spi flash, 8 pins only..

phammanh · June 14, 2022, 4:59am

I have the same problem with 21.02.3. It seems that the problem isn't fixed. Does anyone have the solution?