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.

Building DSPLink 1.65.00.03

Other Parts Discussed in Thread: OMAP3530

Hi everyone,

 

     I’m currently working on the BeagleBoard xM Rev B. I’ve booted up the board successfully with a demo Angstrom image (bootloaders + kernel image + filesystem) which I downloaded from : http://www.angstrom-distribution.org/demo/beagleboard .

 

     I now want to install DSPLink on the Beagleboard. For that purpose, I downloaded TI’s DSPLink 1.65.00.03 from the link : http://software-dl.ti.com/dsps/dsps_public_sw/DSPLink/1_65/1_65_00_03/index_FDS.html .

 

  • I read the InstallGuide, UserGuide and Release Notes that came alongwith the DSPLink Package release.
  • I’ve downloaded all the compatible versions of the dependencies required (DSP/BIOS, CGTools, Code Sourcery ARM-Linux ToolChain, PSP), as mentioned in the Release Notes and have installed them in all the correct directories, as mentioned in the Install Guide.
  • After installation of all the dependencies, I modified the correct Makefiles (.mk) to point to the correct paths for the dependencies.

 

      But when I started building all the sources and the sample applications by using the “make –s [debug | release]” command, I started getting an error which was (Bold letters):

 

root@ubuntu:~/dsplink_linux_1_65_00_03/dsplink/gpp/src# make -s debug


[SRC                 ] ======= DIRS ================== INCLUDE ============
[API                 ] ------- DIRS ------------------ INCLUDE ------------

[SRC                 ] ======= DIRS ================== DEBUG ==============
[API                 ] ------- DIRS ------------------ DEBUG --------------

[SRC                 ] ======= DIRS ================== EXPORT =============
[API                 ] ------- DIRS ------------------ EXPORT -------------

[SRC                 ] ======= BLDINFO =============== DEBUG ==============
[API                 ] ------- DIRS ------------------ DEBUG --------------
[API                 ] ------- BLDINFO --------------- DEBUG --------------

[SRC                 ] ======= CLEAN ================= DEBUG ==============
[API                 ] ------- CLEAN ----------------- DEBUG --------------

[SRC                 ] ======= INCLUDES ===================================
[API                 ] ------- INCLUDES -----------------------------------
[API                 ] ------- DIRS ------------------ INCLUDE ------------

[SRC                 ] ======= OBJECTS =============== DEBUG ==============
[API                 ] ------- DIRS ------------------ DEBUG --------------
[API                 ] ------- OBJECT ---------------- DEBUG --------------
Fetching the configuration file CFG_OMAP3530_SHMEM.c ...
Fetching the configuration file CFG_Linux.c ...
Fetching the configuration file CFG_ARM.c ...
Compiling CFG_system.c...
Compiling CFG_Linux.c...
Compiling CFG_ARM.c...
Compiling CFG_OMAP3530_SHMEM.c...
Compiling proc.c...
Compiling chnl.c...
Compiling msgq.c...
Compiling mpcs.c...
Compiling _mpcs.c...
Compiling _idm_usr.c...
Compiling ringio.c...
Compiling _ringio.c...
Compiling mplist.c...
Compiling _mplist.c...
Compiling pool.c...
Compiling _pool.c...
Compiling pool_arch.c...
Compiling _sync_usr.c...
Compiling _mem_usr.c...
Compiling drv_api.c...
Compiling _mpcs_os.c...
Compiling notify.c...
Compiling _notify.c...

[SRC                 ] ======= TARGETS =============== DEBUG ==============
[API                 ] ------- TARGET ---------------- DEBUG --------------
Generating library : /home/ubuntu/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/API/BIN/DEBUG/dsplink.o...
Generating library : /home/ubuntu/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/API/BIN/DEBUG/dsplink.lib...
Generating archive : /home/ubuntu/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/API/BIN/DEBUG/dsplink.a...
/home/ubuntu/TI/arm-2009q1-203/bin/arm-none-linux-gnueabi-ar: creating /home/ubuntu/dsplink_linux_1_65_00_03/dsplink/gpp/BUILD/API/BIN/DEBUG/dsplink.a

[SRC                 ] ======= EXPORTS =============== DEBUG ==============
[API                 ] ------- EXPORT ---------------- DEBUG --------------
Building kernel side code using kbuild

  ERROR: Kernel configuration is invalid.
         include/linux/autoconf.h or include/config/auto.conf are missing.
         Run 'make oldconfig && make prepare' on kernel src to fix it.


  WARNING: Symbol version dump /home/ubuntu/TI/omap3530/REL_OMAP35x_02.00.00.01/PSP_02.00.00.01/src/linux-02.00.00.01/Module.symvers
           is missing; modules will have no dependencies and modversions.

  Building modules, stage 2.
/home/ubuntu/TI/omap3530/REL_OMAP35x_02.00.00.01/PSP_02.00.00.01/src/linux-02.00.00.01/scripts/Makefile.modpost:43: include/config/auto.conf: No such file or directory
make[2]: *** No rule to make target `include/config/auto.conf'.  Stop.
make[1]: *** [modules] Error 2
make: *** [debug] Error 2

 

 

 

 

          After this, I tried to run the “make oldconfig && make prepare” command on the kernel source code that was present in the PSP directory, but to no avail. I even used the “make CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm menuconfig” command and configured the kernel for OMAP3530 and the BeagleBoard, but I still keep getting this error when I try to build the sources for both the GPP and DSP side. Does the PSP version 3.00.00.05 have some problem ? Please help me as I’ve been stuck due to this error for over a week now.  

 

Thanks in advance

Harsh

  • You need to do more than just config'ing the Linux kernel, you also need to build the kernel image.  Can you try that?:
        % make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

    Regards,

    - Rob

  • Hi Robert !

          Thanks for the response. Actually I already have a working BeagleBoard with Angstrom binaries. Do I dont just need to compile the sources for DSPLink so as to generate a kernel module (.ko) which I can insert into the existing kernel configuration using the "insmod" command ? Why do I need to make another kernel Image (uImage) ?

     

    Regards

    Harsh 

  • Hi Robert !

           I have another doubt.

          The release notes for DSPLink 1.65.00.03 does not mention the PSP version which needs to be downloaded.

          But the Install Guide for the OMAP3530 mentions a number of kernel sources, which has confused me. Page 11 (of 23), section 7 "Setting up Linux Workstation" says that REL_OMAP35x_02.01.00.02 release needs to be installed, whereas Page 12, section "7.1.2 Kernel" mentions that PSP Version 3.00.00.05 needs to be downloaded. And to top it all, on Page 15, in the Build the DSP/BIOS Link section, the path to the Rules.mk mentions REL_OMAP35x_03.00.00.03. I'm really confused as to what PSP version I should download and use for building the sources. 

          Please mention the PSP version that needs to be downloaded and please also give the download link.

     

    Thanks in advance

    Harsh

     

  • Harsh Gupta said:
    Thanks for the response. Actually I already have a working BeagleBoard with Angstrom binaries. Do I dont just need to compile the sources for DSPLink so as to generate a kernel module (.ko) which I can insert into the existing kernel configuration using the "insmod" command ? Why do I need to make another kernel Image (uImage) ?

    It's not so much the kernel binary uImage that is needed for building a .ko file, but some of the intermediate files that get generated as part of a kernel build.  I'm not sure what files in particular, but you need to point to more than just source files in the kernel for building a .ko that will insmod with that kernel.

    Having said that, if you follow my instruction you will get a dsplinkk.ko that has been linked against a kernel that is different than the one you're running.  This can cause problems during insmod, since the kernel binary that you're running is not the one from the tree that you pointed your dsplinkk.ko build to.

    Go ahead and try out the dsplinkk.ko with the prebuilt Beagleboard kernel image that you're already using, and if it insmod's OK then you should be good-to-go.  But if there is a problem during insmod, you will need to either run the kernel binary that you built yourself (for the dsplinkk.ko build), or you will need to point your dsplinkk.ko build at the fully populated tree from which the Beagleboard prebult kernel came.

    Regards,

    - Rob

  • Harsh Gupta said:

          The release notes for DSPLink 1.65.00.03 does not mention the PSP version which needs to be downloaded.

    I found this copy of release notes for DSPLink 1.65.00.03: http://processors.wiki.ti.com/images/b/bb/ReleaseNotes.pdf

    In there it mentions this:

     3.2.2.5 For working with OMAP3530 PSP release PSP release AM35x-OMAP35x-PSP-SDK-03.00.00.05 with tool chain version arm-2009q1-203.

     

     

    CCS 3.3 IDEDSP CG Tools version v6.0.18 or greaterStandalone DSP/BIOS™ 5.32.04.

     

     

     

    Harsh Gupta said:

          Please mention the PSP version that needs to be downloaded and please also give the download link.

    I found this link, see if it helps: http://software-dl.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/OMAP_03_00/index.html

    Regards,

    - Rob