This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

ezsdk 5.02.01.59 - Matrix GUI failed to launch

Other Parts Discussed in Thread: PMP

Hi,

we've moved from ezsdk .80 to 5.02.01.59 for dm816x. Tried to use both pre-build binaries and rebuild sdk, but can't see Matrix GUI on the display.

I'm booting up from NFS:

Kernel command line: console=ttyO2,115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=192.168.10.59:/root/targetfs ip=dhcp

(when i'm back to targetfs and uImage built by ezsdk .80, everth. is fine)
Please, advise on how to fix/debug it.
here're some last lines of boot-up:
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Starting telnet daemon.
Loading HDVPSS Firmware
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
cat: write error: No space left on device
cat: write error: No space left on device
HDMI W1 rev 2.0
Starting syslogd/klogd: done
Starting thttpd.
Starting PVR
/dev/mem opened.
Memory mapped at address 0x40247000.
Read at address  0x48180F04 (0x40247f04): 0x00000001
Write at address 0x48180F04 (0x40247f04): 0x00000000, readback 0x00000000
/dev/mem opened.
Memory mapped at address 0x402aa000.
Read at address  0x48180900 (0x402aa900): 0x00000102
Write at address 0x48180900 (0x402aa900): 0x00000002, readback 0x00000002
/dev/mem opened.
Memory mapped at address 0x402a3000.
Read at address  0x48180920 (0x402a3920): 0x00040002
Write at address 0x48180920 (0x402a3920): 0x00000002, readback 0x00000002
Starting Matrix GUI application.
...
Arago Project http://arago-project.org dm816x-evm ttyO2
Arago 2011.05 dm816x-evm ttyO2
dm816x-evm login: root
root@dm816x-evm:~# lsmod
Module                  Size  Used by
bufferclass_ti          4946  0 
omaplfb                10794  0 
pvrsrvkm              155450  2 bufferclass_ti,omaplfb
ti81xxhdmi             12992  0 
ti81xxfb               20247  3 
vpss                   61787  3 omaplfb,ti81xxhdmi,ti81xxfb
syslink              1103655  0 
ipv6                  209879  12 
                                                                                        

  • Be sure to run the setup.sh to setup the correct u-boot environment variables.  Also check that you're using the filesystem as part of the SDK.  Also, could you try sd card boot to be sure there are no other setup related issues (i.e. nfs).

  • MarcPyne,

    the bootargs seems to be correct and there is no error messages as in suggested topic.

     

    Marcus,

    have done setup.sh and verified bootargs. I can launch MatrixGUI if i'm back to targetfs and uImage from previous ezsdk(80).

    Flashing uboot image u-boot.noxip.bin to nand from new ezsdk didn't solve the problem.

    could it be a graphics/display problem? Could you advise how to debug it?

     

    thanks.

  •  

    Could you provide the complete log?  I'm curious to know if what you're experiencing is related to

    http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/p/132039/474395.aspx#474395

     

  • Marcus,

    here the boot log:

     

    DHCP client bound to address 192.168.10.26

    Using DaVinci EMAC device

    TFTP from server 192.168.10.59; our IP address is 192.168.10.26

    Filename 'uImage-dm816x-evm.bin'.

    Load address: 0x81000000

    Loading: T #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             #################################################################

             ################

    done

    Bytes transferred = 2410936 (24c9b8 hex)

    ## Booting kernel from Legacy Image at 81000000 ...

       Image Name:   Arago/2.6.37-psp04.00.00.12/dm81

       Image Type:   ARM Linux Kernel Image (uncompressed)

       Data Size:    2410872 Bytes = 2.3 MiB

       Load Address: 80008000

       Entry Point:  80008000

       Verifying Checksum ... OK

       Loading Kernel Image ... OK

    OK

     

    Starting kernel ...

     

    Uncompressing Linux... done, booting the kernel.

    Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Mon Aug 29 21:39:54 IST 2011

    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

    Machine: ti8168evm

    bootconsole [earlycon0] enabled

    vram size = 52428800 at 0

    reserved size = 52428800 at 0

    FB: Reserving 52428800 bytes SDRAM for VRAM

    Memory policy: ECC disabled, Data cache writeback

    OMAP chip is TI8168 1.1

    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 52224

    Kernel command line: console=ttyO2,115200n8 rootwait root=/dev/nfs nfsroot=192.168.10.59:/root/targetfs,nolock rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vra

    m=50M ti816xfb.vram=0:16M,1:16M,2:6M ip=dhcp

    PID hash table entries: 1024 (order: 0, 4096 bytes)

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

    Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

    Memory: 206MB = 206MB total

    Memory: 203476k/203476k available, 58668k reserved, 0K highmem

    Virtual kernel memory layout:

        vector  : 0xffff0000 - 0xffff1000   (   4 kB)

        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)

        vmalloc : 0xd0800000 - 0xf8000000   ( 632 MB)

        lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)

        modules : 0xbf000000 - 0xc0000000   (  16 MB)

          .init : 0xc0008000 - 0xc0038000   ( 192 kB)

          .text : 0xc0038000 - 0xc0492000   (4456 kB)

          .data : 0xc0492000 - 0xc04d89c0   ( 283 kB)

    SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

    NR_IRQS:407

    IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts

    Total of 128 interrupts on 1 active controller

    GPMC revision 6.0

    Trying to install interrupt handler for IRQ400

    Trying to install interrupt handler for IRQ401

    Trying to install interrupt handler for IRQ402

    Trying to install interrupt handler for IRQ403

    Trying to install interrupt handler for IRQ404

    Trying to install interrupt handler for IRQ405

    Trying to install interrupt handler for IRQ406

    Trying to install type control for IRQ407

    Trying to set irq flags for IRQ407

    OMAP clockevent source: GPTIMER1 at 27000000 Hz

    Console: colour dummy device 80x30

    Calibrating delay loop... 986.31 BogoMIPS (lpj=4931584)

    pid_max: default: 32768 minimum: 301

    Security Framework initialized

    Mount-cache hash table entries: 512

    CPU: Testing write buffer coherency: ok

    devtmpfs: initialized

    omap_voltage_early_init: voltage driver support not added

    regulator: core version 0.5

    regulator: dummy: 

    NET: Registered protocol family 16

    OMAP GPIO hardware version 0.1

    OMAP GPIO hardware version 0.1

    omap_mux_init: Add partition: #1: core, flags: 0

    _omap_mux_get_by_name: Could not find signal i2c2_scl.i2c2_scl

    _omap_mux_get_by_name: Could not find signal i2c2_sda.i2c2_sda

    NOR: Can't request GPMC CS

    registered ti816x_vpss device

    registered ti816x_gpio_vr device

    registered TI816x on-chip HDMI device

    registered ti816x_sr device

    pm_dbg_init: only OMAP3 supported

    Registered ti81xx_fb device

    ti816x_pcie: Invoking PCI BIOS...

    ti816x_pcie: Setting up Host Controller...

    ti816x_pcie: Register base mapped @0xd0820000

    ti816x_pcie: Starting PCI scan...

    PCI: bus0: Fast back to back transfers enabled

    bio: create slab <bio-0> at 0

    regulator: VFB: 800 <--> 1025 mV at 1010 mV 

    vgaarb: loaded

    SCSI subsystem initialized

    usbcore: registered new interface driver usbfs

    usbcore: registered new interface driver hub

    usbcore: registered new device driver usb

    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz

    omap_i2c omap_i2c.2: bus 2 rev4.0 at 100 kHz

    Advanced Linux Sound Architecture Driver Version 1.0.23.

    Switching to clocksource gp timer

    musb-hdrc: version 6.0, host, debug=0

    musb-hdrc musb-hdrc.0: dma type: dma-cppi41

    registerd cppi-dma Intr @ IRQ 17

    Cppi41 Init Done

    musb-hdrc: kernel must blacklist external hubs

    musb-hdrc musb-hdrc.0: MUSB HDRC host driver

    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1

    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

    usb usb1: Product: MUSB HDRC host driver

    usb usb1: Manufacturer: Linux 2.6.37 musb-hcd

    usb usb1: SerialNumber: musb-hdrc.0

    hub 1-0:1.0: USB hub found

    hub 1-0:1.0: 1 port detected

    musb-hdrc musb-hdrc.0: USB Host mode controller at d080c000 using DMA, IRQ 18

    musb-hdrc musb-hdrc.1: dma type: dma-cppi41

    musb-hdrc: kernel must blacklist external hubs

    musb-hdrc musb-hdrc.1: MUSB HDRC host driver

    musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2

    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

    usb usb2: Product: MUSB HDRC host driver

    usb usb2: Manufacturer: Linux 2.6.37 musb-hcd

    usb usb2: SerialNumber: musb-hdrc.1

    hub 2-0:1.0: USB hub found

    hub 2-0:1.0: 1 port detected

    musb-hdrc musb-hdrc.1: USB Host mode controller at d081e800 using DMA, IRQ 19

    NET: Registered protocol family 2

    IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

    TCP established hash table entries: 8192 (order: 4, 65536 bytes)

    TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

    TCP: Hash tables configured (established 8192 bind 8192)

    TCP reno registered

    UDP hash table entries: 256 (order: 0, 4096 bytes)

    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

    NET: Registered protocol family 1

    RPC: Registered udp transport module.

    RPC: Registered tcp transport module.

    RPC: Registered tcp NFSv4.1 backchannel transport module.

    NetWinder Floating Point Emulator V0.97 (double precision)

    PMU: registered new PMU device of type 0

    omap-iommu omap-iommu.0: ducati registered

    omap-iommu omap-iommu.1: sys registered

    JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.

    msgmni has been set to 397

    io scheduler noop registered

    io scheduler deadline registered

    io scheduler cfq registered (default)

    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

    omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0

    omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1

    omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2

    console [ttyO2] enabled, bootconsole disabled

    console [ttyO2] enabled, bootconsole disabled

    brd: module loaded

    loop: module loaded

    ahci ahci.0: forcing PORTS_IMPL to 0x3

    ahci ahci.0: AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl platform mode

    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc 

    scsi0 : ahci_platform

    scsi1 : ahci_platform

    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16

    ata2: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x180 irq 16

    m25p80 spi1.0: found m25p05-nonjedec, expected w25x32

    m25p80 spi1.0: m25p05-nonjedec (64 Kbytes)

    Creating 4 MTD partitions on "spi_flash":

    0x000000000000-0x000000040000 : "U-Boot"

    mtd: partition "U-Boot" extends beyond the end of device "spi_flash" -- size truncated to 0x10000

    0x000000010000-0x000000012000 : "U-Boot Env"

    mtd: partition "U-Boot Env" is out of reach -- disabled

    0x000000000000-0x000000280000 : "Kernel"

    mtd: partition "Kernel" extends beyond the end of device "spi_flash" -- size truncated to 0x10000

    0x000000010000-0x000000010000 : "File System"

    mtd: partition "File System" is out of reach -- disabled

    omap2-nand driver initializing

    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )

    Creating 5 MTD partitions on "omap2-nand.0":

    0x000000000000-0x000000260000 : "U-Boot"

    0x000000260000-0x000000280000 : "U-Boot Env"

    0x000000280000-0x0000006c0000 : "Kernel"

    0x0000006c0000-0x00000cee0000 : "File System"

    0x00000cee0000-0x000010000000 : "Reserved"

    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6

    davinci_mdio davinci_mdio.0: detected phy mask fffffff9

    davinci_mdio.0: probed

    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown

    davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver unknown

    usbcore: registered new interface driver cdc_ether

    usbcore: registered new interface driver dm9601

    Initializing USB Mass Storage driver...

    usbcore: registered new interface driver usb-storage

    USB Mass Storage support registered.

    mice: PS/2 mouse device common for all mice

    i2c /dev entries driver

    Linux video capture interface: v2.00

    usbcore: registered new interface driver uvcvideo

    USB Video Class driver (v1.0.0)

    OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec

    usbcore: registered new interface driver usbhid

    usbhid: USB HID core driver

    notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbf900000

    usbcore: registered new interface driver snd-usb-audio

    asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok

    ALSA device list:

      #0: TI81XX EVM

    TCP cubic registered

    NET: Registered protocol family 17

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

    omap_voltage_late_init: Voltage driver support not added

    smartreflex smartreflex: Driver initialized

    ata1: SATA link down (SStatus 0 SControl 300)

    ata2: SATA link down (SStatus 0 SControl 300)

    mmc0: new high speed SDHC card at address e624

    mmcblk0: mmc0:e624 SD08G 7.40 GiB 

     mmcblk0: p1 p2 p3

    davinci_mdio davinci_mdio.0: resetting idled controller

    net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f014)

    net eth1: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:02, id=282f014)

    Sending DHCP requests ..

    PHY: 0:01 - Link is Up - 1000/Full

    .., OK

    IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.10.19

    IP-Config: Complete:

         device=eth0, addr=192.168.10.19, mask=255.255.255.0, gw=192.168.10.1,

         host=192.168.10.19, domain=, nis-domain=(none),

         bootserver=0.0.0.0, rootserver=192.168.10.59, rootpath=

    VFS: Mounted root (nfs filesystem) on device 0:14.

    devtmpfs: mounted

    Freeing init memory: 192K

    INIT: version 2.86 booting

    Error opening /dev/fb0: No such file or directory

    Please wait: booting...

    Starting udev

    udevd (80): /proc/80/oom_adj is deprecated, please use /proc/80/oom_score_adj instead.

    udev: starting version 141

    Root filesystem already rw, not remounting

    Caching udev devnodes

    Populating dev cachemv: cannot rename '/tmp/devices': No such file or directory

    FAT: bogus number of reserved sectors

    VFS: Can't find a valid FAT filesystem on dev mmcblk0.

    NET: Registered protocol family 10

    EXT3-fs (mmcblk0): error: can't find ext3 filesystem on dev mmcblk0.

    EXT2-fs (mmcblk0): error: can't find an ext2 filesystem on dev mmcblk0.

    FAT: bogus number of reserved sectors

    VFS: Can't find a valid FAT filesystem on dev mmcblk0.

    ISOFS: Unable to identify CD-ROM format.

    ALSA: Restoring mixer settings...

    NOT configuring network interfaces: / is an NFS mount

    No state is present for card EVM

    Found hardware: "" "" "" "" ""

    Hardware is initialized using a generic method

    hwclock: can't open '/dev/misc/rtc': No such file or directory

    No state is present for card EVM

    Tue Aug 30 00:37:00 UTC 2011

    hwclock: can't open '/dev/misc/rtc': No such file or directory

    INIT: Entering runlevel: 5

    EXT3-fs: barriers not enabled

    kjournald starting.  Commit interval 5 seconds

    EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

    EXT3-fs (mmcblk0p2): using internal journal

    EXT3-fs (mmcblk0p2): recovery complete

    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode

    EXT3-fs: barriers not enabled

    kjournald starting.  Commit interval 5 seconds

    EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended

    EXT3-fs (mmcblk0p3): using internal journal

    EXT3-fs (mmcblk0p3): recovery complete

    EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode

    Starting system message bus: dbus.

    Loading HDVICP2 Firmware

    DM816X prcm_config_app version: 2.0.0.1

    Doing PRCM settings...

            PRCM for IVHD0 is in Progress, Please wait.....  

                            BW Phy Addr : 0x48180600 Data : 0x00000002

                            AW Phy Addr : 0x48180600 Data : 0x00000002

                            Phy Addr : 0x48180c04 Data : 0x00000037

                            BW Phy Addr : 0x48180620 Data : 0x00070000

                            AW Phy Addr : 0x48180620 Data : 0x00070002

                            BW Phy Addr : 0x48180624 Data : 0x00030000

                            AW Phy Addr : 0x48180624 Data : 0x00010002

                            Phy Addr : 0x48180600 Data : 0x00000102

                            BW Phy Addr : 0x48180c10 Data : 0x00000007

                            AW Phy Addr : 0x48180c10 Data : 0x00000003

                            Phy Addr : 0x48180c14 Data : 0x00000004

                            BW Phy Addr : 0x58088000 Data : 0x09a3658d

                            AW Phy Addr : 0x58088000 Data : 0xeafffffe

                            BW Phy Addr : 0x58098000 Data : 0x7fd6a47a

                            AW Phy Addr : 0x58098000 Data : 0xeafffffe

                            BW Phy Addr : 0x48180c10 Data : 0x00000003

                            AW Phy Addr : 0x48180c10 Data : 0x00000000

                            Phy Addr : 0x48180c14 Data : 0x00000007

            PRCM for IVHD0 is Done Successfully  

            PRCM for IVHD1 is in Progress, Please wait.....  

                            BW Phy Addr : 0x48180700 Data : 0x00000002

                            AW Phy Addr : 0x48180700 Data : 0x00000002

                            Phy Addr : 0x48180d04 Data : 0x00000037

                            BW Phy Addr : 0x48180720 Data : 0x00070000

                            AW Phy Addr : 0x48180720 Data : 0x00050002

                            BW Phy Addr : 0x48180724 Data : 0x00030000

                            AW Phy Addr : 0x48180724 Data : 0x00010002

                            Phy Addr : 0x48180700 Data : 0x00000102

                            BW Phy Addr : 0x48180d10 Data : 0x00000007

                            AW Phy Addr : 0x48180d10 Data : 0x00000003

                            Phy Addr : 0x48180d14 Data : 0x00000004

                            BW Phy Addr : 0x5a088000 Data : 0x6b2c4f27

                            AW Phy Addr : 0x5a088000 Data : 0xeafffffe

                            BW Phy Addr : 0x5a098000 Data : 0x19c27a1a

                            AW Phy Addr : 0x5a098000 Data : 0xeafffffe

                            BW Phy Addr : 0x48180d10 Data : 0x00000003

                            AW Phy Addr : 0x48180d10 Data : 0x00000000

                            Phy Addr : 0x48180d14 Data : 0x00000007

            PRCM for IVHD1 is Done Successfully  

            PRCM for IVHD2 is in Progress, Please wait.....  

                            BW Phy Addr : 0x48180800 Data : 0x00000002

                            AW Phy Addr : 0x48180800 Data : 0x00000002

                            Phy Addr : 0x48180e04 Data : 0x00000037

                            BW Phy Addr : 0x48180820 Data : 0x00070000

                            AW Phy Addr : 0x48180820 Data : 0x00050002

                            BW Phy Addr : 0x48180824 Data : 0x00030000

                            AW Phy Addr : 0x48180824 Data : 0x00010002

                            Phy Addr : 0x48180800 Data : 0x00000102

                            BW Phy Addr : 0x48180e10 Data : 0x00000007

                            AW Phy Addr : 0x48180e10 Data : 0x00000003

                            Phy Addr : 0x48180e14 Data : 0x00000004

                            BW Phy Addr : 0x53088000 Data : 0xfdacf2b6

                            AW Phy Addr : 0x53088000 Data : 0xeafffffe

                            BW Phy Addr : 0x53098000 Data : 0xa283fffe

                            AW Phy Addr : 0x53098000 Data : 0xeafffffe

                            BW Phy Addr : 0x48180e10 Data : 0x00000003

                            AW Phy Addr : 0x48180e10 Data : 0x00000000

                            Phy Addr : 0x48180e14 Data : 0x00000007

            PRCM for IVHD2 is Done Successfully  

    PRCM Initialization completed 

    SysLink version : 2.00.02.80

    SysLink module created on Date:Aug 29 2011 Time:22:30:41

    FIRMWARE: Memory map bin file not passed

    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]

    FIRMWARE: Default memory configuration is used

    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1

    FIRMWARE: Memory Configuration status : In Progress

    FIRMWARE: 1 start Successful

    Starting telnet daemon.

    Loading HDVPSS Firmware

    FIRMWARE: Memory map bin file not passed

    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]

    FIRMWARE: Default memory configuration is used

    MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1

    FIRMWARE: Memory Configuration status : In Progress

    FIRMWARE: 2 start Successful

    cat: write error: No space left on device

    cat: write error: No space left on device

    HDMI W1 rev 2.0

    Starting syslogd/klogd: done

    Starting thttpd.

    Starting PVR

    /dev/mem opened.

    Memory mapped at address 0x4011f000.

    Read at address  0x48180F04 (0x4011ff04): 0x00000001

    Write at address 0x48180F04 (0x4011ff04): 0x00000000, readback 0x00000000

    /dev/mem opened.

    Memory mapped at address 0x4025b000.

    Read at address  0x48180900 (0x4025b900): 0x00000102

    Write at address 0x48180900 (0x4025b900): 0x00000002, readback 0x00000002

    /dev/mem opened.

    Memory mapped at address 0x4032a000.

    Read at address  0x48180920 (0x4032a920): 0x00040002

    Write at address 0x48180920 (0x4032a920): 0x00000002, readback 0x00000002

    Starting Matrix GUI application.

  • After boot-up, when you connect the HDMI cable to your display, can you confirm that the display can detect a signal (1080p-60)?

    Archith

  • When the board is on, when i unplug the display it shows 'check signal cabel' and when i connect it back the display shows for a second 'digital power saving mode'.

    I can see matrix gui when i'm back to previous ezsdk setup (fs+image).

  • Ilya,

     

    Could you use the uImage from the other post I mentioned on this thread.  You're issue may be related to the AVS driver adjusting the voltage level too low, thus cause other device peripheral to fail.

     

     

  • Marcus,

    have tried the image, but it didn't solve the issue.

  • Please help with the issue.