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.

insmod vpss.ko error!!!



8148 2G mem

bootargs :

bootargs=console=ttyO0,115200n8 root=/dev/nfs rw mem=80M vram=4M nofityk.vpssm3_sva=0xBFD00000 rootdelay=5 nfsroot=192.168.1.168:/opt/ti_8127/filesys,nolock eth=00:0C:0C:A0:01:81 ip=192.168.1.186 cmemk.phys_start=0x85000000 cmemk.phys_e
nd=0x89000000 cmemk.allowOverlap=1 earlyprintk

insmod:

insmod ./kermod/vpss.ko debug=1  mode=hdmi:1080p-60 sbufaddr=0xbfb00000

if i use "insmod vpss.ko mode=hdmi:1080p-60 sbufaddr=0xbfb00000" ,

i got the error when camera start:

Failed to send version command to M3 0xfffffff0

.....

VPSS_FVID2: Unable to get firmware version
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 './kermod/vpss.ko': -1 No such device

anyone here can help me ?

thanks a lot.

  • Hello,

    What is the software release that you are using here?

    yue gu1 said:

    Failed to send version command to M3 0xfffffff0

    .....

    This error means wrong boot args.

    Could you try with : 

    notifyk.vpssm3_sva=0xBF900000

    Check your mem value as well.
    Could you try with the default bootargs.

    Are you rebuilt the kernel? If yes, you should copy also all the modules like syslink.ko, vpss.ko etc.

    Best Regards,
    Margarita

  • i tryed  notifyk.vpssm3_sva=0xBF900000 , it not work , error is same as before;

    i rebuilted the kernel and i copyed all the ko files;

    how to check mem value ?

    occred "Failed to send version command to M3 0xfffffff0" error, it is must be bootarg 's error ?

    thanks again
  • Hello,

    These are the default bootargs

    console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M vmalloc=500M ti814xfb.vram=0:16M,1:16M,2:6M ip=off noinitrd

    Could you try to set the mem, vram vmalloc and vpssm3_sva?

    Best Regards,

    Margarita

  • FYI: When I were migrating to IPNC RDK3.8 from 3.2, I saw such problems at the beginning as well.

    I remember the problem was not the vpss.ko itself, it's in the VPSS firmware.can you post the whole output from remote_debug? maybe you got some errors before the insmod operation.