element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
RIoTboard
  • Products
  • Dev Tools
  • Single-Board Computers
  • RIoTboard
  • More
  • Cancel
RIoTboard
Forum Screen Resolution with preinstalled Android
  • Blog
  • Forum
  • Documents
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join RIoTboard to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Verified Answer
  • Replies 16 replies
  • Subscribers 24 subscribers
  • Views 2169 views
  • Users 0 members are here
Related

Screen Resolution with preinstalled Android

Former Member
Former Member over 11 years ago

I connected riotboard via HDMI to different monitors with different physical resolutions and android started every time with an resolution of 640x480. How can I change this? Thanks for help.

  • Sign in to reply
  • Cancel
  • vandana
    0 vandana over 11 years ago

    You should be able to change the resolution in u-boot mode passing the following arguments:

     

      MX6Solo RIOT U-Boot > setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32

    video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

     

    MX6Solo RIOT U-Boot > saveenv

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to vandana

    Great, now I'm worse off than before!  What were the settings before I tried the above? With the above settings neither of the  three small (less than 40") HD TVs I have at my disposal will resolve the settings and my HDMI equipped HP computer monitor isn't happy with them either. My monitor suggests 1920x1280 at 60Hz.  I don't think the Riot board will go that high.   I tried editing the settings "shotgun" style to see what works with my gear. The best I could come up with is a 24 Hz setting, but it was real laggy. Could you give me the line that will restore it to what I had?  Or even better give me more possible HD resolution settings to try. What settings are used in the video for the 2 part Android Programming tutorial?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    Here's the original settings:

    image

     

    Which appear to be the same as written above, so not sure why that would make things worse.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    What's the command line that generated the above output?  I'll try mine and see if these are my settings.  Prior to me loading the "correct" settings, my Riot Board was booting into the 640x480 mode the same as kas671 was talking about.  I loaded the settings that vandana suggested and none of my monitors would resolve it. I think I eventually got a resolution that would show by by changing @60 to either 24 or 30 ( I can't remember which).  It still didn't display a full HD desktop, and the screen flashes.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    Connect to the terminal via J18, hit a key to stop the boot process, and at the U-boot prompt type "print". It's about in the middle of all the stuff that will scroll past.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    My print out is identical. Is there a chance we were sent different Android revs?  My info is:

     

    3.0.35-06429-g55e239f

    android@embest-tech#3

    Fri Dec 20 10:31:44 CST 2013

     

    I also notices in the videos, their lock screen wallpaper (besides being 1280x720 res) is a different image.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    Here is my DeBug cosole output on boot.  Can anyone look at this and see why I can't get hdmi resolution?

     

    Hit any key to stop autoboot:  3  2  1  0

     

    kernel   @ 10808000 (4738952)

    ramdisk  @ 11800000 (233818)

    kernel cmdline:

    use uboot command line:

     

     

    console=ttymxc1,115200 init=/init nosmp

    video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32 video=mxcfb1:off

    fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

     

     

    Starting kernel ...

     

    Initializing cgroup subsys cpu

    Linux version 3.0.35-06429-g55e239f (android@embest-tech) (gcc

    version 4.6.x-google 20120106 (prerelease) (GCC) ) #3 SMP

    PREEMPT Fri Dec 20 10:31:44 CST 2013

    CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction

    cache

    Machine: Freescale i.MX 6Solo RIOT Board

    Ignoring unrecognised tag 0x54410008

    Memory policy: ECC disabled, Data cache writealloc

    CPU identified as i.MX6DL/SOLO, silicon rev 1.1

    PERCPU: Embedded 7 pages/cpu @c1307000 s6592 r8192 d13888 u32768

    Built 1 zonelists in Zone order, mobility grouping on.

    Total pages: 208128

    Kernel command line: console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32

    video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

    PID hash table entries: 2048 (order: 1, 8192 bytes)

    Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)

    Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)

    Memory: 767MB 54MB = 821MB total

    Memory: 820560k/820560k available, 228016k reserved, 431104K highmem

    Virtual kernel memory layout:

        vector  : 0xffff0000 - 0xffff1000   (   4 kB)

        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

        DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)

        vmalloc : 0xd9800000 - 0xf2000000   ( 392 MB)

        lowmem  : 0xc0000000 - 0xd9000000   ( 400 MB)

        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)

        modules : 0xbf000000 - 0xbfe00000   (  14 MB)

          .init : 0xc0008000 - 0xc0046000   ( 248 kB)

          .text : 0xc0046000 - 0xc08d3f94   (8760 kB)

          .data : 0xc08d4000 - 0xc0975de0   ( 648 kB)

           .bss : 0xc0975e04 - 0xc0afdb48   (1568 kB)

    Preemptible hierarchical RCU implementation.

    NR_IRQS:624

    MXC GPIO hardware

    sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms

    Set periph_clk's parent to pll2_pfd_400M!

    arm_max_freq=1GHz

    MXC_Early serial console at MMIO 0x21e8000 (options '115200')

    bootconsole [ttymxc1] enabled

    Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)

    pid_max: default: 32768 minimum: 301

    Mount-cache hash table entries: 512

    Initializing cgroup subsys debug

    Initializing cgroup subsys cpuacct

    Initializing cgroup subsys freezer

    CPU: Testing write buffer coherency: ok

    hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

    Brought up 1 CPUs

    SMP: Total of 1 processors activated (1581.05 BogoMIPS).

    print_constraints: dummy:

    NET: Registered protocol family 16

    print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal

    print_constraints: vddcore: 725 <--> 1300 mV at 1150 mV fast normal

    print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal

    print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal

    print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal

    print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal

    ram_console: got buffer at 3ff00000, size 100000

    ram_console: found existing buffer, size 17318, start 17318

    console [ram-1] enabled

    ----ldb_init

    hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.

    hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.

    hw-breakpoint: maximum watchpoint size is 4 bytes.

    L310 cache controller enabled

    l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32050000, Cache size: 524288 B

    bio: create slab <bio-0> at 0

    mxs-dma mxs-dma-apbh: initialized

    print_constraints: VDDA: 2500 mV

    print_constraints: VDDIO: 3300 mV

    machine_constraints_voltage: VDDD: unsupportable voltage constraints

    reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22

    reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22

    print_constraints: vmmc: 3300 mV

    vgaarb: loaded

    SCSI subsystem initialized

    spi_imx imx6q-ecspi.0: probed

    usbcore: registered new interface driver usbfs

    usbcore: registered new interface driver hub

    usbcore: registered new device driver usb

    Freescale USB OTG Driver loaded, $Revision: 1.55 $

    mc_pfuze 1-0008: recv failed!:-5,0

    mc_pfuze: probe of 1-0008 failed with error -1

    imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed

    mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a

    MIPI CSI2 driver module loaded

    Advanced Linux Sound Architecture Driver Version 1.0.24.

    Bluetooth: Core ver 2.16

    NET: Registered protocol family 31

    Bluetooth: HCI device and connection manager initialized

    Bluetooth: HCI socket layer initialized

    Bluetooth: L2CAP socket layer initialized

    Bluetooth: SCO socket layer initialized

    i2c-core: driver [max17135] using legacy suspend method

    i2c-core: driver [max17135] using legacy resume method

    Switching to clocksource mxc_timer1

    NET: Registered protocol family 2

    IP route cache hash table entries: 16384 (order: 4, 65536 bytes)

    TCP established hash table entries: 65536 (order: 7, 524288 bytes)

    TCP bind hash table entries: 65536 (order: 7, 786432 bytes)

    TCP: Hash tables configured (established 65536 bind 65536)

    TCP reno registered

    UDP hash table entries: 256 (order: 1, 8192 bytes)

    UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)

    NET: Registered protocol family 1

    RPC: Registered named UNIX socket transport module.

    RPC: Registered udp transport module.

    RPC: Registered tcp transport module.

    RPC: Registered tcp NFSv4.1 backchannel transport module.

    PCI: CLS 0 bytes, default 32

    Unpacking initramfs...

    Freeing initrd memory: 228K

    PMU: registered new PMU device of type 0

    Static Power Management for Freescale i.MX6

    wait mode is enabled for i.MX6

    cpaddr = d9820000 suspend_iram_base=d98b8000

    PM driver module loaded

    IMX usb wakeup probe

    the wakeup pdata is 0xd63fbb20

    add wake up source irq 75

    IMX usb wakeup probe

    the wakeup pdata is 0xd63fb8e0

    cpu regulator mode:ldo_enable

    i.MXC CPU frequency driver

    highmem bounce pool size: 64 pages

    ashmem: initialized

    NTFS driver 2.1.30 [Flags: R/O].

    JFFS2 version 2.2. (NAND) ÂCopyright 2001-2006 Red Hat, Inc.

    fuse init (API version 7.16)

    msgmni has been set to 761

    NET: Registered protocol family 38

    cryptodev: driver loaded.

    io scheduler noop registered

    io scheduler deadline registered

    io scheduler cfq registered (default)

    mxc_mipi_dsi mxc_mipi_dsi: i.MX MIPI DSI driver probed

    MIPI DSI driver module loaded

    mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver hdmi

    mxc_hdmi mxc_hdmi: Detected HDMI controller 0x13:0x1a:0xa0:0xc1

    fbcvt: 1280x720@60: CVT Name - .921M9

    imx-ipuv3 imx-ipuv3.0: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

    mxc_sdc_fb mxc_sdc_fb.1: Can't get fb option for mxcfb1!

    imx-sdma imx-sdma: loaded firmware 1.1

    imx-sdma imx-sdma: initialized

    fbcvt: 1280x720@60: CVT Name - .921M9

    Serial: IMX driver

    imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX

    imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX

    console [ttymxc1] enabled, bootconsole disabled

    console [ttymxc1] enabled, bootconsole disabled

    imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX

    loop: module loaded

    m25p80 spi0.0: unrecognized JEDEC id ffffff

    GPMI NAND driver registered. (IMX)

    vcan: Virtual CAN interface driver

    CAN device driver interface

    flexcan netdevice driver

    FEC Ethernet Driver

    fec_enet_mii_bus: probed

    PPP generic driver version 2.4.2

    PPP Deflate Compression module registered

    PPP BSD Compression module registered

    PPP MPPE Compression module registered

    NET: Registered protocol family 24

    PPTP driver version 0.8.5

    tun: Universal TUN/TAP device driver, 1.6

    tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

    fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

    fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1

    fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000

    fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

    hub 1-0:1.0: USB hub found

    hub 1-0:1.0: 1 port detected

    add wake up source irq 72

    fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller

    fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2

    fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200

    fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00

    hub 2-0:1.0: USB hub found

    hub 2-0:1.0: 1 port detected

    usbcore: registered new interface driver cdc_acm

    cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

    Initializing USB Mass Storage driver...

    usbcore: registered new interface driver usb-storage

    USB Mass Storage support registered.

    usbcore: registered new interface driver usbserial

    usbserial: USB Serial Driver core

    USB Serial support registered for GSM modem (1-port)

    usbcore: registered new interface driver option

    option: v0.7.2:USB Driver for GSM modems

    USB Serial support registered for Qualcomm USB modem

    usbcore: registered new interface driver qcserial

    ARC USBOTG Device Controller driver (1 August 2005)

    android_usb gadget: Mass Storage Function, version: 2009/09/11

    android_usb gadget: Number of LUNs=1

    lun0: LUN: removable file: (no medium)

    Gadget Android: controller 'fsl-usb2-udc' not recognized

    android_usb gadget: android_usb ready

    Suspend udc for OTG auto detect

    USB Host suspend begins

    will suspend roothub and its children

    ehci_fsl_bus_suspend begins, DR

    ehci_fsl_bus_suspend ends, DR

    host suspend ends

    USB Gadget resume begins

    fsl_udc_resume, Wait for wakeup thread finishes

    dr_controller_run: udc enter low power mode

    USB Gadget resume ends

    fsl-usb2-udc: bind to driver android_usb

    mousedev: PS/2 mouse device common for all mice

    generic touchscreen driver, <@>.

    usb 2-1: new high speed USB device number 2 using fsl-ehci

    hub 2-1:1.0: USB hub found

    hub 2-1:1.0: 4 ports detected

    usb 2-1.2: new low speed USB device number 3 using fsl-ehci

    USB Gadget resume begins

    fsl_udc_resume, Wait for wakeup thread finishes

    usb 2-1.4: new low speed USB device number 4 using fsl-ehci

    >>>>> ct365_get_vendor() called <<<<<

    Chip ID: 0x0

    Chip data allocation failed: 0x0

    i2c-core: driver [generic_ts] using legacy suspend method

    i2c-core: driver [generic_ts] using legacy resume method

    i2c-core: driver [isl29023] using legacy suspend method

    i2c-core: driver [isl29023] using legacy resume method

    using rtc device, snvs_rtc, for alarms

    snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0

    i2c /dev entries driver

    Linux video capture interface: v2.00

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16

    mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17

    usbcore: registered new interface driver uvcvideo

    USB Video Class driver (v1.1.0)

    i2c-core: driver [mag3110] using legacy suspend method

    i2c-core: driver [mag3110] using legacy resume method

    imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)

    device-mapper: uevent: version 1.0.3

    device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com

    Bluetooth: Virtual HCI driver ver 1.3

    Bluetooth: HCI UART driver ver 2.2

    Bluetooth: HCIATH3K protocol initialized

    Bluetooth: Generic Bluetooth USB driver ver 0.6

    usbcore: registered new interface driver btusb

    sdhci: Secure Digital Host Controller Interface driver

    sdhci: Copyright(c) Pierre Ossman

    mmc0: SDHCI controller on platform [sdhci-esdhc-imx.3] using ADMA

    mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA

    mmc2: SDHCI controller on platform [sdhci-esdhc-imx.1] using ADMA

    mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed

    VPU initialized

    mxc_asrc registered

    Galcore version 4.6.9.6622

    revserved_memory_account:viv_gpu registerd

    Thermal calibration data is 0x5955185f

    Thermal sensor with ratio = 185

    Anatop Thermal registered as thermal_zone0

    anatop_thermal_probe: default cooling device is cpufreq!

    Registered led device: sys_led

    Registered led device: user_led

    input: Dell Dell QuietKey Keyboard as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.2/2-1.2:1.0/input/input0

    generic-usb 0003:413C:2106.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell QuietKey Keyboard] on usb-fsl-ehci.1-1.2/input0

    mmc0: new high speed DDR MMC card at address 0001

    input: USB Optical Mouse as /devices/platform/fsl-ehci.1/usb2/2-1/2-1.4/2-1.4:1.0/input/input1

    generic-usb 0003:0461:4DFB.0002: input,hidraw1: USB HID v1.11 Mouse [USB Optical Mouse] on usb-fsl-ehci.1-1.4/input0

    mmcblk0: mmc0:0001 MMC04G 3.57 GiB

    mmcblk0boot0: mmc0:0001 MMC04G partition 1 2.00 MiB

    usbcore: registered new interface driver usbhid

    usbhid: USB HID core driver

    mmcblk0boot1: mmc0:0001 MMC04G partition 2 2.00 MiB

    logger: created 256K log 'log_main'

    logger: created 256K log 'log_events'

    logger: created 256K log 'log_radio'

    logger: created 256K log 'log_system'

    mmcblk0: p1 p2 p3 < p5 p6 p7 p8 > p4

    mmcblk0: p4 size 5324800 extends beyond EOD, truncated

    usbcore: registered new interface driver snd-usb-audio

    mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio

    Cirrus Logic CS42888 ALSA SoC Codec Driver

    i2c-core: driver [cs42888] using legacy suspend method

    i2c-core: driver [cs42888] using legacy resume method

    mmcblk0boot1: unknown partition table

    mmcblk0boot0: unknown partition table

    ----sab_sgtl5000_init

    ----enable clko_clk.

    sgtl5000 0-000a: Failed to get supply 'VDDD': -19

    print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal

    sgtl5000 0-000a: sgtl5000 revision 17

    asoc: sgtl5000 <-> imx-ssi.1 mapping ok

    imx_3stack asoc driver

    asoc: mxc-hdmi-soc <-> imx-hdmi-soc-dai.0 mapping ok

    ALSA device list:

      #0: sgtl5000-audio

      #1: imx-hdmi-soc

    oprofile: using arm/armv7-ca9

    GACT probability NOT on

    Mirror/redirect action on

    u32 classifier

        Actions configured

    Netfilter messages via NETLINK v0.30.

    nf_conntrack version 0.5.0 (12824 buckets, 51296 max)

    ctnetlink v0.93: registering with nfnetlink.

    NF_TPROXY: Transparent proxy support initialized, version 4.1.0

    NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.

    xt_time: kernel timezone is -0000

    IPv4 over IPv4 tunneling driver

    GRE over IPv4 demultiplexor driver

    ip_tables: (C) 2000-2006 Netfilter Core Team

    arp_tables: (C) 2002 David S. Miller

    TCP cubic registered

    NET: Registered protocol family 10

    Mobile IPv6

    ip6_tables: (C) 2000-2006 Netfilter Core Team

    IPv6 over IPv4 tunneling driver

    NET: Registered protocol family 17

    NET: Registered protocol family 15

    can: controller area network core (rev 20090105 abi 8)

    NET: Registered protocol family 29

    can: raw protocol (rev 20090105)

    can: broadcast manager protocol (rev 20090105 t)

    Bluetooth: RFCOMM TTY layer initialized

    Bluetooth: RFCOMM socket layer initialized

    Bluetooth: RFCOMM ver 1.11

    Bluetooth: BNEP (Ethernet Emulation) ver 1.3

    Bluetooth: BNEP filters: protocol multicast

    Bluetooth: HIDP (Human Interface Emulation) ver 1.2

    L2TP core driver, V2.0

    PPPoL2TP kernel driver, V2.0

    L2TP IP encapsulation support (L2TPv3)

    L2TP netlink interface

    L2TP ethernet pseudowire support (L2TPv3)

    lib80211: common routines for IEEE802.11 drivers

    lib80211_crypt: registered algorithm 'NULL'

    lib80211_crypt: registered algorithm 'WEP'

    lib80211_crypt: registered algorithm 'CCMP'

    lib80211_crypt: registered algorithm 'TKIP'

    VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

    Bus freq driver module loaded

    Bus freq driver Enabled

    mxc_dvfs_core_probe

    DVFS driver module loaded

    snvs_rtc snvs_rtc.0: setting system clock to 2014-02-22 15:54:40 UTC (1393084480)

    Freeing init memory: 248K

    android_usb: already disabled

    mtp_bind_config

    root@riot_6solo:/ # ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    ERROR: v4l2 capture: slave not found!

    warning: `zygote' uses 32-bit capabilities (legacy support in use)

    request_suspend_state: wakeup (3->0) at 14205317670 (2014-02-22 15:54:51.068988335 UTC)

    eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:04, irq=-1)

    ADDRCONF(NETDEV_UP): eth0: link is not ready

    acc_open

    acc_release

    ehci_fsl_bus_resume begins, DR

    init: sys_prop: permission denied uid:1003 

    name:service.bootanim.exit

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    My Lock Screen Wallpaper was also different. I get full 1080 though on Samsung monitor out of the box. Does anyone know how to use the HDMI and tell it to use the Audio Jack out for sound?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    After playing around with this some more, I haven't yet found a solution but I did find that it has something to do with the particular monitor it's being hooked up to.

     

    Using a HDMI->DVI connector affects the resolution, as it comes up at 640x480 when using that cable. But the same monitor when connected via a HDMI cable will show up at the correct (1280x720) resolution. In Linux I tried playing around with xrandr arguments to get the resolution up when connected over HDMI->DVI, but to no success so far (it complains about "screen cannot be larger than 640x480"). Googling i.mx6 and hdmi/dvi, this seems to be a common issue, and seems to be related to not getting the proper EDID info from the monitor when connected over the adapter.

     

    Meanwhile on my TV at home via HDMI, Android would not display on it, with the TV complaining about incompatible signals. However the same board would work when I booted Linux on it, and show up at the correct resolution (1280x720). I could also adjust the Linux resolution by changing the U-Boot arguments, but was not able to find a working Android solution. Meanwhile other TV's and monitors I connected with this same board worked correctly on both Android and Linux so it seemed to be a rare case.

     

    Out of the box I have the same green background as in the videos, but when connected via the HDMI->DVI cable it's in phone mode so it doesn't look quite the same since at full resolution it'll be in tablet mode.

     

    Mark: I noticed in the Linux sound settings there's a page to configure what the default sound output is which I would assume works. For Android, it seems the solution is to get a special cable or box that extracts the audio from the HDMI signal, but there's not a way to do it as far as I could Google inside Android itself.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago in reply to Former Member

    Out of the box I likewise had a HDMI  "Mode Not Supported" when I connected it to my Samsung TV.  I moved over to my LG TV and it worked no-problem.  I have since connected it to my Acer monitor via HDMI and again no problems.  I did some searching and it might just be a Samsung TV thing. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube