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.

syslink examples crash in DM8148

Other Parts Discussed in Thread: PMP, TPS65910, TLC59108, OMAPL138

Hello,

Kindly help me is fixing the syslink examples problem:

Problem: I am seeing stack traces when I run syslink messageq example in DM8148 board.

Description: I compile linux-omap3 kernel with GCC 4.6.3 toolchain. When I load this kernel, kernel panic occurs.
The stack indicates "omap_mbox_get" function "strcmp": "if (!strcmp(mbox->name, name))" ==> mbox->name has null and kernel panic occurs.

To overcome the kernel panic, I did not include CONFIG_SYSLINK_NOTIFY during kernel compilation.

Then I built syslink. Following is the products.mak and it indicates the various version of tools used in syslink compilation.
DEPOT = _your_depot_folder_
DEVICE = TI814X
GPPOS = Linux
SDK = NONE
TI81XXDSP_DMTIMER_FREQ = 20000000
SYSLINK_BUILD_DEBUG = 1
SYSLINK_BUILD_OPTIMIZE = 0
SYSLINK_TRACE_ENABLE = 1
LOADER = ELF
SYSLINK_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/syslink_2_10_06_28
IPC_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/install/ipc_1_24_03_32
BIOS_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/install/bios_6_33_05_46
XDC_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/install/xdctools_3_23_03_53
LINUXKERNEL = /home/anbarasan/build/dm8148_syslink/linux-omap3_latest/
QNX_INSTALL_DIR = _your_depot_folder_/_your_qnx_install_
CGT_ARM_PREFIX = /home/anbarasan/build/dm8148_syslink/toolchain/bin/armv7l-timesys-linux-gnueabi-
CGT_C64P_INSTALL_DIR =
CGT_C64P_ELF_INSTALL_DIR =
CGT_C674_INSTALL_DIR =
CGT_C674_ELF_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/install/cgt
CGT_M3_ELF_INSTALL_DIR = /home/anbarasan/build/dm8148_syslink/install/ccsv5/tools/compiler/tms470_4.9.1
CGT_A8_ELF_INSTALL_DIR =
EXEC_DIR = /home/anbarasan/build/dm8148_syslink/rfs


After booting linux kernel, I did:
# insmod /lib/modules/2.6.37+/kernel/drivers/dsp/syslink.ko
SysLink version : 2.10.06.28
SysLink module created on Date:Jul 3 2012 Time:15:58:10

Then export TRACE=1, export TRACEFAILURE=1

Then cd /ti/syslink-examples/TI814X/messageq/
# ./run_messageqapp_debug.sh
======== Running app using slaveloader ========
Attached to slave procId 0.
Loading procId 0.
BUG: Your driver calls ioremap() on system memory. This leads
to architecturally unpredictable behaviour on ARMv6+, and ioremap()
will fail in the next kernel release. Please fix your driver.
------------[ cut here ]------------
WARNING: at arch/arm/mm/ioremap.c:211 __arm_ioremap_pfn_caller+0x58/0x194()
Modules linked in: syslink
Backtrace:
[<c004edc8>] (dump_backtrace+0x0/0x110) from [<c03c6cf0>] (dump_stack+0x18/0x1c)
r6:c0493c2a r5:000000d3 r4:00000000 r3:60000013
[<c03c6cd8>] (dump_stack+0x0/0x1c) from [<c0073a40>] (warn_slowpath_common+0x54/0x6c)
[<c00739ec>] (warn_slowpath_common+0x0/0x6c) from [<c0073a7c>] (warn_slowpath_null+0x24/0x2c)
r8:00029e20 r7:00000000 r6:00000000 r5:0008b000 r4:00029e20
r3:00000009
[<c0073a58>] (warn_slowpath_null+0x0/0x2c) from [<c00529d4>] (__arm_ioremap_pfn_caller+0x58/0x194)
[<c005297c>] (__arm_ioremap_pfn_caller+0x0/0x194) from [<c0052b8c>] (__arm_ioremap_caller+0x5c/0x64)
[<c0052b30>] (__arm_ioremap_caller+0x0/0x64) from [<c0065004>] (omap_ioremap+0x60/0x64)
r4:8b000000
[<c0064fa4>] (omap_ioremap+0x0/0x64) from [<bf036168>] (MemoryOS_map+0x1f4/0x3a4 [syslink])
r7:00000002 r6:d4df9000 r5:00000000 r4:cc1adc60
[<bf035f74>] (MemoryOS_map+0x0/0x3a4 [syslink]) from [<bf005d34>] (_ProcMgr_map+0x1f0/0x4d4 [syslink])
r7:00000002 r6:d4df9000 r5:cc1adcc8 r4:00000001
[<bf005b44>] (_ProcMgr_map+0x0/0x4d4 [syslink]) from [<bf011278>] (ElfLoaderTrgWrite_copy+0x114/0x384 [syslink])
[<bf011164>] (ElfLoaderTrgWrite_copy+0x0/0x384 [syslink]) from [<bf015c48>] (DLIF_copy+0x10/0x1c [syslink])
[<bf015c38>] (DLIF_copy+0x0/0x1c [syslink]) from [<bf014450>] (DLOAD_load+0x740/0xa60 [syslink])
[<bf013d10>] (DLOAD_load+0x0/0xa60 [syslink]) from [<bf010960>] (ElfLoader_load+0x268/0x374 [syslink])
[<bf0106f8>] (ElfLoader_load+0x0/0x374 [syslink]) from [<bf001bb4>] (Loader_load+0xe4/0x160 [syslink])
[<bf001ad0>] (Loader_load+0x0/0x160 [syslink]) from [<bf0041e0>] (ProcMgr_load+0x224/0x304 [syslink])
[<bf003fbc>] (ProcMgr_load+0x0/0x304 [syslink]) from [<bf008928>] (ProcMgrDrv_ioctl+0xa84/0x19f8 [syslink])
[<bf007ea4>] (ProcMgrDrv_ioctl+0x0/0x19f8 [syslink]) from [<c00d833c>] (do_vfs_ioctl+0x4d4/0x548)
r8:00000000 r7:00000007 r6:c020e0a2 r5:cc18dd00 r4:befdbc18
[<c00d7e68>] (do_vfs_ioctl+0x0/0x548) from [<c00d8408>] (sys_ioctl+0x58/0x7c)
r9:cc1ac000 r8:00000000 r7:00000007 r6:c020e0a2 r5:befdbc18
r4:cc18dd00
[<c00d83b0>] (sys_ioctl+0x0/0x7c) from [<c004b280>] (ret_fast_syscall+0x0/0x30)
r8:c004b428 r7:00000036 r6:befdbc5c r5:00000000 r4:befdbf08
---[ end trace 7d82e7345d7e0d85 ]---
BUG: Your driver calls ioremap() on system memory. This leads
to architecturally unpredictable behaviour on ARMv6+, and ioremap()
will fail in the next kernel release. Please fix your driver.
------------[ cut here ]------------
WARNING: at arch/arm/mm/ioremap.c:211 __arm_ioremap_pfn_caller+0x58/0x194()
Modules linked in: syslink
Backtrace:
[<c004edc8>] (dump_backtrace+0x0/0x110) from [<c03c6cf0>] (dump_stack+0x18/0x1c)
r6:c0493c2a r5:000000d3 r4:00000000 r3:60000013

and the trace continues....

  • Anbarasan,

    It looks like the DSP memory is overlapping with the memory allocated to Linux.  If you look at your bootargs, you should see the memory given to the Linux kernel, for example, something like:

        mem=256M@0x80000000

    (If you just have something like 'mem=256M', you can assume that it will start from the address 0x80000000)

    Can you change this environment variable so that Linux memory will not overlap with the DSP memory?

    Best regards,

        Janet

  • HI,

    Try with MEM=169M.

    Thanks and regards

    Sachin kumar

  • Hello Janet, Sachin,

    Thanks for your reply.
    I apologize for not telling you my bootargs variable and few other details in my first post.

    ----------------------------------------------------------

    1. The bootargs I use is:
    console=ttyO0,115200 ip=dhcp root=/dev/nfs rw mem=128M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M

    2. I am using the following linux kernel version:
    TI Linux kernel: v2.6.37_TI81XXPSP_04.04.00.01.patch1
    I downloaded it like this:
    git clone git://arago-project.org/git/projects/linux-omap3.git
    git checkout 5ce4084039ee5b2a30a2c75cfb06315af953d679

    3. The issue about crash in omap_mbox_get is tracked here:
    https://github.com/DFE/HidaV/issues/5
    And a relevant discussion: http://www.digipedia.pl/usenet/thread/12941/45743/

    As mentioned in thread, omap_mbox_get crash occurs if I use gcc version 4.6.3.
    The crash does not occur if I use gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) and the linux kernel boots successfully.

    ----------------------------------------------------------

    Sachin, I tried with mem=169M but that did not help i.e.,
    when I build with CONFIG_SYSLINK_NOTIFY=y in kernel, I get omap_mbox_get crash.
    when I do not use CONFIG_SYSLINK_NOTIFY, I get the stack trace when I run the syslink examples.

    With respect to this crash, using mem=169M is same as using mem=128M.(same behavior)

    ----------------------------------------------------------

    My aim is to run syslink examples on a linux kernel that is compiled with gcc 4.6.3. So, as a first step, I wanted to try syslink and kernel versions that TI said they have verified and I followed this release notes:
    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/syslink/2_10_06_28/exports/syslink_2_10_06_28/syslink_2_10_06_28_ReleaseNotes.html
    and used all the tools mentioned in the "Validation" section. I use the versions mentioned in release notes.
    But even that did not work. Following is the bootlog and the syslink error: (You can see in bootlog that I am using TI suggested toolchain (Sourcery G++ Lite 2009q1-203).

    Log with Sourcery G++ Lite 2009q1-203:
    ======================================
    Environment size: 977/8188 bytes
    TI8168_EVM#
    bootdelay=3
    baudrate=115200
    verify=yes
    ramdisk_file=ramdisk.gz
    loadaddr=0x81000000
    script_addr=0x80900000
    loadbootscript=fatload mmc 0 ${script_addr} boot.scr
    bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}
    ethaddr=64:7b:d4:15:a7:14
    ethact=DaVinci EMAC
    nfs_boot=run bootargs_nfs; bootp; bootm
    bootargs_nfs=setenv bootargs console=ttyO0,115200 ip=dhcp root=/dev/nfs rw mem=258M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M
    filename=kernel_dm8168evm-1
    bootfile=kernel_dm8168_evm-1
    netmask=255.255.255.0
    autoload=yes
    ipaddr=10.1.0.99
    serverip=192.168.56.101
    gatewayip=10.1.0.1
    bootcmd=tftp uImage_dm8168;bootm
    bootargs=console=ttyO2,115200 ip=dhcp root=/dev/nfs nfsroot=192.168.56.101:/home/anbarasan/ti/dm8168_syslink/rfs rw mem=128M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M M
    stdin=serial
    stdout=serial
    stderr=serial
    ver=U-Boot 2010.06 (Nov 16 2011 - 18:11:27)

    Environment size: 977/8188 bytes
    TI8168_EVM#run bootcmd
    Using DaVinci EMAC device
    TFTP from server 192.168.56.101; our IP address is 10.1.0.99; sending through gateway 10.1.0.1
    Filename 'uImage_dm8168'.
    Load address: 0x81000000
    Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ##############################################
    done
    Bytes transferred = 2562960 (271b90 hex)
    ## Booting kernel from Legacy Image at 81000000 ...
    Image Name: Linux-2.6.37
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2562896 Bytes = 2.4 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 (anbarasan@anbarasan-vm) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Fri Jun 22 13:42:33 EDT 2012
    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 0x0
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8168 1.0
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 19712
    Kernel command line: console=ttyO2,115200 ip=dhcp root=/dev/nfs nfsroot=192.168.56.101:/home/anbarasan/ti/dm8168_syslink/rfs rw mem=128M earlyprintk notifyk.vpssm3_sva=0xBF9000M
    PID hash table entries: 512 (order: -1, 2048 bytes)
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 78MB = 78MB total
    Memory: 73224k/73224k available, 57848k reserved, 0K highmem
    Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
    vmalloc : 0xc8800000 - 0xf8000000 ( 760 MB)
    lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
    pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
    modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
    .init : 0xc0008000 - 0xc003b000 ( 204 kB)
    .text : 0xc003b000 - 0xc04d8000 (4724 kB)
    .data : 0xc04d8000 - 0xc0520f00 ( 292 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_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    omap_voltage_add_dev: VDD specified does not exist!
    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_gpio_vr device
    registered ti816x_sr device
    pm_dbg_init: only OMAP3 supported
    registered ti81xx_vpss device
    registered ti81xx_vidout device
    registered ti81xx on-chip HDMI device
    registered ti81xx_fb device
    registered ti81xx_vin device
    ti81xx_pcie: Invoking PCI BIOS...
    ti81xx_pcie: Setting up Host Controller...
    ti81xx_pcie: Register base mapped @0xc8820000
    ti81xx_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 920 mV
    vgaarb: loaded
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    USBSS revision 4ea20808
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    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
    MUSB controller-0 revision 4ea20800
    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 c881e000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    MUSB controller-1 revision 4ea20800
    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 c8826800 using DMA, IRQ 19
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    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 143
    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 w25x32, expected m25p80
    m25p80 spi1.0: w25x32 (4096 Kbytes)
    Creating 4 MTD partitions on "spi_flash":
    0x000000000000-0x000000040000 : "U-Boot"
    0x000000040000-0x000000042000 : "U-Boot Env"
    0x000000042000-0x0000002c2000 : "Kernel"
    0x0000002c2000-0x000000400000 : "File System"
    omap2-nand driver initializing
    ONFI flash detected
    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 fffffffd
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, 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
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    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
    Power Management for TI81XX.
    smartreflex smartreflex: Driver is not initialized, nTarget values are not found
    regulator_init_complete: disabling VFB
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    ata2: SATA link down (SStatus 0 SControl 300)
    ata1: SATA link down (SStatus 0 SControl 300)
    mmc0: new high speed SDHC card at address 1234
    mmcblk0: mmc0:1234 SA04G 3.68 GiB
    mmcblk0: p1 p2
    davinci_mdio davinci_mdio.0: resetting idled controller
    net eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, id=282f013)
    PHY 0:02 not found
    net eth1: could not connect to phy 0:02
    Sending DHCP requests ..
    PHY: 0:01 - Link is Up - 1000/Full
    ., OK
    IP-Config: Got DHCP answer from 10.1.0.1, my address is 10.1.0.11
    IP-Config: Complete:
    device=eth0, addr=10.1.0.11, mask=255.255.0.0, gw=10.1.0.1,
    host=10.1.0.11, domain=example.org, nis-domain=(none),
    bootserver=10.1.0.1, rootserver=192.168.56.101, rootpath=/home/anbarasan/targetfs
    VFS: Mounted root (nfs filesystem) on device 0:15.
    devtmpfs: mounted
    Freeing init memory: 204K
    INIT: version 2.86 booting
    Error opening /dev/fb0: No such file or directory
    Please wait: booting...
    Starting udev
    WARNING: -e needs -E or -F
    udevd (78): /proc/78/oom_adj is deprecated, please use /proc/78/oom_score_adj instead.
    FAT: bogus number of reserved sectors
    VFS: Can't find a valid FAT filesystem on dev mmcblk0.
    EXT3-fs: barriers not enabled
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
    EXT3-fs (mmcblk0p2): using internal journal
    EXT3-fs (mmcblk0p2): recovery complete
    EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
    Root filesystem already rw, not remounting
    Caching udev devnodes
    Undefined users:
    Skipping /etc/default/volatiles/99_hal
    ALSA: Restoring mixer settings...
    No state is present for card EVM
    Found hardware: "" "" "" "" ""
    Hardware is initialized using a generic method
    No state is present for card EVM
    Configuring update-modules.
    Configuring omap3-sgx-modules.
    Configuring hicolor-icon-theme.
    # GdkPixbuf Image Loader Modules file
    # Automatically generated file, do not edit
    # Created by gdk-pixbuf-query-loaders from gtk+-2.20.1
    #
    g_module_open() failed for /--update-cache: /--update-cache.so: cannot open shared object file: No such file or directory
    Configuring pango-module-basic-x.
    Configuring pango-module-basic-fc.
    Configuring ttf-dejavu-common.
    Configuring ttf-dejavu-sans.
    Configuring gdk-pixbuf-loader-png.
    Configuring gdk-pixbuf-loader-jpeg.
    Configuring gdk-pixbuf-loader-gif.
    Configuring gdk-pixbuf-loader-xpm.
    Configuring dbus.
    Adding system startup for /etc/init.d/dbus-1.
    Configuring hal.
    Configuring policykit.
    Configuring gnome-keyring.
    Configuring ti-cmem-module.
    Configuring ti-syslink-module.
    Configuring kernel-module-tunnel4.
    Configuring kernel-module-sit.
    Configuring kernel-module-xfrm6-mode-beet.
    Configuring kernel-module-xfrm6-mode-tunnel.
    Configuring kernel-module-xfrm6-mode-transport.
    Configuring kernel-module-scsi-wait-scan.
    Configuring kernel-module-ssb.
    Configuring kernel-module-vpss.
    Configuring kernel-module-sii9022a.
    Configuring kernel-module-ti81xxhdmi.
    Configuring kernel-module-ti81xxfb.
    Configuring kernel-module-tvp7002.
    Configuring kernel-module-ti81xxvo.
    Configuring kernel-module-ti81xxvin.
    Configuring kernel-image-2.6.37.
    NET: Registered protocol family 10
    NOT configuring network interfaces: / is an NFS mount
    Sun Apr 29 22:50:00 UTC 2012
    INIT: Entering runlevel: 5
    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 : 0xeafffffe
    AW Phy Addr : 0x58088000 Data : 0xeafffffe
    BW Phy Addr : 0x58098000 Data : 0xeafffffe
    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 : 0xeafffffe
    AW Phy Addr : 0x5a088000 Data : 0xeafffffe
    BW Phy Addr : 0x5a098000 Data : 0xeafffffe
    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 : 0xeafffffe
    AW Phy Addr : 0x53088000 Data : 0xeafffffe
    BW Phy Addr : 0x53098000 Data : 0xeafffffe
    AW Phy Addr : 0x53098000 Data : 0xeafffffe
    BW Phy Addr : 0x48180e10 Data : 0x00000003
    AW Phy Addr : 0x48180e10 Data : 0x00000000
    Phy Addr : 0x48180e14 SysLink version : 2.10.03.20
    SysLink module created on Date:Jun 22 2012 Time:13:47:20
    Data : 0x00000007
    PRCM for IVHD2 is Done Successfully
    PRCM Initialization completed
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: Memory Configuration status : In Progress
    FIRMWARE: 1 start Successful
    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: Memory Configuration status : In Progress
    FIRMWARE: 2 start Successful
    HDMI W1 rev 2.0
    I2C No Ack

    Starting system message bus: dbus.
    Starting telnet daemon.
    Starting syslogd/klogd: done
    Starting thttpd.
    Starting PVR
    Starting SGX fixup for ES6.x
    Starting Matrix GUI application.

    _____ _____ _ _
    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    | | _| .'| . | . | | __| _| . | | | -_| _| _|
    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    |___| |___|

    Arago Project http://arago-project.org dm816x-evm ttyO2

    Arago 2011.09 dm816x-evm ttyO2

    dm816x-evm login: root
    root@dm816x-evm:~# export TRACE=1
    root@dm816x-evm:~# export TRACEFAILURE=1
    root@dm816x-evm:~# cd /ti/syslink-examples/TI816X/
    root@dm816x-evm:/ti/syslink-examples/TI816X# cd messageq/
    root@dm816x-evm:/ti/syslink-examples/TI816X/messageq# ./run_messageqapp_debug.sh

    ======== Running app using slaveloader ========
    Trace enabled
    Trace SetFailureReason enabled
    Attached to slave procId 0.
    Loading procId 0.
    Loaded file ./messageq_ti81xx_dsp.xe674 on slave procId 0.
    Started slave procId 0.
    MessageQApp sample application
    Trace enabledAssertion at Line no: 301 in /home/anbarasan/ti/dm8168_syslink/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../.d

    Trace SetFailureReason enabled
    Run for all supported proc IDs
    Entered MessageQApp_startup
    Warning! Unsupported procID specified for running the sample application! proc ID: [1]
    Warning! Unsupported procID specified for running the sample application! proc ID: [2]
    *** Ipc_control: API (through IOCTL) failed on kernel-side!
    Error [0xffffffff] at Line no: 1077 in file /home/anbarasan/ti/dm8168_syslink/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/Ipc.c
    Error in Ipc_control Ipc_CONTROLCMD_LOADCALLBACK [0xffffffff]
    Leaving MessageQApp_startup ffffffff
    Trace enabled
    Trace SetFailureReason enabled
    Stopped slave procId 0.
    Unloaded slave procId 0.
    Detached from slave procId 0.
    ======== Running app using aAssertion at Line no: 301 in /home/anbarasan/ti/dm8168_syslink/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/.d
    rguments ========
    MessageQApp sample application
    Trace enabled
    Trace SetFailureReason enabled
    Entered MessageQApp_startup
    Loading and starting procId [0] with [./messageq_ti81xx_dsp.xe674]
    Attached to slave procId 0.
    Loading procId 0.
    Loaded file ./messageq_ti81xx_dsp.xe674 on slave procId 0.
    Started slave procId 0.
    SlaveLoader_startup status [111693824]
    *** Ipc_control: API (through IOCTL) failed on kernel-side!
    Error [0xffffffff] at Line no: 1077 in file /home/anbarasan/ti/dm8168_syslink/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/Ipc.c
    Error in Ipc_control Ipc_CONTROLCMD_LOADCALLBACK [0xffffffff]
    Leaving MessageQApp_startup ffffffff
    root@dm816x-evm:/ti/syslink-examples/TI816X/messageq#

    ---------------------------------------------------------------

    After the above errros, I tried with gcc 4.6.3 and I see errors that I posted in as my first message in this thread.


    To summarize,
    1. there is some problem with syslink examples with older toolchain.
    2. with 4.6.3 gcc verison, the kernel does not boot and syslink examples also do not work.

  • Anbarasan,

    Could you try just running the MessageQ app with:

        ./messageqapp_debug 1 DSP ./messageq_ti81xx_dsp.xe674

    The script you are running (run_messageapp_debug.sh) is trying to load the example on the M3 where you have the firmware loaded.

    Best regards,

        Janet

  • Hello Janet,

    I made a mistake with the logs that I posted. I started the thread for DM8148 but I posted logs for DM8168 board in my last post. Unfortunately I cannot test in DM8168 board any more (it is broken) but soon I will run the commands in DM8148 board as you said and get all necessary logs...

  • Hello Janet,

    I downloaded EZSDK (DM814x EZSDK 5.04 Installer) from http://software-dl.ti.com/dsps/dsps_public_sw/ezsdk/latest/index_FDS.html

    I installed it in Ubuntu 10.04 machine (A virtualbox machine), compiled u-boot, kernel and syslink.

    anbarasan@anbarasan-vm:~/ti/dm8148_syslink/component-sources/syslink_2_10_03_20$ make .show-products
    DEPOT = _your_depot_folder_
    DEVICE = TI814X
    GPPOS = Linux
    SDK = EZSDK
    TI81XXDSP_DMTIMER_FREQ = 20000000
    SYSLINK_BUILD_DEBUG = 1
    SYSLINK_BUILD_OPTIMIZE = 0
    SYSLINK_TRACE_ENABLE = 1
    LOADER = ELF
    SYSLINK_INSTALL_DIR = /home/anbarasan/ti/dm8148_syslink/component-sources/syslink_2_10_03_20
    IPC_INSTALL_DIR = /home/anbarasan/ti/dm8148_syslink/component-sources/ipc_1_24_02_27
    BIOS_INSTALL_DIR = /home/anbarasan/ti/dm8148_syslink/component-sources/bios_6_33_02_31
    XDC_INSTALL_DIR = /home/anbarasan/ti/dm8148_syslink/component-sources/xdctools_3_23_01_43
    LINUXKERNEL = /home/anbarasan/ti/dm8148_syslink/board-support/linux-2.6.37-psp04.04.00.01
    QNX_INSTALL_DIR = _your_depot_folder_/_your_qnx_install_
    CGT_ARM_PREFIX = /opt/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-linux-gnueabi-
    CGT_C64P_INSTALL_DIR =
    CGT_C674_INSTALL_DIR =
    CGT_C674_ELF_INSTALL_DIR = /home/anbarasan/ti/dm8148_syslink/dsp-devkit/cgt6x_7_3_1
    CGT_M3_ELF_INSTALL_DIR =
    CGT_A8_ELF_INSTALL_DIR =
    EXEC_DIR = /home/anbarasan/ti/dm8148_syslink/rfs

    I used the RFS that is present EZSDK installer. I booted the hardware and I got lot of error messages related to IPV6 modules. So I removed it from kernel (using menuconfig) and removed the so file in /lib/modules/2.6.37/kernel/net/ipv6/

    After that I ran syslink examples and get error like the one in DM8168. Commands are pasted below (I copied and pasted the command you mentioned: ./messageqapp_debug 1 DSP ./messageq_ti81xx_dsp.xe674). You can also see the bootargs that I used in kernel boot log.

    Am I missing something? 

    link up on port 0, speed 1000, full duplex
    BOOTP broadcast 1
    BOOTP broadcast 2
    DHCP client bound to address 192.168.99.154
    Using cpsw device
    TFTP from server 192.168.99.3; our IP address is 192.168.99.154
    Filename 'kernel_dm8148_evm-1'.
    Load address: 0x81000000
    Loading: *#################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ##########
    done
    Bytes transferred = 2712400 (296350 hex)
    ## Booting kernel from Legacy Image at 81000000 ...
    Image Name: Linux-2.6.37
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 2712336 Bytes = 2.6 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 (anbarasan@anbarasan-vm) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #2 Fri Jul 6 09:56:27 EDT 2012
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: ti8148evm
    bootconsole [earlycon0] enabled
    vram size = 52428800 at 0x0
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is TI8148 2.0
    SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 19712
    Kernel command line: console=ttyO0,115200 ip=dhcp root=/dev/nfs rw mem=128M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M
    PID hash table entries: 512 (order: -1, 2048 bytes)
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 78MB = 78MB total
    Memory: 72900k/72900k available, 58172k reserved, 0K highmem
    Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000 ( 4 kB)
    fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
    DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
    vmalloc : 0xc8800000 - 0xf8000000 ( 760 MB)
    lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
    pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
    modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
    .init : 0xc0008000 - 0xc003c000 ( 208 kB)
    .text : 0xc003c000 - 0xc0521000 (5012 kB)
    .data : 0xc0522000 - 0xc056d780 ( 302 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 20000000 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 598.01 BogoMIPS (lpj=2990080)
    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_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    omap_voltage_add_dev: VDD specified does not exist!
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    omap_mux_init: Add partition: #1: core, flags: 4
    NOR: Can't request GPMC CS
    Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    registered ti81xx_vpss device
    registered ti81xx_vidout device
    registered ti81xx on-chip HDMI device
    registered ti81xx_fb device
    registered ti81xx_vin device
    ti81xx_pcie: Invoking PCI BIOS...
    ti81xx_pcie: Setting up Host Controller...
    ti81xx_pcie: Register base mapped @0xc8820000
    ti81xx_pcie: Starting PCI scan...
    PCI: bus0: Fast back to back transfers enabled
    bio: create slab <bio-0> at 0
    vgaarb: loaded
    SCSI subsystem initialized
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    USBSS revision 4ea2080b
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    pcf857x: probe of 1-0021 failed with error -121
    regulator: VRTC: 1800 mV
    regulator: VIO: 1500 mV
    regulator: VDD1: 600 <--> 1500 mV at 1200 mV
    regulator: VDD2: 600 <--> 1500 mV at 1200 mV
    regulator: VDDCTRL: 600 <--> 1400 mV at 1200 mV
    regulator: LDO1: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO2: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO3: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO4: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO5: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO6: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO7: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO8: 1100 <--> 3300 mV at 1800 mV
    tps65910 1-002d: No interrupt support, no core IRQ
    omap_i2c omap_i2c.3: bus 3 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
    MUSB controller-0 revision 4ea20800
    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 c881e000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    MUSB controller-1 revision 4ea20800
    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 c8826800 using DMA, IRQ 19
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    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) \A9 2001-2006 Red Hat, Inc.
    msgmni has been set to 142
    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
    console [ttyO0] enabled, bootconsole disabled
    console [ttyO0] enabled, bootconsole disabled
    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
    omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
    omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
    omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x1
    ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    m25p80 spi1.0: w25x32 (4096 Kbytes)
    Creating 5 MTD partitions on "spi_flash":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-0x000000060000 : "U-Boot"
    0x000000060000-0x000000062000 : "U-Boot Env"
    0x000000062000-0x0000002e2000 : "Kernel"
    0x0000002e2000-0x000000400000 : "File System"
    omap2-nand driver initializing
    ONFI flash detected
    NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron )
    Creating 6 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-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 fffffffc
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    CAN device driver interface
    CAN bus driver for Bosch D_CAN controller 1.0
    d_can d_can: d_can device registered (irq=52, irq_obj=53)
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    usbcore: registered new interface driver cdc_acm
    cdc_acm: v0.26: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.
    mice: PS/2 mouse device common for all mice
    qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
    qt602240_ts: probe of 1-004a failed with error -5
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    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
    ata1: SATA link down (SStatus 0 SControl 300)
    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
    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)
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    omap_voltage_late_init: Voltage driver support not added
    Power Management for TI81XX.
    Detected MACID=90:d7:eb:c6:8a:89
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    mmc0: new SD card at address e3ea
    mmcblk0: mmc0:e3ea SD01G 968 MiB
    mmcblk0: p1 p2

    CPSW phy found : id is : 0x4dd074

    CPSW phy found : id is : 0x4dd074
    Sending DHCP requests .
    PHY: 0:01 - Link is Up - 0/Half
    PHY: 0:01 - Link is Down
    .
    PHY: 0:00 - Link is Up - 1000/Full
    ., OK
    IP-Config: Got DHCP answer from 192.168.99.3, my address is 192.168.99.154
    IP-Config: Complete:
    device=eth0, addr=192.168.99.154, mask=255.255.255.0, gw=192.168.99.1,
    host=dm8148_evm-1, domain=, nis-domain=(none),
    bootserver=192.168.99.3, rootserver=192.168.99.3, rootpath=/data/boards/dm8148_evm-1/rfs
    VFS: Mounted root (nfs filesystem) on device 0:15.
    devtmpfs: mounted
    Freeing init memory: 208K
    INIT: version 2.86 booting
    Please wait: booting...
    Error opening /dev/fb0: No such file or directory
    Starting udev
    udevd (82): /proc/82/oom_adj is deprecated, please use /proc/82/oom_score_adj instead.
    FAT: bogus number of reserved sectors
    VFS: Can't find a valid FAT filesystem on dev mmcblk0.
    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
    Root filesystem already rw, not remounting
    Caching udev devnodes
    ALSA: Restoring mixer settings...
    NOT configuring network interfaces: / is an NFS mount
    Mon Apr 30 02:04:00 UTC 2012
    INIT: Entering runlevel: 5
    Loading HDVICP2 Firmware
    DM814X prcm_config_app version: 2.0.0.1
    Doing PRCM settings...
    PRCM for IVHD0 is in Progress, Please wait.....
    BW Phy Addr : 0x48180600 Data : 0x00000001
    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 : 0xb007b5fd
    AW Phy Addr : 0x58088000 Data : 0xeafffffe
    BW Phy Addr : 0x58098000 Data : 0x4f095856
    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 Initialization completed
    SysLink version : 2.10.03.20
    SysLink module created on Date:Jul 6 2012 Time:08:56:35
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: Memory Configuration status : In Progress
    FIRMWARE: 1 start Successful
    Loading HDVPSS Firmware
    FIRMWARE: I2cInit will be done by M3
    FIRMWARE: Memory map bin file not passed
    Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
    ===Mandatory arguments===
    <Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
    <Location of Firmware> firmware binary file
    <start|stop> to start/stop the firmware
    ===Optional arguments===
    -mmap input memory map bin file name
    -i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
    FIRMWARE: isI2cInitRequiredOnM3: 1
    FIRMWARE: Default memory configuration is used
    MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
    FIRMWARE: Memory Configuration status : In Progress
    FIRMWARE: 2 start Successful
    Configuring fb0 to LCD
    HDMI W1 rev 4.0
    I2C No Ack

    Starting system message bus: dbus.
    Starting Dropbear SSH server: modprobe: FATAL: Could not read '/lib/modules/2.6.37/kernel/net/ipv6/ipv6.ko': No such file or directory

    modprobe: FATAL: Could not read '/lib/modules/2.6.37/kernel/net/ipv6/ipv6.ko': No such file or directory

    dropbear.
    Starting telnet daemon.
    modprobe: FATAL: Could not read '/lib/modules/2.6.37/kernel/net/ipv6/ipv6.ko': No such file or directory

    Starting network benchmark server: netserver.
    Starting syslogd/klogd: done
    Starting thttpd.
    Starting PVR
    /dev/mem opened.
    Memory mapped at address 0x400d6000.
    Read at address 0x48180F04 (0x400d6f04): 0x00000001
    Write at address 0x48180F04 (0x400d6f04): 0x00000000, readback 0x00000000
    /dev/mem opened.
    Memory mapped at address 0x402b2000.
    Read at address 0x48180900 (0x402b2900): 0x00000102
    Write at address 0x48180900 (0x402b2900): 0x00000002, readback 0x00000002
    /dev/mem opened.
    Memory mapped at address 0x40234000.
    Read at address 0x48180920 (0x40234920): 0x00040002
    Write at address 0x48180920 (0x40234920): 0x00000002, readback 0x00000002
    Calibrating touchscreen (first time only)ts_open: No such file or directory
    .
    Starting Matrix GUI application.

    _____ _____ _ _
    | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
    | | _| .'| . | . | | __| _| . | | | -_| _| _|
    |__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
    |___| |___|

    Arago Project http://arago-project.org dm814x-evm ttyO0

    Arago 2011.09 dm814x-evm ttyO0

    dm814x-evm login: root
    root@dm814x-evm:~#
    root@dm814x-evm:~# cd i lsmod
    Module Size Used by
    bufferclass_ti 4950 0
    omaplfb 10794 0
    pvrsrvkm 155618 2 bufferclass_ti,omaplfb
    tlc59108 1545 0
    ti81xxhdmi 16163 0
    ti81xxfb 21979 2
    vpss 74936 3 omaplfb,ti81xxhdmi,ti81xxfb
    syslink 1113458 0
    root@dm814x-evm:~# cd t ti /ti root@dm814x-evm:~# cd /ti/ root@dm814x-evm:~# cd /ti/syslink-examples/ root@dm814x-evm:~# cd /ti/syslink-examples/TI814X/ root@dm814x-evm:~# cd /ti/syslink-examples/TI814X/
    root@dm814x-evm:/ti/syslink-examples/TI814X# cd me root@dm814x-evm:/ti/syslink-examples/TI814X# cd messageq/
    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# export TRACE=1
    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# export TRACEFAILURE=1
    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# ./messageqapp_debug 1 DSP
    ./messageq_ti81xx_dsp.xe674
    MessageQApp sample application
    Trace enabled
    Trace SetFailureReason enabled
    Entered MessageQApp_startup
    Loading and starting procId [0] with [./messageq_ti81xx_dsp.xe674]
    Attached to slave procId 0.
    Loading procId 0.
    Loaded file ./meAssertion at Line no: 301 in /home/anbarasan/ti/dm8148_syslink/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/IpcDrv.c: (status >= 0) : failed
    ssageq_ti81xx_dsp.xe674 on slave procId 0.
    Started slave procId 0.
    SlaveLoader_startup status [111693824]
    *** Ipc_control: API (through IOCTL) failed on kernel-side!
    Error [0xffffffff] at Line no: 1077 in file /home/anbarasan/ti/dm8148_syslink/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/Ipc.c
    Error in Ipc_control Ipc_CONTROLCMD_LOADCALLBACK [0xffffffff]
    Leaving MessageQApp_startup ffffffff
    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# uname -a
    Linux dm814x-evm 2.6.37 #2 Fri Jul 6 09:56:27 EDT 2012 armv7l unknown
    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# cpu cat /proc/cpuinfo
    Processor: ARMv7 Processor rev 2 (v7l)
    BogoMIPS: 598.01
    Features: swp half thumb fastmult vfp edsp neon vfpv3
    CPU implementer: 0x41
    CPU architecture: 7
    CPU variant: 0x3
    CPU part: 0xc08
    CPU revision: 2

    Hardware: ti8148evm
    Revision: 0000
    Serial: 0000000000000000

  • Hello Anbarasan,

    I think there may be an issue with the memory map for the SysLink example and the default EZSDK memory map.  According to the DM814x_EZ_Software_Developers_Guide.pdf, the SysLink examples cannot be run with the firmware loaded.  Here are the steps to stop the firmware (taken from the ezsdk user's guide):

    Note! The syslink samples use a different memory map from the default EZSDK installation. In order to run
    syslink examples, you must boot with a different memory for linux. When booting, ensure that the linux
    bootargs is changed from the default values to MEM=169M


    Note! The syslink samples cannot be run out with graphics or firmware loaded. Please execute the following
    steps to teardown the graphics plane and ensure that no firmware is running.


    target # /etc/init.d/pvr-init stop
    target # /etc/init.d/matrix-gui-e stop
    target # /etc/init.d/load-hd-firmware.sh stop


    Now the system is ready to run all syslink samples.


    target # modprobe syslink
    target # cd /usr/share/ti/syslink-examples/TI814X
    Execute the following script to run the example application
    target # ./runsamples_debug.sh

    Have you tried these steps first?

    Best regards,

        Janet

  • Hello Janet, 

    Thanks. I am able run the examples after using the stop commands (I should have read that in the guide beforehand. when i ran the sample applications in OMAPL138 board i did not do those steps and got the samples working. i just followed the same for dm8148 and got error. now it is working after using the stop commands.) I have pasted the output below. The sample applications with codesourcery toolchain is working. Thanks.

    What do you think the problem with 4.6.3 gcc and TI's linux 2.6.37 kernel? do you have any suggestions regarding this? http://www.digipedia.pl/usenet/thread/12941/45743/

    https://github.com/DFE/HidaV/issues/5

    root@dm814x-evm:/ti/syslink-examples/TI814X/messageq# ./run_messageqapp_release.

    sh
    ======== Running app using slaveloader ========
    Attached to slave procId 0.
    Loading procId 0.
    Loaded file ./messageq_ti81xx_dsp.xe674 on slave procId 0.
    Started slave procId 0.
    MessageQApp sample application
    Run for all supported proc IDs
    Entered MessageQApp_startup
    Warning! Unsupported procID specified for running the sample application! proc ID: [1]
    Warning! Unsupported procID specified for running the sample application! proc ID: [2]
    After Ipc_loadcallback:
    status [0x0]
    After Ipc_startcallback:
    status [0x97d2000]
    Leaving MessageQApp_startup 97d2000
    Entered MessageQApp_execute
    MessageQApp_threadHandler entered
    Registering heapId 0 with MessageQ for procId: 0
    MessageQ_create name MSGQ_30 status [0x0] : procId [0]
    Sending synchronizaion notification to ProcId: 0
    Sent synchronizaion notification to ProcId: 0
    MessageQ_open Status [0x0] : procId [0]
    MessageQApp_queueId [0x0] : procId [0]
    Sending a message #100 to 0
    Sending a message #200 to 0
    Sending a message #300 to 0
    Sending a message #400 to 0
    Sending a message #500 to 0
    Sending a message #600 to 0
    Sending a message #700 to 0
    Sending a message #800 to 0
    Sending a message #900 to 0
    Sending a message #1000 to 0
    Leaving MessageQApp_threadHandler 0
    Leaving MessageQApp_execute
    Entered MessageQApp_shutdown()
    After Ipc_stopCallback status: [0x97d2000]
    Leaving MessageQApp_shutdown() (0x97d2000)
    Stopped slave procId 0.
    Unloaded slave procId 0.
    Detached from slave procId 0.
    ======== Running app using arguments ========
    MessageQApp sample application
    Entered MessageQApp_startup
    Loading and starting procId [0] with [./messageq_ti81xx_dsp.xe674]
    Attached to slave procId 0.
    Loading procId 0.
    Loaded file ./messageq_ti81xx_dsp.xe674 on slave procId 0.
    Started slave procId 0.
    SlaveLoader_startup status [111693824]
    After Ipc_loadcallback:
    status [0x0]
    After Ipc_startcallback:
    status [0x97d2000]
    Leaving MessageQApp_startup 97d2000
    Entered MessageQApp_execute
    MessageQApp_threadHandler entered
    Registering heapId 0 with MessageQ for procId: 0
    MessageQ_create name MSGQ_30 status [0x0] : procId [0]
    Sending synchronizaion notification to ProcId: 0
    Sent synchronizaion notification to ProcId: 0
    MessageQ_open Status [0x0] : procId [0]
    MessageQApp_queueId [0x0] : procId [0]
    Sending a message #100 to 0
    Sending a message #200 to 0
    Sending a message #300 to 0
    Sending a message #400 to 0
    Sending a message #500 to 0
    Sending a message #600 to 0
    Sending a message #700 to 0
    Sending a message #800 to 0
    Sending a message #900 to 0
    Sending a message #1000 to 0
    Leaving MessageQApp_threadHandler 0
    Leaving MessageQApp_execute
    Entered MessageQApp_shutdown()
    After Ipc_stopCallback status: [0x97d2000]
    Shutting down procId [0]
    Stopped slave procId 0.
    Unloaded slave procId 0.
    Detached from slave procId 0.
    SlaveLoader_shutdown status [0]
    Leaving MessageQApp_shutdown() (0x0)

  • Anbarasan,

    I'm glad to hear that the example is working now.  As for the 4.6.3 toolchain, I'm not sure that this is actually related to the kernel crash you were seeing earlier, since that was happening before you changed the amount of memory allocated to Linux.  In fact, the error in the log says:

    BUG: Your driver calls ioremap() on system memory.

    This probably indicates that a section of DSP memory is overlapping with the Linux memory.  When you changed the Linux memory to mem=169M, that crash went away, correct?  You could try going back to the 4.6.3 toolchain, and see if your SysLink example now runs.

    Best regards,

        Janet

  • Hello Janet,

    After applying the following patch, I got the kernel to load successfully when compiled with gcc 4.6.3. Syslink and syslink examples compiled with the same toolchain also works without throwing any error. Thanks a lot for your help. 

    git log -p c03773206bf2249a890c4d420ed32ef500630095

    commit c03773206bf2249a890c4d420ed32ef500630095
    Author: Kevin Hilman <khilman@ti.com>
    Date: Fri Feb 11 19:56:43 2011 +0000

    OMAP2+: mailbox: fix lookups for multiple mailboxes

    The pointer math in omap_mbox_get() is not quite right, and leads to
    passing NULL to strcmp() when searching for an mbox that is not first
    in the list.

    Convert to using array indexing as is done in all the other functions
    which walk the mbox list.

    Tested on OMAP2420/n810, OMAP3630/zoom3, OMAP4430/Blaze

    Signed-off-by: Kevin Hilman <khilman@ti.com>
    Signed-off-by: Tony Lindgren <tony@atomide.com>

    diff --git a/arch/arm/plat-omap/mailbox.c b/arch/arm/plat-omap/mailbox.c
    index 459b319..49d3208 100644
    --- a/arch/arm/plat-omap/mailbox.c
    +++ b/arch/arm/plat-omap/mailbox.c
    @@ -322,15 +322,18 @@ static void omap_mbox_fini(struct omap_mbox *mbox)

    struct omap_mbox *omap_mbox_get(const char *name, struct notifier_block *nb)
    {
    - struct omap_mbox *mbox;
    - int ret;
    + struct omap_mbox *_mbox, *mbox = NULL;
    + int i, ret;

    if (!mboxes)
    return ERR_PTR(-EINVAL);

    - for (mbox = *mboxes; mbox; mbox++)
    - if (!strcmp(mbox->name, name))
    + for (i = 0; (_mbox = mboxes[i]); i++) {
    + if (!strcmp(_mbox->name, name)) {
    + mbox = _mbox;
    break;
    + }
    + }

    if (!mbox)
    return ERR_PTR(-ENOENT);

  • Great!  I'm glad to hear the SysLink samples are working now.  I see you need the kernel patch when using gcc 4.6.3 to prevent the first kernel crash in omap_mbox_get().  The mem=169M is needed to prevent the DSP memory from being mapped into Linux memory, preventing the second crash you were getting.  And you also need to stop the firmware on the M3's.

    Best regards,

        Janet

  • Is there an plans to merge this patch back into the active branches? As far as I can see this is still broken in the latest kernel.

  • This patch is actually in the latest kernel (from the git tree), however, it still crash. The memory gets corrupted after the registration phase somehow.

    EDIT: Not it's not, I was looking in a more recent (vanilla) kernel tree. So to confirm, this patch is NOT in the top of the git tree for TI.

  • Yeah, it's not in the arago omap3 project yet. That also makes me wonder if there's any plans to merge this kernel back with upstream or if we're stuck with 2.6.37 for ever.