02-04-2023, 11:29 PM
>>
I deduce that:
manjaro-arm-installer presumably installed U-Boot on SPIFlash when installing Manjaro on the emmc.
This version of U-Boot is unsuitable for SPIFlash.
I can disable the SPIFlash to try to start U-Boot on the emmc or on the SD card (hardware deactivation).
>>
1) possible but unlikely
2) code is same, but locations different (idbloader@0, uboot@6M), also idbloader
has some extra blank sectors inserted in it
3) the recovery button is also supposed to short SPI, this is NOT 100% reliable
To put the rk3399 into otg mode there must be no media
rkdevelop will work, it is a bit 'fiddly'
since you said you have a usb stick boot, try to install mtd-utils,
then ,,, flash_erase /dev/mtd0 0 0
OR mtd_debug erase /dev/mtd0 0 16777216
both programs in mtd-utils
It is unlikely that the manjaro update wrote to the nand
I deduce that:
manjaro-arm-installer presumably installed U-Boot on SPIFlash when installing Manjaro on the emmc.
This version of U-Boot is unsuitable for SPIFlash.
I can disable the SPIFlash to try to start U-Boot on the emmc or on the SD card (hardware deactivation).
>>
1) possible but unlikely
2) code is same, but locations different (idbloader@0, uboot@6M), also idbloader
has some extra blank sectors inserted in it
3) the recovery button is also supposed to short SPI, this is NOT 100% reliable
To put the rk3399 into otg mode there must be no media
rkdevelop will work, it is a bit 'fiddly'
since you said you have a usb stick boot, try to install mtd-utils,
then ,,, flash_erase /dev/mtd0 0 0
OR mtd_debug erase /dev/mtd0 0 16777216
both programs in mtd-utils
It is unlikely that the manjaro update wrote to the nand