Of course. He can’t sysupgrade that, because the partition layout is different. He needs to install the correct partition layout and bootloader once.
Finally I’ve was able to boot from any medium but different branches
- SD with the latest snapshot (Everything works well from here but have less space and it isn’t reliable
- eMMC With 21.02 and the commented issues
- NAND with 21.02 and I don’t care as is just being used to try flash eMMC
Yes that’s the site where I downloaded the images
I couldn’t found an updated eMMC .img to flash the snapshots just have SD .img and my SD is much smaller, and less reliable, tried to wrote that one to the eMMC but doesn’t work.
Tried also to boot from 21.02 eMMC and apply this sysupgrade but as you mentioned it doesn’t have any effect.
Could be due to be different branches or that is allowed? (This is a basic doubt I guess)
I followed different instructions for full installation, but not sure if your version
Thanks a lot for your help,
You didn’t listen. That’s the problem.
There is no emmc/nand image for mainline openwrt…this is installed from sdcard image via uboot menu (debug-uart necessary to see it). Uboot is before linux kernel starts…
So bootup from sd,flash nand,boot from nand,flash emmc.
He has no serial adapter. He needs to setup the uboot boot cmd to automatically install.
So change default boot option from one to whatever install to nand is. Then the same for the NAND uboot config.
I don’t know how easy that is with the default image he can download from openwrt website.
Is there any guide to follow in order to do this?
Could be, may you point me to what I’m missing?
Then it is time to get one (ftdi)…else it is hard to find error when system does not bootup properly and not reachable via network.
You are missing either a serial to usb adapter, preferably ftdi, or a customized openwrt image that defaults to installing or a customized uboot that has builtin telnet console or Webserver, neither of which exist yet.
Yes, the guides here in the forum, the wiki. And they all state you need a serial to usb adapter. That’s the guide. There is no other.
How thoughtful of them to not mention that a serial cable was a must-have accessory. Took two months to arrive from China to Argentina. I’ve spent nearly two more weeks pulling my hair out over this. Buying it upfront would have saved me the shipping fee and a ton of frustration.
Thanks for your support and have a great year
Happy New Year!
You can set up the installation as needed via SSH.
SD boot => SSH =>
fw_setenv bootcmd "env default bootcmd ; saveenv ; run ubi_init ; bootmenu 0"reboot
Wait until the installation to NAND completes, and the router boots from SD.
Turn off the router, switch the boot to NAND.
NAND boot => SSH =>
fw_setenv bootcmd "env default bootcmd ; saveenv ; run emmc_init ; bootmenu 0"reboot
Wait for the router to reboot. Turn off the router, switch to eMMC boot.
Boot from eMMC => profit
With UART access, it’s easier, and you can view logs in case of an error. However, this is not an essential tool, and it can be bypassed, although it’s an unusual option that doesn’t immediately come to mind for the user.
Aren’t there steps missing? You can’t install from SD to MMC, because as Frank mentioned, there is just one controller in the CPU. It’s either one or the other.
Doesn’t he need to switch to NAND boot after the first execution of your changes? As far as I understand them you switch the default uboot option to install, right?
So it’s SD boot, fw_env changes, SD boot (installs to NAND), NAND boot, fw_env changes, NAND boot (installs to eMMC), eMMC boot?
This 21.02 MTK SDK version, that comes with; is it the only one (as compared to openwrt.org’s snapshots) that lights up the 2G/5G/6G blue LEDs on BE14000 card?
Otherwise looks workable, and AC and AX speeds are good, but how to turn on EHT320 on the 6 GHz radio? Regardless what I try on /etc/config/wireless, iwinfo shows HT20 on rax0 radio. This with the 21.02 SDK version only - I can turn on EHT320 on the 24.10 snapshot versions.
Any help appreciated.
I would have gone on the 24.10, either rc4 or snapshot, but for some reason or another, it occasionally freezes my SSH connections on WLAN… and only the SSH connections. Plus the aforementioned LED weirdness.
For led i guess there is anything missing in driver which was added in sdk somewhere…looked through some of the patches there,but have not found something led-related
Maybe you can try if self compiling from this repo has also led support. Possibly bpi released image modified a bit.
For hang i have no idea…i guess it is an issue in dma handling,but only affecting ssh is strange…what have you tried? Ping,other tcp based protocol?
Yes, ping (which doesn’t count, as is either udp or icmp). Even for more weird, plain-old Telnet session doesn’t suffer at those times. Only SSH.
We really need to keep topics separate. Could you create a new one for this issue?
2 Likes
Could be some issue in encryption. If there 1 packet gets lost and not retransmitted by tcp (or broken again) it could break ssh.
@totkeks ack better 2 topics one for mt7996-led one for ssh hang there
Sorry about topic loaning. Didn’t have credentials to start my own.
You’re right. I mixed up the memory type when I wrote that, but not the commands.
run ubi_init installs to NAND,
run emmc_init installs to eMMC.
I corrected my message.