MattWestB

Bullseye 22.04 My image

H96 MAX V12 RK3318 4gb EMMC 64gb Tested ☑️
 
Armbian-unofficial_24.5.0-trunk_Rk3318-box_bullseye_current_6.6.23_minimal (SERVER)
 

That's right.
I use multitool only to erase internal flash and then use rkdeveloptool to flash loader and image as it is described in first page.
The device boots from sdcard in both cases, blank or flashed emmc but if there is a proper partition on internal flash Armbian works right, otherwise turns off(I heve tried to erase emmc and create partition with fdisk tool in Armbian, and OS works properly ). Armbian boots from internal flash too.
I think booting issue and turning off after minute are two different cases. Turning off probably is some kind of interaction between RAM and EMMC into EMCP chip itself(kingston 08emcp08-el3cv100).
This is dumped android firmware:
https://drive.google.com/file/d/1ZLl-KCvGS47SAO8tY1YDvCHDv6YWIWRP/view?usp=sharing

thats look like a power or thermal problem maybe , did you managed to try (sdcard or usb) with cpu-stability to overlays= line in /boot/armbianEnv.txt
or verbosity=7 and look in the Serial log maybe still always same step where it break
 
hope you have a serial adapter at the box

Hi All
 
 
 
Thanks for the help.
 
I am now searching for the clock, but mine scope is max 100 Mhz so maybe it do not see or just noise.
The pins you mention 6 and 7 just has voltage on it, no clock signal.
 
The idea of the use of the empty nand place I did also has idea of, because these boards are made for mucho 
chips so yes it can be there. Mine board has a eMc/ram indeed. I can reball a new one if fake or a bad one.
 
On the back of the board is no pads, there some below the rt3229 cpu.
 
Are there more pins to short on emmc on free space on board, can I go with other menas to get into the system,
ssh or so.
 
 
 
 

Can you making one hi rec photo of both sides of the PCB its likely have pads for MASKROM but you can using the pads for MMC / NAND but need looking for the pining of then for getting the right one.
Also if being in MASKROM it shall booting DC-card with bootloader on it.
Then having (updated not factory Android) bootloader on the EMMC it shall also booting USB-flach sticks without problem.

@pakos96 attached to this message there is a script that does the trick to change the ddrbin frequency.
Can be used on the boot block device directly on the board, or on a file to modify a ddrbin binary or an armbian image before sdcard burn.
 
Usage and examples are in-built with the script, so launching it without arguments provides all the help that could be needed.
 
Some notes:
THIS IS AN EXPERT THING. If you're not an expert, do not do this; do not come here later sobbing you made a mistake, or you will receive more insults that will make you cry even more 🫣 always always always test the ddrbin frequency change on a system booting from sdcard if there is a bootloader installed in eMMC, it has priority: changing the ddrbin on sdcard won't have any effect until you clean the eMMC (or the bootloader) some boards (notably X88 Pro) do not like ddr frequencies above 330MHz: they won't boot changing the ddrbin frequency of the bootloader in the eMMC is very dangerous! You may brick the board (only way out: maskrom via eMMC clock pin gating)  
ddrbin-switch-freq.sh

@suser try to set another "display type" values in openvfd config: https://github.com/arthur-liberman/vfd-configurations

@Bert Kortenbach, In many attempts that I had on my box, I even thought that the memory chip had burned out! It's memory lock , I had to clean it using rkdeveloptool, the only way that worked was to first make the system run properly on the SDCARD and then use the armbian-install command, after that, the system is running on the box without problems, I make the backup with multitools, and the restoration works fine too, this image generated by this process also works normally on my older box! After a lot of work, trial and error, a lot of help from people here, everything is working fine in my boxes!

If i have understanding it right if erasing the eMMC and installing the loader in  it the its possible jump stating eternal media also USB as secondary uboot is on the media. Then the system is using the first boot bin from the eMMC and the uboot from the media.
Your try is working OK until the trust OS is starting and its getting some problems (legacy kernel need one old type and current need one newer one for working OK).
I think fabiobassa is the one that having more deep knowledge of this functions but its very deep in the RK boot code.

@NiTr0 armbian has uart Speed at 115200
Original ddrbin at 1500000
I think you already switched to 115200
Other than this It hangs After trust loadingvthatbis quite strange 
 
Let see also  @jock opinion

yes I switched speed to 115200.
 
it seems like rockchip miniloader starts from eMMC and then boots from microSD.
 
I wrote first 128KB of eMMC content to SD card with multiboot image (except 1st sector with partition table) - and it boots OK with empty eMMC.

It seems like trouble was with ddr init code, I replaced it in multiboot image (2-87 sectors) - and it's booted OK.

while you can do a supervised install of Home Assistant on this box, I recommend getting a 2GB RAM variants specially if your going to run esphome to compile the firmware, 1GB RAM will literally crash the box during firmware compilation, all of that because of the very limited 1GB RAM. Else, if you can run HA without esphome, it works fine. Make sure to use a high endurance SD card as your storage for all the database logs, configurations. etc... just spare the eMMC for system use. Heck there are times that its actually much better to run armbian on SD card with home assistant because eMMC on these cheap boxes are really slow, specially the eMCP variants.

@ego worker thanks for checking in. Perhaps the bootloader installed in the internal flash memory is too old. I see that u-boot is v2021.04, but current one is v2022.04.
Your version is not applying the device tree overlays at all, hence the instability and the missing HDMI when trying to run armbian.
 
You may try to transfer the updated bootloader from the sdcard to the internal flash with:
 
sudo dd if=/dev/mmcblk0 of=/dev/mmcblk2 bs=32k skip=1 seek=1 count=32  
but also double check that you have overlays=led-conf7 in /boot/armbianEnv.txt (check also on both the internal flash and sdcard; u-boot should take the one from the boot device, but bugs in u-boot are around the corner...)
 

@jock armbian you provided. Halts. no hdmi
MXQ PRO 4K5G, R29.txt
 
+ multitoll, works fine, with HDMI
multitoll.txt
 
+with led7 conf, also rip, no hdmi
armbianwithLed7fix.txt
 
my board
https://github.com/kenavru/rk3228_TVBox/blob/main/IMG_20230804_180414.jpg

That's the main problem for the general solution you propose. Looking into the base device tree of the kernel (rk322x.dtsi), that gpio pin (gpio 2, pin RK_PB3) is declared in use only by gigabit ethernet devices. Also looking in the original device trees of the boards there is no other trace than gigabit ethernet pin. Surely no tv box with rk322x has been produced with gigabit ethernet, so from that point of view it could be safe to enable it.
 
But looking at the base dtsi is not enough to declare that any board does not use that pin: as it happens on r29/r2b/h20, any other manufacturer may have decided that the pin may control something more or less important, or perhaps it is internally wired to something, tinkering with that may affect other boards. It is a remote possibility, though it can happen.
 
Multitool (and libreelec too) has the pin enabled by default, so we will see if it can have side effects on other boards.

In https://github.com/armbian/build/pull/5762/files its LED 7 and 8 heaving the GPIO2 for enabling HDMI. 
Now one question is the GPIO2 used for both normally not used by other board ?
If yes i think its good putting it in rk322x-led-conf-default.dts then the user is getting HDMI working from beginning and dont need struggling setting it up with SSH or terminal. This is only if its OK for all other board but i think its great if its possible.
 
And one more thanks for great work done !!!

I already opened a pull request on armbian, when it will be accepted, new kernel will be built with fixes, but I have no control on when the new kernels will be built by the armbian servers.

As normal not by the book:
Renamed the DTB directory and putting the from the 7zip:ed deb file in one new with the same name as the original and then checking privs and sync reboot and the LEDs is being blue/read and HDMI is working OK with bootlogging and TTY CLI  !!!

 
  ┌──────────────────────────────────────────────────────────────────────┐     │               • MobaXterm Professional Edition v22.0 •               │     │               (SSH client, X server and network tools)               │     │                                                                      │     │ ➤ SSH session to root@192.168.2.65                                   │     │   • Direct SSH      :  ✔                                             │     │   • SSH compression :  ✔                                             │     │   • SSH-browser     :  ✔                                             │     │   • X11-forwarding  :  ✘  (disabled or not supported by server)      │     │                                                                      │     │ ➤ For more info, ctrl+click on help or visit our website.            │     └──────────────────────────────────────────────────────────────────────┘       _    _________  ____            _  _ __| | _|___ /___ \|___ \__  __    | |__   _____  __ | '__| |/ / |_ \ __) | __) \ \/ /____| '_ \ / _ \ \/ / | |  |   < ___) / __/ / __/ >  <_____| |_) | (_) >  < |_|  |_|\_\____/_____|_____/_/\_\    |_.__/ \___/_/\_\ Welcome to Armbian 23.8.1 Jammy with Linux 6.1.50-current-rk322x No end-user support: community creations System load:   77%              Up time:       0 min Memory usage:  15% of 975M      IP:            172.17.0.1 192.168.2.65 172.30.32.1 CPU temp:      78°C             Usage of /:    41% of 7.1G RX today:      209.0 MiB [ General system configuration (beta): armbian-config ]  
I have no desktop installed then its no need for supervised HA with RCP.
 
Shall testing little more but all looks OK and my EVE Thread plugs is reporting all parameters over Thread and RCP integration so looks very good.
DMESG is attached but no journal then its have all HA logs also the Zigbee and Thread credentials and i think you dont need them and if i PM you with them. RK3228B.zip
 
Great work done !!!

Tryed the 6.1.55 install by the book and looks also working like 6.1.50 hand patched.
Attaching install and dmesg logs. RK3228B55.zip
 
Shall being good if some more user with desktop installed can testing it so Joke can getting it better verified that is working and putting it in the current release if all is OK.
 
PS: The kernel install is still complaining of missing firmware that it have doing longer time now but my RK3318 box is not doing it on all kernels i have running on it.

@jock, @fabiobassa and @MattWestB, Update!  I did update armbian in sdcard, install lxde, did @jock institutions, and did image file and install with multitool in internal memory and work, boot and hdmi ! Now, it have debian 12 in internal and debian 10 legacy in mine personalized card, all work! 
@jock and @fabiobassa, because it to be a emcp, i can't user the Buster older, in internal memory, kernel limitation? I use a program that only  install in debian 10 or ubuntu 16, Can I install new kernel in debian buster?
Thank you!
 
log-dmesg-lxde-MXQ-R2B.txt

@MattWestB I've uploaded convenient deb packages with update dtbs for both kernel 6.1 and 6.5; now they should be finally fixed and work, at least I tested on my board and they work pretty fine.
 
You can download the deb package from here - for your installed system with kernel 6.1 you may want to download and install linux-dtb-current package
Please do a backup as you already did of the /boot/dtb directory on your existing installation!
 

Here is another dmesg txt from my r29 board.
R29dmesg.txt

Ok, I need to better check what is going on with kernel 6.1 then; perhaps it is a misalignment with the base dtb, but I will try to be more specific tomorrow. Thanks in the meantime!

@joke, Ok, I followed your instructions, and hdmi worked after setting the led to 7, there is dmesg! The @MattWestB box, erased internal memory,  it do boot from card or usb, but mine, only multiboot sdcard work! To boot Armbian SDcard, I write multiboot image in the internal memory, without card, multiboot initialise, with sdcard, it boot normalite! If i to write other image, new or older or legacy, in internal memory, it breaks box, only maskmod and rkdeveloptool to recovery! 
log-dmesg-MXQ-R2B.txt