DM365 Leopard SDK Legacy Getting Started Guide
This guide includes instructions and tips users should follow to get their DM365 Leopard Board to work with the RR Evaluation SDK. For this guide different commands need to be executed on the host machine and the target. Commands to be run on the Ubuntu host have a yellow background. Commands to be run on the Ubuntu target have an aqua background.
Before compiling the SDK the toolchain needs to be installed on your host computer. Copy the contents of the tarball (the download link should be provided in the mail sent to you containing download instructions) inside /opt.
Notice the tarball contents are inside a folder named opt, DO NOT replace this folder with your local opt directory, just use its contents (arm-linux-gnueabi directory).
Several packages are needed in order to compile the SDK. While compiling you will be prompted to install them using sudo apt-get <packages>.
Configure the features you want to have in your board using:
Compile the SDK:
install the bootloader on the target:
and install it on the target:
To install the devdir on the target make sure the board is on the bootloader prompt.
SD boot recover
If you brick your board, this can be recovered from an SD card. In order to make a bootable SD card you first need to have a successfully compiled SDK.
- SD card preparation:
1. Insert the SDcard to the host port
2. Find out the device mounting point (e.g. /dev/sdd1)
3. On your devdir root directory type:
make sd_boot_recover device=/dev/sdX
where sdX is your device mounting point.
- Boot recover
1. Insert the SD card (if you already inserted it, disconnect and connect again).
make install sd_boot_recover
3. Set switch 2 of DIPSW1 to ON, 1 and 3 to OFF. This is SD card boot mode.
4. Power up the board, it will automatically erase the NAND flash, and burn UBL, u-boot, kernel and filesystem
5. Set all pos of DIPSW1 to OFF for NAND boot mode.
6. Connect serial cable to PC and power cycle the board (it should boot up). Insert the SD card to the board.
Setting up video components
The output and mode used for video playback/capture can be set during the SDK configuration process. The first step is to enter the configuration script:
Inside Architecture configurations select the options you desire on Video Output and Video Default Resolution.
Finally compile your changes and install
make make install
Activation of video capture modules
While configuring the SDK go to Kernel configuration->Device drivers->Multimedia support->Video capture adapters and activate the devices you desire.
When you boot your board the RidgeRun logo will be displayed, in order to display video the following commands must be executed:
loadmodules.sh fbset -disable
Component output initialization
There's a known bug with the component output initialization. Before you play or capture video using the component output this commands must be executed on the target:
echo "COMPOSITE" > /sys/class/davinci_display/ch0/output echo "COMPONENT" > /sys/class/davinci_display/ch0/output
CMEM pools modification
Depending on the video displayed, the CMEM pools need to be modified to meet the requirements. This is needed when you execute a pipeline and the following error is displayed:
CMEMK Error: Failed to find a pool which fits <poolsize>
First you need the start and end addresses of the CMEM pools, these can be obtained executing loadmodules.sh and checking the output: a line like the next one will be printed
Loading CMEM from 0x<startaddr> to 0x<endaddr>
rmmod cmemk modprobe cmemk phys_start=<startaddr> phys_end=<endaddr> pools=<somepools>, <mynewpools>
where <mynewpools> must be in format: <numberofpools>x<poolsize> (e.g 2x128). You may also need to resize/delete <somepools>
Output volume modification
To increase/decrease the volume for audio playback (or other audio options) type
and modify as desired.