Hqnicolas

✔️ Temperature display works on docker management https://casaos.io/ VFD display isn't needed, It's a GPIO function from android with an custom app runing the GPIO. 😰include this board on armbian standart is BIG Work. @hzdm You will need to compare our DTS file with the StationM2 file, and create a H96MAXv56.DTS easy to describe, hard to work around. It's enough work for a team because you will need to take into account the files included in DTSi and DTS are fitted in a cascade, you will need to understand the kernel 6.2 DTS and 6.4 DTS modifications

@Sunil sankar @Kenneth Hidalgo @wootje @beiqidai @maka @SteeMan @paradigman The 8gb device arrived! Since my images was build on 4gb device. it doesnt works more than a single boot on 8gb device. 😅 on installation, armbian expands the EFI disk to a Linux disk. So, today i have generated a fix to v1.0 images work on 8gb devices. First Boot Comand: fdisk /dev/mmcblk1 t 4 1 w What you will see on screen if you do the First Boot Comand: fdisk Welcome to fdisk (util-linux 2.37.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. This disk is currently in use - repartitioning is probably a bad idea. It's recommended to umount all file systems, and swapoff all swap partitions on this disk. Command (m for help): t Partition number (1-4, default 4): 4 Partition type or alias (type L to list all): 1 Changed type of partition 'Linux filesystem' to 'EFI System'. Command (m for help): w The partition table has been altered. Syncing disks. Now if you reboot the 8gb device, it will find the linux partition without problem.

@blust0ne don't use my images for safety reasons, Please to sensitive content, compile your own SD-card image from the armbian repo. if you have any doubts about the image creation process please ask. Like I said, create 2 partitions on your drive, fdisk /dev/mmcblk1 N default default (lower this value to match the size of your root image) T 1 W drop the content of your Armbian v0.5 SD card on it, (same as v0.7 tutorial) in the first partition, drop the boot folder content to the root of the drive. Drop on rootfs.img just the files from root of SD image (files without folder), Drop the 2 files that you create and compile it from @hzdm tutorial. And create a image with DD like the v0.7 tutorial. That's your rootfs.img sudo dd if=/dev/mmcblk1p1 of=~/root.img bs=4096 status=progress

Thank you for the feedback. This is board difference, factory change components without documentation. The new images work here, but the @hzdm don't

Feel free to share to the community your experiences with 7seg GPIO on H96 MAX. it can be used to other things like digital output to automation!

Next Step to the H96 MAX v56: Using Rockchip SoCs NPU. Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ

Next Step to the H96 MAX v56: @thc013 what did you think about using Rockchip SoCs NPU? Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ

The Reality is: polity block it today, pirates path it tomorrow, life goes on. Pirate guis looks like Hydra Heads. the fact that there are so many android devices being sold to watch Streaming Bullshit. if this devices were used correctly it could be more useful like web browsing or learning W3s. I did my homework Edit: Seized devices were sent to public schools in the interior of the Brazilian desert Edit: It seems that millions of devices have already been made

this question is worth more than all software solutions!

Just remember that my device is 4gb 32gb I don't test 8gb 64gb images until my device arrive from China The v0.8 version was build from 64gb @hzdm and v0.9 ported it to 32gb and 64gb

I don't have time to test the dtb from server on desktop after flash. If it works, please let me know. That was happens here because the USB2.0 use the same ports from display. If display don't start from kennel, the USB2.0 hangs the system. To know the files position, Take the hzdm bootfs and mount it to see what's inside. Don't use his files, just the position.

And in this meantime I spend 8 months on a toxic job. 35 days after I left, here we are, rebuilding Armbian.

@hzdm The result from your post ThankYou! Keep Pushing on Arm Devices!

####################### EMMC: V1.0 Release Version ####################### # Tested on 8gb device (16/11/2023) # Tested on 4gb device (03/11/2023) # Flash RkdevTool v2.86 Doesn't Work on Windows 11 Computers! How to build this images? V0.7 Root + Build Update What is that? Yes, it's a v0.7 update image, that you flash a little gpt file to repair partition on EMMC. So, you will use the same v0.7 Update images that you have. The Gpt file First Things First! Drop Config.cfg the RkDevTool config file on folder Righ click on white background from RKDevTool click on Load Config Select the Config.cfg Flash Update.img Restart device on loader mode Flash gpt.img The Gpt file Yes, you can Skip Root flash. But you can drop the v0.7 Root.img file on this device. Please Reflash GPT.img after new Root.img 🏆 help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. Since It will be the image that i use on my server, This is my Last Collaboration in this project, if you done something better, post it here. ################################ 8GB devices Fix ############################## 8GB device First Boot Comand: # this GPT file was generated from a 4gb device. # in 8gb device you will need to trick the gpt after instalation # First boot comand: fdisk /dev/mmcblk1 t 4 1 w On 8gb device Screen you will see: fdisk Welcome to fdisk (util-linux 2.37.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. This disk is currently in use - repartitioning is probably a bad idea. It's recommended to umount all file systems, and swapoff all swap partitions on this disk. Command (m for help): t Partition number (1-4, default 4): 4 Partition type or alias (type L to list all): 1 Changed type of partition 'Linux filesystem' to 'EFI System'. Command (m for help): w The partition table has been altered. Syncing disks. Now if you reboot the 8gb device, it will find the linux partition without no problem. gpt.img config.cfg

It's time for a new joint venture. using the @hzdm method, i create the single burn firmware. How to build this images? ######################## EMMC Server: v0.9 image Beta ######################## insert the gpt file to use the same image to burn different devices. First Things first: Read the RkDevTool config! For 8gb/64gb devices: Uncheck disable the GPT image file to flash. For 4gb/32gb devices: Check enable the GPT image file to flash. Lets flash! how? Follow the HZDM tutorial. 🏆 help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions.

Working in a solution for GPT over EMMC. Since this solution makes 8gb images work on 4gb devices I will try: https://opensource.rock-chips.com/wiki_Partitions this is the 4gb 32gb image GPT: Command (? for help): i Partition number (1-4): 1 Partition GUID code: DE110000-0000-4051-8000-460A00003284 (Unknown) Partition unique GUID: F51C0000-0000-455E-8000-20DF000015D9 First sector: 16384 (at 8.0 MiB) Last sector: 24575 (at 12.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'security' Command (? for help): i Partition number (1-4): 2 Partition GUID code: 57090000-0000-4C1B-8000-2CC300006C3E (Unknown) Partition unique GUID: DC7B0000-0000-400E-8000-1A30000064FB First sector: 24576 (at 12.0 MiB) Last sector: 32767 (at 16.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'uboot' Command (? for help): i Partition number (1-4): 3 Partition GUID code: 9E010000-0000-491F-8000-2EDD00003399 (Unknown) Partition unique GUID: F6680000-0000-4F67-8000-11C500006AE2 First sector: 32768 (at 16.0 MiB) Last sector: 40959 (at 20.0 MiB) Partition size: 8192 sectors (4.0 MiB) Attribute flags: 0000000000000000 Partition name: 'trust' Command (? for help): i Partition number (1-4): 4 Partition GUID code: 7D0B0000-0000-4D02-8000-2621000044DE (Unknown) Partition unique GUID: 5FA600DD-BFC2-4260-A3DA-562CB9D13F00 First sector: 40960 (at 20.0 MiB) Last sector: 61071326 (at 29.1 GiB) Partition size: 61030367 sectors (29.1 GiB) Attribute flags: 0000000000000000 Partition name: 'root'

@hzdm i create an Server image Based on your instructions. but my device is an 4gb 32gb device how can you change the GPT LBA from this files? there is a source of this start.img file? the initial error: Trying to boot from MMC1 GPT: last_usable_lba incorrect: X > 747bfde part_get_info_efi: *** ERROR: Invalid GPT *** part_get_info_efi: *** Using Backup GPT *** on device to repair the initial error, when "sudo gdisk /dev/mmcblk1:" it reveals the GPT partition is 57gb Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 122142686 Partitions will be aligned on 2048-sector boundaries Total free space is 61407 sectors (30.0 MiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs 2 2158592 122142686 57.2 GiB FFFF rootfs Command (? for help): i 2 Partition number (1-2): 2 Partition GUID code: 1124E418-9008-41F8-9E3D-8D872216C8A1 (Unknown) Partition unique GUID: 67AD7741-4638-47C6-A488-D396583E582A First sector: 2158592 (at 1.0 GiB) Last sector: 122142686 (at 58.2 GiB) Partition size: 119984095 sectors (57.2 GiB) Attribute flags: 0000000000000000 Partition name: 'rootfs' Command (? for help): i Partition number (1-2): 1 Partition GUID code: 8DCD1602-5214-43F9-FFEF-C49A4EE450B7 (Unknown) Partition unique GUID: 5A30833F-8C43-47B1-A41D-84D40883D0C6 First sector: 61440 (at 30.0 MiB) Last sector: 2158590 (at 1.0 GiB) Partition size: 2097151 sectors (1024.0 MiB) Attribute flags: 0000000000000000 Partition name: 'bootfs' How i fix this initial problem: boot from SD card..... and: root@station-m2:~# sudo gdisk /dev/mmcblk1 GPT fdisk (gdisk) version 1.0.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2048-sector boundaries Total free space is 58974142 sectors (28.1 GiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs Command (? for help): n Partition number (2-128, default 2): First sector (34-61071326, default = 2158592) or {+-}size{KMGTP}: Last sector (2158592-61071326, default = 61071326) or {+-}size{KMGTP}: Current type is 8300 (Linux filesystem) Hex code or GUID (L to show codes, Enter = 8300): 1124E418-9008-41F8-9E3D-8D872216C8A1 Changed type of partition to 'Unknown' Command (? for help): x Expert command (? for help): c Partition number (1-2): 2 Enter the partition's new unique GUID ('R' to randomize): 67AD7741-4638-47C6-A488-D396583E582A New GUID is 67AD7741-4638-47C6-A488-D396583E582A Expert command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y After solution: root@station-m2:~# sudo gdisk /dev/mmcblk1 GPT fdisk (gdisk) version 1.0.8 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/mmcblk1: 61071360 sectors, 29.1 GiB Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EC944974-E823-4B58-AEB7-A94651D008F8 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 61071326 Partitions will be aligned on 2048-sector boundaries Total free space is 61407 sectors (30.0 MiB) Number Start (sector) End (sector) Size Code Name 1 61440 2158590 1024.0 MiB FFFF bootfs 2 2158592 61071326 28.1 GiB FFFF Unknown I will try soon: https://opensource.rock-chips.com/wiki_Partitions it works! to flash your method over 4gb 32gb devices Just flash the gpt.img inside the start.img located on 0x00000000 GPT 4gb to use in 8gb HZDM images gpt.img

Combine a ROOT image with an UPDATE image and BOOM = v0.7 build firmware i will finish this step in a week or two.... if you have an 8gb device, use the @hzdm method UPDATE: H96 MAX V56 RK3566 4gb and 8gb Ram SD-Card images: Release Version v0.5DEBIAN12 BETA Release Version v0.5ARMBIAN23 BETA UPDATE: H96 MAX V56 RK3566 4gb and 8gb EMMC images: Release Version V0.7DEBIAN12 BETA Release Version V0.7ARMBIAN23 BETA

Take your debian SD card image and: now you have an ROOT v0.7 IMAGE MADE BY YOURSELF!

!!!!!!!NOW YOU HAVE AN SD CARD v0.5 image!!!!!

@hzdm Dear friend, Your MOD on USB2.0 doesnt boot with SERVER version of armbian!!!! for server images Please use the OLD DTB file without USB2.0 it solves the boot problem on Server images!!! @Sunil sankar i'm building updated versions from the SD-card images based on v0.5 All that you need to compile armbian: https://drive.google.com/file/d/1G5KBVq1oR-QrIKG3FoHmUTwh8OSAG018/view?usp=sharing H96MAX_DTB_DTS_WIFI_NOVEMBER_2023.zip

Don't use it, I'm trying to rebuild it [emoji28] wait a week or two...

i will test the 4gb version too Please report your 8gb device by: armbianmonitor -u due to the high demand for 8gb devices I bought a unit to test the images here too, I'm going to put in a 1tb SSD with a sata adapter and create a bitcoin lightning node 1R$ = 0,20U$ 5R$ = 1U$ 54,12U$ = 271,37R$ with taxes 51,11U$ = 256,28R$ with taxes

@rossbcan dmesg | grep mmcblk0 cat /var/log/syslog | grep mmcblk0 armbianmonitor -u Result before SDcard insert: https://paste.armbian.com/qixunuqehi After Connect by insert SDcard: https://paste.armbian.com/rucaleyigi