Board Support Package¶
This page includes the downloads for the board support package for the MityDSP-L138 and MityDSP-1808 family of modules. The board support package is a snapshot release of the various software and FPGA components associated with the SoM. The hierarchy of the most recent installation package is as follows:
docs/ -> Documentation Data
examples/industrial_io -> example files for fpga and software that will run on the industrial I/O board
fpga/ -> files needed for FPGA development using Critical Link Framework
fpga/vhdl -> top level VHDL framework
fpga/cores/build_spartan6 -> netlists for IP cores available from Critical Link
fs/mityomap-base.{jffs2,tgz} -> base root filesystems, based on open-embedded build
fs/mityomap-full.{jffs2,tgz} -> larger root filesystem, includes qt libraries and more utilities
lib/ARM -> runtime libraries for the ARM processor
lib/DSP -> runtime libraries for the DSP core processor
sw/3rdparty -> Third party software/libraries needed for the support package
sw/ARM/linux/linux-davinci/ -> snapshot of kernel source tree used for included uImage (kernel image)
sw/ARM/linux/drivers/ -> custom drivers (linux, DSP Bios) for Critical Link Supplied FPGA framework / cores
sw/ARM/linux/libdsp -> linux library used by CL for ARM/DSP communication (sits on top of DSPLINK)
sw/ARM/linux/oe -> Open-Embedded overlay used to build root filesystem
sw/ARM/u-boot-mitydspl138/ -> snapshot of u-boot source tree used for included u-boot-bin.ubl image
sw/DSP/lib -> DSP libraries used by CL for ARM/DSP comms, DSP/BIOS peripheral drivers, etc.
sw/DSP/templates -> DSP BIOS configuration templates
sw/gel -> gel files for ARM or DSP for CCS 3 or 4
sw/common -> common files needed for DSP / ARM compilation
images/ -> binary images released with this build
images/uImage -> kernel image loadable via u-boot
images/u-boot.bin -> Das u-boot binary image
images/u-boot-ubl.bin -> Das u-boot binary image with necessary UBL header for in-field upgrades
images/modules -> kernel modules for Critical Link provided FPGA framework / cores
(THESE ARE ALREADY INSTALLED IN THE ROOT FILESYSTEM IMAGES...)
images/sfh_OMAP-L138.exe -> Windows serial SPI flasher for recovering dead boards
images/SPIWriter_MityDSP-L138.out -> SPI writer program for SPI flasher routine
images/UBL_SPI_MEM.ais -> image of 1st stage SPI boot image
BSP Release Installation¶
One of the first steps in setting up your build environment will be to install the MityDSP-L138/MityARM-18XX board support package. The BSP is a bash executable script that will self-extract a snapshot of the source files, libraries and drivers used for developing ARM and DSP applications as well as FPGA images using the Critical Link developed EMIFA framwork. It also includes a couple of sample root file system images set up for booting the ARM core, based on the Angstrom distribution. It does not include compiler tools (e.g., the gcc ARM cross compiler, DSP code generation tools from TI, or the Xilinx synthesis tools), you'll need to add those to your environment as Critical Link cannot redistribute that software.
Linux Operating Systems¶
Begin by copying the release .run file to a temporary directory on your Ubuntu system. Open a terminal and cd to the temporary directory.
Change the attributes of the file to make it executable (chmod +x releasexxxxx.run).
Make sure that /bin/sh is linked to bash. If you do an "ls -al /bin/sh", you can verify that it points to bash. If not, do the following:
[mitydsp@mitydsp:~ ] sudo rm /bin/sh
[mitydsp@mitydsp:~ ] sudo ln -s /bin/bash /bin/sh
Now run the file (./releasexxxxx.run). Be sure to use a capital Y when responding to the license agreement.
Windows Operating Systems¶
If you are interested in installing the BSP files on a windows operating system for developing DSP applications or FPGA applications using the windows versions of the tools (Code Composer, Xilinx ISE, etc.), you can run the same procedure as for the linux operating system using Cygwin to self extract the files in order to get the libraries and FPGA utility software, etc. Note: the ARM toolchain provided by Critical Link (gcc) only runs on Linux. You may choose to use the ARM-9 toolchain from CodeSourcery, but Critical Link cannot support this configuration.
To install the MDK files, you need to first install cygwin. You will need to ensure that bash and the base packages are installed when running the installer.
Once cygwin is installed, copy the release .run file to a temporary directory on your system. Open a cygwin terminal and cd to the temporary directory.
Make sure that /bin/sh is linked to bash. If you do an "ls -al /bin/sh", you can verify that it points to bash. If not, do the following:
[mitydsp@mitydsp:~ ] sudo rm /bin/sh
[mitydsp@mitydsp:~ ] sudo ln -s /bin/bash /bin/sh
Now run the file (./releasexxxxx.run). Be sure to use a capital Y when responding to the license agreement.
Note: If you use the default arguments and cygwin is installed in the default location (C:/cygwin), the location of the files is c:/cygwin/home/${USERNAME}/MDK_******* or /cygdrive/c/cygwin/home/${USERNAME}/MDK_********. These files should now be accessible for building CCS or Xilinx FPGA images without the need to have a linux VM running.
Releases¶
- Current : Jan-2014 Board Support Pacakge, linux self extractinge .run file
- OLD: Dec-2013 Board Support Package, linux self extracting .run file
- OLD : May-2013 Board Support Package, linux self extracting .run file
- OLD : Aug-2012 Board Support Package, linux self extracting .run file
- OLD : Mar-2012 Board Support Package, linux self extracting .run file
- OLD : Dec-2011 Board Support Package, linux self extracting .run file
- OLD : Jul-2011 Board Support Package, linux self extracting .run file
- OLD : Mar-2011 Board Support Package, linux self extracting .run file
- OLD : Oct-2010 Board Support Package, bzip2 compressed tarball
Go to top
