• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 1760 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.

Trouble with VPSS kernel module on DM385

David Plows
Intellectual 320 points

Other Parts Discussed in Thread: DM385

Hey everyone,

I'm working on a custom DM385 board using the Car Black Box RDK. I've changed the kernel configuration to match our board and have attempted loading RDK software & modules onto it, but there seems to be an issue with either communicating with the M3 coprocessor or loading VPSS related software. On a normal boot, the system stops initializing the RDK framework when ti_mcfw_cbb_main.c calls a script titled /opt/cbb/scripts/wait_cmd.sh after loading firmware to the M3 coprocessor, and waits for a response, which it never gets which causes the system initialization to hang. If I comment out the wait_cmd.sh script call to continue on with RDK initialization I get a bootlog like

################ mcfw main start (tick_time: 9139 ms) ##############

 [host] DS.Ahn: bitRate(8000000, 5000000, 0, 0)

 [host] DS.Ahn: frameRate(30, 30, 0, 0)

 [host] DS.Ahn: shm_id[0]app load
IN LOAD!!!!!!!!!!!!!!!!!!!!!
 [c6xdsp ] Remote Debug Shared Memory @ 0xbff00000
 [m3video] Remote Debug Shared Memory @ 0xbff05020
 [m3vpss ] Remote Debug Shared Memory @ 0xbff0a040
STARTING OSA_KERMOD
LOADING OSA_KERMOD.KO
<6>DMA: Module install successful, device major num = 248
DMA: Module install successful, device major num = 248
<6>DRV: Module install successful
DRV: Module install successful
<6>DRV: Module built on Apr 29 2015 08:46:00
DRV: Module built on Apr 29 2015 08:46:00
<3>VPSS_FVID2: M3 firmware version 0x0 is old,please update firmware version.
VPSS_FVID2: M3 firmware version 0x0 is old,please update firmware version.
<3>VPSS_CORE : Failed to init fvid2 interface,
VPSS_CORE : Failed to init fvid2 interface,
<4>vpss: probe of vpss failed with error -22
vpss: probe of vpss failed with error -22
<3>VPSS_CORE : failed to register ti81xx-vpss driver
VPSS_CORE : failed to register ti81xx-vpss driver

insmod: error inserting './kermod/vpss.ko': -1 No such device
 [host] Loaded file ./firmware/carbb_rdk_fw_m3vpss.xem3 on slave procId 1.

 [host] Started slave procId 1.

 [host] After Ipc_loadcallback status [0x00000000]
 [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 200000000
<4>ti81xxfb: Unknown symbol vps_grpx_get_ctrl (err 0)
ti81xxfb: Unknown symbol vps_grpx_get_ctrl (err 0)
<4>ti81xxfb: Unknown symbol vps_grpx_get_num_grpx (err 0)
ti81xxfb: Unknown symbol vps_grpx_get_num_grpx (err 0)
 [m3vpss ] notify_attach  rtnVal  0
 [m3vpss ] initProxyServer  rtnVal  0
 [m3vpss ]
 [m3vpss ]  *** UTILS: CPU KHz = 400000 Khz ***
 [m3vpss ]
 [m3vpss ]  93: SYSTEM  : System Common Init in progress !!!
 [m3vpss ]  93: SYSTEM: IPC init in progress !!!
 [m3vpss ]  93: SYSTEM: Attaching to [HOST] ...
insmod: error inserting './kermod/ti81xxfb.ko': -1 Unknown symbol in module

 [host] Application Start Completed (tick_time: 10114 ms)
after app load
app run

 [host]


################ App_cbb_run start (tick_time: 10119 ms) ##############

 [host] App_cbb_run: Share Memory Addr=0x40438000

 [host] frameRateVal1: 30

 [host] frameRateVal2: 30

 [host] frameRateVal3: 0

 [host] nMpeg41bitrate: 8000000

 [host] nMpeg42bitrate: 5000000

 [host] njpegquality: 80
 [m3vpss ]  143: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  146: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3vpss ]  146: SYSTEM: Creating MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
 [m3vpss ]  147: SYSTEM: Creating MsgQ [VPSS-M3_MSGQ] ...
 [m3vpss ]  147: SYSTEM: Creating MsgQ [VPSS-M3_ACK_MSGQ] ...
ApproDrvInit: 16

 [host] After Ipc_startcallback status [0x00000000]
 [m3vpss ]  149: SYSTEM: Notify register to [HOST] line 0, event 10 ...
 [m3vpss ]  150: SYSTEM: IPC init DONE !!!
queue id:98307

 [host]  0: SYSTEM: System Common Init in progress !!!

 [host]  28: SYSTEM: IPC init in progress !!!
 [m3vpss ]  165: MEM: Shared Region 2: Base = 0xb8000000, Length = 0x06900000 (105 MB)
 [m3vpss ]  166: MEM: Shared Region 1: Base = 0x89000000, Length = 0x03c00000 (60 MB)
 [m3vpss ]  168: SYSTEM  : System Common Init Done !!!

 [host]  57: SYSTEM: CPU [DSP] is N<6>DMA: ChannelID allocated:4
DMA: ChannelID allocated:4
OT available on <6>DMA: ChannelID allocated:9
DMA: ChannelID allocated:9
this platform !!!

 [host]  57: SYSTEM: CPU [VIDEO-M3] syslink proc ID is [0] !!!

 [host]  57: SYSTEM: CPU [VPSS-M3] syslink proc ID is [1] !!!

 [host]  57: SYSTEM: CPU [HOST] syslink proc ID is [2] !!!

 [host]  57: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...

 [host]  59: SYSTEM: Creating MsgQ [HOST_MSGQ] ...

 [host]  60: SYSTEM: Creating MsgQ [HOST_ACK_MSGQ] ...

 [host]  63: SYSTEM: Opening MsgQ [VPSS-M3_MSGQ] ...

 [host]  64: SYSTEM: Notify register to [VPSS-M3] line 0, event 10 ...

 [host]  65: SYSTEM: IPC init DONE !!!

 [host]  68: SYSTEM: Creating ListMP [HOST_IPC_OUT_29] in region 0 ...

 [host]  73: SYSTEM: Creating ListMP [HOST_IPC_IN_29] in region 0 ...

 [host]  74: SYSTEM: ListElem Shared Addr = 0x4059e180

 [host]  75: SYSTEM: Creating ListMP [HOST_IPC_OUT_30] in region 0 ...

 [host]  79: SYSTEM: Creating ListMP [HOST_IPC_IN_30] in region 0 ...

 [host]  88: SYSTEM: ListElem Shared Addr = 0x405b7e00

 [host]  91: SYSTEM: Creating ListMP [HOST_IPC_OUT_24] in region 0 ...

 [host]  93: SYSTEM: Creating ListMP [HOST_IPC_IN_24] in region 0 ...

 [host]  94: SYSTEM: ListElem Shared Addr = 0x405d1a80

 [host]  96: SYSTEM: Creating ListMP [HOST_IPC_OUT_25] in region 0 ...

 [host]  98: SYSTEM: Creating ListMP [HOST_IPC_IN_25] in region 0 ...

 [host]  100: SYSTEM: ListElem Shared Addr = 0x405f1480

 [host]  101: SYSTEM: Creating ListMP [HOST_IPC_OUT_26] in region 0 ...

 [host]  103: SYSTEM: Creating ListMP [HOST_IPC_IN_26] in region 0 ...

 [host]  104: SYSTEM: ListElem Shared Addr = 0x40610e80

 [host]  105: SYSTEM: System Common Init Done !!!
12345

 [host]  135: MCFW  : CPU Revision [ES1.0] !!!

 [host]  135: MCFW  : Detected [UNKNOWN] Board !!!

 [host]  135: MCFW  : Sensor is NOT connected !!!

 [host]  135: MCFW  : Base Board Revision [UNKNOWN] !!!

 [host] rear cam is not detected !!

 [host] Vsys_allocBuf - addr = 0x4d3ae000,size = 65011712

 [host] MCFW_IPCBITS:App_streamSysInit:virt addr of 85000000 cir buffer  is 4d3ae000

 [host] first stream: 1920 1080 8000000 30

 [host] second stream: 1280 720 5000000 30

 [host] third stream: 1920 1080 80
##########pInfo->totalsize 65011712
queue id:98307
queue id:65538

 [host] MCFW_IPCBITS:App_ipcBitsRecvStreamFxn:Entered...
 [host] MCFW_IPCFRAMES:App_ipcFramesSendRecvFxn:Entered...
 [host] Vsys_allocBuf - addr = 0x5239a000,size = 5640

 [host] DCC buffer allocated for size 5640

 [host] DCC Default File Intialization Done

 [host] Before System_linkControl SYSTEM_M3VPSS_CMD_GET_DISPLAYCTRL_INIT
 [m3vpss ] tiedVencs VPS_DC_VENC_HDMI | VPS_DC_VENC_HDCOMP
 [m3vpss ] System_dispSetPixClk: Error 0 @ line 270
 [m3vpss ]  355: Assertion @ Line: 385 in links_m3vpss/system/system_dctrl.c: FVID2_SOK == retVal : failed !!!

Init_CbbMcFW(2342)::     # Init_StreamEnv end (tick_time: 10476 ms) #

Init_CbbMcFW(2354)::     # end (tick_time: 10506 ms) #

My uboot environment variables are

bootcmd=ipnc_ff_init 1;mmc rescan 0; fatload mmc 0 0x81000000 uImage; bootm 0x81000000
bootdelay=3
baudrate=115200
verify=no
bootfile=uImage
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=32:30:3a:63:64:3a
ethact=cpsw
bootargs=console=ttyO0,115200n8 noinitrd mem=80M rootwait vram=8M notifyk.vpssm3_sva=0xBFD00000 root=/dev/mmcblk0p2 rw ip=off cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2010.06 (Apr 26 2015 - 13:39:32) DM385_CBB_0.80.00


Which from what I can tell seems like an issue with either the kernel module or the firmware not being properly loaded to the coprocessor. The vpss.ko file being loaded is built against our most recent kernel. I can tell it's not an issue with the hardware as the same issue arises when launching the system from a verified working devkit (nSketch CBB EVM) so it seems to me like there must be some issue with my current kernel configuration that's causing it to fail as that is really the only significant change between the working eval software and our custom board's software that I can think of. I can post the relevant configuration/pin muxing if anyone else thinks this may be the issue, and I'm open for any other suggestions as well. Apologies if I forgot to provide any important information.

Thanks,

Dave

  • 0
    TI__Guru**** 497105 points
    Hi Dave,
    Above command line assumes that the vpss shared memory is located at the offset 0xBFD00000. If you have changed memory map and moved this hdvpss shared memory from this default location, can you search in your map file and provide correct location in notifyk.vpssm3_sva parameters?
    It looks like modules are loaded correctly, shared memory is different for vpss.
    Rgds,Brijesh
  • 0 in reply to Brijesh Jadav
    Intellectual 320 points

    Thanks for the suggestion Brijesh,

    I've taken a look at the memory map file for HDVPSS. I haven't modified any of these values in my development, but could you point me exactly to which address I should be providing as a parameter? I'm guessing it would be NOTIFY_SHARED_ADDR? If so, during a build of the system I can verify that the calculated address is 0xBFD00000. I've attached the memory map file if you think there might be a mistake. In the meantime I think I'll start reverting changes that I've made on the kernel level to see if anything I've done could have caused this. Much gratitude to any additional responses.

    Thanks,

    DaveBIOS_m3vpss.cfg

  • 0 in reply to David Plows
    Intellectual 320 points
    I went back entirely to the devkit kernel configuration and uboot, and the problem still persists with the same filesystem. I think this must point to a change I've made in the filesystem/userspace causing the issue, whether it's a specific kernel module or a change with one of the initialization scripts/applications. I'm going to keep reverting changes until I can narrow it down, I don't think it can be vpss.ko as it hangs before that's loaded, and I've reverted the firmware that's loaded to the M3 from an old working SD which also doesn't seem to be the issue either. I might be overlooking something simple or I'm doing something very wrong with my current setup. Again, any suggestions are welcome.
  • 0 in reply to David Plows
    Intellectual 320 points
    After I used an MLO with the correct memory timings/settings on the devkit everything started working with it once again, so that tells me there must be an issue with the DDR leveling values I've obtained and am using on my custom board. I guess I'll have to keep messing around with them to see if I can get them right. There must be an issue with the memory map created with these DDR timings/values that causes communication between the main and co-processor to not cooperate. I'll update again once I get it straightened out but this seems to be the issue/solution to my problem.
  • 0 in reply to David Plows
    TI__Guru**** 497105 points

    David,

     

    Sorry, will not be able to help in DDR leveling configuration. I could help if something related to hdvpss.

     

    Rgds,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 320 points

    Thank you for the assistance Brijesh.

    My custom board's DDR3 chip is operating on a 16-bit bus, and my DDR3_EMIF_SDRAM_CONFIG value is 0x61C05232 to indicate that the chip is operating in narrow mode. Is there any sort of makefile rule or setting that needs to be set to build the firmware that's loaded to the M3 VPSS to indicate this? I'm thinking this might be the issue.


    Thanks,

    Dave