OMAP L1 SDK build on fedora

Hi Carl,

Can you please include your SDK version so that we can reproduce the issue?

Thanks, Niclas

I downloaded all the latest releases from the website; bios was 5.41_02_14,  the code gen build tools 6.1.9.

 OMAP was  OMAP_L138_arm_1_00_00_08.tar.gz.  I didn't download codeSourcery yet- told I didn't need to to

simply verify the make check.

  fedora is 2.6.22.14

   This work was done just this week.      thx   Carl

If the SDK software components were installed as <root> and you are trying to execute the "make' as a different <user> there might be a permission issue.  You might what to check permissions on the SDK root directory and it's installed components..

Permission a-side,  to successfully perform a 'make check' from the top level SDK, you do in fact need a few more components to be installed including the Code Sourcery Tools.  Instructions on installing all necessary components are located at:

http://wiki.davincidsp.com/index.php/GSG:_Installing_the_Software_for_OMAP-L1#Installation_steps

and also following the step from the 'Rebuilding the Linux Kernel -> Preparing you Environment" section at:

http://wiki.davincidsp.com/index.php/GSG:_Building_Software_Components_for_OMAP-L1#Preparing_your_Environment

and setting all the correct variables in the top level Rules.make as noted:

http://wiki.davincidsp.com/index.php/Building_The_OMAP-L1_SDK#Quick_build_instructions_for_OMAPL-138

I did not install as root..  but I was advised I didn't need CodeSourcery.

 Actually i had installed it, but then un-installed it when i found it had put files in several unexpected places;

 it didn't for example put the codeSourcery_ Lite in the CodeSourcery directory.

 So I uninstalled.

 But I'll re-install, as well as run the step on Rebuilding the Linux Kernel.

  I didn't do that originally because the OMAP 138 from LogicPD had embeded Linux installed already.

 So i was trying to check this rather involved  build utility installation a step at a time.               thx    Carl

I still suspect a permission issue in the directory where the SDK was installed.  As even without the Code Sourcery Tools and following the steps 'Preparing your environment" section for Rebuilding the Linux Kernel, you should get an error as follows when running 'make check' :

user@user-desktop:~/OMAP_L138_arm_1_00_00_08$ make check
Checking that components in Rules.make are found:
.
WARNING: <CROSS_COMPILER_DIR>/bin/arm-none-linux-gnueabi-gcc doesn't exist, check your Rules.make..
WARNING: <KERNEL_DIR>/DaVinci-PSP-SDK-03.20.00.08/da850/linux-03.20.00.08/Documentation doesn't exist, check your Rules.make..
WARNING: /docs doesn't exist, check your Rules.make..
Done checking! If no warning messages above, all components are found..

Thats what I expected , by doing the   make check  before the other installations were done.    Sort of an intermediate

 test to let me know the first steps of the install were OK.   I expected the results you show - that I still need to install components.

So I'd like to be able to get this message,before proceeding to the next steps. 

 If i do a make check out side the SDK directory,  ie one level above the OMAP_L138_arm  etc  ,    I get this message:

  make: *** No rule to make target 'check' . Stop

  which suggested I was not somehow prohibited from usin this make facility.

  Could there be a problem in the .bachrc          I set the path , I think.             thx   Carl

What was the exact permission error you encountered when running 'make check', was it similar to the following:

user@user-desktop:~/OMAP_L138_arm_1_00_00_08$ make check
/bin/sh: /home/user/OMAP_L138_arm_1_00_00_08/bin/check.sh: Permission denied
make: *** [check] Error 126

I was able to get this error by simply changing my permission in the SDK install directory, by doing the following:

user@user-desktop:~/OMAP_L138_arm_1_00_00_08$ chmod -x *

Note:  I force the error to occur.

I un-tared OMAPL138 SDK (tar zxf OMAP_L138_arm_1_00_00_08.tar.gz) obtained from the OMAPL138 SDK web-site, to ensure that permission were set correctly in this file, when I executed 'make check' I got this:

user@user-desktop:~/OMAP_L138_arm_1_00_00_08$ make check
/bin/sh: cannot open SDK_INSTALL_DIR: No such file
make: *** [check] Error 2

Thus permission for the content of this file seems to be fine.

Note:  To un-do my forced permission error above, I undid my permission change as follows:

user@user-desktop:~/OMAP_L138_arm_1_00_00_08$ chmod +x *

  Here's the error I get:

   /bin/sh: /bin/check.sh: Permission denied

 make: ***[check] error 1

  I'm doing a re-install now.  the first step, after a download from the web site, is to make all the .bin files executables.

this is done with>   chmod +x *.bin.

 does this change the compressed tar file executable,  the OMAP_L138-arm_1_00   etc.tar.gz also executable?

 do I need to repeat the last stpe you show,which is the    chmod +x *    ?      thx     carl

The  < chmod +x *.bin > just make the *.bin files (BIOS, XDCTOOLS, etc) executable by you so that they can be installed.

Most of the OMAPL138 SDK component are contained in the tar.gz file (OMAP_L138_arm_1_00_00_08.tar.gz).  You simple need to extract it and all the proper permission for everything it extract should be set.

With that said, to fix your current installation you could run:

chmod +x * from with in your OMAP_L138-arm_xx_xx_xx_xx.  This should fix your current problem.  The interesting question is why did the permissions change on your setup when the extracted OMAP_L138_arm_1_00_00_08.tar.gz sets it correctly in the first place.

   FYI,  the first line in Rules.make   is :

   SDK_INSTALL_DIR      =   </home/shop/CR_work/OMAP_L138_arm_1_00_00_08>

  this causes the "permission denied"  message.  see anything wrong?     thx  CR

   do you guys have any further comments or recommendations on how to resolve the   rules- check issue I'm having?       thx   Carl

I have to assume that TI is unable at this time to answer the question of whether Fedora can be used as a workstation to develop

embedded Linux applications for the OMAP 138.       

You should remove the '<' and '>' from the definition of your SDK_INSTALL_DIR.

The SDK_INSTALL_DIR, should be defined as:

SDK_INSTALL_DIR      =   /home/shop/CR_work/OMAP_L138_arm_1_00_00_08