You have to install lucy for webfrontend.
Wifi should work (maybe you need to load modules for it.
My nor does not even have bootheaders…and if you flash nor or nand after sdboot does basicly not matter,you do not need openwrt or a linux kernel there to flash emmc…only external storage like usb (of if stored somewhere on the nor/nand) for loading bins to write (nor is too small for it)
Maybe you bought it before they started to deliver the router with a preloaded firmware. In this video (at 1:08) they mention that “Image file has been burned to NAND before delivery”… however it is burned to NOR, not NAND… and it seems he is booting from NOR, so it is only a mistake in the video, but the firmware is already flashed. At least in my device it was there.
I tried the bananapi_bpi-r3-sdcard.img image from the https://downloads.openwrt.org/snapshots/targets/mediatek/filogic
The stock image has issue i think, I never succeeded boot to EMMC after flash SD -> NAND -> EMMC using stock SD image, so I compiled & using SD image from compilation and did a Restore Boot loader, recovery, production image to them (NAND, EMMC) on boot menu (need UART connection).
It is highly recommended to get a UART adapter before you plan to flash firmware to any device, as some recovery procedure requires UART input, or you can observe the output in case something goes wrong.
Correct, it came with firmware installed on NAND on my BPI-R3.
It seem that it is flahsed to NOR and NAND, too… but in the video it mentions NAND, but the switches are all “Low”, which means the NOR flash.
I suggest you compile official Openwrt firmware (Snapshot) and copy to SD then boot from SD, it will be a lot easier than Sinovoip’s method, you can flash NAND, NOR, SD, EMMC right on the boot menu. see the 7,8 menu item.
Openwrt snapshot works wonderfully with BPI-R3, wireless AC,AX performance is amazing.
Ok, I buy an UART cable and will do that. Is it possible to build openwrt on windows? Is it easy?
Haven’t tried that in Windows linux subsystem, a real Linux is so easy to setup nowadays, almost plug & play with all the hardware detected & installed properly.
Forget about Windows, you are already at the front door of Linux (openwrt), so why not step in?
I also tried WSL to call the “wipefs”, but then give up… So booted an Ubuntu from usb drive. I’m a .NET developer, mostly working on a desktop (WPF) project, so I need Windows for that… maybe I’ll install it on a 2nd laptop.
Add a SSD/resize partition… make a dual boot.
That’s not true. OpenWrt uses overlayfs usually backed by a filesystem in a persistent storage volume on the device used for booting. This doesn’t need to be configured in any way and happens by default.
Only in case of that filesystem not being available, tmpfs is used for overlay. Ie. when something is broken you still get to a shell somehow, but it’s not a good setup for production, obviously.
I guess that about 95% of all devices supported by OpenWrt come with rather small SPI-NOR or SPI-NAND flash chips. Linux and rootfs easily fits in less than 10 MiB, still leaving a few MiB for user data and configuration to the user even on just 16 MiB SPI-NOR.
128 MiB of SPI-NAND is really huge for a router firmware, you end up with > 80 MiB of free space even with excessive amount of pre-installed software. Ok, if you are a device vendor and want to ship translations for 26 different human languages for UI, all possible USB drivers, … out of the box, then SPI-NAND is a good choice.
IMHO eMMC is really only needed for multimedia OS (hence the name…) or when using the device as a server to host complex container or VM images to provide additional services provided only in this format (but in that case it’s probably advisable to add NVMe SSD).
Of course, when using a general purpose OS like Debian, that’s a different story. It comes with all documentation and even development tools on-disk and hence needs lots more space…
You don’t need to build OpenWrt from source if you are not planning to modify low-level sources. Just use the OpenWrt Firmware Selector which also allows you to customize the generated firmware image (click on Customize installed packages), e.g. adding luci-ssl will generate an image with pre-installed Web-UI.
lol yeah correct, but how I wish we all are expert like you dangowrt. without UART its like a blind man driving a car for me, in case something went wrong I don’t know which direction to go. I am still scratching my head with Xiaomi AX3200.
hi I also encounter the same problem in here https://forum.banana-pi.org/t/banana-pi-bpi-r3-openwrt-image/13236/50
hi every morning i have one question when i set openwrt and click save & apply button then use openwrt luci`s reboot it is recovery to not set openwrt how can i fix this bug? or operational problems?
problem persists
OK I will try be later~ thx
i use openwrt firmware and it can success save my set, but new i receive other question. when i ues web-ui and change luci set just like server name , and i click save/apply can see countdown timer , when countdown timer in 85 and web say save [The configuration changes have been applied.] and now i poweroff and poweron, wait to ui and check my change and i find The configuration changes haven`t been applied.but if i ues web-ui system reboot onece than poweroff and poweron The configuration changes have been applied,so how can i check this question or fix it?
Same problem while using SD or EMMC. With NAND its OK, settings is saving successfully.
In bootlog is presented that:
[ 2.602669] eeFlashId(0xffff) isn't match with 0x7986!
[ 2.602671] Flash content is empty, so use AX6000 configuration by default!
Update
Installed to eMMC image from OpenWRT site.
Now all OK with settings saving, but R3 doesn’t works with 160MHz 5G channel and I have only 87.2MB overlay to store applications…
for resizing partition daniel posts some instructions and warnings because this may break sysupgrade if root-partition is larger or equal in size of ram
for 5G-channel: it depends on regioncode is there is any free 160MHz-channel as this maps different channels together and afair i have seen a patch which allows only 80Mhz channelwidth.