X88 Pro Pro X3 / X99 Max Plus / Transpeed X3 Plus - Status #1621
Comments
|
https://github.com/unifreq/linux-6.1.y/tree/main/arch/arm64/boot/dts/amlogic Thank you for your sharing. Compress the The above is the source code of the kernel's Device Tree Source (DTS). What modifications have you made to the original version in your Device Tree Binary (DTB) file? It might be better to create a new dedicated DTS file, which would make maintenance and updates easier compared to using a fixed DTB file. |
ophub
added
documentation
the ziped dts and dtb files are attached |
|
Based on the information you provided, there is no need to add a new DTB (Device Tree Blob). The original DTB file included in the kernel, You can modify the name of the DTB in |
|
unfortunatelly no boot on the meson-sm1-x96-max-plus-q2.dtb Please see the screen with log errors (sory I do not have working uart/debug connection to this board)
|
|
This is the source code of q2, he just made the same modification as the bluetooth chip. According to the post you posted above, danboid also introduced in his warehouse, you can use my q2 directly, no need to use his modified files anymore.
You download other series or different kernel firmware try the q2 |
lunar_6.1.42
lunar_5.15.123
lunar_5.10.189
lunar_5.4.252
different dtb for S905x in lunar_6.1.42I checked each dtb for s905x in Conclusions
@ophub what do think about this ? |
|
Your DTS file is not the source file; it's a decompiled file. It cannot be compiled within the kernel. It can only be adjusted at specific points through decompilation. This kind of Device Tree Blob (DTB) has been tested in the current version, but there is no guarantee it will work correctly in future kernel versions. It's advisable to identify the differences, follow the kernel's DTS writing conventions, and create a dedicated DTS file. You can refer to the writing style in I've placed |
DTS@ophub Thanks for explanation concerning DTS, I will try to learn more about DT, if I will be able I will prepare real DTS based on existing dts in kernel and orginal dts from android. Test of the attached compilationI tested the build that you attached - everything works OK (Boot, HDMI, Ethernet. WiFi, BT) Installation on eMMCBefore I tried the installation I noticed that my DTBs on device is encrypted after decryption I run the
The installation was successful: But the box is not butting from eMMC, black screen without even start logo(this time), Do you have any idea how to improve the installation script based on information from the link -> partition Information from ampart-web-reporter let me know please then I will do an installation test. |
|
armbian-install -m yes |
no boot, logs from installation below: what else can we try? |
|
I just tried to flash it back using Amlogic USB Burning Tool, I tried 4 times, the same error in the same address
|
|
Hi @ophub I'm back :) I flashed the box via Amlogic USB Bourning tool, with unchecked erase checkboxes and it was successful, then I flashed again with checked erase checkboxes it was successful too. Now I'm on 5.15.127-ophub, as you can see memory is wrong the DTB is again encrypted What we are doing now - standard installation? Or I should I firs make DTB non-encrypted to use ampart? |
|
In the absence of mainline u-boot support, armbian can only recognize more than 3G, not the perfect 3.7G, which is normal. If you want to recognize 3.7 G, you can see how to compile amlogic u-boot in the document It seems that the current bootloader of the Android system can only boot from the usb, but cannot boot from the emmc. Before solving u-boot and dtb, use it in usb first. |
|
Another potential reason for the failure to boot from eMMC is writing to an insecure partition location. Firstly, restore your device to the Android system. Then, following the partition identification method outlined in the repository, verify the location and modify the armbian-install script to include the dedicated partition. https://github.com/ophub/amlogic-s9xxx-armbian/tree/main/documents Refer to section 12.10 of the documentation. |
|
Hi @ophub thanks for the tip according to this report -> ampart-web-reporter I tried wit these settings
I assumed that 1.09375GB is 1120MB
Unfortunately there is no boot, only logo appears... I will test this more |
|
Hi @ophub I made it :) my "hello world" dts:
Ethernet -> OKLED Screen Display -> OKI will test this dts more then I will put it to the https://github.com/unifreq/linux-6.1.y/tree/main/arch/arm64/boot/dts/amlogic |
|
ok, thanks |
|
Hi @ophub I created u-boot for box x88-pro-x3 - I did all according to the instruction -> How to build the u-boot file Now I have files in the u-boot root directory and in the fip directory. |
|
OK I made it :) I did:
it works! @ophub let me know what files should I send you to add it to the repo? |
|
Thank you for sharing. Please send me the file: Alternatively, you can submit it here: https://github.com/ophub/u-boot/tree/main/u-boot/amlogic/bootloader Modification: Rename |
u-boot for X88 Pro Pro X3 / X99 Max Plus / Transpeed X3 Plus tested on X88 Pro Pro X3, details: ophub/amlogic-s9xxx-armbian#1621
add x88prox3-u-boot.bin.sd.bin details: ophub#1621
|
Thanks @ophub ! 2 pull requests added: I will test the build after these pull requests merge |
|
Translation: The production process for both systems is also basically the same. |
|
Hi @ophub I checked the builds and it works but only on X88 Pro Pro X3 box with 100MB Ethernet To be 100% sure I created u-boot again taking the Is there any way to make it works, do you have any advice how I can start the Armbian from eMMC? Thanks in advance for your comments! |
|
When booting from an SD card, it uses the bootloader from the eMMC. However, when you write to the eMMC, using the "-m yes" parameter overwrites the Android bootloader with the mainline u-boot. Therefore, when booting from the eMMC again, it requires the correct mainline u-boot. Can your box with the Gigabit Ethernet card boot using the unmodified original u-boot? If it can, you can modify the configuration to have two lines, one for the 100MB and one for the Gigabit Ethernet, making it easier to differentiate. Please provide photos of the appearance and bottom model codes of your two boxes to help distinguish them. If you have photos of the motherboard, including the short-circuit rescue point, please provide those as well. If you have the Android system firmware, please provide a download link for others to test. |
|
Hi @ophub !
Thank you for the explanation - now it is clear :)
No, unfortunately I can not boot from eMMC on 1GB Ethernet version, I tried all the possibilities - no success :(
Please see the photos below, the only difference I can see is in the Ethernet part:
1GB Top
1GB Bottom
100MB Top
100MB Bottom
https://drive.google.com/file/d/1H-bRELInEf1hTpEEKZr0Bc55-h3GiLJF/view?usp=drive_link @ophub please let me know if you have any idea how we can boot this 1GB from eMMC. Thanks! |
|
The kernel of version 6.1.y requires a correct u-boot bootloader. If the emmc is not working, further testing and adjustment of the u-boot are necessary. |
add x88prox3-u-boot.bin.sd.bin details: #1621
|
I have one of this but it seems like has fake ram and after playing around with this a bit I got it stuck on boot. |
|
I am wondering if this is not caused by different hardware I think mine has a different label
|
|
Is a bit strange because there no bad sectors but low level format reports errors |
add x88prox3-u-boot.bin.sd.bin details: #1621
|
Hi Guys, I've got a similar board, where the labels are the same on the main PCB, but this DTB did not have a good ethernet&BLE driver or memory size for me. All the other parts are OK. However, when I tried the sei610.dtb version, it started perfectly for eth0 and BLE as well, but the memory size is still just half of the total. I've checked the memory chips as well, there are 8 pieces from K4B4G0446D HYH9 which seems real for the 4GB RAM. When this issue is cleared I wish to move the system to the internal eMMC. |
Device Information | 设备信息
Armbian Version | 系统版本
Describe the bug | 问题描述
How can I share my dts/dtb to add this box to the supported devices?
Any help how to fix reported problems below will be appreciated.
Please provide a detailed description of the issue and, if necessary, attach a screenshot.
I was able to run the lunar on mainline kernel 6.1.42 on X88 Pro Pro X3 4/128GB using my dtb file.
I can share this file and we can add this box to supported devices list.
Almost all works correctly except the LED Screen Display, Bluetooth and eMMC Installation, but I can work on this.
LED Screen Display -> NOK
I tried to control the display according to the instruction led_screen_display_control.md but it doesn't work, the error is:
Bluetooth -> NOK
It partly works but the pairing is not possible.
eMMC Installation -> NOK
after this, the box is not starting from eMMC
What works :)
SSH -> OK
HDMI -> OK
WiFi -> OK
Ethernet -> OK
USB -> OK
Home Assistant Supervisor -> OK
to support docker cgroup v1 I added
systemd.unified_cgroup_hierarchy=0parameter setting in cmdlinethanks for the description How to Modify cmdline Settings 👍
aditonally to solve this
I added this to the Linux kernel boot parameters
apparmor=1 security=apparmorand now it is OK
The pictures of the board
Thanks ❤️
@ophub you are my hero :)
Any tips how to fix problems (installation on eMMC, LED Screen Display and BT) will be appreciated 👍
The text was updated successfully, but these errors were encountered: