Hi All,
I updated one of my two RK3288 boards (Viewsonic) with newer Android factory firmware (using Windows) and now it won't boot mainline u-boot when I use the same exact recipe that worked previously:
sudo ${UPGD} db rkbin/rk32/rk3288_boot.bin sudo ${UPGD} wl 0x40 tftpboot/u-boot-dtb.bin
Been trying to figure out what's wrong. My theory is that the newer firmware enabled one of the "boot areas" of the eMMC and the "wl 0x40" command above only writes to the user area of the eMMC.
I can still load and run one of the Android u-boots using the boot_merger method:
./tools/boot_merger --subfix ".10.bin" ./tools/rk_tools/RKBOOT/RK3288.ini
then flashing via:
sudo ${UPGD} ul u-boot-android/RK3288UbootLoader_V2.30.10.bin
But these u-boot's are virtually useless since they striped of useful commands (like mmc commands).
I tried using the above boot_merger command on mainline u-boot but it only boots this far (I've tried u-boot-dtb.bin and u-boot.bin):
-------------------------- U-Boot 2016.11-08467-g05b8ba7-dirty (Jan 15 2017 - 10:40:37 -0800)
Model: SCT36-RK3288 DRAM: 128 MiB --------------------------
Note the incorrect DRAM size. My normal boot looks like:
-------------------------- U-Boot SPL 2016.11-08467-g05b8ba7-dirty (Dec 18 2016 - 11:00:14)
U-Boot 2016.11-08467-g05b8ba7-dirty (Dec 18 2016 - 11:00:14 -0800)
Model: SCT36-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 0, dwmmc@ff0f0000: 1 ... --------------------------
Note that this runs SPL, then normal u-boot whereas the previous one didn't run SPL.
Any ideas how I can get mainline u-boot running on this board?
Thanks much,
Rick