• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 99 subscribers
  • Views 910 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DVSDK and MVL upgrading

Bob Yiu
Prodigy 130 points

Hi,all,I'm using mvl 4.0 and DVSDK 1.20,How to upgrade my dvsdk to 2.0? Can I just copy
some nessesary files from DVSDK 2.0 folder to DVSDK 1.2 folder?

By the way I've bought mvl 5.0 form TI,But my DM357 is bought from SEED,

How to up my MVL 4.0 of SEED DM357 to my new bought TI MVL 5.0?  ( SEED does not provide MVL5.0, the newest version of MVL  they provided is mvl 4.0.1)

Thanks!

  • 0
    TI__Mastermind 41665 points

    Bob Yiu said:
    Hi,all,I'm using mvl 4.0 and DVSDK 1.20,How to upgrade my dvsdk to 2.0? Can I just copy
    some nessesary files from DVSDK 2.0 folder to DVSDK 1.2 folder?

    There are many version differences between DVSDK 1.2 and DVSDK 2.0 so in general it would be better to try to port your project to DVSDK 2.0 than it would be to port your DVSDK 1.2 to 2.0, DVSDK 2.0 is essentially different enough to be a new stand alone product. This being said I would just install DVSDK 2.0 and start working with it in place of 1.2.

    Bob Yiu said:
    How to up my MVL 4.0 of SEED DM357 to my new bought TI MVL 5.0?  ( SEED does not provide MVL5.0, the newest version of MVL  they provided is mvl 4.0.1)

    Unfortunately I am not very familiar with the SEED DM357, however in general the MVL 5.0 much like the DVSDK 2.0 is quite different, most porting issues I have seen actually tend to come from the MVL 4.x to MVL 5.x migration. The major reason you would run into trouble is because MVL 5.0 uses a newer Linux kernel with a newer set of drivers, so it is possible that you will run into compatibility issues with the SEED board if the appropriate patches are not available.

  • 0
    TI__Mastermind 37340 points

    Bob Yiu said:

    How to up my MVL 4.0 of SEED DM357 to my new bought TI MVL 5.0? 

    I am curious what you mean by new bought TI MVL 5.0; are you referring to the free software http://focus.ti.com/docs/toolsw/folders/print/s1sdklnx.html? or maybe you bought the EVM http://focus.ti.com/docs/toolsw/folders/print/tmdsevm357.html? or something else...

  • 0 in reply to Juan Gonzales
    Prodigy 130 points

    Juan Gonzales said:

    How to up my MVL 4.0 of SEED DM357 to my new bought TI MVL 5.0? 

     

    I am curious what you mean by new bought TI MVL 5.0; are you referring to the free software http://focus.ti.com/docs/toolsw/folders/print/s1sdklnx.html? or maybe you bought the EVM http://focus.ti.com/docs/toolsw/folders/print/tmdsevm357.html? or something else...

     

    [/quote]

    Hi,Juan! Thanks for your reply.My MVL 5.0 is bought from montavista zone

     

  • 0 in reply to Bernie Thompson TI
    Prodigy 130 points

    Bernie Thompson said:

    The major reason you would run into trouble is because MVL 5.0 uses a newer Linux kernel with a newer set of drivers, so it is possible that you will run into compatibility issues with the SEED board if the appropriate patches are not available.

    Hi,Bernie! Thanks for your reply!

    Would you please provide more detailed information?Any document would be apprieciated

    I booted  my SEED DM357 with MVL 5.0 today,but it failed to mount the nfs,What should I do to solve the problem? Thanks

    The error information is as below

     

    Looking up port of RPC 100003/2 on 192.168.100.129

    portmap: server 192.168.100.129 not responding, timed out

    Root-NFS: Unable to get nfsd port number from server, using default

    Looking up port of RPC 100005/1 on 192.168.100.129

    portmap: server 192.168.100.129 not responding, timed out

    Root-NFS: Unable to get mountd port number from server, using default

    mount: server 192.168.100.129 not responding, timed out

    Root-NFS: Server returned error -5 while mounting /home/xiaozhuzhu/Davinci/files

    ys

    VFS: Unable to mount root fs via NFS, trying floppy.

    VFS: Cannot open root device "nfs" or unknown-block(2,0)

    Please append a correct "root=" boot option

    Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

     

  • 0 in reply to Bob Yiu
    TI__Mastermind 37340 points

    Bernie made some pretty good points above (e.g. mv 5.0 is quite different than mv 4.0.1 in many respects).  The fact that you are using SEED EVM further complicates things a bit.  You see, our DVSDK software and the MV 5 kernel available from MVZone are written specifically for the Spectrum Digital DM357 EVM (not the SEED EVM).  This likely means that you will have the responsability of figuring out the differences between the EVMs and modify software accordingly.  Ideally (in my humble opinion), SEED should grab the latest kernel available from TI or MV Zone (MV 5) and do the porting themselves to support their offering with the latest software possible; however, they operate independantly from TI so there is not much we can do.

  • 0 in reply to Bob Yiu
    TI__Mastermind 41665 points

    The NFS error you have may not necessarily be related to the differences between MVL 4 and MVL 5, this is likely some issue on your host PC NFS server, there is a prior thread that discussed this very error: https://community.ti.com/forums/t/2815.aspx

  • 0 in reply to Bernie Thompson TI
    Prodigy 130 points

    Thanks,Bernie!

    I think my host PC NFS server is OK because everingthing is OK when I mounted the PC NFS server using mvl4.01,does this means that my PC NFS server configuration is correct?

    Is the configuration the same when mounting NFS using mvl 4 and mvl 5?

     

  • 0 in reply to Bob Yiu
    TI__Mastermind 41665 points

    Bob Yiu said:
    Is the configuration the same when mounting NFS using mvl 4 and mvl 5?

    The NFS configuration should be, though you would be pointing to a different folder on your host (the one containing the MVL5 filesystem) which means you would have to make adjustments to your NFS configuration. This being said it may be worth checking your /etc/exports file to ensure everything is correct in there, how do you have your exports file setup?