Jump to content

CSC Armbian for RK322X TV Boxes


jock
 Share

Recommended Posts

Sorry for the late reply, it looks like I'm allowed only one post per day due to bot/spam prevention measures.

The board is marked as MXQ-HX-V2.0 and has a sv6256p wifi chip which means no wi-fi for me (not that I really needed it, but still...)

 

Here's a picture:

 

igmMRXL.jpg

 

I can clearly see the serial port pads marked between the USB and SPDIF connector so I should be fine if anything goes pear shaped.


Still, I'd feel more comfortable knowing if there's been any test done on this board.
I don't need video output or anything else as this is going to be the DNS server of my local network (Pi-Hole, DNSCrypt and all that jazz), but I'd really appreciate not having to sacrifice an SD to hold the rootfs and, more importantly, the ethernet MUST work.

Link to comment
Share on other sites

Armbian Linux community supported weekly builds download

@jock at the end I was impatient and I cleared the emmc and tried to restore the backup... Everything went well, Android has been restored successfully! I think I was lucky because the backup is 2.5gb, under the fat32 limit, but after decompression it is as big as the all emmc (16gb). The problem is that I cannot extract anything from it, since the decompressed file is not an archive according 7zip, it's just a file without any extension. After cleared the emmc again, Linux from sd booted successfully and also after flashing in the emmc. wifi, hdmi works (only audio doesn't but I don't need that). I'm a bit disappointed by the performance, xfce doesn't run that fast, but it's ok since I need just to install klipper for my 3d printer and I hope it's enough for this purpose. Thank you for all the support, you have been precious!

 

 

 

 

Link to comment
Share on other sites

Looks like this board doesn't like booting from the SD.

I've tried booting both Multitool and the latest Armbian image and both time it just booted into Android.

 

When powering on while keeping the uboot button hidden in the AV connector it just doesn't do anything, black screen.

Link to comment
Share on other sites

2 hours ago, donluca said:

Still, I'd feel more comfortable knowing if there's been any test done on this board.
I don't need video output or anything else as this is going to be the DNS server of my local network (Pi-Hole, DNSCrypt and all that jazz), but I'd really appreciate not having to sacrifice an SD to hold the rootfs and, more importantly, the ethernet MUST work.

Normally the base dtb shipped with armbian should work fine with all boards out of the box.

 

Since your board looks very similar to MXQ_V72/V73, you may also try to apply the led-conf for that board via rk322x-config, but actually you can also keep the base dtb if your board is stable.

The wifi chip is not supported in mainline kernel, only the ssv6051 works; there is an adapted driver but you have to compile it by yourself.

Ethernet will work out of the box.

Anyway a dmesg log can already tell if the peripherals of the device are all detected or not, but for your tasks probably it is much more useful to see if the eMCP flash supports DDR or HS200 modes.

 

Link to comment
Share on other sites

51 minutes ago, marras said:

@jock at the end I was impatient and I cleared the emmc and tried to restore the backup... Everything went well, Android has been restored successfully! I think I was lucky because the backup is 2.5gb, under the fat32 limit, but after decompression it is as big as the all emmc (16gb). The problem is that I cannot extract anything from it, since the decompressed file is not an archive according 7zip, it's just a file without any extension. After cleared the emmc again, Linux from sd booted successfully and also after flashing in the emmc. wifi, hdmi works (only audio doesn't but I don't need that). I'm a bit disappointed by the performance, xfce doesn't run that fast, but it's ok since I need just to install klipper for my 3d printer and I hope it's enough for this purpose. Thank you for all the support, you have been precious!

Ah ok, not I got it... you tried to decompressed the backup twice, and the second time came the error. Well that's right, once you decompress the first time, you get a binary image that indeed cannot be decompressed again. You need a specific tool if you want to extract anything from it, but as long as your board boots and works fine there is no need for the dtb to be inspected.

The performance is what you get from an old armv7 chip, it has no horsepower to be a complete desktop replacement but works really fine for server/command line tasks.

Link to comment
Share on other sites

Just tried rebooting using "reboot update" via a terminal emulator on Android and with the Armbian image in the SD card slot it booted back to Android, but with the Multiboot image it gave me a green screen... and that was pretty much it.

At this point I'm a bit scared to proceed and try to wipe the eMMC since I can't test Armbian by booting it from the SD card 😐

Edited by donluca
Link to comment
Share on other sites

27 minutes ago, donluca said:

Looks like this board doesn't like booting from the SD.

I've tried booting both Multitool and the latest Armbian image and both time it just booted into Android.

 

When powering on while keeping the uboot button hidden in the AV connector it just doesn't do anything, black screen.

Yes, when you push the button you can then use rkdeveloptool to erase flash or upload a new firmware to the board, but you need a male-to-male cable to connect your PC to the OTG port of the board.

There is some reference about in the first page of the forum on how to do that.

 

The Armbian image as-is is not supposed to boot from sdcard if there is the android firmware, but the multitool should boot from sdcard no matter what firmware is there.

Well you can erase your flash if you don't care about the original android firmware; then the board will boot from sdcard in any case, but still your case is a bit weird because usually the multitool boots fine.

Link to comment
Share on other sites

13 minutes ago, donluca said:

At this point I'm a bit scared to proceed and try to wipe the eMMC since I can't test Armbian by booting it from the SD card 😐

 

Normally all the other board works that way because that behaviour is embedded in the SoC, but I don't know if the manufacturer did some weirdness with your board and that does not apply to you, but if you wipe the emmc the board should boot from sdcard, and then armbian can boot.

 

What is preventing armbian from running from sdcard is the android firmware, if you remove it from the emmc then both armbian and multitool should boot fine from sdcard.

 

edit: ha, I just reread the post and got the thing about the multitool green screen... well that's a very good sign, that means there is something not exactly right for your board in the dtb or the kernel. Do the led is fixed on/off or it is blinking? The serial adapter may tell more about the crash.

 

Link to comment
Share on other sites

A terrible suspicion came to me right as I was writing the previous post, so I did a quick cat /proc/cpuinfo... and it has an H3 CPU.

Everything that was written on the box and on the eBay auction was completely off.

 

It looks like this one: 

 

 

Apologies for wasting your time, I'll go and try out another image for the correct CPU!

Link to comment
Share on other sites

after contemplating on installing armbian, I finally managed to do it and it boots on first try but only in sd card. I'm kinda scared to flash it to the internal memory and mess up the box because it has emcp. 

at first the multitool didn't detect any emcp then after hitting the restart it sees the partition, backed it up and wipe it. I guess I got lucky

The board model is MXQ_71. Fingers crossed that my backup works if I will try to restore the original firmware.

Link to comment
Share on other sites

2 hours ago, speed21 said:

after contemplating on installing armbian, I finally managed to do it and it boots on first try but only in sd card. I'm kinda scared to flash it to the internal memory and mess up the box because it has emcp. 

If the armbian boots from sdcard the worst thing that may happen, once installed on eMCP, is the rootfs that does not get recognized. It is not as scary as it may sound, because you will indeed be able to reboot from sdcard into armbian/multitool.

I think you're safe enough.

Link to comment
Share on other sites

Hi @jock and @fabiobassa, it's great that you guys support the TV boxes that Armbian won't, amazing!

I have a HDMI stick with a RK3229 SOC, and this pathetic stick/board is a clone of a product with the brand "Any-cast", which at the same time is a clone of the Google Chromecast.

 

I thought I had bricked it, but I wonder if there's anything to do with it? 

I didn't expect to run Armbian on it, but if I can ssh into it and run something like lighttpd, it will be already great

 

I think the two soldered spot near the USB port is the UART serial, but I'm not sure

I also managed to do

rkdeveloptool db rk322x_loader_vxxx.bin

, seems that the image is flashed successfully, but it still show "Maskrom" mode after I do

rkdeveloptool ld

But I'm afraid to say that I'm not too clear about what I am doing 😅

(Oh there is an external WiFi chip that is soldered to a USB cable, you can look at the last three photos)

 

G5o6u24.jpgfHw0JI0.jpg

5CaZ7Ua.jpgsyeIWw9.jpg

Z4mWzJl.jpgbOggSib.jpgYJgWRn9.jpg

Link to comment
Share on other sites

7 hours ago, im_chc said:

I thought I had bricked it, but I wonder if there's anything to do with it? 

I didn't expect to run Armbian on it, but if I can ssh into it and run something like lighttpd, it will be already great

You can try and follow the "Restore" paragraph on the first page.

It shows how to manually upload an image to the internal flash without using the multitool but just the basic maskrom mode.

 

But from the photos I see that your stick has a SPI flash memory.

It has never been tested and I don't think any image could even boot there because both u-boot and kernel must be aware of that hardware, and in current images they aren't.

Link to comment
Share on other sites

I have a mxq 4k tv box (rk322x), I am aware that the hardware is very modest. however the only thing i want is to run vlc with an rstp stream but the video is getting really slow. dmesg gives the following error:

 

[10453.002041] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property

 

Welcome to Armbian 22.08.8 Buster with Linux 4.4.194-rk322x

Linux rk322x-box 4.4.194-rk322x #2 SMP Wed Aug 25 20:09:42 UTC 2021 armv7l GNU/Linux

 

*** Audio and Video over HDMI works. Audio is fine, but video in VLC and browsers is very slow ***

OUTPUT HDMI

 

 

 

perspicaz@rk322x-box:~$ dmesg | grep hdmi
[    2.078912] i2c i2c-0: of_i2c: modalias failure on /hdmi@200a0000/ports
[    2.078945] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    2.079081] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy)
[    2.080661] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb0d13808)
[    2.708067] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13
[    2.708076] dwhdmi-rockchip 200a0000.hdmi:     colorspace: RGB
[    2.708083] dwhdmi-rockchip 200a0000.hdmi:     scan mode: Underscan
[    2.708090] dwhdmi-rockchip 200a0000.hdmi:     colorimetry: No Data
[    2.708096] dwhdmi-rockchip 200a0000.hdmi:     picture aspect: No Data
[    2.708103] dwhdmi-rockchip 200a0000.hdmi:     active aspect: Same as Picture
[    2.708110] dwhdmi-rockchip 200a0000.hdmi:     itc: IT Content
[    2.708117] dwhdmi-rockchip 200a0000.hdmi:     extended colorimetry: xvYCC 601
[    2.708124] dwhdmi-rockchip 200a0000.hdmi:     quantization range: Full
[    2.708130] dwhdmi-rockchip 200a0000.hdmi:     nups: Unknown Non-uniform Scaling
[    2.708137] dwhdmi-rockchip 200a0000.hdmi:     video code: 0
[    2.708144] dwhdmi-rockchip 200a0000.hdmi:     ycc quantization range: Full
[    2.708150] dwhdmi-rockchip 200a0000.hdmi:     hdmi content type: Graphics
[    2.708156] dwhdmi-rockchip 200a0000.hdmi:     pixel repeat: 0
[    2.708164] dwhdmi-rockchip 200a0000.hdmi:     bar top 0, bottom 0, left 0, right 0
[    2.815413] rc rc0: RC for dw_hdmi as /devices/platform/200a0000.hdmi/rc/rc0
[    2.816118] input: RC for dw_hdmi as /devices/platform/200a0000.hdmi/rc/rc0/input0
[    4.199640] of_get_named_gpiod_flags: can't parse 'simple-audio-card,hp-det-gpio' property of node '/hdmi-sound[0]'
[    4.199673] of_get_named_gpiod_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/hdmi-sound[0]'
[    4.201805] asoc-simple-card hdmi-sound: i2s-hifi <-> 100c0000.i2s0 mapping ok
[   59.147020] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[   59.147095] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[   59.147148] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[   59.147180] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[   59.147208] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[   59.147239] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10425.340092] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13
[10425.340123] dwhdmi-rockchip 200a0000.hdmi:     colorspace: RGB
[10425.340144] dwhdmi-rockchip 200a0000.hdmi:     scan mode: Underscan
[10425.340163] dwhdmi-rockchip 200a0000.hdmi:     colorimetry: No Data
[10425.340181] dwhdmi-rockchip 200a0000.hdmi:     picture aspect: No Data
[10425.340201] dwhdmi-rockchip 200a0000.hdmi:     active aspect: Same as Picture
[10425.340220] dwhdmi-rockchip 200a0000.hdmi:     itc: IT Content
[10425.340239] dwhdmi-rockchip 200a0000.hdmi:     extended colorimetry: xvYCC 601
[10425.340258] dwhdmi-rockchip 200a0000.hdmi:     quantization range: Full
[10425.340277] dwhdmi-rockchip 200a0000.hdmi:     nups: Unknown Non-uniform Scaling
[10425.340295] dwhdmi-rockchip 200a0000.hdmi:     video code: 0
[10425.340314] dwhdmi-rockchip 200a0000.hdmi:     ycc quantization range: Full
[10425.340332] dwhdmi-rockchip 200a0000.hdmi:     hdmi content type: Graphics
[10425.340351] dwhdmi-rockchip 200a0000.hdmi:     pixel repeat: 0
[10425.340371] dwhdmi-rockchip 200a0000.hdmi:     bar top 0, bottom 0, left 0, right 0
[10450.713162] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13
[10450.713170] dwhdmi-rockchip 200a0000.hdmi:     colorspace: RGB
[10450.713175] dwhdmi-rockchip 200a0000.hdmi:     scan mode: Underscan
[10450.713180] dwhdmi-rockchip 200a0000.hdmi:     colorimetry: No Data
[10450.713184] dwhdmi-rockchip 200a0000.hdmi:     picture aspect: No Data
[10450.713189] dwhdmi-rockchip 200a0000.hdmi:     active aspect: Same as Picture
[10450.713193] dwhdmi-rockchip 200a0000.hdmi:     itc: IT Content
[10450.713198] dwhdmi-rockchip 200a0000.hdmi:     extended colorimetry: xvYCC 601
[10450.713202] dwhdmi-rockchip 200a0000.hdmi:     quantization range: Full
[10450.713207] dwhdmi-rockchip 200a0000.hdmi:     nups: Unknown Non-uniform Scaling
[10450.713211] dwhdmi-rockchip 200a0000.hdmi:     video code: 0
[10450.713215] dwhdmi-rockchip 200a0000.hdmi:     ycc quantization range: Full
[10450.713219] dwhdmi-rockchip 200a0000.hdmi:     hdmi content type: Graphics
[10450.713224] dwhdmi-rockchip 200a0000.hdmi:     pixel repeat: 0
[10450.713228] dwhdmi-rockchip 200a0000.hdmi:     bar top 0, bottom 0, left 0, right 0
[10453.002041] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10453.002109] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10453.002145] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10453.002165] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10453.002185] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
[10453.002204] [drm:dw_hdmi_rockchip_set_property] *ERROR* failed to set rockchip hdmi connector property
 

Edited by PerspicaZ
Link to comment
Share on other sites

On 12/2/2022 at 1:22 AM, PerspicaZ said:

*** Audio and Video over HDMI works. Audio is fine, but video in VLC and browsers is very slow ***

Hey...

 

I think this is expected...

 

From the 1st page:
"Full GPU acceleration on legacy kernel, mainline kernel has lima driver compiled in but X11 is very slow - you are still free to compile and install mali kernel driver on mainline yourself."

 

You could try to install jock's media package and then test videos on Kodi..

Link to comment
Share on other sites

Hey @jock

 

I'm planning to use rk322x-box on streaming project...

 

I'm testing Armbian 21.08.8 Focal with legacy kernel...

 

install_media.tgz installed

 

I want to use ffmpeg on my project.. so I checked somes features..


 

ffmpeg -decoders |grep mpp


V..... h264_rkmpp h264 (rkmpp) (codec h264)
V..... hevc_rkmpp hevc (rkmpp) (codec hevc)
V..... vp8_rkmpp vp8 (rkmpp) (codec vp8)
V..... vp9_rkmpp vp9 (rkmpp) (codec vp9


 

ffmpeg -encoders |grep mpp


no output.. no encoders...

 

Downloaded some samples to test

 

mkdir bbb
cd bbb
wget https://test-videos.co.uk/vids/bigbuckbunny/mp4/h264/1080/Big_Buck_Bunny_1080_10s_30MB.mp4
mv Big_Buck_Bunny_1080_10s_30MB.mp4 Big_Buck_Bunny_1080_10s_30MB_h264.mp4
wget https://test-videos.co.uk/vids/bigbuckbunny/mp4/h265/1080/Big_Buck_Bunny_1080_10s_30MB.mp4
mv Big_Buck_Bunny_1080_10s_30MB.mp4 Big_Buck_Bunny_1080_10s_30MB_h265.mp4
wget https://test-videos.co.uk/vids/bigbuckbunny/webm/vp8/1080/Big_Buck_Bunny_1080_10s_30MB.webm
mv Big_Buck_Bunny_1080_10s_30MB.webm Big_Buck_Bunny_1080_10s_30MB_vp8.webm
wget https://test-videos.co.uk/vids/bigbuckbunny/webm/vp9/1080/Big_Buck_Bunny_1080_10s_30MB.webm
mv Big_Buck_Bunny_1080_10s_30MB.webm Big_Buck_Bunny_1080_10s_30MB_vp9.webm

 

Here is my decoders tests...

 

VP8
ffmpeg -c:v vp8_rkmpp -i Big_Buck_Bunny_1080_10s_30MB_vp8.webm -benchmark -f null -

frame= 300 fps= 51 q=-0.0 Lsize=N/A time=00:00:10.16 bitrate=N/A speed=1.72x
video:120kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
bench: utime=0.924s stime=0.676s rtime=5.970s
bench: maxrss=32212kB

VP9
ffmpeg -c:v vp9_rkmpp -i Big_Buck_Bunny_1080_10s_30MB_vp9.webm -benchmark -f null -

frame= 300 fps= 72 q=-0.0 Lsize=N/A time=00:00:10.26 bitrate=N/A speed=2.48x
video:120kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
mpp[5929]: hal_vp9d_api: hal_vp9d_flush in
mpp[5929]: hal_vp9d_api: hal_vp9d_reset in
bench: utime=1.256s stime=0.880s rtime=4.184s
bench: maxrss=34360kB

H264
ffmpeg -c:v h264_rkmpp -i Big_Buck_Bunny_1080_10s_30MB_h264.mp4 -benchmark -f null -

Error while decoding stream #0:0: Resource temporarily unavailablepeed=0.977x
Last message repeated 78 times
Error while decoding stream #0:0: Resource temporarily unavailablepeed=0.682x
Last message repeated 112 times
Error while decoding stream #0:0: Resource temporarily unavailablepeed=0.518x
Last message repeated 65 times
^Came= 34 fps=0.1 q=-0.0 size=N/A time=00:00:01.13 bitrate=N/A speed=0.00282x

Not working...Too slow.. freeze sometimes

H265
ffmpeg -c:v hevc_rkmpp -i Big_Buck_Bunny_1080_10s_30MB_h265.mp4 -benchmark -f null -

frame= 300 fps= 65 q=-0.0 Lsize=N/A time=00:00:10.16 bitrate=N/A speed=2.22x
video:120kB audio:0kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: unknown
bench: utime=1.688s stime=1.052s rtime=4.621s
bench: maxrss=35472kB

 

VP8, VP9 and H265 seems ok

 

My questions...

 

How to use hardware encoding?

 

How to fix H264 hardware decoding?

 

Thx a lot!

Link to comment
Share on other sites

Hello, @jock I flashed armbian bullseye on my tvbox with emcp and it works fine. now I am having problems  running this thing headless. I installed OMV6 and every time I try to fire up the box without plugging in any display the OMV crashes. I can't log in nor do anything to it but I can ssh the box. I bought an hdmi dummy plug to try if it works but it still crashing.

Edited by speed21
Link to comment
Share on other sites

3 hours ago, speed21 said:

Hello, @jock I flashed armbian bullseye on my tvbox with emcp and it works fine. now I am having problems  running this thing headless. I installed OMV6 and every time I try to fire up the box without plugging in any display the OMV crashes. I can't log in nor do anything to it but I can ssh the box. I bought an hdmi dummy plug to try if it works but it still crashing.

Hmmm, I did not understand if the board crashes or OMV becomes unresponsive (and which part, since OMV leverages nginx and php for the web admin and samba/nfs/ftp for the file serving services).

 

You say that you can "ssh the box", but you mean that you can login via ssh and the board still operates normally or the ssh service is apparently responding but you can't login?

I have a board with debian buster that is running OMV perfectly fine for several months right now, but also I'm experimenting with an eMCP board that has Home Assistant and running as wireless AP without any issues. Both of the board are running headless with no problems or crashes. The eMCP board is a MXQPRO_V73, should not be far different than your MXQ_V71 (I may guess it is a MXQPRO_V71? You could post some high resolution photos that may be helpful identifying the board and its components)

Link to comment
Share on other sites

Quote

Hmmm, I did not understand if the board crashes or OMV becomes unresponsive (and which part, since OMV leverages nginx and php for the web admin and samba/nfs/ftp for the file serving services).

 

You say that you can "ssh the box", but you mean that you can login via ssh and the board still operates normally or the ssh service is apparently responding but you can't login?

I have a board with debian buster that is running OMV perfectly fine for several months right now, but also I'm experimenting with an eMCP board that has Home Assistant and running as wireless AP without any issues. Both of the board are running headless with no problems or crashes. The eMCP board is a MXQPRO_V73, should not be far different than your MXQ_V71 (I may guess it is a MXQPRO_V71? You could post some high resolution photos that may be helpful identifying the board and its components)

 

When I ssh to it, it works fine, I can log-in and throw a bunch of cli commands and it responds, but If I try to log-in to OMV (running Docker, Portainer and Jellyfin) usually it's just stuck on loading screen or in some case I can login but it hangs. also, when I transfer files to the shared drive it freezes especially when I copy a folder with small files inside. but If I plug it to my monitor it works fine. it also does this weird thing that If I try to reboot, it shuts down.

I am using Armbian_22.05.0-trunk_Rk322x-box_bullseye_current_5.15.25 to it.
Yup my board is a MXQPRO_V71 with 8GB Micron eMCP chip on it. 

211.jpg

233.jpg

244.jpg

Edited by speed21
Link to comment
Share on other sites

Sorry for the weird question, is possible to print, in console or some where else, the received IR codes?

I have a smartphone with IR and the tvboxs  have a receiver...so maybe i can create my "database" of custom codes of my controllers by saving the codes captured by armbian on tvbox.

 

Would it be possible?

Edited by MR01
Link to comment
Share on other sites

@MR01 Yes of course you can, you should try to investigate ir-keytable utility that should help you receive the raw scancodes, in particular the -t flag to do testing.

Usually one of the common protocol is NEC (practically all tvbox remotes use the NEC protocol), but you may have to guess it in case it does not work with your smartphone, which usually is software programmable to emulate several devices.

Link to comment
Share on other sites

@speed21 Well I don't have experience with OMV in docker, I run mine on the bare operating system without issues, but actually I don't know if installation scripts have been adapted to OMV6: you could try to install it from armbian-config if you don't worry about having it outside docker, or you can try and run your own container but that may take some time...

 

edit: your MXQPRO_V71 Is very very similar to mine MXQPRO_V73, which is very well supported with the proper led-conf overlay, you should have no particular issues with the hardware.

Link to comment
Share on other sites

I have another board , marking MXQPRO_V72,

SOC RK3228A,

eMMC H9TQ65A8GTMC,

WiFi ESP8089

Boot well from SD card (Multitool and Armbian image written to the card). But when writing an image to eMMC using MULTITOOL, it does not boot.

Also Armbian-config and Armbian-install are not executed due to lack of space.

Also WiFi ESP8089  is not seen in the system booted from SD card.

What could I have done wrong?

Edited by Maker39
Link to comment
Share on other sites

@Maker39 hello, welcome back ;)

Your board should be well supported, esp8089 also is well supported and performs very well.

Which image are you running? You should use an up-to-date image running with mainline kernel. Older images and legacy have not been tested or are not supported at all on eMCP boards.

 

Also please post a dmesg log from your armbian sdcard installation.

Link to comment
Share on other sites

@jockI try many images, last loaded  Armbian 23.02.0-trunk Kinetic with Linux 6.0.11-rk322x

dmesg after armbian-install

[  239.317263] mmc_host mmc2: Bus speed (slot 0) = 2343750Hz (slot req 2343750Hz, actual 2343750HZ div = 0)
[  239.392916] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[  239.396109] I/O error, dev mmcblk2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 2
[  239.413523] Buffer I/O error on dev mmcblk2, logical block 0, lost async page write
[  245.431404] ext3: Unknown parameter 'compress-force'
[  245.446842] ext4: Unknown parameter 'compress-force'
[  245.479972] /dev/mmcblk2p1: Can't open blockdev
[  245.515559] /dev/mmcblk2p1: Can't open blockdev

 

Link to comment
Share on other sites

@Maker39 Yes, that piece of dmesg is exactly was I looking for and it explains the reason why the device does not boot from emmc.

It could be that the eMMC is broken, but if Android was booting and working fine I guess the part is physically ok and there is some configuration issue.

 

I suggest to you to run armbian on sdcard and do some tests with rk322x-config.

You need to try the various combinations from the eMMC section:

image.png.c019f09b1dbd8d3ced843631d67ed9db.png

 

From there try these combinations:

* emmc-pins alone

* emmc-pins + emmc-ddr-ph45

* emmc-pins + emmc-ddr-ph180

* emmc-pins + emmc-hs200

* don't set any options

 

and see if any of them provides stable access to eMMC. On every reconfiguration of course you need to reboot the machine.

If you get a fairly stable combination, you can install it onto emmc.

 

Another question: was the multitool able to access the eMMC without particular issues?

Link to comment
Share on other sites

@Maker39 Well maybe the eMMC is really broken if it kernel can't write the sector 0 of the device but doing those tests with rk322x-config may help.

 

About the esp8089, you should post dmesg log (or, even better, the URL given by armbianmonitor -u). The esp8089 driver is there and it is perfectly working.

Did you select the right led-conf from rk322x-config? (Yours should be led-conf6)

 

Also the original dtb may come handy

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

×
×
  • Create New...