• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 488 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

DVSDK 4.02 for DM368IPNC

Anton Yabchinskiy

Hello.

Is it possible to make use of TI's DVSDK for DM368IPNC? Or it's only for EVM, and IPNC is incompatible with EVM?

I've tried to boot prebuilt kernel image ~/ti-dvsdk_dm368-evm_4_02_00_06/psp/prebuilt-images/uImage-dm368-evm.bin and it doesn't boot. All the output during boot is:

Loading from NAND 128MiB 3,3V 8-bit, offset 0x500000
   Image Name:   Arago/2.6.32.17-psp03.01.01.39/d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2148072 Bytes =  2 MB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Arago/2.6.32.17-psp03.01.01.39/d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2148072 Bytes =  2 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

And it hangs until rebooted. Bootargs are the following:

mem=48M console=ttyS1,115200n8 root=/dev/mtdblock3 rootfstype=cramfs

I've also tried ttyS0 as the console.

Yes, it probably panicked for some reason (unable to mount root), but I was expecting to see at least some printk()s (kernel version, etc.).

Also I've tried prebuilt kernel images from Arago project (http://arago-project.org/files/releases/davinci-psp_03.01.01.39/images/dm365-evm/uImage-dm365-evm.bin), with exactly the same result.

IPNC is that much incompatible to EVM? What could be done to add support for DM368IPNC to DVSDK and it's kernel?

DVSDK's approach to video streaming with it's GStreamer is much more pleasant and convenient, comparing to IPNC's av_capture, and I'd really like to use it.

  • 0
    Genius 3925 points

    Hope this helps:

    http://blog.sina.com.cn/s/blog_5e330a280100oowk.html

    let me know if you still have problems.

  • 0 in reply to Hongfeng Wang
    Genius 3475 points

    I made similar changes, but kept ubl and uboot from ipnc,

    Kernel:

    /psp/linux-2.6.32.17-psp03.01.01.38/arch/arm/mach-davinci/board-dm365-evm.c

    static __init void dm365_evm_init(void) {
    ....
      //dm365_init_spi0(BIT(0), dm365_evm_spi_info, ARRAY_SIZE(dm365_evm_spi_info));  //remove-comment out - SPI0 initialisation 
    }

    static struct davinci_uart_config uart_config __initdata = {
     //.enabled_uarts = (1 << 0),
     .enabled_uarts = (3 << 0), 
      };
    ___________________________________________________________________
    /psp/linux-2.6.32.17-psp03.01.01.38/arch/arm/mach-davinci/include/mach/serial.h
    //#define DAVINCI_UART1_BASE (IO_PHYS + 0x20400)
    #define DAVINCI_UART1_BASE (IO_PHYS + 0x106000)  //NEW
    ____________________________________________________________________

    Filesystem:

    filesys/etc/inittab
    //S:2345:respawn:/sbin/getty 115200 ttyS0
    S:2345:respawn:/sbin/getty 115200 ttyS1
    __________________________________________________________________________________________________

    Bootargs : console = ttyS1
    setenv bootcmd 'tftpboot 0x80700000 uImage; bootm 0x80700000'
    setenv bootargs 'console=ttyS1,115200n8 noinitrd ip=192.168.1.168:192.168.1.23:192.168.1.1:255.255.255.0:::off root=/dev/nfs rw nfsroot=192.168.1.33:/home/marko1/workdir/dvsdk_4/filesystem/filesys_dbg mem=60M video=davincifb:vid0=OFF:vid1=OFF:osd0=720x576x16,4050K dm365_imp.oper_mode=0 davinci_capture.device_type=1 earlyprintk'

  • 0 in reply to Hongfeng Wang

    Thanks. This does helps.

  • 0 in reply to Anton Yabchinskiy

    Now as I'm trying to boot from NAND I've encountered another issue. Kernel boots, but it's unable to mount root. There seems to be some issue with nand device.

    I have it enabled in kernel config:

    CONFIG_MTD_NAND_DAVINCI=y

    There is mtdparts in bootargs:

    root=/dev/mtdblock3 mtdparts=nand_davinci.0:3m(bootloader)ro,2m(params)ro,4m(kernel),24m(filesystem),2m(data1),-(data2)

    But there is nothing nand-related in dmesg. There is no errors, and it doesn't dump nand device layout. And finally:

    VFS: Cannot open root device "mtdblock3" or unknown-block(0,0)
    Please append a correct "root=" boot option; here are the available partitions:
    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

    Is it something wrong with kernel configuration?

    The config file is here: http://pastebin.com/FYYLai5n

    And here is the dmesg: http://pastebin.com/SC502jH8

  • 0 in reply to Hongfeng Wang

    Hongfeng Wang said:
    let me know if you still have problems.

    Could you please share your kernel configuration file?

  • 0 in reply to Anton Yabchinskiy
    Genius 3925 points

    My board doesn't have NAND at all, it boots from SD card only.