[BPI-R64] OpenWRT kernel 5.4.40 running from eMMC

[svintuss]

Thank you, but I still need to load EEPROM for MT7615. As we discovered in this thread my board doesn’t have any preloaded calibration data.

[frank-w]

Then you need to add function for loading eeprom from file,this is how i did it:

mt76: allow loading eeprom from file

[svintuss]

Thank you. I will try it.

/lib/firmware/mediatek/%s_rf.bin is the path for EEPROM file? What does %s stand for? For MT7615 File should be named mt7615e_rf.bin?

P. S. Looks like you all made a great job and quite a progress since autumn.

[frank-w]

/lib/firmware/mediatek/%s_rf.bin is the path for EEPROM file? What does %s stand for? For MT7615 File should be named mt7615e_rf.bin ?

right %s is placeholder for driver name (dev->dev->driver->name). for files/filenames see https://github.com/frank-w/BPI-R2-4.14/commit/d1bc0e34c56d00663cd36b2242a924738924ef8c

[svintuss]

Do I need to make these changes to eeprom.c only or to mt7615/eeprom.c too?

[frank-w]

afair load-code is only in “global” eeprom.c, chip-specific is only interpretion of fields…just try to apply my patch and place files in your filesystem. make sure mt76 is compiled as module.

[svintuss]

• Installation to eMMC (and SPI-NAND) can be done using the bootloader menu when booting from SD card and also triggered to happen on next boot my modifying bootloader environment from inside OpenWrt. See https://openwrt.org/toh/sinovoip/bananapi_bpi-r64_v1.1#sd_card_installation
• The opposite is true now: There are only squashfs images, the same image can be used on SPI-NAND, eMMC and SD card for sysupgrade.
• mt76 still doesn’t supper loading EEPROM for MT7622 built-in 802.11bgn WiFi in a meaningful way for this board, you will need to patch to load from file.
• Yes, Bluetooth works out of the box.

Thank you for your wonderful job on making OpenWrt work.

However I’m stuck in a rather ridiculous situation: I’ve applied patches from @frank-w to load firmware from files, compiled OpenWrt, installed it on an SD card (and eMMC), have a working board with working WiFi, but it doesn’t have LUCI or uhttpd. Even though I’ve checked LUCI in menuconfig as a module. Could you give some advice on where to dig further?

[schnickidischnack (Nick)]

Is uhttpd listed when you call: opkg list-installed?

[svintuss]

Not unless I choose LuCI as built-in in menuconfig [*] indtead of [M].

[dangowrt (Daniel Golle)]

That’s the intended outcome then. If you want things to end up in the generated rootfs, you need to select them as * ie. built-in in OpenWrt’s menuconfig. Otherwise the build system will generate .ipk packages but will not install these packages in the generated image.

[svintuss]

Thank you.

That means that I need to create my own http server with all the packages? Or I can use mainline repo?

[alga_kbk]

Hi Guys, I have a question, does the BPI-R64 will work with the “OpenWrt-21.02”, where it uses the kernel 5.4. I tried it but wasn’t successful. An official branch of “OpenWrt-21.02”, when chosen BPI-R64 it doesn’t generate the img file, just sysupgrade bin file. When tried to upgrade with the bin file wasn’t successful. Could you guys point out how/which changes or patches needed to build OpenWrt-21.02 for BPI R64