dale
Members-
Posts
41 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by dale
-
I have a question about booting from sd card. While with empty emmc (erase with rkdeveloptool), the board falls back to maskrom mode even the sd card (with working os) is inserted. It can boot armbian into sd card if I flash miniloader and u-boot in to emmc. I wonder how can we get it to boot fully from sd card.
-
@Nick A do you know how to remove key ring error? [π³|π±] git: Fetch from remote completed, rev-parsing... [ 'debootstrap-debian-devel' 'master' 'FETCH_HEAD' ] [π³|π±] Debootstrap version [ '1.0.142' for /armbian/cache/sources/debootstrap-debian-devel/debootstrap ] [π³|π±] Installing base system with 5 packages [ Stage 1/2 ] [π³|π¨] I: Retrieving InRelease [π³|π¨] I: Checking Release signature [π³|π¨] E: Release signed by unknown key (key id F8D2585B8783D481) [π³|π¨] The specified keyring /usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out of date. [π³|π¨] You can find the latest Debian release key at https://ftp-master.debian.org/keys.html [π³|π₯] error! [ Debootstrap first stage failed /armbian/cache/sources/debootstrap-debian-devel/debootstrap bookworm yes ]
-
@Nick A this is updated patch for x98h that enables wifi after warm reboot. 2001-arm64-dts-allwinner-h618-add-x98h.patch
-
I have a working img that boots fine from sd card. However the dtb is not perfectly working. Below are dts from android and linux (partial working). I hope that someone can help me with rewriting device tree source for it. Thank you! rk3399-emb3531.dts.txtrk3399-emb3531-android.dts.txt
-
@fabiobassa thank you, it is worth a try.
-
Hi all, I decided to revive my old rk3229 board with NAND. Could someone please tell me how to unbrick it?
-
Hi all, I would like to ask support for the board EMB-3531. I'm having problem with booting this board from SD card. Here are some informations about this board. I hope that someone can help me with it. Thank you so much! I try to erase the emmc and flash the MiniLoaderAll.bin but it doesn't help. Or i don't have a correct image with armbian for this board. https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf
-
Could you please explain why we need to erase and flash bootloader again? Could you elaborate the reason behind this step?
-
can you please share the config for the 3568 / or patch so I can refer to for the 3399 chip? Thank you!
-
Hi @Hqnicolas I have same issue with booting from SD card for a board (RK3399) . Can you please share the u-boot image or guide to compile for that chip?
-
Hi @Nick A, can you please publish the updated git verision with 6.17?
-
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
@Hqnicolas I will give it a try, but atm I'm happy with existing working patch for tm16xx. Edit: it seemed that @jock has updated the patch with latest code https://github.com/armbian/build/pull/8679 -
@Nick A I fixed the wifi issue after warm reboot for x98h with this patch:
-
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
I gave this a try but no success. The structure of original source code doesn't match the one for armbian. It would be great if you could make a patch as in this link -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
Can you make a patch for armbian? It will be easy for us to try. -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
Hi, I finally got my display to work with below DT overlay source. My device is x98h. Thank you! /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0x0>; spi-3wire; spi-lsb-first; spi-rx-delay-us = <1>; spi-max-frequency = <500000>; tm16xx,transposed; tm16xx,digits = [00 01 02 03]; tm16xx,segment-mapping = [00 01 02 03 04 05 06]; #address-cells = <2>; #size-cells = <0>; led@4,0 { reg = <4 0>; function = LED_FUNCTION_USB; }; led@4,1 { reg = <4 1>; function = LED_FUNCTION_SD; }; led@4,2 { reg = <4 2>; function = "hi-wifi"; }; led@4,3 { reg = <4 3>; function = "low-wifi"; }; led@4,4 { reg = <4 4>; function = "colon"; }; led@4,5 { reg = <4 5>; function = "apps"; }; led@4,6 { reg = <4 6>; function = LED_FUNCTION_LAN; }; }; }; }; -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
Hi, thanks for checking. I check dmesg -T | grep spi_gpio and see the error spi_gpio spi: probe with driver spi_gpio failed with error -22. Also the /sys/class/leds is empty. Do you think the gpio pins are not correct? Below are current gpio pins I try this time mosi-gpios = <&pio 2 11 GPIO_ACTIVE_HIGH>; /* PC11 = data */ sck-gpios = <&pio 2 12 GPIO_ACTIVE_HIGH>; /* PC12 = clock */ cs-gpios = <&pio 7 5 GPIO_ACTIVE_LOW>; /* PH5 = strobe/latch */ -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
@Jean-Francois Lessard sorry for making you confused. Device tree source for tm16xx driver that I convert from a working openvfd.conf is below /dts-v1/; /plugin/; #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/leds/common.h> &{/} { display_client: spi { #address-cells = <1>; #size-cells = <0>; compatible = "spi-gpio"; sck-gpios = < 7 GPIO_ACTIVE_HIGH>; mosi-gpios = < 2 GPIO_ACTIVE_HIGH>; cs-gpios = < 12 GPIO_ACTIVE_LOW>; num-chipselects = <1>; display@0 { compatible = "fdhisi,fd628"; reg = <0>; spi-3wire; spi-lsb-first; spi-max-frequency = <500000>; digits { #address-cells = <1>; #size-cells = <0>; 01 02 03 04 }; leds { #address-cells = <2>; #size-cells = <0>; led@{GRID0},0 { reg = <{GRID0} 0>; function = "apps"; }; led@{GRID1},1 { reg = <{GRID1} 1>; function = "setup"; }; led@{GRID2},2 { reg = <{GRID2} 2>; function = LED_FUNCTION_USB; }; led@{GRID3},3 { reg = <{GRID3} 3>; function = LED_FUNCTION_SD; }; led@{GRID4},4 { reg = <{GRID4} 4>; function = "colon"; }; led@{GRID5},5 { reg = <{GRID5} 5>; function = "hdmi"; }; led@{GRID6},6 { reg = <{GRID6} 6>; function = "video"; }; }; }; }; }; The convert script I downloaded from this commit https://github.com/jefflessard/tm16xx-display/blob/a93b257ed4c73780fcdefbb1f1dd189599cf6ecc/vfdconf-convert Can you please help get it to work? Thanks! -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
@Jean-Francois Lessard I'm sorry for the typo. Yes the controller is tm1628. ls /sys/class/leds --> shows empty. Dmesg doesn't show any message for tm16xx. I've attached the working overlay source for openvfd which I have the clock digits working at least with. (The full icons would be card, usb, Low wifi, hi wifi, apps and eth) openvfd_x98h.dts -
Help wanted to test a new OpenVFD alternative
dale replied to Jean-Francois Lessard's topic in Amlogic meson
Hi, @Jean-Francois Lessard I'm using a x98h box with self-built image. I have issue with the tm16xx kernel module using a patch https://github.com/paolosabatino/armbian-build/blob/main/patch/kernel/archive/rockchip64-6.16/general-driver-tm16xx-led-driver.patch The vfd controller is AIP1688 which is similar to fd628. Do you have any idea why it fails? -
@Nick A it has same issue. I thik it is related to the device tree declaration. Should it be something like this? https://github.com/LYU4662/aic8800-sdio-linux-1.0
-
@robertoj thank you for the answer. I will look at it. @Nick A Hi Nick, for your x98h box, is the wifi working after a reboot command?
-
-
Hi every one, Do we have a fix for bluetooth?
