written firmware successful to boot1…also found a nice guide from daniel here just used usb to transfer the files and used original files without concatenating before
usb start
mmc partconf 0 1 2 2
mmc erase 0x0 0x120
load usb 0:1 $loadaddr EthMD32.dm.bin
mmc write $loadaddr 0x0 0x20
load usb 0:1 $loadaddr EthMD32.DSP.bin
mmc write $loadaddr 0x20 0x100
mmc partconf 0 1 1 0
but have not tested it as i need to patch out my builtin-firmware before
Any news regarding the nvme support?
My uboot has nvme support for r3(mini) and r4 and sent patch to uboot mailinglist…no comment yet
Only got info that mt7981 was not yet working
Wish I had the time for it… So I won’t be doing that.
@frank-w did some work on that, but I do not know the state of it.
I used the openwrt driver,cleaned it a bit and “fixed” the working-once-issue and added the builtin-firmware (which cannot be added upstream). So basicly working,but no time for upstreaming yet. We need to switch to of_upstream (let uboot use linux dts) to upstream the filogic pci driver port from john.
this is what i currently work on…
Lucien posted phy driver officially
https://patchwork.ozlabs.org/project/uboot/patch/[email protected]/
Does this mean that failsafe functionality is possible via the web UI in uboot? I have used it on other routers before. This should make the unbrick process easier.
I do not know webui in uboot…but this patch is making network-support in uboot mainline once accepted and merged, so you do not need additional patches like in my repo or in openwrt.
Thanks. After some digging, the image I linked shows the failsafe feature provided by the OEM via modded uboot. It is not available in vanilla uboot.
Basicly it depends on working uboot and structure of the remaining image how this is done in uboot…not sure how to get a minimal webserver in uboot running. Easies way imho is a initrd which also must not be bricked