Hqnicolas Posted November 26, 2024 Author Posted November 26, 2024 @cmuki try to run https://forum.armbian.com/topic/40483-efforts-to-develop-firmware-for-h96-max-m9-rk3576-tv-box-8g128g/#findComment-202914 your benchmark shows the rknpu Status of performance related governors found below /sys (w/o cpufreq): * dmc: dmc_ondemand / 528 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 528 1068 1560 2112) * 27700000.npu: rknpu_ondemand / 300 MHz (rknpu_ondemand dmc_ondemand userspace powersave performance simple_ondemand / 300 400 500 600 700 800 900 1000) 0 Quote
Tusemanu Posted December 3, 2024 Posted December 3, 2024 On 11/26/2024 at 11:38 AM, Hqnicolas said: your benchmark shows the rknpu Expand Hello. Those. Is RKNPU working correctly? Have you tried VPU, GPU, does it work? 0 Quote
Hqnicolas Posted December 4, 2024 Author Posted December 4, 2024 On 12/3/2024 at 12:52 PM, Tusemanu said: Those. Is RKNPU working correctly? Have you tried VPU, GPU, does it work? Expand for tv-box it's all at your own risk anything you find in this thread should always be considered non-functional or unreleased do not buy any tv-box, buy only official boards from manufacturers https://www.armbian.com/partners/ 1 Quote
kevchi Posted December 21, 2024 Posted December 21, 2024 Hi all. Any idea how to root the device? 0 Quote
tnt Posted December 22, 2024 Posted December 22, 2024 (edited) has anyone managed to save the changed u-boot environment? it seems that uboot.img is a binary u-boot file that stores the environment variables that are set during compilation. Edited December 22, 2024 by tnt add remark 0 Quote
Hqnicolas Posted January 2 Author Posted January 2 (edited) On 12/22/2024 at 12:24 PM, tnt said: has anyone managed to save the changed u-boot environment? Expand You don't need to save the u-boot env, it's included in your armbian build. @tnt don't trust any image from factory or other forum users, just build your own images. On 9/13/2024 at 7:51 PM, hzdm said: I was able to fix the reset button in U-boot. I got the uboot.dtb file from the Android firmware. To add it to the build - you need to replace the armsom-sige5-rk3576_defconfig file in the build/patch/u-boot/legacy/u-boot-armsom-rk3576/defconfig/ directory Expand armsom-sige5-rk3576_defconfigFetching info... Edited January 2 by Hqnicolas 0 Quote
Hqnicolas Posted January 2 Author Posted January 2 On 12/21/2024 at 10:11 AM, kevchi said: Hi all. Any idea how to root the device? Expand this is an Linux development community, Here is an tutorial for android users: https://youtu.be/1vpepaQ-VQQ 0 Quote
Freeze Posted January 4 Posted January 4 Hello. Thanks for your work, fine result. i've tested desktop image and.. 1) For begginers, before executing the command "rkdeveloptool db...", make sure that the board is in operation mode => maskrom rkdeveloptool list rkdeveloptool rd 3 #and after that h96 ready to: rkdeveloptool db RK3576_MiniLoaderAll.bin rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop.img ========================== 2) Disable hibernate, i catched it on SSH session (pic 1) helped me gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type nothing 3) HDMI i use virtual monitor for stable work, without real monitor #in terminal sudo nano /usr/share/X11/xorg.conf.d/10-quirks.conf add it on end of file and save. Switch off hdmi from h96 and restart. Section "Monitor" Identifier "Monitor0" HorizSync 28.0-80.0 VertRefresh 48.0-75.0 # https://arachnoid.com/modelines/ # 1920x1080 @ 60.00 Hz (GTF) hsync: 67.08 kHz; pclk: 172.80 MHz Modeline "1920x1080_60.00" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync EndSection Section "Device" Identifier "Card0" Driver "dummy" VideoRam 256000 EndSection Section "Screen" DefaultDepth 24 Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Depth 24 Modes "1920x1080_60.00" EndSubSection EndSection On other PCs, only the virtual display works. In this case, both can work. It doesn't have to be that way, but it's useful in this case. ====================================== One question. I soldered sd slot on h96, but cant see disk on terminal, lsblk shows just mmcblk2. is it poorly soldered or do I need to do something else? 0 Quote
tnt Posted January 5 Posted January 5 On 1/2/2025 at 12:40 PM, Hqnicolas said: You don't need to save the u-boot env, it's included in your armbian build. @tnt don't trust any image from factory or other forum users, just build your own images. Expand I am considering the possibility of implementing the dual boot feature, for example emmc (android), usb/sd armbian. 0 Quote
Freeze Posted January 5 Posted January 5 After apt-get update and upgrade DTB files was damaged :(( How its recovery, dont know rkdeveloptool dont working rkdeveloptool reboot-maskrom Reset Device quit, creating comm object failed! It's log from console interface(COM port) Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x40040000 ... sha256(1d13f803de...) + OK ## Checking uboot 0x40200000 ... sha256(ad96202f45...) + OK ## Checking fdt 0x4033dd80 ... sha256(6d0c8a3eca...) + OK ## Checking atf-2 0x400f0000 ... sha256(2f297c059b...) + OK ## Checking atf-3 0x3fe70000 ... sha256(9d9e1b461e...) + OK ## Checking optee 0x48400000 ... sha256(31c3421ab3...) + OK Jumping to U-Boot(0x40200000) via ARM Trusted Firmware(0x40040000) Total: 94.153/238.645 ms INFO: Preloader serial: 0 NOTICE: BL31: v2.3():v2.3-749-g30018b771:derrick.huang, fwver: v1.04 NOTICE: BL31: Built : 09:43:01, Apr 16 2024 INFO: ext 32k is not detected INFO: ARM GICv2 driver initialized INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: BL31: Initializing runtime services INFO: BL31: Initializing BL32 I/TC: I/TC: OP-TEE version: 3.13.0-791-g185dc3c92 #hisping.lin (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Tue Apr 16 11:05:25 CST 2024 aarch64, fwver: v1.01 I/TC: OP-TEE memory: TEEOS 0x200000 TA 0xc00000 SHM 0x200000 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x40200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-armbian-2017.09-S57b8-P9d8d-H8c72-V8051-Bda0a-R448a (Sep 13 2024 - 04:56:59 +0000) Model: Rockchip RK3576 Evaluation board MPIDR: 0x0 PreSerial: 0, raw, 0x2ad40000 DRAM: 4 GiB Sysmem: init Relocation Offset: bda21000 Relocation fdt: fb9f9a70 - fb9fecf0 CR: M/C/I Using default environment DM: v2 mmc@2a310000: 1, mmc@2a330000: 0 Bootdev(atags): mmc 0 MMC0: HS400 Enhanced Strobe, 200Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition Failed to load DTB, ret=-19 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 Model: Rockchip RK3576 Evaluation board download key pressed... entering download mode... RKUSB: LUN 0, dev 0, hwpart 0, sector 0x0, count 0x3a3e000 \usb device is high-speed \usb device is high-speed 0 Quote
Hqnicolas Posted January 5 Author Posted January 5 On 1/5/2025 at 11:15 AM, Freeze said: After apt-get update and upgrade DTB files was damaged Expand @Freeze the answer is in your name.... sudo apt install armbian-config sudo armbian-config select # SYSTEM select # FREEZE 0 Quote
Hqnicolas Posted January 5 Author Posted January 5 On 1/5/2025 at 9:16 AM, tnt said: I am considering the possibility of implementing the dual boot feature, for example emmc (android), usb/sd armbian. Expand just solder an SD card reader. it will works: https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/12/#findComment-196381 https://forum.armbian.com/topic/24091-efforts-to-develop-firmware-for-h96-max-v56-rk3566-4g32g/#findComment-165929 0 Quote
Freeze Posted January 5 Posted January 5 Ok, but now, how i can recovery damage DTB files? I cant start armbian, just console is working 0 Quote
Hqnicolas Posted January 5 Author Posted January 5 (edited) On 1/5/2025 at 11:52 AM, Freeze said: how i can recovery damage DTB files? Expand I don't know how you guys are burning the armbian images on this model so, emmc internal memory is not accessible without rkDevTool burning system, you will need to reflash the armbian system. This brings me an old warning, don't trust a TV box to store your files, always configure a cloud like gdrive, ms onedrive, nextcloud.... On 9/8/2024 at 7:17 AM, hzdm said: Press the reset button. Turn on the power. $rkdeveloptool db RK3576_MiniLoaderAll.bin $rkdeveloptool wl 0x0 Armbian-unofficial_24.8.0-trunk_H96-m9_noble_vendor_6.1.75_gnome_desktop-test_1.img Expand I don't have this model of TV box, my country has closed it to external products, If you manage to recover, share it with others on the forum. Edited January 6 by Hqnicolas 0 Quote
tnt Posted January 17 Posted January 17 (edited) On 1/5/2025 at 11:52 AM, Hqnicolas said: just solder an SD card reader. Expand soldering the card reader case was not successful. Perhaps the controller or some other elements need to be unsoldered. Edited January 17 by tnt Add photo 0 Quote
Hqnicolas Posted January 17 Author Posted January 17 (edited) On 1/17/2025 at 5:27 PM, tnt said: soldering the card reader case was not successful. Perhaps the controller or some other elements need to be unsoldered. Expand It seems that this time they excluded the passive components from the board, look at the v56 board SD reader, you will need to add 2 ceramic capacitors to the board i think. and also check the Reader body 4 large GND pads if it's sodered. no device is needed to use the SD reader you must have a TTL connected to the board to debug, clear the EMMC with this method: using the T95 Method On android ROM flash the Wipe_part on Boot partition flash the Wipe_part on Recovery partition Connect the power cord... wait 1 second and in a fraction of second, connect the sd-Card on device..... if it doesn't boot, try again in a different timming 2 seconds after power. Based on this example Quote Expand Edited January 17 by Hqnicolas 0 Quote
Vincenzoernst1 Posted January 18 Posted January 18 @tnt i also didnt get the the sd slot running. i soldered 3 NEW slots and none of them worked. since i ordered a 10 pack from china i didnt mind to dump them after unsoldering. i always got a dmesg error (logs somewhere above). there are 2 errors possible: bad china quality slots there is something on the board missing. also i dont think there was somthing wrong with the soldering since im an enineer and solder on daily basis. btw. i uses a hot air gun for solderding, therefor it i also should be working. if there are now 2 of us having problems i might thingk its no problem on my side..... 1 Quote
Deoptim Posted January 19 Posted January 19 On 1/18/2025 at 2:30 PM, Vincenzoernst1 said: i also didnt get the the sd slot running. Expand In dts RK809 node for that device needed configuration for SD card 3v3 regulator and 1v8 regulator - than theoretically SD card will work fine. 0 Quote
Hqnicolas Posted yesterday at 03:14 AM Author Posted yesterday at 03:14 AM (edited) Armbian's archives can be uncompressed with 7-Zip on Windows, Keka on OS X and 7z on Linux. Images shall only be written with imaging tools that validate burning results. This saves you from corrupted SD card contents. Approved Tools: USBImager a lightweight cross-platform imaging tool Balena Etcher an electron / node.js based cross-platform imaging tool (may contain spyware) Flashing Firmware on h96 max m9 rk3576 tv box h96 max m9 https://drive.google.com/drive/folders/1g63F8fGSLEA9iK2_Mqzd6F0xfaTRnGlm?usp=sharing https://drive.google.com/file/d/1hbM1ZCH8NU_snjVeZ-_hfRlnC_dgFcrK/view?usp=sharing https://drive.google.com/file/d/1n1Aw78G5zXKRYj5Nx19U_FrBIoU_NS6h/view?usp=sharing h96 max m9s https://drive.google.com/drive/folders/1Q360l5XbTVsWIvWkqy2xJ0sLpqHRSApM?usp=sharing https://drive.google.com/file/d/1n1Aw78G5zXKRYj5Nx19U_FrBIoU_NS6h/view?usp=sharing https://drive.google.com/file/d/1hbM1ZCH8NU_snjVeZ-_hfRlnC_dgFcrK/view?usp=sharing - Download the desired version of the stock firmware from the link from the post with the firmware. - To make it easier to install the firmware, create in the root directory of any disk (section) a folder (directory) with a memorable name, Latin characters and without spaces, for example H96MAX . - In the download folder (where the downloaded files are saved) on your computer, copy or move to the created folder H96MAX the previously downloaded archive file RK3576_firmware_tools.com and the stock firmware file that you will install. - Go to the H96MAX folder and unpack the downloaded archive RK3576_firmware_tools.com. Enter the folder RK3576_firmware_tools and further to the folder DriverAssitant_v5.12. Highlight the file name DriverInstall.exe with the mouse cursor and right-click on this line (PCM), open the context menu and click on the line - Run as administrator. Confirm (Yes / OK) in the system window - "Allow ...". In the driver installer window that appears, click on the virtual driver removal button "Uninstall driver", wait for the successful driver removal window. Confirm OK. Close the driver installer window. To remove possible leftovers and traces of the previous driver in the registry and in the Windows system, restart your computer. This will only benefit your computer's operating system. Pre-installing the driver is done in order to exclude possible failures during driver installation, because you do not know exactly whether a particular version of the processor driver was installed and which version of Rockchip. - After restarting your computer, go back to the folder \ H96MAX \ RK3576_firmware_tools \ DriverAssitant_v5.12. Highlight the file name DriverInstall.exe with the mouse cursor and right-click on this line (PCM), open the context menu and click on the line - Run as administrator. Confirm (Yes / OK) in the system window - "Allow ...". In the driver installer window that appears, now click on the virtual driver installation button "Install driver", wait for the successful driver installation window. Confirm OK. Close the driver installer window. The entire driver is installed. - Go to the H96MAX folder. Make sure that it contains the previously downloaded archive of the desired firmware. Typically, firmware downloaded from publicly available links is packed with archivers - zip, 7z, etc., in order to reduce its size and minimize the risk of data damage. For the firmware program, it is not an archive file that is needed, but the firmware image packed with an archiver. Therefore, the downloaded archive must be unpacked to get the firmware image itself (a file with a unique name and an .img extension). Unpack the firmware file. Go to the new unpacked archive folder and check if there is a file with the unique name of the installed firmware image and the .img extension. If your computer is running Windows 7, then to unpack the firmware file you will need a third-party archiver - WinRAR, 7z, etc. After making sure that there is a firmware image, go back to the H96MAX folder, then to the RK3576_firmware_tools folder, then to the FactoryTool_v1.89 folder. Make sure that there is a FactoryTool.exe file. This is the executable file of the firmware program. Do not close the explorer window with the FactoryTool.exe program folder open. - Go to the console with the TV connected. If the prefix is on, with a long press on the Power button on the panel, call the system menu and select and confirm Disable in it. The prefix should turn off and not go into service. You can check this if you press any button on the remote control (except the Power button) and the prefix does not turn on. If the console is turned off, follow the following steps in the sequence as indicated. Confidently pull the BP cable plug out of the console's power socket. Turn off the TV. Disconnect the TV from the mains. Disconnect the HDMI cable from the console. Disconnected from all cables, transfer to the computer. - On your computer, open an Explorer window with the FactoryTool.exe program folder. Double-click on the FactoryTool.exe file name and run the firmware program. In the opened window of the running program, click on the "Firmware" button (top left corner of the window) and in the window that appears, go to the directory where the unpacked firmware image that needs to be installed is located. Highlight the image file name with the mouse cursor and click "Open". The file selection window will close automatically and the firmware window will become active. Make sure that the program displays the path and file name of the firmware image in the "Firmware" section under the button of the same name, and in the Bootloader and Chip lines, the bootloader version number and the RK3576 chip name are indicated respectively. Until the Factory Tool program window is active, click on the "Restore" tab. After that, the "Restore" radio button should become active (light up). Remove your hands from the mouse and keyboard, the FactoryTool window should remain active and in the foreground. That's it, you can proceed to the final part of the firmware process itself. - Securely insert the plug of a previously prepared USB cable into the working USB port of the computer. Insert the previously prepared (sharpened) match into the hole in the headrest on the rear panel of the console. Dip it into the hole until the characteristic click and with one hand, lock the match in this position. With the other hand, take an elongated cable plug and confidently insert it into the USB 3.0 port (blue) of the prefix. After 1-2 seconds, a line will appear in the FactoryTool firmware window with information about the system number of the hub to which the prefix was connected, the type of the Loader device. Release and remove the match. In the program window, click on the virtual button "Run" and the direct firmware process will begin. Wait until the process is complete. After 2-3 minutes, if the firmware is successful, the line with information will be highlighted in green, an inscription will appear Success (Success) and the time spent on the firmware. Press the virtual button "Stop" at the top of the program window, close the program window. Disconnect the USB cable plug from the console. Re-interrogation for the new version is done. Move the console to the TV. - Make sure the TV is completely disconnected from the mains. Reliably connect the cable from the TV HDMI input to the console's HDMI output. Turn on the TV from the mains. Turn on the TV from the remote control. Wait until the TV is completely loaded. Confidently insert the plug of the console's pin cable into the console's power socket, if the console's power supply was disconnected from the mains, connect it. When you turn it on for the first time after the overload, the firmware in the console's memory should start, this will take longer than the usual download after turning it off. When the console boots up, make the necessary device settings. Edited yesterday at 03:36 AM by Hqnicolas 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.