Here is the list of problems I faced while starting to work with LeopardBoard and RidgeRunSDK. As a windows developer, I spent a lot of time solving them.
I decided to compile them here for the other people like me. I wish there was a good wiki for LeopardBoard or at least an active FAQ section.
Notice: Most of the information is collected from different sources (designsomething.org forum, TI website, google...), so I am not the one who did all the job :) Please be aware that they come from my own experience and it is not the official FAQ by TI or RidgeRun. It might have errors and might not apply to other similar situations .
Problems while installing RidgeRunSDK:
* I try to install RRSDK and it finishes very quickly and says that everything is ok, but there is no MAKE command available after install inside the installation directory:
While installing RidgeRunSDK, you must be connected to the internet at all times and during the installation, you must see a list of things it installs. (It takes from 10 min to 1 hour depending on the speed of your internet connection.)
* RidgeRunSDK installation looks stuck in one of the steps and I do not know whether it is still working or not:
Try running RRSDK from the command prompt without the GUI by:
./LeopardBoardDM365sdk-EVAL2011Q2-Linux-x86-Install.bin --mode console
and follow the prompts. It is more verbose than the GUI, and you can see what the problem is, and what it is doing.
Problems while making or running RidgeRunSDK:
You can delete all the files and folders inside the installation directory of RR except Download and Installer.
Then run this command: svn up It will recreate all the directory structures and all needed files and re-downloads the patches and uses the files inside Download directory instead of downloading all of them again.
* When I try to run "Make config" ,I get this error: "DVSDK is currently on use by another RidgeRun SDK"
Go to the installation directory of your TI DVSDK directory (Not the RidgeRun SDK!) and delete rrsdk-path, rules.make, rules.make*
Then issue a Make command from inside the RidgeRunSDK directory.
*I get an error that says, "Cannot compile DVSDK-x-x"
Just install TI-DVSDK in the same directory again.
Part 2 is added below...
Good that your helping other people with the SDK. There's a getting started guide at:
And a FAQ at:
One more thing about the: * When I try to run "Make config" ,I get this error: "DVSDK is currently on use by another RidgeRun SDK" problem
The best way to handle this problem is to issue a make distclean at $DEVDIR/proprietary/dvsdk-x-x inside the DEVDIR that is using the DVSDK, and after that, build the SDK that wants to use the DVSDK. Currently we can't share DVSDKs between devdirs because paths get wired all over the place
Carlos AgueroEmbedded Software EngineerRidgeRun
Thanks Carlos for the info.
I have already checked those links, but it's been a while since the last time they have been updated.
And also the list of FAQs is very short.
Thanks Again. And I try to continue adding things I learn about LeopardBoards and RRSDK
SD card and external USB devices
* Mounting the SD card and using the files in a SD card
When the power is applied boot process is finished, insert an SD card into the device.
After some seconds it will echo some info about the card like this:
mmc0: new high speed SDHC card at address b368
mmcblk0: mmc0:b368 NCard 7.47 GiB
Now we know the name of the device we need. (i.e. mmcblk0 in my device. It can be different in your device)
Now we need a folder on our LeopardBoard to use it as the mount point for our SD card.
I use a folder called CARD in the root for this purpose.
now mount the SD card by:
mount /dev/mmcblk0 /CARD
If everything goes well, you won't see any errors.
now go to the folder we just created, and check the files in it.
all the files which are an the SD card are listed and can be used.
* [USB Host] Use a USB mass storage devices (e.g. USB card reader, USB hard disk, USB flash disk,...)
You need to change two jumpers in order to be able to power the external device. They are J1 and J4
J1 is open by default. Close it for USB host mode.
J4 is on pins 1 and 2 by default. Set it to pins 2 and 3 for USB host mode.
Jumpers positions for USB host mode
Power up the device and wait for the boot completion
Connect an external USB device to the USB port (You might need a USB adapter to connect your device to your board)
wait until it is ready and write down the name on the device.
refer to the steps above for mounting the disk. (Steps for mounting an SD card.)
Boot and Configuration files
* Booting the board without using the ethernet cable.
By default, LeopardBoard boots up using NFS. Which means you need to have a network connection during the boot process.
If you want to use the board as an standalone device, you need to use JFFS2, so that during the boot process it reads everything from the NAND memory, and no network connection is required.
To change the settings goto:
Filesystem Config > Filesystem image target >
and select JFFS2 for NAN boot.
exit the config
Please note that it might take some minutes before everything is programmed, so be patient.
* cmdline: Where is it?
Sometimes in some guides they ask you to change cmdline.
you can find it in your Linux machine at:
you need to change it after any make command and before make install, as it is overwritten by the make command.
* loadmodules.sh: Where is it?
In many guides including the official guide from RigdeRun, they ask you to run loadmodules.sh but where is it?
If you have RRSDK2011Q2, there is no loadmodules.sh file to edit or run. It is already integrated in the boot commands and loads automatically.
Instead, all the configuration files reside in $DEVDIR/fs/fs/etc and $DEVDIR/fs/fs/etc/init.d
* Memory error: CMEMK Error: Failed to find a pool which fits <poolsize>
If you get this error while trying to play or record a file, you can fix it in RRSDK2011Q2 as follows.
First of all make sure you have selected 720p (Not 480p) in make config under maximum video input buffer size.
It increases the buffer size for the video engine and it is not related to your real output size. (e.g. You can have CVBS output with 480p resolution but you must select 720p for increasing the buffer size)
Then goto make config>Proprietary software and change the amount of memory you want to assign for cmem as follows:
Here are some typical values to be able to play and record H.264 480p video files.
Amount of Reserved memory from kernel:= 0x3b00000 (Default is 0x1D00000)
Amount of reserved memory for cmemk:= 0x3200000 (Default is 0xF00000)
PART 3, Comming soon...
Lots of great information - thanks for sharing
> I wish there was a good wiki for LeopardBoard or at least an active FAQ section.
I suggest you go to
click on the "Create Account" in the upper right corner, then add this information to the FAQ section on that page (or move the FAQ to a new page and add a link from this page).
I have a few minor technical corrections to some of your entries. After you add your content to processors.wiki.ti.com I will add more details as to what is going on so my technical corrections will make sense to you.
I have added the topics above to TI's Wiki page as you asked.Here is the link: http://processors.wiki.ti.com/index.php/Leopard_Board_DM365_FAQ
Your technical corrections are most welcomed.Morteza