Sadly, I’m also new to this, so I’m not comfortable commenting on your problem. You can try to contact/message @stich86. He’s been very helpful to me in the past. Also, try to follow the steps found here: [BPI-R3 Mini] Boot from NAND fails - #48 by stich86 first.
I always prefer a FT232(RL), but this is I also use it for rockchip devices. The FT232 can be set exactly to 1500000 baud, which you need for rockchip. The PL2303 will choose something near it, but not exactly 1500000. It also works great on the BPI-R3(mini)
you have to run this from (linux) client, not inside uboot…you have uboot running, but without usb support is tricky…afair stock uboot does also not support network…aren’t you able to boot linux from this uboot?
maybe you can list mmc partitions? but if you have an openwrt there you have no boot-partition like on debian to load kernel from in an easy way.
You must not open putty on same com port…it blocks the serial port like minicom in linux…only 1 application can access the serial device. And when the app is running it waits for device to start…then it sends the 2 files and closes…then you can start your putty on same com-port and you should be in uboot with usb support
the app says the payload is not found…i see you started the application with full path (so not changing the current work dir)…where have you the files? ideally they should be in same dir as the mtk_uartboot binary, then change to this dir and then run with ./mtk_uartboot
As you are “only” in uboot you have to convert it to uboot commands
So printing the correct filenames
ls usb 0:1
load usb 0:1 $loadaddr filename
mmc write ...
the problem is that mmc write needs offsets and cannot write to partitions…
one option would be starting a linux-kernel with initrd and doing the linux-steps i linked, or chainloading a openwrt u-boot (load …$uaddr u-boot.bin;go $uaddr) to do the steps manually.