Processors

Processors forum

State Resolved
Locked Locked
Replies 20 replies
Subscribers 103 subscribers
Views 4902 views
Users 0 members are here

Support feedback

Options

Options

Related

insmod vpss.ko hangs

Rahul Patel

Prodigy 120 points

I m working on DM8168 EVM board. I have downloaded the PSP release PSP-04.00.01.13 and applied the 2 patches available at location: http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DM816x_04_00/04_00_01_13/index_FDS.html. Then I built the kernel and all the modules, replaced all the modules on target file system and then boot the machine with the new uImage.

lsmod command showed me that syslink module has been already inserted. so i did not have to insert it. Then i updated the firmware with command.: ./slaveloader startup VPSS-M3 ti816x_hdvpss.xem3.

Then I inserted the vpss module with command: insmod vpss.ko

This command hangs the board and I cant see anything on terminal. I tried starting a telnet session but the board did not respond.

I don't understand what do now. I tried with the prebuilt images comes with the package also but geting the same result. Please help.

Regards,

Rahul

over 13 years ago

0 yihe over 13 years ago

TI__Guru 65550 points

Rahul,

what is your bootargs? did you download the new M3 firmware along with patch2 release?

Regards,

yihe

0 Rahul Patel over 13 years ago in reply to yihe

Prodigy 120 points

yihe,

My bootargs are:

*************************

bootdelay=3

baudrate=115200

verify=yes

ramdisk_file=ramdisk.gz

loadaddr=0x81000000

script_addr=0x80900000

loadbootscript=fatload mmc 1 ${script_addr} boot.scr

bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}

stdin=serial

stdout=serial

stderr=serial

ethaddr=40:5f:c2:21:1e:ac

ethact=DaVinci EMAC

ver=U-Boot 2010.06 (Jun 01 2011 - 12:30:57)

bootargs=console=ttyO2,115200n8 rootwait rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti816xfb.vram=0:16M,1:16M,2:6M root=/dev/nfs nfsroot=192.168.1.p

bootcmd=dhcp;setenv serverip 192.168.1.141;tftpboot;bootm

autoload=no

serverip=192.168.1.141

bootfile=uImage-dm816x-evm.bin

Environment size: 697/8188 bytes

*******************************

I downloaded the "TI816x-HDVPSS-01.00.01.33.zip" package having slaveloader and ti816x_hdvpss.xem3; and executed the command "./slaveloader startup VPSS-M3 ti816x_hdvpss.xem" before inserting vpss.ko. Does this what you mean by "new M3 firmware" or do i need anything else?

0 yihe over 13 years ago in reply to Rahul Patel

TI__Guru 65550 points

Rahul,

could you try notifyk.vpssm3_sva=0xA0000000 in your bootargs

Regards,

yihe

0 Rahul Patel over 13 years ago in reply to yihe

Prodigy 120 points

Yihe,

I have tried "notifyk.vpssm3_sva=0xA0000000" earlier also after reading it from user guide, but it causes a few problems:

1. while booting up it gives errors as shown below:

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

You can see the attached log of boot up.

2. Also after upgrading the firware, I executed "insmod vpss.ko" which failed with following error prints:

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

notify_shm_drv_sendevent failed! status = 0xfffffff0

notify_send_event failed! status = 0xfffffff0

VPSS_CORE : Failed to init fvid2 interface,

vpss: probe of vpss failed with error -22

VPSS_CORE : failed to register ti81xx-vpss driver

insmod: error inserting 'vpss.ko': -1 No such device

Fullscreen 5383.Log_bootUpWith0xA0000000.txt Download

LOGGGG

SysLink version : 2.00.04.83
SysLink module created on Date:Nov  7 2011 Time:22:44:21
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version :  2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
FATAL: Error inserting vpss (/lib/modules/2.6.37/kernel/drivers/video/ti81xx/vpss/vpss.ko): No such device
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
FATAL: Error inserting ti81xxfb (/lib/modules/2.6.37/kernel/drivers/video/ti81xx/ti81xxfb/ti81xxfb.ko): No such device
open /dev/fb0: No such file or directory
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
FATAL: Error inserting ti81xxhdmi (/lib/modules/2.6.37/kernel/drivers/video/ti81xx/ti81xxhdmi/ti81xxhdmi.ko): No such device
Starting system message bus: dbus.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
expr: syntax error
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven


Usage: fbset [options] [mode]

Valid options:
  General options:
    -h, --help         : display this usage information
    --test             : don't change, just test whether the mode is valid
    -s, --show         : display video mode settings
    -i, --info         : display all frame buffer information
    -v, --verbose      : verbose mode
    -V, --version      : print version information
    -x, --xfree86      : XFree86 compatibility mode
    -a, --all          : change all virtual consoles on this device
  Frame buffer special device nodes:
    -fb <device>       : processed frame buffer device
                         (default is /dev/fb0)
  Video mode database:
    -db <file>         : video mode database file
                         (default is /etc/fb.modes)
  Display geometry:
    -xres <value>      : horizontal resolution (in pixels)
    -yres <value>      : vertical resolution (in pixels)
    -vxres <value>     : virtual horizontal resolution (in pixels)
    -vyres <value>     : virtual vertical resolution (in pixels)
    -depth <value>     : display depth (in bits per pixel)
    -nonstd <value>    : select nonstandard video mode
    -g, --geometry ... : set all geometry parameters at once
    -match             : set virtual vertical resolution by virtual resolution
  Display timings:
    -pixclock <value>  : pixel clock (in picoseconds)
    -left <value>      : left margin (in pixels)
    -right <value>     : right margin (in pixels)
    -upper <value>     : upper margin (in pixel lines)
    -lower <value>     : lower margin (in pixel lines)
    -hslen <value>     : horizontal sync length (in pixels)
    -vslen <value>     : vertical sync length (in pixel lines)
    -t, --timings ...  : set all timing parameters at once
  Display flags:
    -accel <value>     : hardware text acceleration enable (false or true)
    -hsync <value>     : horizontal sync polarity (low or high)
    -vsync <value>     : vertical sync polarity (low or high)
    -csync <value>     : composite sync polarity (low or high)
    -gsync <value>     : synch on green (false or true)
    -extsync <value>   : external sync enable (false or true)
    -bcast <value>     : broadcast enable (false or true)
    -laced <value>     : interlace enable (false or true)
    -double <value>    : doublescan enable (false or true)
    -rgba <r,g,b,a>    : recommended length of color entries
    -grayscale <value> : grayscale enable (false or true)
  Display positioning:
    -move <direction>  : move the visible part (left, right, up or down)
    -step <value>      : step increment (in pixels or pixel lines)
                         (default is 8 horizontal, 2 vertical)
Starting PVR
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
VPSS_CORE : Failed to init fvid2 interface,
vpss: probe of vpss failed with error -22
VPSS_CORE : failed to register ti81xx-vpss driver
FATAL: Error inserting omaplfb (/lib/modules/2.6.37/kernel/drivers/gpu/pvr/omaplfb.ko): No such device
/dev/mem opened.
Memory mapped at address 0x40271000.
Read at address  0x48180F04 (0x40271f04): 0x00000001
Write at address 0x48180F04 (0x40271f04): 0x00000000, readback 0x00000000
/dev/mem opened.
Memory mapped at address 0x400d4000.
Read at address  0x48180900 (0x400d4900): 0x00000102
Write at address 0x48180900 (0x400d4900): 0x00000002, readback 0x00000002
/dev/mem opened.
Memory mapped at address 0x40332000.
Read at address  0x48180920 (0x40332920): 0x00040002
Write at address 0x48180920 (0x40332920): 0x00000002, readback 0x00000002
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:~#

0 -Perry over 13 years ago in reply to Rahul Patel

Intellectual 440 points

I experienced the same problem with "insmod vpss.ko". I also run into "unknown symbol" issue with Patch2.
Any help will be appreciated.

-Perry
 
 
root@dm816x-evm:/lib/modules/2.6.37/kernel/drivers/video/ti81xx/ti81xxfb# insmod ti81xxfb.ko 
ti81xxfb: Unknown symbol vps_grpx_get_ctrl (err 0)
ti81xxfb: Unknown symbol vps_grpx_get_num_grpx (err 0)
insmod: error inserting 'ti81xxfb.ko': -1 Unknown symbol in module


root@dm816x-evm:~/PSPPatchForVideoCapture/TI816x-HDVPSS-01.00.01.33# insmod vpss.ko
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0
notify_shm_drv_sendevent failed! status = 0xfffffff0
notify_send_event failed! status = 0xfffffff0

0 yihe over 13 years ago in reply to Rahul Patel

TI__Guru 65550 points

Rahul,

From the log file, you were using firmware_loader. If the M3 firmware directly from the PSP download was used, please use notifyk.vpssm3_sva=0xa0000000 and slaveloader to load M3 firmware. please check the below link to follow to load modules.

http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide#Read_This_First

http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide#Load_VPSS.2C_Fbdev.2C_and_V4L2_Display_Driver_Modules

Regards,

yihe

0 Rahul Patel over 13 years ago in reply to yihe

Prodigy 120 points

Yihe,

I am not using firmware_loader. I am loading the firmware using the command: ./slaveloader startup VPSS-M3 ti816x_hdvpss.xem3

Also, I have got the slaveloader and ti816x_hdvpss.xem3 from the location: http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/DM816x_04_00/04_00_01_13/index_FDS.html (from DM816x HDVPSS binary package under the tag DM816x Linux PSP - 04.00.01.13.patch2)

Still I m getting those errors. Please suggest what to do.

-Rahul

0 yihe over 13 years ago in reply to Rahul Patel

TI__Guru 65550 points

Rahul,

In the log you provided in the previous post, firmware_loader was used.

Could you provide your bootargs, complete log file(start from uboot) and the script to load the M3 firmware and vpss.ko?

Did you rebuild the uImage, vpss.ko after applying the patch?

Regards,

yihe

0 Carl Blake over 13 years ago in reply to Rahul Patel

Expert 1160 points

I've been following this thread with great interest since I'm encountering a similar issue. I haven't had a chance to try this yet, but I'm assuming that I need to change the bootargs notifyk.vpssm3_sva from 0xbf900000 to 0xA0000000 as yihe mentioned earlier. I did have some questions for you, Rahul.

- In your first post you said you rebuilt linux and all its modules and that you replaced all the modules. You didn't say that you had replaced the uImage. Did you do that? I'm pretty certain that has to be done.

- You mentioned that you were using slaveloader to load the ti816x_hdvpss.xem3 file, but you didn't say whether you had unloaded the older firmware. You can execute the command "/etc/init.d/load-hd-firmware.sh stop" to remove the modules and unload the old firmware. Then I believe you can follow the instructions to reload the modules and the newer firmware using slaveloader. Before you issue the stop command make certain you've removed the omaplfb module or the stop won't work correctly. It probably makes more sense to edit /etc/init.d/load-hd-firmware.sh to use slaveloader to load the new firmware and the modules rather than doing the convoluted steps I described here.

I haven't done any of this yet so I don't know for sure that this will work. I'm waiting until we finish some other testing we're in the middle of before I make the attempt.

Yihe, I'm currently using ezsdk 05.03.01.15. This release has patch2 installed. Am I correct in thinking that I don't need the modules provided in TI816x-HDVPSS-01.00.01.33 but only the slaveloader program and the ti816x_hdvpss.xem3 firmware file? I'm thinking this is true since patch2 was applied to 05.03.01.15 and a new uImage had been provided as well as a new targetfs. Please let me know if I still need to use the modules provided with the ti816x_hdvpss.xem3 file.

Yihe, please correct any statements I've made that are wrong.

Carl

0 Rahul Patel over 13 years ago in reply to Carl Blake

Prodigy 120 points

Finally, my issue got resolved. the issue was about firmware reloading.. Yes, I was using slaveloader but then "/etc/init.d/load-hd-firmware.sh" script was also loading the firmware using firmware_loader and so the things were not working as expected. Thanks yihe for pointing it out. I modified "/etc/init.d/load-hd-firmware.sh" script and it's working fine now..

-Rahul

0 yihe over 13 years ago in reply to Carl Blake

TI__Guru 65550 points

Carl,

Does 05.03.01.15 state which HDVPSS it supports. if 05.03.01.13 have the .33 M3 firwmare. I do not think you need anything.

if 05.03.01.15 does not provide .33 firmware, then what you described is right.

Regards,

yihe

0 Carl Blake over 13 years ago in reply to yihe

Expert 1160 points

How would I determine which HDVPSS it supports. The release notes don't really say. I did notice that /usr/share/ti/ti-media-controller-utils has newer xem3 files including a hdvpss file with a v4l2 reference (dm816x_hdvpss_v4l2.xem3). Should I be loading this file instead of the ti816x_hdvpss.xem3 in 05.03.01.15? Are there any restrictions with loading the other xem3 files? Does the notifyk.vpssm3_sva bootarg need to change if I use any of these other files?

Carl

0 yihe over 13 years ago in reply to Carl Blake

TI__Guru 65550 points

Carl,

Please check this post. it should answer your answers.

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/717/t/153145.aspx

Regards,

yihe

0 Carl Blake over 13 years ago in reply to yihe

Expert 1160 points

Aha, new load-hd-firmware shell scripts. I didn't see that before. One question, if we use the v4l2 script do we still need to change the notifyk.vpssm3_sva bootarg from 0xbf900000 to 0xa0000000 or should we keep it set to 0xbf900000?

Carl

0 yihe over 13 years ago in reply to Carl Blake

TI__Guru 65550 points

Carl,

Keep 0xbf900000 and that is what SDK requires.

Regards,

yihe

0 Diego Moimas over 13 years ago in reply to yihe

Prodigy 40 points

Hi,
we're using Mistral DM8148 EVM.

We trying to setup the environment to run with 256MB of SDRAM.

We need to run a gstreamer pipeline playing HD video from RTP source, using h264 decoder (on m3) and aac decoder (on dsp) and targeting video output on HDMI.

Currently we are able to do that with 512MB of SDRAM (without recompiling M3+DSP firmwares), modifying u-boot to configure LISA registers as suggested in EZSDK Memory Map page from processors.wiki.ti.com.
Furthermore we disabled EMIF1 and interleaving: we use 512MB (or 256MB) in single bank configuration.

SDK version: 5.03.01.15 + overlay, codesourcery 2009q1
OS: Ubuntu LTS 10.04 64bit + ia32libs

We did the following changes in our build environment:
- modified uboot for 256MB, following guidelines provided in EZSDK Memory Map for 512 (obiouvsly we mapped only 256MB not-interleaved)
- fixed timer references in files containing code about dmtimer0 (timer3) - it runs at 20MHz and not at 32kHz
- created some symlinks in order to solve missing file with hardcoded paths issues
   - in ex.: omx-ti81xx-src_xx_xx_xx_xx/packages -> omx-ti81xx-src_xx_xx_xx_xx/src
- changed memory map (following EZSDK Overlay Installer build instructions and performing changes in other files): see attachments
- we changed in 'Makefile' from EZSDK_INSTALLATION_DIR, around line 410 we added target edma3_lld_ti814x_arm_libs instead of edma3_lld_ti816x_arm_libs. We also changed edma3 makefile because this target didn't provide code for compiling M3 firmware but only for A8+DSP.
- in the same makefile, we removed building and installation of supplied u-boot
- in the same makefile, we modified "components_linux" target in "components_linux: linux cmem osal syslink_hlos syslink_driver sgx-driver edma3lld omx" to compile automatically "edma3lld" before "omx"
- modified load-hd-firmware.sh (see attachments)
- modified kernel command line to adjust ram and knoitify address
- we left setting of 1G(1024MB) in following files:
   - ldrmem_seg.h (all copies)
   - memsegdef_dm81xxbm.c (all copies)
   - memsegdef_default.c (all copies)
   - rules_m3.mk (in omx-ti81xx-src_xx_xx_xx_xx/makerules)
   - build_config.mk (in omx-ti81xx-src_xx_xx_xx_xx)
- we recompiled the whole SDK with make all and then installed with make install. Then we copied firmwares from "omx-ti81xx-src_xx_xx_xx_xx/bin/dm814xbm" and "omx-ti81xx-src_xx_xx_xx_xx/bin/dm81xx" to "$(targetfs)/usr/share/ti/ti-media-controller-utils"


If load-hd-firmware.sh loads dm814xbm_m3video_whole_program_debug.xem3 and dm814xbm_m3vpss_whole_program_debug.xem3:
   - Firmwares load but system hangs inserting vpss.ko (even inserting with debug=1 generates no output on serial console).
   - This happens both with 256 and 512MB u-boot versions.

If load-hd-firmware.sh loads dm814x_hdvicp.xem3 and dm814x_hdvpss.xem3:
   - System hangs after "MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1", loading the first firmware.

Thanks in advance.

Best regards,

Diego

3463.load_hd_firmware.pdf

0272.EZSDK_MemCf_256.pdf

Edit: we're almost sure that we need more memory in IPC_SR_FRAME_BUFFERS (at least 51MB to process a 720p) but it's not such a problem now.

0 Vimal Jain over 13 years ago in reply to Diego Moimas

TI__Expert 6535 points

Diego,

It appears to be memory map conflict. Could you please make sure in your bootargs notfiy address mentioned matches with the M3 memory map. Also have you made firmware-loader changes as It needs same memory map as in M3 firmware. Loading first Video and then VPSS is right order.

Regards

Vimal

0 Diego Moimas over 13 years ago in reply to Vimal Jain

Prodigy 40 points

Hi Vimal,

thanks for your reply.

I can assure that notify address in kernel command line (u-boot bootargs) is coherent with other changes in memory map: changing it in u-boot environment leads to 'notify'-releated errors when firmwares (debug version) try to load.

We rebuilt the whole SDK reverting memory map back to 1GB settings and we got stuck in the same way.

We have still to try to put back "edma3_lld_ti816x_arm_libs" in Makefile of SDK (around line 410) instead of "edma3_lld_ti814x_arm_libs"; changing it in "edma3_lld_ti814x_arm_libs" is the only difference we still have in our local copy of SDK respect "EZSDK Overlay Build Instructions".

Diego

0 Diego Moimas over 13 years ago in reply to Diego Moimas

Prodigy 40 points

Hi all,

keeping "edma3_lld_ti816x_arm_libs" in Makefile of SDK (around line 410) solved the problem.

It works with every mem config.

Thanks.

D.

0 ranchu over 10 years ago in reply to Diego Moimas

Guru 20755 points

Hello,

I hope someone here can help me.
I have some strange behaviour when moving from ubifs (with ecc bch8) to jffs (hamming ecc).
Everything worked except for the vpss notify.
On Linux boot, the boot got freeze in notiify step, with the jffs.
When I removed the parameter from bootargs, it all works well.

Does anyone have any idea ?

Thank you,
Ran