Jump to content

Efforts to develop firmware for H96 MAX V56 RK3566 8G/64G

Hqnicolas

By Hqnicolas
in Rockchip CPU Boxes

 Share

Recommended Posts

Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
6 hours ago, rossbcan said:

 

I soldered in SD Card holder. Are you sure about "Detect SD-CARD" success you reported? I don't see it.

 

Tested on 4gb / 32gb 

Old board version

The factory can change layout without warning nobody. This is the bad side of TV boxes, and this is why Linux on this type of devices isn't supported by community

Edited by hotnikq
0
Link to comment
Share on other sites
rossbcan

rossbcan

Posted
Posted

@hotnikq

 

Can you please share your SD card detection messages. First establish where it is? mmcX?

 

EG: "dmesg | grep mmcX" and "cat /var/log/syslog | grep mmcX"

 

I believe my SD reader is at mmc0 (mmc@fe2b0000) and here's dmesg (syslog same) out: 

mmc_host mmc0: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
mmc_host mmc0: Bus speed (slot 0) = 375000Hz (slot req 375000Hz, actual 375000HZ div = 0)

controller detected, card not.

 

Thanks; Bill

0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted

@rossbcan


  

 dmesg | grep mmcblk0
Quote

[6006502.273177] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[6006502.288263]  mmcblk0: p1
[6006503.930879] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[6006503.945245]  mmcblk0: p1
[6006506.054509] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[6006506.071547]  mmcblk0: p1
[6006506.095914] I/O error, dev mmcblk0, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2
[6006506.424909] mmcblk0: mmc0:e624 SU08G 7.40 GiB
[6006506.432706]  mmcblk0: p1
 



  

cat /var/log/syslog | grep mmcblk0
Quote

Oct 28 13:36:01 station-m2 kernel: [6006502.273177] mmcblk0: mmc0:e624 SU08G 7.40 GiB
Oct 28 13:36:01 station-m2 kernel: [6006502.288263]  mmcblk0: p1
Oct 28 13:36:01 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:01 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:01 station-m2 devmon[681]: device: [/dev/mmcblk0p1]
Oct 28 13:36:01 station-m2 devmon[681]: devmon: /usr/bin/udevil --mount /dev/mmcblk0p1 --mount-options "nosuid,nodev,noatime"    # (armbi_root)
Oct 28 13:36:02 station-m2 devmon[681]: udevil: /dev/mmcblk0p1 is known to mount - running mount as current user
Oct 28 13:36:02 station-m2 devmon[681]: devmon: error mounting /dev/mmcblk0p1 (32)
Oct 28 13:36:02 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:02 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:03 station-m2 kernel: [6006503.930879] mmcblk0: mmc0:e624 SU08G 7.40 GiB
Oct 28 13:36:03 station-m2 kernel: [6006503.945245]  mmcblk0: p1
Oct 28 13:36:03 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:03 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:03 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:03 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:05 station-m2 kernel: [6006506.054509] mmcblk0: mmc0:e624 SU08G 7.40 GiB
Oct 28 13:36:05 station-m2 kernel: [6006506.071547]  mmcblk0: p1
Oct 28 13:36:05 station-m2 kernel: [6006506.095914] I/O error, dev mmcblk0, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 2
Oct 28 13:36:05 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:05 station-m2 casaos-local-storage[1886]: /usr/sbin/smartctl -a -n standby /dev/mmcblk0 -j
Oct 28 13:36:05 station-m2 casaos-local-storage[1886]:       "/dev/mmcblk0",
Oct 28 13:36:05 station-m2 casaos-local-storage[1886]:         "string": "/dev/mmcblk0: Unable to detect device type",
Oct 28 13:36:05 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:05 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:05 station-m2 devmon[681]: removed:   /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:05 station-m2 kernel: [6006506.424909] mmcblk0: mmc0:e624 SU08G 7.40 GiB
Oct 28 13:36:05 station-m2 kernel: [6006506.432706]  mmcblk0: p1
Oct 28 13:36:05 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0
Oct 28 13:36:05 station-m2 devmon[681]: added:     /org/freedesktop/UDisks/devices/mmcblk0p1
Oct 28 13:36:05 station-m2 devmon[681]: device: [/dev/mmcblk0p1]
Oct 28 13:36:05 station-m2 devmon[681]: devmon: /usr/bin/udevil --mount /dev/mmcblk0p1 --mount-options "nosuid,nodev,noatime"    # (armbi_root)
Oct 28 13:36:06 station-m2 devmon[681]: udevil: /dev/mmcblk0p1 is known to mount - running mount as current user
Oct 28 13:36:06 station-m2 devmon[681]: devmon: error mounting /dev/mmcblk0p1 (32)
 

 

  

armbianmonitor -u

 

Result before SDcard insert:

https://paste.armbian.com/qixunuqehi

 

Quote

LINE: 206
 

Device             tps    kB_read/s    kB_wrtn/s    kB_dscd/s    kB_read    kB_wrtn    kB_dscd
mmcblk1           1,17         1,25         9,76         6,32    7503519   58613937   37952260
mmcblk1p1         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p2         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p3         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p4         1,17         1,25         9,76         6,32    7501079   58613937   37952260
mmcblk1boot0      0,00         0,00         0,00         0,00        120          0          0
mmcblk1boot1      0,00         0,00         0,00         0,00        120          0          0
zram0             0,26         0,40         0,65         0,00    2431644    3888720          0
zram1             0,25         0,01         1,25         0,00      80668    7522996          0
zram2             0,00         0,00         0,00         0,00          0          0          0

 

 

After Connect by insert SDcard:

https://paste.armbian.com/rucaleyigi

Quote

Line 206:

Device             tps    kB_read/s    kB_wrtn/s    kB_dscd/s    kB_read    kB_wrtn    kB_dscd
mmcblk1           1,17         1,27         9,76         6,32    7643011   58614277   37952260
mmcblk1p1         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p2         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p3         0,00         0,00         0,00         0,00        216          0          0
mmcblk1p4         1,17         1,27         9,76         6,32    7640571   58614277   37952260
mmcblk1boot0      0,00         0,00         0,00         0,00        120          0          0
mmcblk1boot1      0,00         0,00         0,00         0,00        120          0          0
zram0             0,26         0,41         0,65         0,00    2432728    3888720          0
zram1             0,25         0,01         1,25         0,00      80668    7523260          0
zram2             0,00         0,00         0,00         0,00          0          0          0
mmcblk0           0,00         0,00         0,00         0,00       5490          0          0
mmcblk0p1         0,00         0,00         0,00         0,00       3290          0          0

 

 

0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
7 hours ago, Sunil sankar said:

testing it now


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

 

p3.jpg.dba7daeda4b722ac3a3358b0cf6807cd.jpg

p2.jpg.065e7cf8fc89d10a99b177b4c9ec1c2c.jpg

p4.jpg.79ac59e92e1bad992d926d0c9319dc65.jpg

 

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
On 10/28/2023 at 6:30 AM, Sunil sankar said:

@hzdm the armbian server image doesn't work it doesn't boot .



@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

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted
23 minutes ago, Sunil sankar said:

how I can compile one with debian

 

On 6/15/2023 at 11:18 PM, hotnikq said:

if you wanna do all that creepy again with other devices and images, (please do it on other devices) and topic


this is all you need to create this image,
first step:
Compile armbian on linux desktop

dont forgot to do it with modified DTS file: 


Select "CUSTOM KERNEL OPTION"

When the wizard stop and ask for kernel modification:

Drop DTS + DTB files on /build/cache/sources/linux-kernel-worktree/6.2__media__arm64/arch/arm64/boot/dts/rockchip

and exit Kernel modification wizard from armbian compiler

 

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


 

0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
28 minutes ago, Sunil sankar said:

Can you pls suggest how I can compile one with debian


Take your debian SD card image and:

 

On 6/15/2023 at 11:18 PM, hotnikq said:


 

any resemblance to this topic is mere adaptation

 

Mount that image virtual device like /media/armbian_boot 

fdisk -l your-armbian-image-for-sd-card.img
mount -o loop your-armbian-image-for-sd-card.img /media/armbian_boot

if you can't "like WSL2"

sudo apt-get install kpartx
sudo kpartx -av your-armbian-image-for-sd-card.img
sudo mount -o loop /dev/mapper/loop0p1 /media/armbian_boot


Second Step:  prepare an sd card or usb flash dummy , can be anithing with 6gb 

fdisk /dev/mmcblk1
N
default
default (lower this value to match the size of your root image)
T
1
W


third step: format that flash drive for ext4 

mkfs.ext4 /dev/mmcblk1p1

 

fourth step: mount that clear partition and copy the entire virtual drive to the flash device 

mount /dev/mmcblk1p1 /mnt/

rsync -avx /media/armbian_boot/ /mnt/

 

fifth Step: Edit your uuid From Armbian Boot config "uuid for /dev/mmcblk1p1" 

blkid

nano -w /mnt/boot/extlinux/extlinux.conf

sync
umount /mnt


sixth step: make an hardware RAW.img from hardware flash drive with these parameters 

sudo dd if=/dev/mmcblk1p1 of=~/root.img bs=4096 status=progress

PS: can be /dev/SDA" I do it on my h96max" so it's mmcblk1

 

 

now you have an ROOT v0.7 IMAGE MADE BY YOURSELF!

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
On 11/2/2023 at 4:27 PM, Sunil sankar said:

how I can compile one with debian


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

 

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
On 10/7/2023 at 7:27 AM, hzdm said:

rkdeveloptool wl 0x0 start.img


@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

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)

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

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)

 

16 hours ago, MeJune said:

Is it possible to display a digital clock on the box? (like android mode)

 

On 10/8/2023 at 11:38 AM, hotnikq said:

if you want this extra features, it can be solved by editing the DTB file
mipi DSi, display 7seg and infrared controller, all can be translated from android DTB to Linux DTB.
in my case it can be found on /boot/dtb/rockchip/rk3566-firefly-roc-pc.dtb
and the setup are made by the /boot/extlinux/extlinux.conf
an example how to manipulate this files 

 

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!

 

 

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
8 hours ago, blust0ne said:

Please tell me the process of making bootfs.img  in more detail. 

@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,
 

On 10/24/2023 at 9:28 AM, hotnikq said:

based on @hzdm method i will make this image using Distro Boot with Boot.scr

 

https://wiki.trenz-electronic.de/display/PD/Distro+Boot+with+Boot.scr

 

mount the H96MAX update.img


Files that will help
 

1. MiniLoaderAll.bin and U-boot are taken from Armbian image from Orange Pi 3B board.
2. The /boot directory was moved to a separate bootfs partition.
3. Rename  file /boot/extlinux/extlinux.conf in extlinux.conf.bak
4. In /boot directory boot.cmd and boot.scr files were created with the following contents

  

sudo apt-get update
sudo apt install u-boot-tools

 

  

setenv docker_optimizations "on"
setenv bootlogo "false"

echo "Boot script loaded from ${devtype} ${devnum}"

if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1"; fi
if test "${bootlogo}" = "true"; then
        setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}"
else
        setenv consoleargs "splash=verbose ${consoleargs}"
fi


part uuid mmc 1:2 partuuid
setenv bootargs   androidboot.console=ttyFIQ0 root=PARTUUID=${partuuid} rootwait  rw rootfstype=ext4 ${consoleargs}   no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash p>
load mmc 1:1 0x42000000 Image
load mmc 1:1 0x44000000 dtb/rockchip/rk3566-firefly-roc-pc.dtb
load mmc 1:1 0x46000000 uInitrd
booti 0x42000000 0x46000000 0x44000000


# Recompile with:
# mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

  

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

 

Edited by hotnikq
0
Link to comment
Share on other sites
Hqnicolas

Hqnicolas

Posted
  • Author
Posted (edited)
On 10/28/2023 at 1:46 PM, hotnikq said:

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

 

@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.

Edited by hotnikq
0
Link to comment
Share on other sites
hzdm

hzdm

Posted
Posted (edited)

Hey, everybody!


I haven't replied in a while because I've been moving from one house to another.

Now I have some free time and I have prepared an automatic Armbian build. You won't have to do any more extra steps with the image. You need to copy the files to the build directory with the git armbian repo ( Build Armbian )

 

1. Copy the h96-max-v56 directory to build/packages/blobs/  directory
2. Copy the h96-max-v56.conf file to the build/config/boards/ directory
3. Run the image build 

From server 

./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy 

From  Desktop
cinnamon 

./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools email multimedia internet office' DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base


xfce 

./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools email multimedia internet office' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=jammy

https://drive.google.com/file/d/1oYK4EhbfcThfBs3F1Ri582jf6PYYp5x2/view?usp=drive_link

 

How to install this Armbian:

 

On Windows OS:

1. Download, unzip and install the software: RKDevTool_Release_v3.15_and_DriverAssitant_v5.12
https://drive.google.com/file/d/14HWcHYHDrgUBFWholrDCKUWDPHw1r4F1/view?usp=drive_link

2. Run RKDevTool. Right-click in the partition list window (1). Select "Load Config". Open armbian.cfg file (2)

image.png.87f9f22c9182e5610b251d43fc41333a.png
https://drive.google.com/file/d/1MhmUJ8DaikZzwjBliY-PrOrvSrcBPwSA/view?usp=drive_link

4. Shutting down H96 MAX. Press the Reset button. Turn on the H96 MAX. The message "Found One MASKROM Device" or "Found One LOADER Device" should appear. (1) 
Mark all 2 sections with check marks (2)
Open 2 files for each section (3)
Check "Write by Address" (4).
Press the "Run" button (5). The download will start.
When the message "Download image OK" appears, the download is finished (6). 
H96 MAX will automatically reboot. 

Done.

image.thumb.png.401b3c29a19285509e564c45bd319333.png

 

On Linux OS

 

rkdeveloptool db MiniLoaderAll.bin   # If this is not your first time flashing with this firmware, an error may appear here\. It\'s not a big deal
rkdeveloptool wl 0x0 Armbian_23.11.0-trunk_H96-max-v56_jammy_current_6.1.62.img

rkdeveloptool rd

 

PS: This image is functionally the same as the previous ones. It is still the same Station M2 image, only it already has all the past improvements built in and is easier to install!

Edited by hzdm
0
Link to comment
Share on other sites
hzdm

hzdm

Posted
Posted (edited)

I have collected several images using this methodology. On my 8Gb RAM - 60Gb console everything started.
Check if you have other consoles. Maybe these images will work for all H96-max-v56 modifications.

 

Server Standard -  Armbian_23.11.0-trunk_H96-max-v56_jammy_current_6.1.62.zip  

https://drive.google.com/file/d/19jFhGDuej2k7XkAqkh7Cuz3AhWRG8C0D/view?usp=drive_link

(./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy)

 

Server Minimal - Armbian_23.11.0-trunk_H96-max-v56_jammy_current_6.1.62_minimal.zip

https://drive.google.com/file/d/1c0UajTtfiZ1dAcT2f4tHdxZf6sYd2r9m/view?usp=drive_link

(./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=jammy)

 

Desktop Cinnamon -  Armbian_23.11.0-trunk_H96-max-v56_jammy_current_6.1.62_cinnamon_desktop.zip

https://drive.google.com/file/d/1CFdI3YhHNPCXUbyXPXTdlaPZMAsrg9lv/view?usp=drive_link

(./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no KERNEL_CONFIGURE=no RELEASE=jammy DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools email multimedia internet office' DESKTOP_ENVIRONMENT=cinnamon DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base)

 

Desktop XFCE -  Armbian_23.11.0-trunk_H96-max-v56_jammy_current_6.1.62_xfce_desktop.zip

https://drive.google.com/file/d/1yfnWlUcot578PJ2fU8khfj7TBC1kU6GU/view?usp=drive_link

(./compile.sh build BOARD=h96-max-v56 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='3dsupport browsers desktop_tools email multimedia internet office' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=jammy)

 

This image is functionally the same as the previous ones. It is still the same Station M2 image, only it already has all the past improvements built in and is easier to install!

Edited by hzdm
0
Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept