Howto build ndk 2.20.06.35 with ccs5

Patrik Svensson

Hi, have tried to build the ndk according to the wiki Rebuilding the NDK Core http://processors.wiki.ti.com/index.php/Rebuilding_the_NDK_Core.
Got this error: Import failed because its compiler definition is not available (Please contact support).
This happens when I try to import Existing CCS/CCE Eclipse project.
Tried an alternative import existing project into workspace, cannot build due to non-existant package.bld.
Can someone give me some ideas on howto proceed with this
Enclosing the modified Config.bld in the ndk:

* ======== config.bld ========

* This script is run prior to all build scripts. It initializes the

* rootDir configuration parameter of all supported targets.

* must define Code Generation Tools and BIOS installation locations here

* These variables are used to find the correct BIOS header files during a

* rebuild of the NDK libraries. At least one of these variables must be

* defined, depending on whether or not you are building for DSP/BIOS 5.x

* or SYS/BIOS 6.x.

* Note: when defining the path to your BIOS installation, you should use the

* forward slash ("/") character for path separation.

* For example, if you have installed SYS/BIOS 6 in the following

* location:

* C:/Program Files/Texas Instruments/bios_6_30_00_28

* Then you should specify bios6path as follows:

* // note use of "/" as path seperator:

* var bios6path = "C:/Program Files/Texas Instruments/bios_6_30_00_28/packages";

* Default build is for SYS/BIOS 6.30.00.28

//var bios5path = "C:/Program Files/Texas Instruments/bios_5_41_05_20/packages";

var bios5path = C:/ti/bios_5_41_11_38

//var bios6path = "C:/Program Files/Texas Instruments/bios_6_30_00_28/packages";

/* location of Code Generation Tools */

var rootDir = "C:/ti/ccsv5/tools/compiler/c6000"

// var rootDirArm = "C:/Program\ Files/Texas\ Instruments/ccsv4/tools/compiler/tms470"

var tiTargets = xdc.loadPackage('ti.targets');

//var elfTargets = xdc.loadPackage('ti.targets.elf');

//var armElfTargets = xdc.loadPackage('ti.targets.arm.elf');

var c6xSuffix = "-mi10 -mo -pdr -pden -pds=238 -pds=880 -pds1110 ";

/* TI targets we use */

tiTargets.C64P.rootDir = rootDir;

tiTargets.C64P.ccOpts.prefix = "-mv6400+ -o2 -ms2";

//tiTargets.C64P_big_endian.rootDir = rootDir;

//tiTargets.C64P_big_endian.ccOpts.prefix = "-mv6400+ -o2 -ms2 -DBIGENDIAN ";

//tiTargets.C674.rootDir = rootDir;

//tiTargets.C674.ccOpts.suffix = c6xSuffix;

/* ELF targets */

//armElfTargets.Arm9.rootDir = rootDirArm;

//armElfTargets.Arm9.ccOpts.prefix += " -ms";

//armElfTargets.A8F.rootDir = rootDirArm;

//armElfTargets.A8F.ccOpts.prefix += " -ms";

//elfTargets.C66.rootDir = rootDir;

//elfTargets.C66.ccOpts.suffix = c6xSuffix;

//elfTargets.C66.ccOpts.suffix += "--embed_inline_assembly ";

//elfTargets.C66_big_endian.rootDir = rootDir;

//elfTargets.C66_big_endian.ccOpts.suffix = c6xSuffix;

//elfTargets.C66_big_endian.ccOpts.suffix += "--embed_inline_assembly -DBIGENDIAN ";

Build.targets = [

tiTargets.C64P,

// tiTargets.C64P_big_endian,

// tiTargets.C674,

// armElfTargets.Arm9,

// armElfTargets.A8F,

// elfTargets.C66,

// elfTargets.C66_big_endian,

];

var commonDir = "ti/ndk/buildutils/";

var ndkPath = "$(PKGROOT)/ti/ndk/";

/* Configure the NDK Release Version Information */

var ndkReleaseVersion = [2,20,00];

/* Include Path */

var ndkPathInclude = " -i" + ndkPath + "/inc" + " -i" + ndkPath + "/inc/tools";

over 13 years ago

0 Tom Kopriva over 13 years ago

TI__Mastermind 20480 points

Hi Patrik,

could you post the full error log or a snapshot of it?

Are you using DSP/BIOS 5 or SYS/BIOS 6?

If you are using DSP/BIOS, could you check the bios5path variable in the config.bld? It should contain "packages".

var bios5path = C:/ti/bios_5_41_11_38/packages

If you are using SYS/BIOS, which versions of SYS/BIOS and XDCtools are you using?

0 Patrik Svensson over 13 years ago in reply to Tom Kopriva

Prodigy 50 points

1447.config.bld.txt
3617.error.log

Hi,
I am using DSP/BIOS 5.
You're right about the variable, corrected it but still the same error about the compiler configuration.
Trying to attach some files.

(The config.bld.txt was renamed from config.bld to fool your insertfile tool)

0 Tom Kopriva over 13 years ago in reply to Patrik Svensson

TI__Mastermind 20480 points

Hi Patrik,

The ndk_core_build project isn't working properly for me either (CCS v5.1.09000). The next release of the NDK will have a different procedure and wiki page explaining on how to build the NDK core libraries.

For now here's a workaround using the Windows Command Prompt.

Go into the windows command prompt.
C:\> cd C:\myNdkBuilds\custom_ndk_2_20_06_35\packages\ti\ndk
C:\myNdkBuilds\custom_ndk_2_20_06_35\packages\ti\ndk> xdc all

Once the libraries have been rebuilt, you should be able to build your NDK project against them using the same step described in Building Your Project Using the Rebuilt NDK Core Libraries for DSP/BIOS 5 Users.

0 Patrik Svensson over 13 years ago in reply to Tom Kopriva

Prodigy 50 points

Thanks, I managed to build the stack.
I also managed to build a c6455 hal driver but I did it my way by patching some files.
Is there a more official description on how to add custom drivers or code to the stack (I guess it's a somekind of standard build system but which?)?

// Patrik

0 Steven Connell over 13 years ago in reply to Patrik Svensson

TI__Mastermind 45025 points

Patrik,

You can add whatever code you wish to the NDK core stack and just rebuild as you already have in order to get the changes in.

For the evmOMAPL138 driver support (in the NSP product), we enabled it to be rebuilt in a similar fashion. However, the same cannot be said for older drivers (such as dsk6455), which shipped with NDK 2.0.

One document that may be of use to you is the NDK driver design guide. You can find a link to that in the NDK release notes.

Steve

Processors

Processors forum

Howto build ndk 2.20.06.35 with ccs5