I have the AsiaRF 7916 mini pci module. After some research I seen where the MT7915e module works for the AsiaRF 7916 module. If I try to do the entire build with the needed modules it fails.
Is there a way to just compile kmod-mt7616-firmware and kmod-mt7615e by their selves?
Why not using an up to date kernel? Daniel pushes his changes for r4 to official openwrt. Kernel 6.1 should support mt7916 better than the 5.4 of bpi openwrt.
I’m sorry for the questions but could you explain how to do that? Just use the snapshot? Or should I build it? Will that snapshot that’s already built for the r4 support the 7915e? If I use the snapshot do I still need the 7916-firmware?
With the openwrt git hub I was easily able to build openwrt for the R4. I don’t know how to get it to build the bl emmc image, emmc image, and the nand image though… What do I add to the .config to get these other images to build?
I follow you I think, but the uboot file for the nand is 1mb. Doesn’t seem right does it? I thought I’d have a full image to flash to the nand. When my build is finished I have a 31mb sd image and then several images for the nand and emmc that are all 1mb or smaller. When I built with the BPI openwrt git hub it created several full size images.
Yes, I have that image too. That image was missing some of the modules I needed so I had to compile my own. It’s not a big deal, I just wanted to flash over to the EMMC.
Also their images are the same size as mine. I thought the EMMC image I flash would be a full size image, the ones you linked and mine are all 1mb.
Everything needed to install to NAND or eMMC is included in the SD card image. If you connect serial console you can install to SPI-NAND and then from there to eMMC using the bootloader menu. I know, 31 MiB doesn’t seem enough, but for OpenWrt terms this is a huge file
Edit: In mainline OpenWrt we do not need different images for SD card, NAND and eMMC. The same image can be used once the bootloader has been installed.
It’s really dead simple and the only file you need from all the files created in bin/targets/mediatek/filogic is the sdcard image. The other files are meant for bootloader updates when everything is installed already.
There are generally two way to install bootloader and OpenWrt images to the device:
Using OpenWrt/Linux (using command line, can be done via SSH) or using the U-Boot serial console (easy, menu driven, needs serial connection).
The generated SD card image basically also contains bootloader images for SPI-NAND and eMMC. And the same recovery (= with initramfs) and production (= using squashfs as rootfs) OpenWrt images used on the SD card can be used on SPI-NAND and eMMC.
So installation always starts with the SD card image written to a microSD which is then used to boot the R4 (and it’s the exact same procedure with mainline OpenWrt also on the R2, R64 and R3).
If you have the serial console connected it’s very easy, you just use the arrow-keys or numbers to chose the menu item Install bootloader, recovery and production to NAND. That will take care of installing everything to SPI-NAND. Then change the dip switches to boot from NAND, reset the board for that to take effect and be done if you are fine with OpenWrt running off the SPI-NAND. If you want to run OpenWrt from the eMMC, find the option Install bootloader, recovery and production to eMMC. in the bootloader menu when booting from SPI-NAND.
I’ve been waiting a few weeks for an E key → mPCIe adapter to arrive; I’m hoping (but realistically not likely, considering their intentional breakage surrounding Location Aware Regulatory) a Intel BE200 module could be coerced into working in AP mode:
