OpenEmbedded/Yocto for UDOO Boards

Discussion in 'Yocto' started by graugans, Nov 7, 2015.

  1. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    you have to go to meta-qt5 directory
     
  2. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    I'll build one tomorrow
     
  3. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Last edited: Apr 2, 2016
    Ayeed Shaikh and modjo like this.
  4. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
    will it run on udoo neo? does it have support for qt5 application development?
     
  5. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    No, it is for Quad and Dual and is a GUI image some other guy asked for. I have finished the qt5 build but there are issues with CAN what I want to fix before uploading

    Gesendet von meinem FP2 mit Tapatalk
     
  6. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Last edited: Apr 3, 2016
    Ayeed Shaikh and modjo like this.
  7. modjo

    modjo Active Member

    Joined:
    Sep 29, 2014
    Messages:
    417
    Likes Received:
    127
    @graugans , in your qt5.6 image did you add qtserialbus ?
     
  8. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Not, yet. Could you be so kind and send me the recipe?

    Gesendet von meinem FP2 mit Tapatalk
     
  9. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
  10. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
    How to change the default hdmi to lvds7 i tried uEnv video_output =lvds7 but still its booting with hdmi
     
  11. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    This, should work. How did you edit the file? Looks like u-boot is a bit picky when it comes to line endings.

    Gesendet von meinem FP2 mit Tapatalk
     
  12. modjo

    modjo Active Member

    Joined:
    Sep 29, 2014
    Messages:
    417
    Likes Received:
    127
    No problem, see here for qtserialbus and qtquickcontrols2
     
    graugans likes this.
  13. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
    # Environment script for the UDOO Neo board
    # save this file with unix-like newlines! (\n, 0x0A)

    #save this file with unix-like newlines! (\n, 0x0A)

    video_output=lvds7
    m4_enabled=true
    # Select weather to use custom device tree or not
    # Put the custom device tree file in the folder "dts-overlay" in your boot partition
    # use_custom_dtb=true|false
    # any other value (or if the variable is not specified) will default to "false"
    #use_custom_dtb=true
     
  14. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Sorry for being imprecise, how did you modify the file. What Operating system and what Editor?

    Gesendet von meinem FP2 mit Tapatalk
     
  15. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
    I used gedit using ubuntu 14.0
     
    graugans likes this.
  16. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Thx, I will test this this afternoon. Ubuntu is fine Windows maybe problematic.
     
  17. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1

    # Environment script for the UDOO Neo board
    # save this file with unix-like newlines! (\n, 0x0A)

    # Enable or Disable the Cortex M4 CPU
    # m4_enabled=true|false
    # any other value (or if the variable is not specified) will default to "true"
    #m4_enabled=false

    # Set the screen connected to the board
    # video_output=hdmi|lvds7|lvds15|disabled
    # any other value (or if the variable is not specified) will default to "hdmi"
    #video_output=hdmi

    # Select weather to use custom device tree or not
    # Put the custom device tree file in the folder "dts-overlay" in your boot partition
    # use_custom_dtb=true|false
    # any other value (or if the variable is not specified) will default to "false"
    #use_custom_dtb=true

    This was your uEnv.txt i changed video_output=lvds7.
     
  18. Ayeed Shaikh

    Ayeed Shaikh Member

    Joined:
    Mar 9, 2016
    Messages:
    52
    Likes Received:
    1
    Ok no issues and thanks for providing me the image. I actually want it to boot with lvds7 and not with hdmi.
     
  19. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141
    Can you verify what device tree is loaded by hooking up a USB <-> UART 3.3V TTL adapter. I described it here

    When I set the
    Code:
    video_output=lvds
    The u-boot output looks like this:


    Code:
    reading uEnv.txt
    702 bytes read in 12 ms (56.6 KiB/s)
    Running bootscript from mmc ...
    Device Tree: imx6sx-udoo-neo-full-lvds7-m4.dtb
    ** File not found /var/opt/m4/m4last.fw **
    reading /m4startup.fw
    108208 bytes read in 23 ms (4.5 MiB/s)
    ## Starting auxiliary core at 0x84000000 ...
    reading /zImage
    4131152 bytes read in 206 ms (19.1 MiB/s)
    Booting from mmc ...
    reading imx6sx-udoo-neo-full-lvds7-m4.dtb
    45748 bytes read in 42 ms (1 MiB/s)
    Kernel image @ 0x80800000 [ 0x000000 - 0x3f0950 ]
    ## Flattened Device Tree blob at 83000000
       Booting using the fdt blob at 0x83000000
       Using Device Tree in place at 83000000, end 8300e2b3
    Switched to ldo_bypass mode!
    
    Starting kernel ...
    
    [    0.000000] Booting Linux on physical CPU 0x0
    [    0.000000] Linux version 3.14.56_1.0.x-udoo+gabdce68 (chris@quadros) (gcc version 5.3.0 (GCC) ) #1 SMP PREEMPT Sun Apr 3 20:41:51 CEST 2016
    [    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
    [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [    0.000000] Machine model: UDOO Neo Full
    [    0.000000] Reserved memory: reserved region for node 'm4@0x84000000': base 0x84000000, size 8 MiB
    [    0.000000] Reserved memory: reserved region for node 'm4@0xBFF00000': base 0xbff00000, size 1 MiB
    [    0.000000] cma: CMA: reserved 320 MiB at aa000000
    [    0.000000] Memory policy: Data cache writealloc
    [    0.000000] PERCPU: Embedded 8 pages/cpu @bf639000 s8256 r8192 d16320 u32768
    [    0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p2 rootwait rw ${mmcrootfstype} uart_from_osc clk_ignore_unused cpuidle.off=1 consoleblank=0
    
    The following line indicates the LVDS 7" Display is used:

    Device Tree: imx6sx-udoo-neo-full-lvds7-m4.dtb

    I can not test the LVDS 7" Display because I do not own one by myself. But @modjo may can help. And there is some guidance on the UDOO docs
     
  20. graugans

    graugans Administrator Staff Member

    Joined:
    Sep 17, 2015
    Messages:
    328
    Likes Received:
    141

Share This Page