I see that “bootconf_emmc=mt7988a-bananapi-bpi-r4-pro-8x-emmc” in uboot console, but if there is this var, i have error “Waiting for root device /dev/fit0”. If i use “setenv bootconf_emmc mt7988a-bananapi-bpi-r4-pro-emmc run boot_production” in uboot console, system is starting. This problem only occurs when I build the image myself. Plus, after loading, half the interfaces stop working, and the router behaves erratically. Sorry about my English))
My main goal is to install “sing-box” and Momo
Yes it is an issue i fixed in my tree already but not yet added to andrews PR
-boot_recovery=led $bootled_rec on ; run sdmmc_read_recovery && bootm $loadaddr#$bootconf#$bootconf_emmc ; led $bootled_rec off
+boot_recovery=led $bootled_rec on ; run sdmmc_read_recovery && bootm $loadaddr#$bootconf#$bootconf_sd ; led $bootled_rec off
what target i need to choose? BPI-R4-Pro-8X?
maybe you can give me .config file? 
Yes, it is same as with andrews pr
Hi @frank-w,
To me, it looks this commit is not part of a branch. Is this correct? Is there a branch I could try to get OpenWRT running on such a board that is as close to mainline / vanilla OpenWRT as possible, but working?
Many thanks, yanosz
Pcie overlays are now part of the pr after they got added mainline. Seems i rebased that branch so the commit itself got a new id and the old commit id is no more linked
My last state is R4Pro_PR8
Hi,
many thanks! I was able to boot R4Pro_PR8. It looks fine on a quick glance. There are some PCIE warnings / errors that make me a bit worried, but I haven’t found the time to play with m.2 modules, yet.
Greetz, yanosz
[ 0.079148] mtk-xsphy soc:xs-phy@11e10000: failed to get ref_clk(id-1)
[ 0.079839] mtk-pcie-gen3 11280000.pcie: host bridge /soc/pcie@11280000 ranges:
[ 0.079841] mtk-pcie-gen3 11290000.pcie: host bridge /soc/pcie@11290000 ranges:
[ 0.079858] mtk-pcie-gen3 11280000.pcie: Parsing ranges property...
[ 0.079860] mtk-pcie-gen3 11290000.pcie: Parsing ranges property...
[ 0.079880] mtk-pcie-gen3 11290000.pcie: IO 0x0028000000..0x00281fffff -> 0x0028000000
[ 0.079881] mtk-pcie-gen3 11280000.pcie: IO 0x0020000000..0x00201fffff -> 0x0020000000
[ 0.079901] mtk-pcie-gen3 11280000.pcie: MEM 0x0020200000..0x0027ffffff -> 0x0020200000
[ 0.079903] mtk-pcie-gen3 11290000.pcie: MEM 0x0028200000..0x002fffffff -> 0x0028200000
[ 0.079942] /soc/pcie@11290000: Failed to get clk index: 0 ret: -517
[ 0.079956] mtk-pcie-gen3 11290000.pcie: failed to get clocks
[ 0.080014] mtk-pcie-gen3 11300000.pcie: host bridge /soc/pcie@11300000 ranges:
[ 0.080027] mtk-pcie-gen3 11300000.pcie: Parsing ranges property...
[ 0.080064] mtk-pcie-gen3 11300000.pcie: IO 0x0030000000..0x00301fffff -> 0x0030000000
[ 0.080069] mtk-pcie-gen3 11310000.pcie: host bridge /soc/pcie@11310000 ranges:
[ 0.080083] mtk-pcie-gen3 11300000.pcie: MEM 0x0030200000..0x0037ffffff -> 0x0030200000
[ 0.080086] mtk-pcie-gen3 11310000.pcie: Parsing ranges property...
[ 0.080108] /soc/pcie@11300000: Failed to get clk index: 0 ret: -517
[ 0.080115] mtk-pcie-gen3 11310000.pcie: IO 0x0038000000..0x00381fffff -> 0x0038000000
[ 0.080121] mtk-pcie-gen3 11300000.pcie: failed to get clocks
[ 0.080129] mtk-pcie-gen3 11310000.pcie: MEM 0x0038200000..0x003fffffff -> 0x0038200000
[ 0.080152] /soc/pcie@11310000: Failed to get clk index: 0 ret: -517
[ 0.080162] mtk-pcie-gen3 11310000.pcie: failed to get clocks
The error -517 is eprobedefer and it is tried later when depencies are ready. It is a very early error and should not affect later usability