thc013

lol what a mess
 
do just a proper reverse of the dts then just using a decompiled one .
 
 

it is not a bootsplash problem
 
at boot the kernel searches for device and activates them and if a device takes time to get seen by the kernel the kernel get a amount of time to wait
so when a device for example my usb3 got called before the bootsplash there is no bootsplash because kernel is waiting for the usb before he wants to put something on screen.
 
you can see that effect if you boot through a console then you see the kernel spit out messages sometimes fast sometimes slower
and it happens even more when you reboot but that is more less nowdays because the drivers are getting better
 

they are back in stock now from what i see , i just ordered one last week
 
https://www.aliexpress.com/item/4000575054675.html?spm=2114.12010612.8148356.1.30b67fddNzcI4W

Thnx Werner little cryptic message
 
Yah already updated topic titel i made some fixes
 
HDMI Uboot support works it was a dts change in the kernel dts , &cdn_dp and hantro are not good friends with hdmi yet
so
from SD
 SD (duh) ,USB3, USB-C works so pi 4b users can have some more options as the sd and mmc ,emmc and nvme not tested yet.
From SPI
SD ,USB3 , somehow fusb302 keeps his f up to still be fuzzy so no USB-C yet Uboot gives it no power and mmc and nvme not tested yet .
 
HavE Fun
 
Ps you can now change pi to his own
 
elif [[ $BOARD == orangepi4 ]]; then
    BOOT_USE_BLOBS=yes
    BOOT_SUPPORT_SPI=yes
    BOOT_SOC=rk3399
    DDR_BLOB='rk33/rk3399_ddr_933MHz_v1.24.bin' # Orange Pi 4 does it has 4gb standard and is cheaper and b has also a ai 
    MINILOADER_BLOB='rk33/rk3399_miniloader_v1.19.bin'
    BL31_BLOB='rk33/rk3399_bl31_v1.30.elf'
 
or 
elif [[ $BOARD == orangepi4 ]]; then
    BOOT_USE_MAINLINE_ATF=yes
    BOOT_SUPPORT_SPI=yes
    BOOT_SOC=rk3399
    ATFPATCHDIR='atf-rk3399'
 
if you apply the changes
 
 
 
 
 
 
 
kernel-rockchip64-dev.patch linux-dtb-dev-rockchip64_21.02.0-trunk_arm64.deb linux-u-boot-dev-orangepi4_21.02.0-trunk_arm64.deb orangepi-4-rk3399_defconfig rk3399-orangepi-4-kernel.dts rk3399-orangepi-4-u-boot.dtsi rk3399-orangepi-4-uboot.dts sd-usbc-dmesg.txt spi-uboot-atf-log.txt u-boot-rockchip64-dev.patch

After Seeing all that spi nmve boot hype for the other boards and some time left i took the effort to level up the Orange Pi boards because they are the same as the rest it has a rk3399.
 
The Uboot was a mess so i matched it with the kerenel dts a lot and corrected some issues.
Dts debug is not the friendliest debug it compiles or not
 
And after some trial and error (a lot ) and finding a spi nor flash wich is supported (or you add one of your own) it costs a esp8266 has 4mb spi flash or a old printer who had a 4mb and 8mb
i got a boot from spi so . and with reading the armbian forum i saw 150balbes talked about usb boot and didnt know if usb3 works well after adding some tcphy usb was seen by uboot  .
 
so SPI > USB3 boot works and take note USB3 not USBC (fusb30x) yet
 
so next attempt was emmc so ordered some emmc chips , and because there are a lot i made the mistake to order 4.5 instead at least 5.0 so emmc is not checked but should work nothing realy changed there maybey the env in uboot option
 
and you saw also the ? with nvme yeah that is in the mailbox from ali but should also work but is not tested .
 
And even take the kernel dts and changed that to match the other dts in alphabetic order and added USBC so kernel sees the usbc port and change to what is connected as you can see in the kernel logs .only it broke a little the hdmi uboot option why i think it was late and forgot a dts option but i got both the dtb so only have to check what option i forogot to combine those 2 usbc and hdmi .
 
And sure there will be mistakes by me but at least the orangepi4 has is dts updated and more boot options as before and even more as other boards.
 
i attach the armbian patches and log files for who is interested .
 
have fun with it
 
ow ps
you have to change the
 
\build\config\boards\orangepi4.conf
and add
BOOT_FDT_FILE="rockchip/rk3399-orangepi-4.dtb"
 
and in
\build\config\sources\families\rk3399.conf
add
BOOT_SUPPORT_SPI=yes
 

 
 
 
 
hdmi.dtb hdmi.dts kernel-rockchip64-dev.patch orangepi-4-rk3399_defconfig rk3399-orangepi-4-kernel.dts rk3399-orangepi-4-uboot.dts sd-boot-log.txt sd-dmesg.txt spi-sd-sd-bootlog.txt spi-sd-sd-dmesg.txt spi-sd-sd-dmesg-usbc.txt spi-usb3-hdmi-bootlog.txt spi-usb3-hdmi-dmesg-console.txt spi-usb3-hdmi-dmesg-desktop.txt u-boot-rockchip64-dev.patch usbc.dtb usbc.dts

nah that is to short to help
 
what did you used for spi device
 
wich pins on opi you are using
 
how looks your armbianenv. file dig you include in overlays spi and did you set it to 1
 
or if you using a flash device your armbianenv is different

enable overlay uart 1
and add
param_uart1_rtscts=1
 
to armbianenv.txt
 
and adjust /etc/init.d/ap6212-bluetooth so it looks like this
 
  # Start patching
        rfkill unblock all
        echo "0" > /sys/class/rfkill/rfkill0/state
        echo "1" > /sys/class/rfkill/rfkill0/state
        echo " " > /dev/$PORT
        devmem2 0x1f00060 b 1
        echo 10 > /sys/class/gpio/export
        echo out > /sys/class/gpio/gpio10/direction
        echo 0 > /sys/class/gpio/gpio10/value
        echo 1 > /sys/class/gpio/gpio10/value
        sleep 0.1
        hciattach /dev/$PORT bcm43xx 115200 flow bdaddr $MAC_OPTIONS
        hciconfig hci0 up
 
 and reboot
 
oh you might need to install devmem2
 

tkaiser good work
 
added your fex to the openelec build of jernesk and working properly
 
http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=1124&extra=page%3D1
 
temps are ok
 
[ 5825.541921] [pm]state:0 invalid!
[ 5825.541936] [pm]state:1 valid
[ 5825.541944] [pm]state:3 valid
[ 5825.541950] [pm]state:7 valid