thc013

  • Content Count

    26
  • Joined

  • Last visited

About thc013

  • Rank
    Member

Recent Profile Visitors

930 profile views
  1. Yeah it is a m2 slot and just 2 lanes and there are nvme ssd with a m2 key they are called m2 ssd they copied the m2 slot of the rk3399 board to a pcie/m2 slot with a flex cable so more as 2x pcie is not gonna happen i get today that pcie board , just in time i fixed yesterday the typc boot option in uboot the pinebook and the helios gave the solution rk3399 is not that good in bringing up all rails in 1 time and they do it in the board c file instead with the dts file
  2. 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
  3. 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
  4. 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
  5. try this but then with spi2 that spi port has no devices or flash conected to it and watch your pin numbers look at the link with a mysensors example for a orangepi4 it dont differ much just the spi pin nr spi 0 is the network chip spi 1 is the flash ship spi2 is free
  6. overlays=spi-spidev param_spidev_spi_bus=1 or overlays=spi-spidev spi-add-cs1 param_spidev_spi_bus=1 param_spidev_spi_cs=0 spidev is 1 installed wiringop ? 19 mosi 21 miso 22 ce (my configuration) (gpio pin 56 with wiringop) 23 clk 24 cs so for example my spidev setting in nrf24 radio = RF24(56, 10) and for exampe mysensors ./configure --spi-spidev-device=/dev/spidev1.0 --my-transport=rf24 --my-rf24-ce-pin=56 --my-rf
  7. yeah did you check what is on your optane or emmc or sd ? "Synchronous Abort" handler, esr 0x96000210
  8. dont have my orangepi4 yet but isnt it just for every rk3399 board with a spi on the pinout to boot from spi .
  9. just apt install devmem2 armbian-tools cp /etc/init.d/ap6212-bluetooth /etc/init.d/ap6212-bluetooth.bak cp brcm43438-patch /etc/init.d/ap6212-bluetooth chmod 700 /etc/init.d/ap6212-bluetooth rc-update done it is just that he added the devmen2 patch to another script and since you removed the extras you just install a armbian-tools for brcm_patchram_plus and just change the script
  10. install dev2mem and adjust and make /etc/init.d/ap6212-bluetooth look like this comment out the copy firmware and adjust the rest works for me can change with kernel updates # copy firmware #if [ -f "/lib/firmware/ap6212/bcm43438a0.hcd" ] && [ ! -f /etc/firmware/ap6212/4343A0.hcd ]; then # mkdir -p /etc/firmware/ap6212 # cp /lib/firmware/ap6212/bcm43438a0.hcd /etc/firmware/ap6212/4343A0.hcd #fi #if [ -f "/lib/firmware/ap6212/bcm43438a1.hcd" ] && [ ! -f /etc/firmware/ap6212/BCM43430A1.hcd ]; then # m
  11. thnks didn't compile armbian for a few weeks so got some catch up to do and stupid me the compile.sh script changed it automaticly to master by not finding sunxi-4.18
  12. where moved the sunxi-4.18 build to it is not on armbian git ?
  13. a bit futher make sure devmem2 0x1f00060 b 1 give as result Value at address 0x1F00060 (0xffff9eab1060): 0x1
  14. thnx zhen8883 i didm't notice that bluetooth was again not working . last weeks i fighting with spi and a nrf20l01 i can't get it working with mysensors and the rf24 lib works a bit but i tried al armbians from 5.38 till 5.46 and kernels from 4.14.14 till 4.14.48 and suddenly it is not working anymore . and i saw your blogs and tried a orangepi distro and works right away when activate it . only thing that was mentioned in the mailine bluetooth thread was that the rts and cts are not bind to uart1 in the dts file so i include them and and put them both in
  15. huh wipe out you only have to add the clock and extra gpio pin in the dts file .