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.

MVL_5.0 Tools install

Expert 1130 points

I'm running Monta Vista Linux 5 Pro release, not demo. I unpacked the MVL_5.0 Tools tarball to the /opt directory and a great number of files were installed in montavista directory pro/devkit, common/share and common/lib  Did i just clobber my Monta Vista 5.0 Pro install or are these the same files?

  • MV Pro 5 from MV Zone is different than MV Pro 5 that we include with DVSDK; this is part of the reason you pay MV a license fee.  I would recommend installing these in a separate directory instead of on top of an existing MV distro.

  • So I stick with the demo mv_pro_5.0 and not download montavista linux from Monta Vista zone at any time? I should always use what's included in the dvsdk distro?

  • I create a Makefile project with the Monta Vista toolchain in eclipse. When I use Edition Management and add the path /opt/mv_pro_5.0/montavista it doesn't show up as Installed Editions window. I'm guesing it's because of the licensing. I know this works with the version of Monta Vista Linux that i download from the Monta Vista Zone. But if I use the Monta Vista Zone version of MV Pro 5.0, I need need to luse the LSP that comes with it right???? I'm getting pretty confused on the matching of the versions of DVSDK <=> LSP <=> MV Linux  from TI and Monta Vista.....

  • Hopefully the following explanation will help clear things up. 

    From an LSP (linux kernel) perspective, TI develops TI-specific drivers and makes them available to our customers via DVSDK or LSP releases thru TI sites. 

    Alternatively, you can buy MV license and get access to MVZone; MV Zone gives you access to not only TI specific driver updates but also non-TI Specific driver updates via patches.  Unfortunately, we cannot control how quickly MV pulls in TI specific updates and merges them to their kernel and make them available via patches in MVZone. 

    That said, LSP (or Linux kernel) is only part of the overall software, there is codec engine, demos,.... and if you are using your MV Kernel from MVZone, you must ensure compatibility with the rest of the software and be familiar with working with patches (pretty common when customizing a Linux kernel).  The following wiki has a mapping of the TI patches to the MV patches: http://tiexpressdsp.com/index.php/PSP_Introduction_and_Product_FAQ.  That said, using MV kernel (as opposed to TI Kernel) is not impossible but you must be very familiar with working with Linux patches and take responsability for ensuring compatibility with the rest of the software.