pro777
-
Posts
42 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by pro777
-
-
I tried several hdmi cables. Despite the fact that the boards are almost identical, the result, unfortunately, has not changed:
user@armbian:~$ dmesg | grep i2c [ 4.591484] i2c /dev entries driver [ 4.596757] of_get_named_gpiod_flags: can't parse 'vsel-gpios' property of node '/i2c@ff650000/syr827@40[0]' [ 4.596772] of_get_named_gpiod_flags: can't parse 'vsel-gpio' property of node '/i2c@ff650000/syr827@40[0]' [ 4.623910] of_get_named_gpiod_flags: can't parse 'vsel-gpios' property of node '/i2c@ff650000/syr828@41[0]' [ 4.623925] of_get_named_gpiod_flags: can't parse 'vsel-gpio' property of node '/i2c@ff650000/syr828@41[0]' [ 4.739645] rk3x-i2c ff650000.i2c: Initialized RK3xxx I2C bus at f0fba000 [ 4.748307] rk3x-i2c ff140000.i2c: Initialized RK3xxx I2C bus at f0fbc000 [ 4.756830] rk3x-i2c ff150000.i2c: Initialized RK3xxx I2C bus at f0fbe000 [ 4.828714] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/i2c@ff160000/rk1000-ctl@40[0]' - status (0) [ 5.058954] rk3x-i2c ff160000.i2c: Initialized RK3xxx I2C bus at f0fd2000 [ 5.067966] rk3x-i2c ff170000.i2c: Initialized RK3xxx I2C bus at f0fd4000 [ 5.076760] rk3x-i2c ff660000.i2c: Initialized RK3xxx I2C bus at f0fd6000 [ 6.130961] of_get_named_gpiod_flags: parsed 'rockchip,spk-en-gpios' property of node '/i2c@ff160000/rk1000-codec@60[0]' - status (0) [ 7.587827] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 8.587845] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 9.587831] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 10.587841] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 11.587845] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 13.154237] i2c i2c-6: Added multiplexed i2c bus 7 [ 13.160262] i2c i2c-6: Added multiplexed i2c bus 8 [ 28.767585] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 29.767561] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 30.767564] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 31.767546] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 32.767544] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 33.767553] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 34.767573] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 35.767639] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 36.767661] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 37.767644] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 42.727768] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 43.727786] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 44.727810] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 45.727831] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 46.727898] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 47.927965] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 48.927976] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 49.927992] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 50.928016] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 51.928036] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 52.928084] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 53.928074] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 54.928100] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 55.928158] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 [ 56.928096] rk3x-i2c ff170000.i2c: timeout, ipd: 0x00, state: 1 -------------------------------------------------------------------- root@armbian:/home/user# i2cdetect -y 5 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -------------------------------------------------------------------- root@armbian:/home/user# get-edid -b 5 5 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 5 as per your request. ^CApparently, there are still differences in the electrical scheme.
-
On 5/22/2018 at 10:54 PM, jock said:
Does it work changing i2c5 to i2c4 for you, or you just don't get the timeout messages?
Yes, indeed, I just got rid of the timeout messages in this way.
At me here such board:
If i2c5 is enabled and indicated to read the ddc information from it, i.e.:
Conf.1
&hdmi { /delete-property/pinctrl-names; /delete-property/pinctrl-0; /delete-property/pinctrl-1; ddc-i2c-bus = <&i2c5>; #sound-dai-cells = <0>; status = "okay"; }; &i2c5 { status = "okay"; };then the following information is received:
user@armbian:~$ ls -l /dev/i2c* crw-rw---- 1 root i2c 89, 0 May 25 14:37 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 May 25 14:37 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 May 25 14:37 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 May 25 14:37 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 May 25 14:37 /dev/i2c-4 crw-rw---- 1 root i2c 89, 5 May 25 14:37 /dev/i2c-5 user@armbian:~$ sudo i2cdetect -y 5 [sudo] password for user: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- user@armbian:~$ sudo get-edid -b 5 [sudo] password for user: 5 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 5 as per your request. ^CDDC information can be obtained via i2c at ports 0x37 (DDC) and 0x50 (EDID).
We see that there are no contacts on i2c5 on these ports.
We change dts:
Conf.2
&hdmi { /delete-property/pinctrl-names; /delete-property/pinctrl-0; /delete-property/pinctrl-1; ddc-i2c-bus = <&i2c4>; #sound-dai-cells = <0>; status = "okay"; }; &i2c5 { status = "disabled"; };We get:
user@armbian:~$ ls -l /dev/i2c* crw-rw---- 1 root i2c 89, 0 May 25 14:47 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 May 25 14:47 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 May 25 14:47 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 May 25 14:47 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 May 25 14:47 /dev/i2c-4 user@armbian:~$ sudo i2cdetect -y 4 [sudo] password for user: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: UU -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- user@armbian:~$ sudo get-edid -b 4 4 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 4 as per your request. Bus 4 doesn't really have an EDID... Couldn't find an accessible EDID on this bus. I'm sorry nothing was successful. Maybe try some other arguments if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.As you can see, on i2c4 on ports 0x37 and 0x50 there is also no contact.
We check the following configuration:
Conf.3
&hdmi { /delete-property/pinctrl-names; /delete-property/pinctrl-0; /delete-property/pinctrl-1; //ddc-i2c-bus = <&i2c4>; #sound-dai-cells = <0>; status = "okay"; }; &i2c5 { status = "disabled"; };We get:
user@armbian:~$ ls -l /dev/i2c* crw-rw---- 1 root i2c 89, 0 May 25 14:51 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 May 25 14:51 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 May 25 14:51 /dev/i2c-2 crw-rw---- 1 root i2c 89, 3 May 25 14:51 /dev/i2c-3 crw-rw---- 1 root i2c 89, 4 May 25 14:51 /dev/i2c-4 crw-rw---- 1 root i2c 89, 6 May 25 14:51 /dev/i2c-6 user@armbian:~$ sudo i2cdetect -y 6 [sudo] password for user: 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- user@armbian:~$ sudo get-edid -b 6 6 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 6 as per your request. Bus 6 doesn't really have an EDID... Couldn't find an accessible EDID on this bus. I'm sorry nothing was successful. Maybe try some other arguments if you played with them, or send an email to Matthew Kern <pyrophobicman@gmail.com>.Strangely enough, in the system has appeared i2c6 to the address 0xff980000 (HDMI)
And also there are contacts on the ports of interest!But it is impossible to obtain EDID information.
I also have the MK809-4K on RK3288 chip. I drew attention to the fact that it initially selects the correct mode of HDMI for 1920x1080. Therefore, I also checked the configuration # 3 on it. And it was possible to successfully read the EDID:
user@armbian:~$ ls -l /dev/i2c* crw-rw---- 1 root i2c 89, 0 May 25 11:10 /dev/i2c-0 crw-rw---- 1 root i2c 89, 1 May 25 11:10 /dev/i2c-1 crw-rw---- 1 root i2c 89, 2 May 25 11:10 /dev/i2c-2 crw-rw---- 1 root i2c 89, 4 May 25 11:10 /dev/i2c-4 crw-rw---- 1 root i2c 89, 6 May 25 11:10 /dev/i2c-6 user@armbian:~$ sudo i2cdetect -y 6 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- user@armbian:~$ sudo get-edid -b 6 > edid.bin [sudo] пароль для user: 6 This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface Only trying 6 as per your request. 256-byte EDID successfully retrieved from i2c bus 6 Looks like i2c was successful. Have a good day. user@armbian:~$ parse-edid < edid.bin Checksum Correct Section "Monitor" Identifier "SAMSUNG" ModelName "SAMSUNG" VendorName "SAM" # Monitor Manufactured week 46 of 2012 # EDID version 1.3 # Digital Display DisplaySize 480 270 Gamma 2.20 Option "DPMS" "false" Horizsync 15-81 VertRefresh 24-75 # Maximum pixel clock is 230MHz #Not giving standard mode: 1152x864, 75Hz #Not giving standard mode: 1280x720, 60Hz #Not giving standard mode: 1280x800, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1600x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Extension block found. Parsing... Modeline "Mode 15" 74.25 1920 2448 2492 2640 540 542 547 562 +hsync +vsync interlace Modeline "Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 1" 85.50 1366 1436 1579 1792 768 771 774 798 +hsync +vsync Modeline "Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 3" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline "Mode 5" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline "Mode 6" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace Modeline "Mode 7" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace Modeline "Mode 8" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync Modeline "Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync Modeline "Mode 10" 74.250 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 11" 74.250 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 12" 74.250 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline "Mode 13" 27.027 1440 1478 1602 1716 480 484 487 525 -hsync -vsync interlace Modeline "Mode 14" 27.000 1440 1464 1590 1728 576 578 581 625 -hsync -vsync interlace Modeline "Mode 16" 74.25 1920 2008 2052 2200 540 542 547 562 +hsync +vsync interlace Modeline "Mode 17" 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync Modeline "Mode 18" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync Option "PreferredMode" "Mode 15" EndSectionLet's sum up. Configuration # 3 allows us to successfully obtain the EDID information on the MK809-4K. Failure in the case of Q8 can speak of a hardware problem?
P.S. jock, tell me, please, what code allows "power hold GPIO which keeps the act8846 powering the board"?
-
Hi, JMCC,
When playing video files with the MPV in Armbian, as mentioned above in your message, often there is a video playback error:
user@armbian:~$ LD_LIBRARY_PATH=/opt/libmali-gbm:$LD_LIBRARY_PATH mpv --hwdec=rkmpp --vo=gpu --gpu-api=opengl --gpu-context=drm /media/user/1803-416A/HEVC/Затерянные\ в\ космосе.1998.HEVC.mkv Playing: /media/user/1803-416A/HEVC/Затерянные в космосе.1998.HEVC.mkv (+) Video --vid=1 (*) 'HEVC' (hevc 1920x800 23.976fps) (+) Audio --aid=1 --alang=rus (*) 'Kinomanija' (ac3 6ch 48000Hz) Audio --aid=2 --alang=rus 'Dub' (ac3 2ch 48000Hz) Audio --aid=3 --alang=rus 'R5' (ac3 6ch 48000Hz) Audio --aid=4 --alang=eng 'Original' (ac3 6ch 48000Hz) Subs --sid=1 --slang=rus 'Full' (subrip) Subs --sid=2 --slang=eng 'Full' (subrip) File tags: Title: Lost in Space [vo/gpu] VT_GETMODE failed: Inappropriate ioctl for device [vo/gpu/opengl] Failed to set up VT switcher. Terminal switching will be unavailable. mpi: mpp version: 598cae3 author: Jacob Chen DEBIAN: update rules for release_20171218-2 mpp_rt: NOT found ion allocator mpp_rt: found drm allocator H265D_PARSER: No start code is found. Using hardware decoding (rkmpp). AO: [pulse] 48000Hz 5.1(side) 6ch float VO: [gpu] 1920x800 drm_prime [vo/gpu] Using HW-overlay mode. No GL filtering is performed on the video! [vo/gpu/drmprime-drm] Failed to create framebuffer on layer 0. [vo/gpu/drmprime-drm] Failed to create framebuffer on layer 0. AV: 00:00:00 / 02:10:14 (0%) A-V: 0.000 [vo/gpu/drmprime-drm] Failed to create framebuffer on layer 0. AV: 00:00:00 / 02:10:14 (0%) A-V: 0.000 [vo/gpu/drmprime-drm] Failed to create framebuffer on layer 0. AV: 00:00:00 / 02:10:14 (0%) A-V: 0.000 [vo/gpu/drmprime-drm] Failed to create framebuffer on layer 0. AV: 00:00:00 / 02:10:14 (0%) A-V: 0.000 Exiting... (Quit)Instead of the video image - an empty black screen, although there is sound.
I installed ffmpeg and mpv deb-packages and you collected the package GBM version of libmali in Debian firmware from Rockchip - there are no such problems, everything is beautifully played. I thought maybe Ffmpeg was assembled in Debian and Armbian Ubuntu with different keys. Checked, the difference, seemingly insignificant, ffmpeg in Debian compiled with additional keys:
--enable-librsvg --enable-libxml2 --cross-prefix=arm-linux-gnueabihf- --arch=armhf --target-os=linux
I also checked that the libraries libsdl2, libxml2 and librsvg in Armbian are installed.
Any idea what might be the problem?
-
hi, jock,
please consider the following additions and corrections to dts:
disable i2c5 to get rid of kernel messages like "0xff170000 timeout ..."
&i2c5 { status = "disabled"; };as a result of the previous editing, change the value of the property of ddc-i2c-bus to i2c4
&hdmi { ddc-i2c-bus = <&i2c4>; #sound-dai-cells = <0>; status = "okay"; };maybe you forgot, add, please, the element 'dr_mode = "host";' in the node '&usb_otg', so that OTG will work as a usb-host
&usb_otg { dr_mode = "host"; vusb_d-supply = <&vcc_otg_5v>; vusb_a-supply = <&vcc_otg_5v>; status = "okay"; };it's worth adding clocks to i2s
&i2s { #sound-dai-cells = <0>; clock-names = "i2s_hclk", "i2s_clk", "i2s_clk_out"; clocks = <&cru HCLK_I2S0>, <&cru SCLK_I2S0>, <&cru SCLK_I2S0_OUT>; status = "okay"; };It is better to add parts for RK1000, it is also desirable to add to the kernel drivers for it (CONFIG_MFD_RK1000, CONFIG_DRM_RK1000, CONFIG_SND_SOC_RK1000)
&i2c4 { status = "okay"; rk1000_ctl: rk1000-ctl@40 { compatible = "rockchip,rk1000-ctl"; reg = <0x40>; reset-gpios = <&gpio7 21 GPIO_ACTIVE_LOW>; clocks = <&cru SCLK_I2S0_OUT>; clock-names = "mclk"; status = "okay"; }; rk1000-tve@42 { status = "okay"; compatible = "rockchip,rk1000-tve"; reg = <0x42>; rockchip,data-width = <24>; rockchip,output = "rgb"; rockchip,ctl = <&rk1000_ctl>; #address-cells = <1>; #size-cells = <0>; }; rk1000_codec: rk1000-codec@60 { compatible = "rockchip,rk1000-codec"; reg = <0x60>; #sound-dai-cells = <0>; rockchip,spk-en-gpios = <&gpio7 5 GPIO_ACTIVE_LOW>; rockchip,pa-en-time-ms = <5000>; rockchip,ctl = <&rk1000_ctl>; status = "okay"; }; };replace, please, ir-keys table
ir_key1 { rockchip,usercode = <0x1dcc>; rockchip,key_table = <0xff KEY_POWER>, <0xea KEY_PLAYPAUSE>, <0xe9 KEY_STOP>, <0xf9 KEY_PREVIOUSSONG>, <0xf5 KEY_NEXTSONG>, <0xbe KEY_1>, <0xba KEY_2>, <0xb2 KEY_3>, <0xbd KEY_4>, <0xb9 KEY_5>, <0xb1 KEY_6>, <0xbc KEY_7>, <0xb8 KEY_8>, <0xb0 KEY_9>, <0xb6 KEY_0>, <0xb5 KEY_BACKSPACE>, <0xb7 KEY_F6>, <0xfc KEY_HOME>, <0xf0 KEY_BACK>, <0xbf KEY_MENU>, <0xb3 KEY_TEXT>, <0xef KEY_LEFT>, <0xed KEY_RIGHT>, <0xbb KEY_DOWN>, <0xf8 KEY_UP>, <0xee KEY_ENTER>, <0xfd KEY_VOLUMEDOWN>, <0xf3 KEY_MUTE>, <0xf1 KEY_VOLUMEUP>, <0xfe KEY_F1>, <0xfa KEY_F2>, <0xf6 KEY_F3>, <0xf2 KEY_F4>; };It is also desirable to rename the soundcard in node 'soundcard-hdmi'
simple-audio-card,name = "DW-I2S-HDMI";I updated the firmware for Debian for SD-card. I made it possible to run MPV with hardware decoding h264, h265, according to the message of JMCC. Here is used DHD wi-fi driver. In my opinion, it works at a higher speed than brcmfmac. And with the reboot there seems to be all right.
Update:
I also noticed that when the OTG cable is connected to the computer, Armbian Ubuntu begun rebooted after selecting the reboot command from the menu.
-
jock, thanks for the excellent work!
It is necessary to make efforts for official support in armbian!
-
On 16.04.2018 at 9:28 PM, jock said:
Sorry, that was my mistake. So I was too zealant in changing some regulators in order to support suspend features and so on and disabled the lcd power regulator
Overwrite /boot/dtb/rk3288-q8.dtb with the rk3288-q8.dtb attached to this message and HDMI should finally work. I also provide the device tree source for reference, but copying the binary will suffice.
HDMI joined. But at me Samsung for some reason does not support HDMI parameters which are exposed by a kernel. The inscription "This resolution is not supported" appears. With sound there is a problem: background sound is heard, but bad with speech. Use the RK1000 codec for sound. Drivers can be easily transferred from the Rockchip repository.
-
jock,
Thanks for the provided firmware and instruction. I tried the firmware on your link. I have a problem: there is no display for hdmi. As a monitor I use Samsung TV. Why is it better to work with the kernel from Rockchip: there is an available VPU driver in it, unlike the newest kernels. DTS I use on the basis of a firefly. It requires minimal changes and gives a good result. Try also u-boot from Rockchip with dts from the firefly. There usb is work, mmc do not need to disable - everything is displayed correctly.
-
9 hours ago, jock said:
Great job!
I'm working from the mainline side: kernel 4.16 and latest u-boot (2018-3) are working fine.
I'm still facing a problem against the bootstrap and reboot (looking into the act8846 power regulator datasheet, see this), but most of the hardware is working very well, including gpu-accelerated chromium, wifi, bluetooth. I'm still missing the IR remote control.
Excellent. Can you give a link to your firmware?
How did u-boot 2018.3 run?
-
On 29.03.2018 at 11:19 PM, jock said:
I have some progress here and found some interesting things about.
My TV-Box has LPDDR2 which is not officially supported by u-boot. U-boot supports only DDR3 and LPDDR3 rk3288 boards.
There is a workaround although: I have to use the DDR SPL (Secondary Program Loader) binary supplied by Rockchip which does the RAM initialization. You can see the Rockchip binary at work looking to the log I posted above: the very first lines with the timings are the memory timings autodetected by the SPL.
My tv-box comes with a binary which initializes the memory @200 MHz, but I found another binary which initializes the memory @400 MHz. I tried that to speedup the boot process. It worked and, surprise!, also I got more u-boot messages on the serial line showing a primordial bootstrap, but then the box suddenly turns off.
Another discovery is that if I push and *keep pushing* the box power button, the boot procedure actually goes on for much longer and I get more messages, till the marvellous "Starting kernel"!
Then the box powers off due to emergency shutdown happening when you keep the power button pushed too long. This is what I get (no detailed debug messages here):
DDR Version 1.03 20170411 In Channel a: LPDDR2 400MHz MR0=0x8 MR1=0x887744BB MR2=0x8 MR3=0x8 MR4=0x8 MR5=0x1 MR6=0x1 MR7=0x1 MR8=0x0 MR9=0x18 MR10=0x18 MR11=0x18 MR12=0x18 MR13=0x18 MR14=0x18 MR15=0x18 MR16=0x18 Bus Width=32 Col=10 Bank=8 Row=14/14 CS=2 Die Bus-Width=32 Size=1024MB Channel b: LPDDR2 400MHz MR0=0x8 MR1=0x887744BB MR2=0x8 MR3=0x8 MR4=0x8 MR5=0x2 MR6=0x1 MR7=0x1 MR8=0x0 MR9=0x18 MR10=0x18 MR11=0x18 MR12=0x18 MR13=0x18 MR14=0x18 MR15=0x18 MR16=0x18 Bus Width=32 Col=10 Bank=8 Row=14/14 CS=2 Die Bus-Width=32 Size=1024MB Memory OK Memory OK OUT U-Boot 2017.09-g5ecf0ee-dirty (Mar 29 2018 - 21:56:56 +0200) Model: Q8-RK3288 DRAM: 2 GiB MMC: dwmmc@ff0c0000: 1 MMC Device 0 not found *** Warning - No MMC card found, using default environment In: serial Out: serial Err: serial Model: Q8-RK3288 Net: No ethernet found. starting USB... No controllers found Hit any key to stop autoboot: 0 MMC Device 0 not found no mmc device at slot 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 1485 bytes read in 21 ms (68.4 KiB/s) ## Executing script at 00000000 U-boot loaded from eMMC 106 bytes read in 17 ms (5.9 KiB/s) 54282 bytes read in 58 ms (913.1 KiB/s) 4344436 bytes read in 220 ms (18.8 MiB/s) 8063544 bytes read in 385 ms (20 MiB/s) ## Loading init Ramdisk from Legacy Image at 21000000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4344372 Bytes = 4.1 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to 0fbdb000, end 0ffffa34 ... OK Loading Device Tree to 0fbca000, end 0fbda409 ... OK Starting kernel ...The problem is that probably there is some sort of timer or watchdog which turns the box after a specific timeout, and that timer is not counting while I keep pushing the power button. I may guess that it can be a GPIO that should be turned off or on, but I really don't know which one could be. I gladly accept any experience or hint about this behaviour
Connect the OTG cable from the box to the computer. This will help solve the problem.
P.S. Thanks for the hint with the new Rockchip SPL.
-
Hello,
Look, here you can download firmware for Q8.
Debian 9 for the SD card and MMC with rockchip kernel 4.4.114. Features:
- Installed Mali r14p0 drivers,- Installed the release of the Rockchip MPP library from 171225,
- Use the LXDE desktop,
- Installed Kodi 17.3,
- The Onboard virtual keyboard is installed.
Benefits:- Smooth playback of video 4K H264 and H265 (HEVC) using Qt Simple Player,
- Hardware support Chromium Browser,
- The presence of sound and WI-FI,
- Operation of the IR remote control.P.S. There is also the prospect of adding an Q8 to a supported board for Armbian.
-
26 minutes ago, pro777 said:
I fulfilled 4 tutorial item. Unfortunately, there was a startup error glmark2-es2:
user@armbian:~$ glmark2-es2
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x750 r0p0 status range [1..1], but none of the GPUs matched:
Error: eglInitialize() failed with error: 0x3001
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x750 r0p0 status range [1..1], but none of the GPUs matched:
Error: eglInitialize() failed with error: 0x3001
Error: main: Could not initialize canvasWow, I run the command:
sudo chmod 666 /dev/mali0.
Everything worked!
However, after reboot, the device's rights are returned. How is it better to solve the problem? -
On 17.02.2018 at 2:25 AM, JMCC said:
With the new default kernel based on rockchip-linux, boards with RK3288 SoC have now full kernel support for interacting with the GPU and hardware video decoder. Rockchip-linux also provides libraries and userspace software to make everything work.
I fulfilled 4 tutorial item. Unfortunately, there was a startup error glmark2-es2:
Spoileruser@armbian:~$ glmark2-es2
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x750 r0p0 status range [1..1], but none of the GPUs matched:
Error: eglInitialize() failed with error: 0x3001
ERROR: The DDK is not compatible with any of the Mali GPUs on the system.
The DDK was built for 0x750 r0p0 status range [1..1], but none of the GPUs matched:
Error: eglInitialize() failed with error: 0x3001
Error: main: Could not initialize canvasLibmali packages are installed:
Spoileruser@armbian:~$ aptitude search libmali
i libmali-rk-dev - The mali library for Rockchip RK3288.
i libmali-rk-midgard-t76x-r14p0-r0p0 - The mali library for Rockchip RK3288(not included RK3288W)user@armbian:~$ aptitude show libmali-rk-midgard-t76x-r14p0-r0p0
Package: libmali-rk-midgard-t76x-r14p0-r0p0
State: installed
Automatically installed: no
Multi-Arch: same
Version: 1.6-1
Priority: optional
Section: libs
Maintainer: Randy Li <randy.li@rock-chips.com>
Architecture: armhf
Uncompressed Size: 17.6 M
Depends: libc6 (>= 2.15), libdrm2 (>= 2.3.1), libgcc1 (>= 1:3.5), libstdc++6 (>= 4.8), libx11-6, libx11-xcb1,
libxcb-dri2-0 (>= 1.8), libxcb1
Replaces: libegl1-mesa, libegl1-x11, libgbm1, libgles2-mesa
Provides: libegl1, libegl1-mesa, libgbm1, libgles2-mesa, libwayland-egl1-mesa
Description: The mali library for Rockchip RK3288(not included RK3288W).
user@armbian:~$ dmesg | grep mali
[ 2.150304] mali ffa30000.gpu: Failed to get regulator
[ 2.156148] mali ffa30000.gpu: Power control initialization failed
[ 3.750212] W : [File] : drivers/gpu/arm/midgard/platform/rk/mali_kbase_config_rk.c; [Line] : 113; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available.
[ 3.750410] mali ffa30000.gpu: GPU identified as 0x0750 r0p0 status 1
[ 3.750833] I : [File] : drivers/gpu/arm/midgard/backend/gpu/mali_kbase_devfreq.c; [Line] : 284; [Func] : kbase_devfreq_init(); success initing power_model_simple.
[ 3.751071] mali ffa30000.gpu: Probed as mali0
[ 4.574880] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 415; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '-7b43537', rk_ko_ver is '5', built at '21:01:40', on 'Feb 1 2018'.What can be wrong?
-
On 16.09.2017 at 7:22 PM, balbes150 said:
Update test image kernel 4.13.0-next_20170915
What's new in this firmware?
-
I have KM8P S912. I succeeded to install the LibreEleс 8.2 from kszaq on the SD card. Here the Mali fbdev driver is used by means of the libhybris! I wonder if it's possible to add a Mali driver to the balbes150 firmware similarly?
-
Can you please tell me how to install the firmware on EMMC? Is there any way to install the GPU Mali drivers? Are there any advantages of the 4.13 kernel compared to the 3.14 kernel?
-
balbes150,
thank you very much for your excellent work!
I have a KM8P S912 - on firmware at the 20170908 with the kernel 4.13 works USB-mouse and the keyboard, there is a sound at the resolution of the screen 1920х1080.
As I understand it, there a problem when installing this firmware on EMMC?
CSC Armbian for RK3288 TV Box boards (Q8)
in Rockchip CPU Boxes
Posted
Yes, of course, I do not mind
When I start the firmware with a mainline kernel, the monitor shows: "The mode is not supported"
I need to then compile the kernel with the key CONFIG_DRM_LOAD_EDID_FIRMWARE.