Sergioclr Posted Wednesday at 02:25 PM Posted Wednesday at 02:25 PM Newbie on Armbian. I have an Allwinner H313 (confirmed) box that I want to to use as a basic Samba server. CPU:Allwinner H313Quad Core ARM Cortex A53 GPU:Mali-G31 OPenGL ES3.2 Memory:2GB Flash:16GB OS:Android 10.0 The actual firmware is a secure image and, no matter what procedure I do, I can't load any other image but the secure one. Debugging shows that 'fastbootd' has the "secure" flag set. My intention is to create a basic secure arm64 Debian image but I am having a hard time in doing so. Any ideas (specific Wiki, procedures) on how to create the secure image or "reset" the "secure" flag will be very appreciated. Thanks in advance. 0 Quote
Sergioclr Posted Wednesday at 09:05 PM Author Posted Wednesday at 09:05 PM On a first analysis, I noticed that the git already has a very similar option that I need (H313): ~/build/patch/u-boot/u-boot-sunxi/board_x96q$ arm64-sun50i-h313-add-x96q-lpddr3-defconfig.patch sunsi-add-h616-internal-eth-phy-support.patch so I am stuck on how to proceed because the example has H616 parameters. Help will be appreciated. 0 Quote
Nick A Posted Wednesday at 09:27 PM Posted Wednesday at 09:27 PM (edited) @Sergioclr the H313, H616, H618, and IK316 are essentially the same SoC family. To successfully boot an image, you must match the correct AXP chip (the Power Management IC) and the specific DRAM version used on your board. Essentially, any thread discussing the H616/H618 (excluding older H3/H5/H6 chips) will contain relevant information for these SoCs. PMIC Information: http://linux-sunxi.org/AXP_PMICs DRAM Types: 3: DDR3 4: DDR4 7: LPDDR3 8: LPDDR4 You can try flashing various boot images until one successfully initializes your hardware. (If your box is secure-boot enabled, you will need to add the secure-boot modifications posted above.) https://github.com/NickAlilovic/build/releases/tag/20250306 Alternatively, for a more precise approach: Extract your Device Tree (DTS). Identify the specific AXP chip located on your board. Connect a USB-to-UART TTL device to the RX, TX, and GND pins on your board to monitor the boot sequence. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-232411 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/4/#findComment-187672 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 https://docs.radxa.com/en/rock5/rock5itx/radxa-os/serial?os=windows https://linux-sunxi.org/UART https://www.amazon.ca/IZOKEE-CP2102-Converter-Adapter-Downloader/dp/B07D6LLX19/ref=sr_1_2_mod_primary_new Decompile your Device Tree Blob (DTB😞 dtc -I dtb -O dts -o source.dts source.dtb For a visual reference of a board using these specific chips, check out this hardware breakdown. http://nskhuman.ru/allwinner/krugh618.php?np=3 Edited 6 hours ago by Nick A 0 Quote
Sergioclr Posted Thursday at 06:12 PM Author Posted Thursday at 06:12 PM $ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.4 Compile phase failed due to missing package (ntpdate) Short log: [🌱] Configuration prepared for BOARD build [ x98h.csc ] [✨] Repeat Build Options (early) [ ./compile.sh build BOARD=x98h BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=trixie ] [🌱] Checked directory OK for mount options [ /home/*****/build/.tmp ('main temporary dir') ] [🌱] Preparing [ host ] [🌱] Python2 not available on host release 'trixie' [ ancient u-boot versions might/will fail to build ] [🌱] Updating apt host-side for installing host-side packages [ 50 packages ] [🌱] Installing host-side packages [ binfmt-support bison libc6-dev make dpkg-dev gcc ccache device-tree-compiler dwarves flex imagemagick jq libbison-dev libelf-dev libfdt-dev libfile-fcntllock-perl libmpc-dev libfl-dev lz4 libncurses-dev libssl-dev libusb-1.0-0-dev ntpdate patchutils pkg-config pv qemu-user-static arch-test swig u-boot-tools uuid-dev zlib1g-dev expect colorized-logs zip pigz pbzip2 lzop gdisk aria2 axel parallel rdfind libpython3-dev libffi-dev libgnutls28-dev gcc-aarch64-linux-gnu libc6-amd64-cross gcc-arm-linux-gnueabi gcc-or1k-elf ] [🔨] E: Package 'ntpdate' has no installation candidate [💥] error! [ Failed to install host packages; make sure you have a sane sources.list. ] [💥] Cleaning up [ please wait for cleanups to finish ] [🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-dd186c47-e7eb-49f8-8d38-836915cf0aec.log.ans ] [🌱] Share log manually: [ use one of the commands below (or add SHARE_LOG=yes next time!) ] Note ntpdate has a more recent version: ntpsec-ntpdate Should I try to compile in a Debian 12 computer? I am afraid of messing with 'sources.list'. Thanks in advance. 0 Quote
Nick A Posted Thursday at 06:25 PM Posted Thursday at 06:25 PM @Sergioclr Requirements for self hosted x86_64 / aarch64 machine at least 2GB of memory and ~35GB of disk space for VM, container or bare metal installation Armbian / Ubuntu Jammy 22.04.x for native building or any Docker capable Linux for containerised Windows 10/11 with WSL2 subsystem running Ubuntu Jammy 22.04.x Superuser rights (configured sudo or root access). Make sure your system is up-to-date! Outdated Docker binaries, for example, can cause trouble. 0 Quote
Nick A Posted Thursday at 06:27 PM Posted Thursday at 06:27 PM (edited) @Sergioclr you can also try a newer branch https://github.com/NickAlilovic/build/tree/v20251014 https://github.com/NickAlilovic/build/tree/v20251014?tab=readme-ov-file#build-host-requirements Edited Thursday at 06:28 PM by Nick A 0 Quote
Sergioclr Posted Saturday at 07:55 PM Author Posted Saturday at 07:55 PM (edited) Update: I was able to compile the H98H example and write it to SD card (Armbian Imager). The SD firmware load promptly "bricked" the box! I reloaded the original (secure) image by means of PhoenixSuit software. I am considering building an image using sun50i-h313-x96q-ddr3-v5.1.dts but I don't know how to customize the "@@ -0,0 +1,162 @@" parameters. Could you help me? Thanks in advance. Edited Saturday at 09:30 PM by Sergioclr choice of words 0 Quote
Nick A Posted Saturday at 08:02 PM Posted Saturday at 08:02 PM (edited) @Sergioclryou are only adding one line of code.. so whatever it is just add one. 162 would be 163. Edited Saturday at 08:03 PM by Nick A 0 Quote
Nick A Posted Saturday at 08:25 PM Posted Saturday at 08:25 PM (edited) @Sergioclr can you find a AXP chip on your board? It’s safer to boot images with the same AXP chip. I haven’t bricked any of my boxes. Don’t use armbian-config’s write to emmc until you have a stable image. Edited Saturday at 08:32 PM by Nick A 0 Quote
Sergioclr Posted Saturday at 09:28 PM Author Posted Saturday at 09:28 PM 😳number of lines of code? My bad. Photo with details: 0 Quote
Nick A Posted Saturday at 11:43 PM Posted Saturday at 11:43 PM @Sergioclr Try this one next. 159-add-x96-q-lpddr3-v1.3-defconfig.patch 0 Quote
Sergioclr Posted 20 hours ago Author Posted 20 hours ago After compiling many (10+) images, I was not able to boot a single one through SD card and the "toothpick" technique. It is not my character, but I give up. I am grateful for your support and patience. Thank you. Sergioclr. 0 Quote
Nick A Posted 19 hours ago Posted 19 hours ago (edited) @Sergioclr are you sure the board has secure boot enabled? You should install a USB-to-UART TTL device. Edited 19 hours ago by Nick A 0 Quote
Sergioclr Posted 7 hours ago Author Posted 7 hours ago (edited) Debug (Phoenixsuit) original software loaded (emmc) Photo from TV Box recovery menu: Thanks in advance. Edited 7 hours ago by Sergioclr remove question 0 Quote
Nick A Posted 7 hours ago Posted 7 hours ago @Sergioclr Those unpopulated pads in the top-left corner are likely the UART (Serial) debug port. Check the underside of the board—are the pads labeled GND, TX, and RX there? The most reliable way to boot Linux on this box is to use a USB-to-UART TTL adapter. Without one, we’re essentially working blind. 0 Quote
Sergioclr Posted 4 hours ago Author Posted 4 hours ago Yes, the pads are marked GND, TX and RX (underside)! I have an old USB-to-serial (DB9) cable adapter (PL2303HXA), will it work or I have to buy one like this? 0 Quote
Sergioclr Posted 3 hours ago Author Posted 3 hours ago Question regarding to a post of yours: "Your root_key.pem needs to be in the u-boot root directory" As per instructions, I created the secure-boot.patch in ~/build/patch/u-boot/u-boot-aw but there is no root_key.pem in the u-boot root directory. 0 Quote
Nick A Posted 1 hour ago Posted 1 hour ago (edited) @Sergioclr Search the forums for "PL2303HXA". I think it will work. After you compile your build, check build/cache/sources/u-boot-worktree/u-boot*; you should find root_key.pem there Edited 23 minutes ago by Nick A 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.