Linux forum - Recent Threads

RBL fail to start UBL, ask for symbol file of RBL

Jianjun Zhang — Fri, 14 Jun 2013 09:20:03 GMT

My custom DM6446 board fails to boot from NAND, only get BOOTME, similar to this post:http://e2e.ti.com/support/embedded/linux/f/354/t/52934.aspx

NAND chip is ONFI compliant MT29F1G08ABADAH4.

ubl and u-boot can be flashed in to NAND with NANDWriter.out or sfh_dm644x.exe.

Use slh_dm644x.exe to load ubl from DM644x_FlashAndBootUtils_2_0, successfully boot the u-boot in NAND.

I rebuild ubl and load & run it in IRAM with ccsv5, to make sure the chip is ONFI compliant.

Is there a symbol file of RBL to help debuging RBL in ccs?

Best Regards,

Zhang Jiajun

Linux- c6x- 2. 0- GA User Guide

Dr. Yehuda Singer — Thu, 13 Jun 2013 07:03:43 GMT

Dear all,

I try to program the EVM6678. We execute the command as described in the linux-c6x-2.0.0.63-users-guide page 6-7.

In any combination, I get an errror messgaeWho can help me?

Thanks

Yehuda

P.S.

Here is the response:

$DSS_SCRIPT_DIR/dss.sh program_evm.js evm6678l-le "eeprom51,nand"
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$
[Yehuda.Singer@Yehuda-LInux program_evm]$
[Yehuda.Singer@Yehuda-LInux program_evm]$
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js evm6678l-le "eeprom51,nand"
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR%/dss.sh program_evm.js evm6678l-le "eeprom50,eeprom51"
bash: /usr/local/bin/ti/ccsv5/ccs_base/scripting/bin%/dss.sh: No such file or directory
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js evm6678l-le "eeprom50,eeprom51"
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js EVM evm6678l-le "eeprom50,eeprom51"
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js EVM 6678l-le "eeprom50,eeprom51"
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js EVM 6678l-le
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js EVM 6678-le
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js TMDX EVM EVM 6678-le
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js TMDSEVM EVM 6678-le
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js TMDSEVM 6678-le
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ echo $DSS_SCRIPT_DIR
/usr/local/bin/ti/ccsv5/ccs_base/scripting/bin
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js evm6678l
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written
[Yehuda.Singer@Yehuda-LInux program_evm]$ $DSS_SCRIPT_DIR/dss.sh program_evm.js 6678l
Syntax error in command line
Syntax: program_evm.js [tmdx|tmds]evm[c](<device>)l[x][e][-le|-be] [images_to_write]
    tmdx: TMDX type EVM
    tmds: TMDS type EVM
    c: Not used, for backward compatibility
    <device> is the board name e.g 6472,6678 etc
    l: Low cost EVM
    x: EVM supports encryption
    e: EVM uses 560 Mezzanine Emulator daughter card
    le: Little Endian
    be: Big Endian
    example: TMDXEVM6678L-le
    [images_to_write] OPTIONAL is a list of the images to be written
    example: eeprom50,nor
    If not specified all (eeprom50,eeprom51,nand,nor) will be written

Putting the board into operation - how?

sviss — Sun, 16 Jun 2013 13:06:57 GMT

I want to put my (custom) Sitara AM335x board into operation at power up, automatically.

That is I need to start my console Linux application right after the system is started (Angstroom/Arago).

It is valued also that if at any time I activate my terminal connection I will have a prompt from my console app, be it a hardware UART TTY, or SSL network terminal - as initially configured for the application in question, at it's start.

How do I do that?

The internet is full of advises on "how do I log in automatically?" of a sort "you never should do that"

I do not think this is the best answer and I'd like to invite the Linux experts to share better ideas on this.

Of course, there is an option to write something like a kernel driver/network service and allow the user, after regular log in, connect with this service, from the terminal. Those who tried, know that this is not always an acceptable solution.

So, at minimum,

can I somehow skip the log in process (log in the user automatically after the Linux is started) from the specified terminal, so that to using the bash script of this console terminal, start my console application?

Or any better idea...

Thanks!

am1808 kernel build for sd card

Dan Rockwell — Wed, 06 Jun 2012 21:12:58 GMT

I have the following setting for a kernel build for an am1808. We are using NOR flash with the SD card on SD1 to avoid pinmux conflects. After building and downloading the kernel, I get the below messages (i.e. that follow the config settings). The SD card is partitioned with p1 = fat32 and p2= ext2.

Any suggestions on what I might be missing on the SD Card setup is greatly apprecaited.

CONFIG_MMC=y
CONFIG_MMC_DEBUG=y
# CONFIG_MMC_UNSAFE_RESUME is not set

#
# MMC/SD/SDIO Card Drivers
#
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_BOUNCE=y
# CONFIG_SDIO_UART is not set
# CONFIG_MMC_TEST is not set

#
# MMC/SD/SDIO Host Controller Drivers
#
CONFIG_MMC_SDHCI=y
# CONFIG_MMC_SDHCI_PLTFM is not set
# CONFIG_MMC_AT91 is not set
# CONFIG_MMC_ATMELMCI is not set
CONFIG_MMC_DAVINCI=y
# CONFIG_MMC_SPI is not set
CONFIG_MEMSTICK=y

mmc0: new high speed SD card at address 0002
mmcblk0: mmc0:0002 00000 1.86 GiB
mmcblk0:
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
mmcblk0: retrying using single block read
mmcblk0: error -84 transferring data, sector 0, nr 8, card status 0x900
end_request: I/O error, dev mmcblk0, sector 0
mmcblk0: error -84 transferring data, sector 1, nr 7, card status 0x900
end_request: I/O error, dev mmcblk0, sector 1
mmcblk0: error -84 transferring data, sector 2, nr 6, card status 0x900
end_request: I/O error, dev mmcblk0, sector 2
mmcblk0: error -84 transferring data, sector 3, nr 5, card status 0x900
end_request: I/O error, dev mmcblk0, sector 3
mmcblk0: error -84 transferring data, sector 4, nr 4, card status 0x900
end_request: I/O error, dev mmcblk0, sector 4
mmcblk0: error -84 transferring data, sector 5, nr 3, card status 0x900
end_request: I/O error, dev mmcblk0, sector 5
mmcblk0: error -84 transferring data, sector 6, nr 2, card status 0x900
end_request: I/O error, dev mmcblk0, sector 6
mmcblk0: error -84 transferring data, sector 7, nr 1, card status 0x900
end_request: I/O error, dev mmcblk0, sector 7
Buffer I/O error on device mmcblk0, logical block 0
unable to read partition table

DM8168 EVM can’t boot from NAND flash

Hong Gao1 — Thu, 13 Jun 2013 19:37:25 GMT

I just purchased a new DM8168 EVM, it works with SD card properly, but it can’t boot from NAND flash.

I checked NAND flash with u-boot program, it can’t find NAND device.

I have set NAND selection switch (SW4) in different states (ON/OFF), there is no response for the NAND operation.

We have tried to use the u-boot to test it,t, but it failed to read/write/detect the NAND flash.

I have reopen NAND flash socket, remounted the NAND flash carefully. It does not work.

There is no stock in digikey and arrow for the NAND flash (29F2G16ABAEA).

I believe it is the hardware problem on the board. (NAND flash, socket, pcb trace..?).

Could you replace this EVM for me?

Other suggestions?

Regards,

Hong

SW4 NAND-on:

U-Boot 2010.06 (Apr 29 2012 - 20:35:23)

DRAM: 2 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

Hit any key to stop autoboot: 0
raise: Signal # 8 caught
reading u-boot.bin

210312 bytes read
## Starting application at 0x80800000 ...


U-Boot 2010.06 (Apr 29 2012 - 20:28:20)

TI8168-GP rev 2.1

ARM clk: 987MHz
DDR clk: 796MHz

I2C:   ready
DRAM: 2 GiB
NAND: HW ECC BCH8 Selected
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC or NAND, using default environment

SW4 NAND-off:

U-Boot 2010.06 (Apr 29 2012 - 20:35:23)

DRAM: 2 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

Hit any key to stop autoboot: 0
raise: Signal # 8 caught
reading u-boot.bin

210312 bytes read
## Starting application at 0x80800000 ...


U-Boot 2010.06 (Apr 29 2012 - 20:28:20)

TI8168-GP rev 2.1

ARM clk: 987MHz
DDR clk: 796MHz

I2C:   ready
DRAM: 2 GiB
NAND: HW ECC BCH8 Selected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-b)
NAND bus width 8 instead 16 bit
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0
*** Warning - bad CRC or NAND, using default environment

PAL display on dm368??

enigma pwd — Mon, 17 Jun 2013 09:13:01 GMT

hello:

i want to use "PAL" display on lcd screen, the progress is as below:

image input(PAL) --> video decoder(tvp 5158) --> dm368 --> PAL output --> lcd screen.

but there is no signal output to screen, i typed the commend: echo "PAL" > /sys/class/davinci_display/ch0/mode,

and the mode will be changed from "NTSC" to "PAL", then the screen showed nothing(black), the indicator of lcd is becoming light(that means no input signal ).

when i typed the commend again to change the mode from "PAL" to "NTSC" , there are image output as usual.

does someone know why there are no PAL output signal?? are there something wrong on my way??

any advice will be very appreciate ~ thank you very much!!

Kernel Hangs after u-boot at "starting kernel..."

Prakash Divate — Fri, 14 Jun 2013 11:14:29 GMT

Hi,

We are working on our custom board based on omap 4430. We are trying to bring up android jelly bean 4.2.5p1 on it.

We were successfully able to build x-loader , u-boot and kernel for our board. x-loader and u-boot boot up on the board without any problem however there seems to be an issue with the kernel. As soon as the u-boot tries to load the kernel, it hangs without any further message.

Below is the log, the bootargs used can be seen at the u-boot:

@ @ @D(�` @ @ @k��H��U��.HR�.]�][Y��s Inc X-Loader 1.41.0-gdd880470-dirty (Jun 14 2013 - 13:00:28)
mmc read: Invalid size
Starting OS Bootloader from MMC/SD1 ...

U-Boot 1.1.4-g622fcfe5-dirty (Jun 14 2013 - 12:58:39)

Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment

In:    serial
Out:   serial
Err:   serial
Battery not detected
status[initDisplay]: Probing 0x0b success..
Initializing SD(0) Slot.
ptbl slot: SD:(0).
efi partition table not found
efi partition table:
ptbl slot: EMMC:(1).
     256     128K xloader
     512       3M bootloader
    6656     128K misc
    7680     128K serialno
    7936      16M efs
   40704      16K crypto
   40736       8M recovery
   57120       8M boot
   73504     512M system
1122080     256M cache
1646368     512M userdata
Net:   KS8851SNL
Hit any key to stop autoboot: 0
OMAP4 GOLDENI #
OMAP4 GOLDENI #
OMAP4 GOLDENI #
OMAP4 GOLDENI # setenv bootargs console=ttyO2,115200n8 root=/dev/mmcblk0p2 rootdelay=2 init=/init vram="32M" omapfb.vram="0:32M" rootfstype=ext3
OMAP4 GOLDENI # mmcinit 0; fatload mmc 0 0x80500000 uImage; bootm 0x80500000
mmc read: Invalid size

3519592 bytes read
## Booting image at 80500000 ...
   Image Name:   Linux-3.4.34-01535-g499e8d5-dirt
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3519528 Bytes = 3.4 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
OK
I2C read: I/O error

Starting kernel ...

After this it goes blank.

The mach id used is same at the u-boot and kernel.

I have enabled early_printk in the kernel, but still no luck.

Could someone help on this?

Thank You

Prakash

What could you offer to improve DVSDK?

Constantine — Sun, 05 Sep 2010 18:19:18 GMT

What could you offer to improve DVSDK after your experience with latest DVSDK releases?

Problem with WDT on DM8148

lu yuenjune — Mon, 17 Jun 2013 09:12:21 GMT

Hi Sir :

I work on DM8148 platform and use DVRRDK_03.00.00.00 to develop our system.

Now, I try to test watchdog function and use scope to measure RSTOUT_WD_OUT.

I refer the link below and write a test program.

http://www.deyisupport.com/question_answer/dsp_arm/davinci_digital_media_processors/f/39/t/23557.aspx

When I execute the program, the system did reboot when watchdog overflow, but RSTOUT_WD_OUT is always high.

I have checked the value of PINCNTL262 and it is 0x50001.

Could you give me some suggestion?

Best regards,

Marcus

Cannot build with CCS running on Linux

Geoffrey Tam — Thu, 13 Jun 2013 18:08:11 GMT

I am following the instructions from the example for the BIOS MCSDK user guide (http://processors.wiki.ti.com/index.php/BIOS_MCSDK_2.0_User_Guide#Example_3_-_Running_from_external_memory_.28DDR.29).

I can successfully build the project when CCS is run from Windows by right clicking on the project name, and selecting “Build Project”. When I try the same from the Linux version of CCS, the build console shows the following:

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

/opt/ti/ccsv5/utils/bin/gmake -k all

Cannot run program "/opt/ti/ccsv5/utils/bin/gmake": Unknown reason

Error: Program "/opt/ti/ccsv5/utils/bin/gmake" not found in PATH

PATH=[/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games]

Error: Program "/opt/ti/ccsv5/utils/bin/gmake" is not found in PATH

PATH=[/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games]

**** Build Finished ****

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

I verified that /opt/ti/ccsv5/utils/bin/gmake actually exists, and it does.

It should be noted that in step 5, when adding to the "Project->Properties->Build->C6000 linker->File Search Path" window in the Linux CCS, I used both "${TI_PDK_C6678_INSTALL_DIR}/packages/ti/platform/evmc6678l/platform_lib/lib/debug" and "/opt/ti/pdk_C6678_1_1_2_6/packages/ti/platform/evmc6678l/platform_lib/lib/debug". Neither of these work.

In the Windows CCS, I use "${TI_PDK_C6678_INSTALL_DIR}/packages/ti/platform/evmc6678l/platform_lib/lib/debug" in the "File search path". The project build succeeds.

It should also be noted that if I use "/opt/ti/ccsv5/eclipse/eclipse -noSplash -data /home/evertz/workspace_v5_3/ -application com.ti.ccstudio.apps.projectBuild -ccs.projects led_play_ddr3 -ccs.configuration Debug" from the command line, with "/opt/ti/..." in the "File search path", I get the following:

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

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Jun 13 13:56:34 EDT 2013]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...

================================================================================
Building...

**** Build of configuration Debug for project led_play_ddr3 ****

/opt/ti/ccsv5/utils/bin/gmake -k all
Building file: ../led_play_ddr3.cfg
Invoking: XDCtools
"/opt/ti/xdctools_3_24_05_48/xs" --xdcpath="/opt/ti/ccsv5/ccs_base;/opt/ti/bios_6_34_02_18/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r debug -c "/opt/ti/ccsv5/tools/compiler/c6000_7.4.1" "../led_play_ddr3.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring led_play_ddr3.xe66 from package/cfg/led_play_ddr3_pe66.cfg ...
Killed
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I am using the following Linux distro: Ubuntu 10.04LTS. According to http://processors.wiki.ti.com/index.php/BIOS_MCSDK_2.0_Getting_Started_Guide#Run_the_Installer_.26_Provide_the_installation_path, Ubuntu Linux is supported.

SysLink and linux SDK

Bethany Allik — Wed, 12 Jun 2013 21:02:12 GMT

I am currently running the TI linux SDK (http://www.ti.com/tool/linuxezsdk-sitara) matrix on my Beagleboardxm. I would like to write some programs to do matrix math using the onboard DSP and read that Syslink is currently actively supported by TI. How do I port Syslink to the linux SDK? I'm unsure how Syslink examples would be run even on differing platforms.

Is there a resizer example for DM365?

YJ Liu — Fri, 14 Jun 2013 11:34:16 GMT

Hi,Guys:

Device is DM365, DVSDK-demos is 4.0.0.21, DMAI is 2.2.0.14 .

Since no one response for my post : http://e2e.ti.com/support/embedded/linux/f/354/t/268935.aspx

So I try to know is there a app example about resizer within DM365?

Because in dvsdk, the app "video_loopback_resize()" will not built for DM365, dose it not support?

secure boot for omap 3530

Sreelakshmi Radhakrishnan — Fri, 14 Jun 2013 10:52:20 GMT

Hi all,

I am relatively new to Linux environment.

Does TI offer support for enabling secure boot on OMAP 3530?

A means of verifying that the code that boots up is the same as intended and ensuring that it is not changed/modified.

Thanks

Sreelakshmi R

DM6467+TVP5158+MJPEG strategy help

blake d — Thu, 23 May 2013 18:17:26 GMT

Hello,

I'd just like to point out that I'm a complete newbie when it comes to this stuff, so please bear with me.

I've installed DVSDK 3.10 and I've successfully ran the demos included on the board. My main goal is to get input from the TVP5158 and turn it into a mjpeg. I just wanted a sanity check to make sure that I understand what I need to do to start using an mjpeg codec.

I've downloaded the JPEG Encoder, Version 2.00.01.00 from http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C64XPlus_Video/index_FDS.html. Is this the right thing for the job?

How do I get to a point where I can start developing using the API from the JPEG encoder? Do I need to install a codec server?

Sorry if these questions have very obvious answers.

Thank you in advance.

DM368 video get paused and go on

XIONG Zhihui — Thu, 13 Jun 2013 14:33:45 GMT

Hi all

I am using Appro DM368 IPNC 3.0 SDK, it works fine when I enabled only RTSP IE preview.

However, when I enable both the SD card recording and RTSP IE preview, the camera works well at the beginning, but after its continuous work at about 1 or 2 days, the video in SD card & IE preview becomes get paused and go on (which means the video looks like stops for a short while, and then skips to current frame)

I the UART output, we sam some following messages:

RET_OVERWRITE

Could you give some suggestions on this ?

BTW: the DDR size is 128MB, and 48MB for ARM Linux, 80MB for DSP encoder. And the Mem layout is following:

.profiles[VIDOE_INFO_MP4] =

{

.cache_size = 0xb00000,

.cache_blk_size = (100*1024),

.mem_size = 0x500000,

.mem_blk_size = (100*1024),

.ext_size = MP4_1_EXTRA_SIZE,

How to create applications

blake d — Tue, 11 Jun 2013 19:12:03 GMT

After much frustration with trying to edit the demos to use the jpeg codec, I've decided to take a stab to write my own application to hopefully better understand everything and what I'm doing wrong. However, I am unable to understand how I would create my own dmai application and build it.

There's documentation on how to make a simple app here, but that doesn't help me use any of the tools included in the sdk.

Maybe this is obvious for some, but as someone completely new to davinci development, I have no idea what I'm doing. I've been trying to hack together my own makefile based on the makefiles use to compile and link the demos. I've also tried to search for this on forums, in doc folders, etc, but it just seems really odd to me that there isn't more documentation. I can only assume that I'm just missing something. I mean, not everyone is just trying to hack the demos are they?

Any input/direction/anything would be greatly appreciated.

I have the dm6467T EVM and dvsdk 3.10.00.19 installed.

using remoteproc without DSP/BIOS

Jouko Nikula — Thu, 13 Jun 2013 10:12:58 GMT

Is it possible to use Linux remoteproc to load and start dsp sw if there is no OS on DSP? We are using OMAP-L138.

Segfault when trying to get GST_DEBUG=omx: ...

Johny Bui — Fri, 26 Apr 2013 18:47:19 GMT

Hi Guys,

Wonder if anyone see this problem and know how to solve it? I want to get some debug info for omx component when streaming camera using playbin2 but when ever setting gst-debug=omx it segfault. the stream works fine without setting gst-debug=omx. Any help would be great.

Thanks,

Johny.

gst-launch playbin2 uri=rtsp://192.168.1.109:554/Video-0 --gst-debug=*omx*:1

Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Missing element: GStreamer element stridetransform
WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0: Missing element 'stridetransform' - check your GStreamer installation.
Additional debug info:
gstplaysink.c(1348): gen_video_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0:
video rendering might fail
Segmentation fault

gst-launch playbin2 uri=rtsp://192.168.1.109:554/Video-0 --gst-debug=*omx*:2
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Missing element: GStreamer element stridetransform
WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0: Missing element 'stridetransform' - check your GStreamer installation.
Additional debug info:
gstplaysink.c(1348): gen_video_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0:
video rendering might fail
0:00:02.997597150 3715 0x11d1b0 WARN omx gstomx_base_filter.c:832:buffer_alloc:<omxh264dec0> faking settings changed notification
Segmentation fault

gst-launch playbin2 uri=rtsp://192.168.1.109:554/Video-0 --gst-debug=*omx*:3
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
0:00:01.720704300 3744 0x1213c8 INFO omx gstomx_videomixer.c:2183:init_interfaces: GstChildProxy interface registered
0:00:01.724057100 3744 0x1213c8 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state NULL -> READY
0:00:02.850974750 3744 0x1213c8 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state READY -> PAUSE
D
0:00:02.860297950 3744 0x1213c8 INFO omx gstomx_base_filter.c:690:pad_event:<omxh264dec0> begin: event=newsegment
Missing element: GStreamer element stridetransform
WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0: Missing element 'stridetransform' - check your GStreamer installation.
Additional debug info:
gstplaysink.c(1348): gen_video_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0:
video rendering might fail
0:00:03.635538050 3744 0x1213c8 INFO omx gstomx_base_videodec.c:140:sink_setcaps:<omxh264dec0> setcaps (sink): 0x164440
0:00:03.635910700 3744 0x1213c8 INFO omx gstomx_h264dec.c:93:initialize_port:<omxh264dec0> begin
0:00:03.638602350 3744 0x1213c8 INFO omx gstomx_h264dec.c:136:initialize_port:<omxh264dec0> end
0:00:03.640138450 3744 0x1213c8 INFO omx gstomx_base_filter.c:555:pad_chain:<omxh264dec0> omx: prepare
0:00:03.640242600 3744 0x1213c8 INFO omx gstomx_base_videodec.c:451:omx_setup:<omxh264dec0> begin
0:00:03.641132500 3744 0x1213c8 INFO omx gstomx_base_videodec.c:465:omx_setup:<omxh264dec0> end
0:00:03.655354850 3744 0x1213c8 WARN omx gstomx_base_filter.c:832:buffer_alloc:<omxh264dec0> faking settings changed notification
0:00:03.656067450 3744 0x1213c8 INFO omx gstomx_base_videodec.c:117:settings_changed_cb:<omxh264dec0> caps are: 0x1646e0
0:00:03.656162700 3744 0x1213c8 INFO omx gstomx_base_videodec.c:118:settings_changed_cb:<omxh264dec0> old caps are: (nil)
0:00:03.656252650 3744 0x1213c8 INFO omx gstomx_base_videodec.c:338:src_setcaps:<omxh264dec0> setcaps (src): 0x1646e0
0:00:03.662394950 3744 0x1213c8 INFO omx gstomx_base_videodec.c:362:src_setcaps:<omxh264dec0> G_OMX_PORT_SET_DEFINITION
Segmentation fault

gst-launch playbin2 uri=rtsp://192.168.1.109:554/Video-0 --gst-debug=*omx*:4
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
0:00:01.627636850 3775 0x1226e0 INFO omx gstomx_videomixer.c:2183:init_interfaces: GstChildProxy interface registered
0:00:01.630733150 3775 0x1226e0 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state NULL -> READY
0:00:01.630902200 3775 0x1226e0 DEBUG omx gstomx_core.c:217:g_omx_core_init:<omxh264dec0> loading: OMX.TI.DUCATI.VIDDEC (libOMX_C
ore.so)
0:00:01.631475700 3775 0x1226e0 DEBUG omx gstomx_util.c:57:imp_new: dlopen(libOMX_Core.so) -> 0x169d50
0:00:02.767897700 3775 0x1226e0 DEBUG omx gstomx_core.c:239:g_omx_core_init:<omxh264dec0> OMX_GetHandle(&0x181f60) -> None
0:00:02.768125100 3775 0x1226e0 DEBUG omx gstomx_core.c:248:g_omx_core_init:<omxh264dec0> setting component role:
0:00:02.769847850 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.769980250 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.771759450 3775 0x1226e0 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state READY -> PAUSE
D
0:00:02.771900900 3775 0x1226e0 DEBUG omx gstomx_base_filter.c:767:activate_push:<omxh264dec0> activate
0:00:02.795574800 3775 0x1226e0 INFO omx gstomx_base_filter.c:690:pad_event:<omxh264dec0> begin: event=newsegment
0:00:02.797313050 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.797420300 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.799644000 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.799767350 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.812631200 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x449a50fc
0:00:02.812761500 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x449a50fc
Missing element: GStreamer element stridetransform
WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0: Missing element 'stridetransform' - check your GStreamer installation.
Additional debug info:
gstplaysink.c(1348): gen_video_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0:
video rendering might fail
0:00:02.959935300 3775 0x1226e0 INFO omx gstomx_base_videodec.c:140:sink_setcaps:<omxh264dec0> setcaps (sink): 0x1703c0
0:00:02.960121800 3775 0x1226e0 INFO omx gstomx_h264dec.c:93:initialize_port:<omxh264dec0> begin
0:00:02.960204150 3775 0x1226e0 DEBUG omx gstomx_h264dec.c:95:initialize_port:<omxh264dec0> G_OMX_PORT_GET_DEFINITION (output)
0:00:02.960930800 3775 0x1226e0 DEBUG omx gstomx_h264dec.c:111:initialize_port:<omxh264dec0> nFrameWidth = 1280, nFrameHeight = 72
0, nBufferCountActual = 8
0:00:02.961037600 3775 0x1226e0 DEBUG omx gstomx_h264dec.c:113:initialize_port:<omxh264dec0> G_OMX_PORT_SET_DEFINITION (output)
0:00:02.961784850 3775 0x1226e0 INFO omx gstomx_h264dec.c:136:initialize_port:<omxh264dec0> end
0:00:02.962623300 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:219:sink_setcaps:<omxh264dec0> G_OMX_PORT_SET_DEFINITION
0:00:02.962833950 3775 0x1226e0 DEBUG omx gstomx_base_filter.c:535:pad_chain:<omxh264dec0> buf=0x192490 (time=0:00:01.138618200, d
uration=99:99:99.999999999, flags=00000020, size=34127)
0:00:02.962987650 3775 0x1226e0 INFO omx gstomx_base_filter.c:555:pad_chain:<omxh264dec0> omx: prepare
0:00:02.963066850 3775 0x1226e0 INFO omx gstomx_base_videodec.c:451:omx_setup:<omxh264dec0> begin
0:00:02.986663900 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:462:omx_setup:<omxh264dec0> G_OMX_PORT_SET_DEFINITION 1!!!
0:00:02.986960350 3775 0x1226e0 INFO omx gstomx_base_videodec.c:465:omx_setup:<omxh264dec0> end
0:00:02.987615100 3775 0x1226e0 DEBUG omx gstomx_port.c:128:g_omx_port_setup: <omxh264dec0:in:0> type=0, num_buffers=4, port_index
=0
0:00:02.988202650 3775 0x1226e0 DEBUG omx gstomx_port.c:128:g_omx_port_setup: <omxh264dec0:out:1> type=1, num_buffers=8, port_inde
x=1
0:00:02.988313000 3775 0x1226e0 DEBUG omx gstomx_base_filter.c:90:setup_ports:<omxh264dec0> in_port->omx_allocate=1, out_port->omx
_allocate=1
0:00:02.988394450 3775 0x1226e0 DEBUG omx gstomx_base_filter.c:92:setup_ports:<omxh264dec0> in_port->share_buffer=0, out_port->sha
re_buffer=0
0:00:02.988488200 3775 0x1226e0 DEBUG omx gstomx_core.c:323:g_omx_core_prepare:<omxh264dec0> begin
0:00:02.988562150 3775 0x1226e0 DEBUG omx gstomx_port.c:165:g_omx_port_prepare: <omxh264dec0:in:0> begin
0:00:02.989507950 3775 0x1226e0 DEBUG omx gstomx_port.c:206:g_omx_port_prepare: <omxh264dec0:in:0> end
0:00:02.989600650 3775 0x1226e0 DEBUG omx gstomx_port.c:165:g_omx_port_prepare: <omxh264dec0:out:1> begin
0:00:02.990053450 3775 0x1226e0 WARN omx gstomx_base_filter.c:832:buffer_alloc:<omxh264dec0> faking settings changed notification
0:00:02.990140150 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:105:settings_changed_cb:<omxh264dec0> settings changed
0:00:02.990694050 3775 0x1226e0 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0xf6440
0:00:02.990936600 3775 0x1226e0 INFO omx gstomx_base_videodec.c:117:settings_changed_cb:<omxh264dec0> caps are: 0xf64c0
0:00:03.327558200 3775 0x1226e0 INFO omx gstomx_base_videodec.c:118:settings_changed_cb:<omxh264dec0> old caps are: (nil)
0:00:03.327724500 3775 0x1226e0 INFO omx gstomx_base_videodec.c:338:src_setcaps:<omxh264dec0> setcaps (src): 0xf64c0
0:00:03.329105650 3775 0x1226e0 INFO omx gstomx_base_videodec.c:362:src_setcaps:<omxh264dec0> G_OMX_PORT_SET_DEFINITION
0:00:03.330378200 3775 0x1226e0 DEBUG omx gstomx_port.c:206:g_omx_port_prepare: <omxh264dec0:out:1> end
0:00:03.330496450 3775 0x1226e0 DEBUG omx gstomx_core.c:471:change_state:<omxh264dec0> state=2
0:00:03.331508600 3775 0x1226e0 DEBUG omx gstomx_port.c:220:g_omx_port_allocate_buffers: <omxh264dec0:in:0> begin
0:00:03.332038150 3775 0x1226e0 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 0: OMX_AllocateBuffer(
), size=921600
0:00:03.334615000 3775 0x1226e0 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 1: OMX_AllocateBuffer(
), size=921600
0:00:03.335463300 3775 0x1226e0 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 2: OMX_AllocateBuffer(
), size=921600
Segmentation fault

gst-launch playbin2 uri=rtsp://192.168.1.109:554/Video-0 --gst-debug=*omx*:5
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
0:00:01.815963400 3795 0x150e20 INFO omx gstomx_videomixer.c:2183:init_interfaces: GstChildProxy interface registered
0:00:01.818172250 3795 0x150e20 LOG omx gstomx_base_filter.c:866:type_instance_init:<GstOmxBaseFilter@0x151718> begin
0:00:01.819201300 3795 0x150e20 LOG omx gstomx_base_filter.c:902:type_instance_init:<GstOmxBaseFilter@0x151718> end
0:00:01.819979850 3795 0x150e20 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state NULL -> READY
0:00:01.820136450 3795 0x150e20 DEBUG omx gstomx_core.c:217:g_omx_core_init:<omxh264dec0> loading: OMX.TI.DUCATI.VIDDEC (libOMX_C
ore.so)
0:00:01.820761550 3795 0x150e20 DEBUG omx gstomx_util.c:57:imp_new: dlopen(libOMX_Core.so) -> 0x16aa88
0:00:03.003281000 3795 0x150e20 DEBUG omx gstomx_core.c:239:g_omx_core_init:<omxh264dec0> OMX_GetHandle(&0x1765b0) -> None
0:00:03.003506850 3795 0x150e20 DEBUG omx gstomx_core.c:248:g_omx_core_init:<omxh264dec0> setting component role:
0:00:03.004598300 3795 0x150e20 LOG omx gstomx_base_filter.c:204:change_state:<omxh264dec0> end
0:00:03.004994900 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.005082350 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.007150800 3795 0x150e20 INFO omx gstomx_base_filter.c:150:change_state:<omxh264dec0> begin: changing state READY -> PAUSE
D
0:00:03.007303850 3795 0x150e20 DEBUG omx gstomx_base_filter.c:767:activate_push:<omxh264dec0> activate
0:00:03.007415050 3795 0x150e20 LOG omx gstomx_base_filter.c:204:change_state:<omxh264dec0> end
0:00:03.086922100 3795 0x150e20 INFO omx gstomx_base_filter.c:690:pad_event:<omxh264dec0> begin: event=newsegment
0:00:03.099371200 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.099513100 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.101791300 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.101896750 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.143383400 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:314:src_getcaps:<omxh264dec0> caps=0x461af0fc
0:00:03.143527100 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x461af0fc
Missing element: GStreamer element stridetransform
WARNING: from element /GstPlayBin2:playbin20/GstPlaySink:playsink0: Missing element 'stridetransform' - check your GStreamer installation.
Additional debug info:
gstplaysink.c(1348): gen_video_chain (): /GstPlayBin2:playbin20/GstPlaySink:playsink0:
video rendering might fail
0:00:03.372456750 3795 0x150e20 LOG omx gstomx_base_filter.c:751:pad_event:<omxh264dec0> end
0:00:03.374321850 3795 0x150e20 INFO omx gstomx_base_videodec.c:140:sink_setcaps:<omxh264dec0> setcaps (sink): 0x16bee0
0:00:03.374465950 3795 0x150e20 INFO omx gstomx_h264dec.c:93:initialize_port:<omxh264dec0> begin
0:00:03.374544650 3795 0x150e20 DEBUG omx gstomx_h264dec.c:95:initialize_port:<omxh264dec0> G_OMX_PORT_GET_DEFINITION (output)
0:00:03.376938600 3795 0x150e20 DEBUG omx gstomx_h264dec.c:111:initialize_port:<omxh264dec0> nFrameWidth = 1280, nFrameHeight = 72
0, nBufferCountActual = 8
0:00:03.377055050 3795 0x150e20 DEBUG omx gstomx_h264dec.c:113:initialize_port:<omxh264dec0> G_OMX_PORT_SET_DEFINITION (output)
0:00:03.378504850 3795 0x150e20 INFO omx gstomx_h264dec.c:136:initialize_port:<omxh264dec0> end
0:00:03.379332950 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:219:sink_setcaps:<omxh264dec0> G_OMX_PORT_SET_DEFINITION
0:00:03.379574900 3795 0x150e20 DEBUG omx gstomx_base_filter.c:535:pad_chain:<omxh264dec0> buf=0x17d5c8 (time=0:00:01.427599000, d
uration=99:99:99.999999999, flags=00000020, size=25503)
0:00:03.379698650 3795 0x150e20 LOG omx gstomx_base_filter.c:549:pad_chain:<omxh264dec0> begin: size=25503, state=1
0:00:03.379778350 3795 0x150e20 INFO omx gstomx_base_filter.c:555:pad_chain:<omxh264dec0> omx: prepare
0:00:03.379850600 3795 0x150e20 INFO omx gstomx_base_videodec.c:451:omx_setup:<omxh264dec0> begin
0:00:03.380648350 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:462:omx_setup:<omxh264dec0> G_OMX_PORT_SET_DEFINITION 1!!!
0:00:03.380736900 3795 0x150e20 INFO omx gstomx_base_videodec.c:465:omx_setup:<omxh264dec0> end
0:00:03.381256400 3795 0x150e20 DEBUG omx gstomx_port.c:128:g_omx_port_setup: <omxh264dec0:in:0> type=0, num_buffers=4, port_index
=0
0:00:03.381702750 3795 0x150e20 DEBUG omx gstomx_port.c:128:g_omx_port_setup: <omxh264dec0:out:1> type=1, num_buffers=8, port_inde
x=1
0:00:03.381808000 3795 0x150e20 DEBUG omx gstomx_base_filter.c:90:setup_ports:<omxh264dec0> in_port->omx_allocate=1, out_port->omx
_allocate=1
0:00:03.381889800 3795 0x150e20 DEBUG omx gstomx_base_filter.c:92:setup_ports:<omxh264dec0> in_port->share_buffer=0, out_port->sha
re_buffer=0
0:00:03.381981350 3795 0x150e20 DEBUG omx gstomx_core.c:323:g_omx_core_prepare:<omxh264dec0> begin
0:00:03.382054800 3795 0x150e20 DEBUG omx gstomx_port.c:165:g_omx_port_prepare: <omxh264dec0:in:0> begin
0:00:03.383064200 3795 0x150e20 DEBUG omx gstomx_port.c:206:g_omx_port_prepare: <omxh264dec0:in:0> end
0:00:03.383153900 3795 0x150e20 DEBUG omx gstomx_port.c:165:g_omx_port_prepare: <omxh264dec0:out:1> begin
0:00:03.383626950 3795 0x150e20 WARN omx gstomx_base_filter.c:832:buffer_alloc:<omxh264dec0> faking settings changed notification
0:00:03.383718400 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:105:settings_changed_cb:<omxh264dec0> settings changed
0:00:03.384254750 3795 0x150e20 DEBUG omx gstomx_base_videodec.c:321:src_getcaps:<omxh264dec0> caps=0x1a08e0
0:00:03.721766850 3795 0x150e20 INFO omx gstomx_base_videodec.c:117:settings_changed_cb:<omxh264dec0> caps are: 0x16c360
0:00:03.721898250 3795 0x150e20 INFO omx gstomx_base_videodec.c:118:settings_changed_cb:<omxh264dec0> old caps are: (nil)
0:00:03.721993750 3795 0x150e20 INFO omx gstomx_base_videodec.c:338:src_setcaps:<omxh264dec0> setcaps (src): 0x16c360
0:00:03.723206000 3795 0x150e20 INFO omx gstomx_base_videodec.c:362:src_setcaps:<omxh264dec0> G_OMX_PORT_SET_DEFINITION
0:00:03.724638000 3795 0x150e20 DEBUG omx gstomx_port.c:206:g_omx_port_prepare: <omxh264dec0:out:1> end
0:00:03.724763050 3795 0x150e20 DEBUG omx gstomx_core.c:471:change_state:<omxh264dec0> state=2
0:00:03.725618050 3795 0x150e20 DEBUG omx gstomx_port.c:220:g_omx_port_allocate_buffers: <omxh264dec0:in:0> begin
0:00:03.726097700 3795 0x150e20 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 0: OMX_AllocateBuffer(
), size=921600
0:00:03.728645950 3795 0x150e20 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 1: OMX_AllocateBuffer(
), size=921600
0:00:03.729474500 3795 0x150e20 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 2: OMX_AllocateBuffer(
), size=921600
0:00:03.730310600 3795 0x150e20 DEBUG omx gstomx_port.c:233:g_omx_port_allocate_buffers: <omxh264dec0:in:0> 3: OMX_AllocateBuffer(
), size=921600
Segmentation fault

DM 8148 ( J5 ECO ) EVM Unable to do video playback using gstreamer

Venkatesh Raikar — Wed, 08 May 2013 17:22:15 GMT

Hi All,

Am working on a gstreamer app to playback video, the hardware is J5 ECO EVM ( DM 8148 )

before i start the gstreamer app i wanted to test the video playback using gst-launch . hence i tried the following command :

gst-launch filesrc location= audioVideo.mp4 ! qtdemux name=mux mux.video_00 ! queue  ! h264parse output-format=1 ! omx_h264dec ! omx_mdeiscaler name=d d.src_00 !  'video/x-raw-yuv, width=(int)800, height=(int)480'  ! omx_ctrl  display-mode=OMX_DC_MODE_1080P_30 display-device=LCD !  omx_videosink display-device=LCD enable-last-buffer=false mux.audio_00 ! queue ! omx_aacdec ! alsasink d.src_01  ! fakesink silent=true -v

which i got from the link https://developer.ridgerun.com/wiki/index.php/Gstreamer_pipelines_for_DM816x_and_DM814x

When i execute the command i get the following error :

(gst-launch-0.10:1444): GStreamer-CRITICAL **: pad omxaacdec0:sink returned NULL caps from getcaps function

(gst-launch-0.10:1444): GStreamer-CRITICAL **: pad omxaacdec0:src returned NULL caps from getcaps function

I just started to work on this TI board i have no idea what setup i need to make to get the gstreamer output on the LCD.

Can you please let me know what is the simplest pipeline that i should be using to test a playback of a mp4/mov/avi file gstreamer on LCD display of EVM ?? ( audio & video)

my end goal is to get the video playback done on a Qt Widget window , has anyone tried it on this board any inputs or links will be highly appreciated.

( i have checked that the LCD screen works - the matrix gui runs fine )

Thanks

Regarding clocking ARM at 1.2 GHz on Netra 816x

Sudeep Hegde — Thu, 13 Jun 2013 06:57:26 GMT

Hi,

I learn that the ARM core is configured to run at 1 GHz (987MHz) by default in the u-boot and the TI816X can support ARM running at 1GHz and 1.2 GHz

Please let me know as how to configure the Arm Cortex A8 to 1.2 GHz, we are using linux-2.6.37-psp04.04.00.01 kernel.

Regards,

Sudeep

Regarding clocking ARM at 1.2 GHz on Netra 816x

Sudeep Hegde — Thu, 13 Jun 2013 06:57:10 GMT

Hi,

I learn that the ARM core is configured to run at 1 GHz (987MHz) by default in the u-boot and the TI816X can support ARM running at 1GHz and 1.2 GHz

Please let me know as how to configure the Arm Cortex A8 to 1.2 GHz, we are using linux-2.6.37-psp04.04.00.01 kernel.

Regards,

Sudeep

a question in ti81xxvin_vps_config_format() from ti81xxvin_main.c

Dillon — Sat, 08 Jun 2013 03:55:31 GMT

if (inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_ANY ||
inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_NONE ||
inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_INTERLACED) {
fvid2_fmt.fieldmerged[0] = 1;
fvid2_fmt.fieldmerged[0] = 1;
fvid2_fmt.fieldmerged[0] = 1;
} else {
fvid2_fmt.fieldmerged[0] = 0;
fvid2_fmt.fieldmerged[0] = 0;
fvid2_fmt.fieldmerged[0] = 0;
}

i can't make sure this code is correct , why set three times on fvid2_fmt.fieldmerged[0], i think it's should be

if (inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_ANY ||
inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_NONE ||
inst->buf_obj.fmt.fmt.pix.field == V4L2_FIELD_INTERLACED) {
fvid2_fmt.fieldmerged[0] = 1;
fvid2_fmt.fieldmerged[1] = 1;
fvid2_fmt.fieldmerged[2] = 1;
} else {
fvid2_fmt.fieldmerged[0] = 0;
fvid2_fmt.fieldmerged[1] = 0;
fvid2_fmt.fieldmerged[2] = 0;
}

Syslink Multi Process handling

Johny Bui — Tue, 11 Jun 2013 21:22:12 GMT

Please let me know if any of this information is invalid and if there is away to make this works. Thanks in advance,
Johny.

We are trying to running multi process and receive an assertion in syslink

Assertion at Line no: 1239 in /home/user/ti-ezsdk_dm814x-evm_5_05_02_00/component-sources/syslink_2_20_02_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : failed
Assertion at Line no: 695 in /home/user/ti-ezsdk_dm814x-evm_5_05_02_00/component-sources/syslink_2_20_02_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_INVALIDMESSAGEQ) : failed
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe

....................

Looking around and talking with TI field engineer, the issue is that syslink does not support multi process. To get this error all you need to do is run two gst-launch command at the same time, i.e. gst-launch-0.10 filesrc location=clip2.mp4 ! qtdemux ! h264parse ! omx_h264dec ! omx_scaler ! fakesink

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

Looking at the code, syslink only allow one heapID to be register in MessageQ.c line 1747:

GT_setFailureReason (curTrace,

GT_4CLASS,

"MessageQ_registerHeap",

status,

"Specified heap is already registered.!");

Just for fun, I commented this Failure check out to see what happen - the idea is to have the heap to be shared.

Run into the next issue, which is the NameServer_add - report a duplication because the name is generic (we could change this to have name relate to the pid or something so it will be unique and we won't have this issue). For a quick work around, I comment out the code for checking the duplication. This allow the second gst-launch command to run with no issue until the first gst-launch command finished and clean up. You will see this error:

*** MessageQ_alloc: Heap id is not registered with MessageQ!

Error [0xfffffff2] at Line no: 1327 in file /home/johny/CodeHG/bsp-ti81xx-hg/mods/syslink_2_21_01_05/packages/ti/syslink/utils/hlos/knl/Linux/.c

knl/Linux/MessageQDrv.c MessageQDrv_ioctl - CMD_MESSAGEQ_DESTROY

*** MessageQ_alloc: Heap id is not registered with MessageQ!

Error [0xfffffff2] at Line no: 1327 in file /home/johny/CodeHG/bsp-ti81xx-hg/mods/syslink_2_21_01_05/packages/ti/syslink/utils/hlos/knl/Linux/.c

*** MessageQ_alloc: Heap id is not registered with MessageQ!

I think this happen because the first gst-launch unregister the heap so if we can change syslink to keep a ref count of the heap register and don't clean up until all the command that got run goes down it could works.

Please let me know if this do able or what I am thinking is just wrong. There is no way syslink can works like that.

Thanks again,

Johny.

arago bitbake issue: ImportError: No module named optparse

Jason Z — Mon, 04 Feb 2013 04:54:18 GMT

Dear Sir/Madam,

I am trying to build a supported application using bitbake,

but it seems as the bitbake cannot run due to the following issue:

[linux-devkit]:~/jason/ti/arago-projects> MACHINE=am335x-evm bitbake linphone
Traceback (most recent call last):
File "/home/user/jason/ti/arago-projects/arago-bitbake/bin/bitbake", line 25, in <module>
import sys, os, getopt, re, time, optparse, xmlrpclib
ImportError: No module named optparse

Can you advice how to fix it?

Thanks,

[AM3715] Porting SGX to Kernel 3.2

Michael Questo — Fri, 22 Feb 2013 02:03:38 GMT

I'm trying to port the SGX libries from 2.6.37 kernel (Linux PSP Release : 04.02.00.07) to 3.2 kernel. So far we've been unnsuccesful.

AM3715 Linux EZSDK:

http://software-dl.ti.com/dsps/dsps_public_sw/am_bu/sdk/AM37xSDK/latest/index_FDS.html

SGX Support for AM3715 EZSDK:

http://processors.wiki.ti.com/index.php/RN_4_08_00_01#Kernel.28Linux_PSP.29_versions_supported_or_used_for_validation

Linux forum - Recent Threads

RBL fail to start UBL, ask for symbol file of RBL

Linux- c6x- 2. 0- GA User Guide

Putting the board into operation - how?

am1808 kernel build for sd card

DM8168 EVM can’t boot from NAND flash

PAL display on dm368??

Kernel Hangs after u-boot at "starting kernel..."

What could you offer to improve DVSDK?

Problem with WDT on DM8148

Cannot build with CCS running on Linux

SysLink and linux SDK

Is there a resizer example for DM365?

secure boot for omap 3530

DM6467+TVP5158+MJPEG strategy help

DM368 video get paused and go on

How to create applications

using remoteproc without DSP/BIOS

Segfault when trying to get GST_DEBUG=*omx*: ...

DM 8148 ( J5 ECO ) EVM Unable to do video playback using gstreamer

Regarding clocking ARM at 1.2 GHz on Netra 816x

Regarding clocking ARM at 1.2 GHz on Netra 816x

a question in ti81xxvin_vps_config_format() from ti81xxvin_main.c

Syslink Multi Process handling

arago bitbake issue: ImportError: No module named optparse

[AM3715] Porting SGX to Kernel 3.2

Segfault when trying to get GST_DEBUG=omx: ...