oh, I forgot totally to say that you need to attach USB cable into the OTG port! I told I did it with another rockchip board. and to my shame I cannot say now what exactly of them is OTG. you need to find it out. it's important.
But now when I looked into the rockchips' boot sequence, it doesn't look as optimistic as I thought. because USB OTG interface is tried at the end if nothing succeeded, oppositely to what I thought. Fortunately, for rk3328, but NOT for rk3399, ROM code tries eMMC first. So preparing a properly flashed eMMC module could save your board. If the problem is in the partially working/screwed up SPI NOR flash code.
For rk3399, spi is checked before eMMC and SD which is uh oh. because it can brick the board.
Forget about the rkdevtools, in short, :lol: use an eMMC module. if that doesn't work (but don't be hasty). that means the problem is not in SPI NOR flash.
But now when I looked into the rockchips' boot sequence, it doesn't look as optimistic as I thought. because USB OTG interface is tried at the end if nothing succeeded, oppositely to what I thought. Fortunately, for rk3328, but NOT for rk3399, ROM code tries eMMC first. So preparing a properly flashed eMMC module could save your board. If the problem is in the partially working/screwed up SPI NOR flash code.
For rk3399, spi is checked before eMMC and SD which is uh oh. because it can brick the board.
Forget about the rkdevtools, in short, :lol: use an eMMC module. if that doesn't work (but don't be hasty). that means the problem is not in SPI NOR flash.
ANT - my hobby OS for x86 and ARM.