kisgezenguz Posted February 3 Posted February 3 (edited) Hi Armbian community I have a Giada DN74 media player and would like to install Armbian on the box. First I try (through SD card) some community maintained images like the Orange Pi RK3399 or the Firefly RK3399, but none of them worked. Some google search teach me the Rockchip SoCs have fixed boot order (SPI->eMMC->SD card), and this cause my boot issue. Then search again how boot from SD card, the only solution which I find is to erase eMMC, so I erase the eMMC using: "rkdeveloptool ef". Unfortunately the box still not want to boot, so I open the box and try to identify the UART to see what is happening during the boot. I find a 4 pin connector (see images) which I assume this is the UART console, have a label "MCU_D" (Micro Controller Units Debug?) and have 3,3V on first pin and GND on the last pin. I try to use this connector whit some USB-to-UART (PL2303 and FT232RL) with multiple baud rate (115200, 1500000) without output. At this point was able still connect the box through USB and recover Android because MaskRom mode work fine. After some reading on https://opensource.rock-chips.com/wiki_Boot_option I deiced to build u-boot using evb-rk3399_defconfig and flash to the eMMC (which wan was a big mistake). I assume the box is try to boot from eMMC, but stuck there because is only u-boot on the eMMC nothing else. Unfortunately still no UART output (maybe is not UART connector) but also no Maskrom mode. If I understand right jock guide Unbrick Part, the only option to recover the box if I short EMMC CLK pin to GND. So my question is somebody could help me identify the eMMC CLK pin? Some extra info: According the rk3399 hardware design guide, I need to find a 22 ohm resistor near to the CLK pin. The eMMC is a Kingstone EMMC32G-TX29, and the manual write different CLK frequency's, I am don't know what I need to look. I have a Fnirsi dst-210 3in1 (sure not the best), which I could use measurements but I do not know how to set the oscilloscope parameters to find the CLK. Edited February 3 by kisgezenguz Add extra info 0 Quote
kisgezenguz Posted February 6 Author Posted February 6 Take some time but I was able to identify the CLK pin. Shorting the marked pins (CLK and GND in this case) was able to switch MaskRom mode. Note: in early boot stages the eMMC CLK only working in legacy mode (24Mhz). 1 Quote
BigDi Posted Friday at 09:45 AM Posted Friday at 09:45 AM I own the same box. Do you unbrick your box in the meanwhile? 0 Quote
kisgezenguz Posted Monday at 11:32 AM Author Posted Monday at 11:32 AM Yes, shorting the pins I was switch the device into MaskRom mode and install Android. Now I trying to identify and use the debug console, not much success so far 0 Quote
BigDi Posted yesterday at 07:20 AM Posted yesterday at 07:20 AM (edited) Which DTB did you use? I extracted the Android files and found a resource file named ENTRrk-kernel.dtb. The file began with "Rockchip RK3399 Excavator Board edp (Android)". Could it be possible that the device is compatible with this board? Edited yesterday at 07:23 AM by BigDi 0 Quote
BigDi Posted 19 hours ago Posted 19 hours ago I tried Armbian_26.2.1_Nanopim4v2_trixie_current_6.18.8_minimal.img.xz, wrote it on TF card and it booted into Linux without any changes. 0 Quote
kisgezenguz Posted 13 hours ago Author Posted 13 hours ago Thank you for the update, good to hear there is possible to run Linux on the box. In other hand, little bit is surprising, I try Nanopi M4 image and many other images, but non of work for me. Far as I know Rockchip have fixed boot order (emmc -> sd cadr ... ). Do you have a working Android on emmc and Armbian on sd card? On the weekend I will try also again the SD card boot. To answer your questions: I did not use any DTB at yet I only try rkbin boot loaders which not need to build. I was also able to extract the Android 11 Image there was model name "Giada JHS558" entered, I assume you have older Android version where the vendor use the Excavator Board as basis for the device tree. 0 Quote
BigDi Posted 1 hour ago Posted 1 hour ago (edited) The Nanopi M4 (not V2) has only 2GB of RAM. It could also possible that my device has an other (or older) Android. And you have to use the HDMI port 1 in the "middle". Not the HDMI under the TF slot! Edited just now by BigDi 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.