Unconfigured Ad Widget

Collapse

Announcement

Collapse
No announcement yet.

Yundoo Y8 - ubuntu

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Yundoo Y8 - ubuntu

    Hello,

    Maybe someone can help here. I have installed the Firefly last ubuntu build (Firefly-RK3399-ubuntu16.04-20180416112819.tgz found in the firefly website) and it "almost" work for the Yundoo Y8.

    After flashing this image, the Y8 shows the blue light and after a few seconds, the ethernet becomes active (I can see the ethernet lights flashing, so the driver seems to be initialized)

    But HDMI is down, I can not see the console. At UART serial console, I see this: https://pastebin.com/K8b8yEE0

    From this log, it seems to work everything except the HDMI.

    This is the output related to HDMI initialization:

    Code:
    [    1.413003] i2c i2c-9: of_i2c: modalias failure on /[email protected]/ports
    [    1.413605] dwhdmi-rockchip ff940000.hdmi: registered DesignWare HDMI I2C bus driver
    [    1.414348] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
    [    1.415807] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffff8008cec920)
    [    1.765870] dwhdmi-rockchip ff940000.hdmi: PHY PLL failed to lock
    [    2.147015] rockchip-pinctrl pinctrl: pin gpio4-17 already requested by ff940000.hdmi; cannot claim for ff130000.i2c
    As I was believing that the dtb file at resource partition is a static device specific file, I extracted the resource image from the YundooY8 7.1 android image. I extracted its files to verify that has same filenames as in the Firefly resource image, and yes, both have 2 files: rk-kernel.dtb and logo.bmp. Also, both resource images have same size, so I flashed the Y8 resource image as it is to the resource partition.

    After the flashing I get no blue light anymore nor any UART log. So I reflash the Firefly resource image (previously backuped) and boot again the device. It goes to blue light and no HDMI as before, as expected. Looks like the rk-kernel.dtb from Y8 (android 7.1) is not good for ubuntu 16.04.


    I was thinking as next step to connect via ssh and solve the HDMI problem there if possible.

    Does anybody know how to fix the HDMI issue?

    #2
    Originally posted by isaauco View Post
    Hello,

    Maybe someone can help here. I have installed the Firefly last ubuntu build (Firefly-RK3399-ubuntu16.04-20180416112819.tgz found in the firefly website) and it "almost" work for the Yundoo Y8.

    After flashing this image, the Y8 shows the blue light and after a few seconds, the ethernet becomes active (I can see the ethernet lights flashing, so the driver seems to be initialized)

    But HDMI is down, I can not see the console. At UART serial console, I see this: https://pastebin.com/K8b8yEE0

    From this log, it seems to work everything except the HDMI.

    This is the output related to HDMI initialization:

    Code:
    [ 1.413003] i2c i2c-9: of_i2c: modalias failure on /[email protected]/ports
    [ 1.413605] dwhdmi-rockchip ff940000.hdmi: registered DesignWare HDMI I2C bus driver
    [ 1.414348] dwhdmi-rockchip ff940000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
    [ 1.415807] rockchip-drm display-subsystem: bound ff940000.hdmi (ops 0xffffff8008cec920)
    [ 1.765870] dwhdmi-rockchip ff940000.hdmi: PHY PLL failed to lock
    [ 2.147015] rockchip-pinctrl pinctrl: pin gpio4-17 already requested by ff940000.hdmi; cannot claim for ff130000.i2c
    As I was believing that the dtb file at resource partition is a static device specific file, I extracted the resource image from the YundooY8 7.1 android image. I extracted its files to verify that has same filenames as in the Firefly resource image, and yes, both have 2 files: rk-kernel.dtb and logo.bmp. Also, both resource images have same size, so I flashed the Y8 resource image as it is to the resource partition.

    After the flashing I get no blue light anymore nor any UART log. So I reflash the Firefly resource image (previously backuped) and boot again the device. It goes to blue light and no HDMI as before, as expected. Looks like the rk-kernel.dtb from Y8 (android 7.1) is not good for ubuntu 16.04.


    I was thinking as next step to connect via ssh and solve the HDMI problem there if possible.

    Does anybody know how to fix the HDMI issue?
    You can't use an Android dtb for Linux, they are completely different, only basic things are the same.
    Firefly also has different HDMI and other video output.
    Seems your device also uses different power drivers and pins that need to change in the dts.

    Comment


      #3
      I see, seems that this is not an easy task. :-)

      Thank you for taking a look!

      Comment

      Working...
      X