OpenMP example: ti.omp.examples.platforms.evm6678: can't find referenced package ti.platforms.generic

Mark,
when you click on the project properties->CCS General->RTSC, which products do you have available? The platform ti.platforms.generic is now available only in SYS/BIOS or TI-RTOS, so you have to have one of these products selected.

Sorry, a rather incomplete response as it's late at night...

That error was occurring with SYS/BIOS 6.33.6.50 selected in the list of RTSC product repositories.

I then additionally enabled TI-RTOS 2.0.1.23. After that, linker errors occur when building the example.

For example:

ti_omp_utils_HeapOMP_isBlocking__E  
 ti_sdo_ipc_gates_GateHWSem_query__E         

That is with the "new" xdctools

The TI-RTOS package contains a platform ti.platforms.evm6678, when that is selected the following error results (for both versions of xcdtools):

configuring omp_config.xe66 from package/cfg/omp_config_pe66.cfg ...
js: "/home/markh/ti/omp_1_01_03_02/packages/ti/omp/utils/OpenMP.xs", line 142: TypeError: Cannot read property "base" from undefined (/home/markh/ti/omp_1_01_03_02/packages/ti/omp/utils/OpenMP.xs#142)

I guess all of this begs the question:

* is there some place I can go to look up what versions of the various TI tools and modules work with each other?

Obviously my starting point is that I need to port some code to the EVM6678, I don't really care whether the tools are old as long as they are not buggy. On the other hand all I'd prefer to be using reasonably up-to-date tools as we will also be looking into the Keystone-II multicores.

Mark

It seems that the original problem was fixed, and now you have new ones.
I am not that familiar with Open MP and PDK, but I know that IPC for example contains release notes where you can check for Compatibility Information and find out what the requirements are. I would expect that Open MP and PDK would have such information in their release notes.

Since the project built OK with XDCtools 3.23.x and SYS/BIOS but not TI/RTOS, it seems then that xdctools 3.30.x is missing other things that are present in 3.23.x - hence the unresolved references?

Or could it be that dependencies are tagged with version numbers & while the necessary module is present it is not known to be compatible with xdctools 3.30.x & hence cannot be used?

Is there any other (more automated!) way than examining the release notes for each module, that it is possible to build a list of mutually compatible modules?

Thanks

Mark

Mark,
the unresolved references are coming from Open MP and IPC. It's very likely that the changes between XDCtools 3.23 and 3.30, and SYS/BIOS 6.33 and 6.40 caused it but I can't really tell if the version of Open MP you are using is even tested against newer XDCtools and SYS/BIOS.
I'll have to get someone more familiar with Open MP to help.

As for automated compatibility checks, that functionality is available in XDCtools, but may or may not be used by software packages built using XDCtools.

Hi Mark,

The tools that are compatible are described in the MCSDK 2.01 download page.  Stick to using these tools and you should be good:

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/bios_mcsdk/latest/index_FDS.html

Eric

Thanks both of you for the pointers.

The take-home message seems to be that the best way to get started with the EVM6678 will be with the "old" software known to work with MCSDK 2.01 - I'll leave worrying about the Keystone-II toolchain until such time as there is hardware to play with.

One hopefully final question - the MCSDK page lists CCS 5.21 as a requirement - should I stick with that or go with 5.5 which is the most recent in the 5.x series?

Mark

Things are getting better... (though it's worth noting that as I'm on holiday I've been testing the "way forward" on a vista machine, not the Linux system with which I started...).

I have downloaded & installed CCS5.5 after having some weird behaviour from 5.21 (RTSC unable to access its configuration on the first attempt to install 5.21, and then on the second attempt no processor support for 6678). 

And the OMP "hello" builds fine... phew!

There was one niggle that really ought to be listed as a "gotcha" on the MCSDK 2.01 page, namely that the NDK bundled with MCSDK 2.1.2.6 is broken (as per [url=http://e2e.ti.com/support/embedded/tirtos/f/355/p/268489/938551.aspx]this thread[/url]).

After installing the MCSDK 2.1.2.6 bundle and before starting CCS, one should delete the ndk_2_21_01_38 folder, and download NDK 2.22.03.20 from [url=http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/2_22_03_20/index_FDS.html]here[/url], unpacking the zip file into the directory where ndk_2_21_01_38 was located (as far as I can tell 2.22.03.20 is the most recent NDK release that is compatible with the SYS/BIOS and XDCtools versions bundled with MCSDK 2.01 and CCS 5.5).

Have now tested with the EVM and all is well - though still lots to learn!

I've got the same problem with omp example. I've installed ccs55, mcsdk2.01.02.06, xdctools2.30 and 2.23, ndk2.22.03.20 and after that can't build project. Can you one more time tell what versions of all components you are using?

Excuse me. Already posted