Added updated software manifest
Merge branch 'release/v02.06.03.00'
Errata Advisory fix for C6678, C6657, C6670: Read exception and data corruption
ERRATA ADVISORY 28 (C6678), 14 (C6657), 33 (C6670) OVERVIEW:
* C6678 Errata 28: Page 43 of http://www.ti.com/lit/er/sprz334h/sprz334h.pdf
* C6657 Errata 14: Page 24 of http://www.ti.com/lit/er/sprz381c/sprz381c.pdf
* C6670 Errata 33: Page 58 of http://www.ti.com/lit/er/sprz332f/sprz332f.pdf
* Summary: Under specific circumstances, a pre-fetch for a cacheable
data access (program prefetches are not affected) that bypasses L2
can result in a read exception and/or data corruption.
* Solution: Disable prefetch for MSMC SRAM for C6678, C6657 and C6670
OTHER:
* Update CoreSDK version
* Cleanup whitespace
(MCT-1114)
ERRATA ADVISORY 28 (C6678), 14 (C6657), 33 (C6670) OVERVIEW:
* C6678 Errata 28: Page 43 of http://www.ti.com/lit/er/sprz334h/sprz334h.pdf
* C6657 Errata 14: Page 24 of http://www.ti.com/lit/er/sprz381c/sprz381c.pdf
* C6670 Errata 33: Page 58 of http://www.ti.com/lit/er/sprz332f/sprz332f.pdf
* Summary: Under specific circumstances, a pre-fetch for a cacheable
data access (program prefetches are not affected) that bypasses L2
can result in a read exception and/or data corruption.
* Solution: Disable prefetch for MSMC SRAM for C6678, C6657 and C6670
OTHER:
* Update CoreSDK version
* Cleanup whitespace
(MCT-1114)
Fix Ipc.setEntryMeta call with masterCoreIdx != 0
In OpenMP.xs, when calling Ipc.setEntryMeta, the remoteProcId used must
be the absolute index of the core, not the relative index in the
Multiproc cluster i.e. replace i with 'i+masterCoreIdx'.
This issue occurs only when OpenMP.masterCoreIdx != 0.
(MCT-1058)
In OpenMP.xs, when calling Ipc.setEntryMeta, the remoteProcId used must
be the absolute index of the core, not the relative index in the
Multiproc cluster i.e. replace i with 'i+masterCoreIdx'.
This issue occurs only when OpenMP.masterCoreIdx != 0.
(MCT-1058)
Fix a potential null pointer dereference reported by Klocwork
(MCT-920)
(MCT-920)
Update to build against CoreSDK 2018.00
(MCT-919)
(MCT-919)
Merge tag 'v02.06.02.01' into develop
Hotfix to remove legacy eclipse plugin generation
- MCT-841
Hotfix to remove legacy eclipse plugin generation
- MCT-841
Merge branch 'hotfix/v02.06.02.01'
Hotfix to remove legacy eclipse plugin generation
- MCT-841
- MCT-841
Updated to Core SDK ti2017.04-rc2
Updated Makefiles to build against customized CoreSDK+CMEM
(MCT-773)
(MCT-773)
Merge branch 'release/v02.06.02.00' for PSDK 17Q3 (4.1)
Update version to v02.06.03.00
Merge tag 'v02.06.01.00' into develop
v02.06.01.00
v02.06.01.00
Merge branch 'release/v02.06.01.00'
Update PSDK/CGT
Update version to v02.06.02.00
Merge tag 'v02.06.00.00' into develop
v02.06.00.00
v02.06.00.00
Merge branch 'release/v02.06.00.00'
Update PSDK
Update version to v02.06.01.00
Update PSDK
Update PSDK
Switched C6657 to using software queues
Merge branch 'develop_1q17' into develop
Merge pull request #2 in MCTOOLS/ti-openmp-dsp-runtime from mct623-swqs to develop_1q17
Linked list software queues with individual locks
* commit '7986417e494fa3818546f46acdd93aa146a8ce42':
software queues review feedback
linked list based software queues with less contention on locks
Linked list software queues with individual locks
* commit '7986417e494fa3818546f46acdd93aa146a8ce42':
software queues review feedback
linked list based software queues with less contention on locks
software queues review feedback
linked list based software queues with less contention on locks
Merge branch 'release/v02.05.00.00'
Update version to v02.05.01.00
Merge pull request #1 in MCTOOLS/ti-openmp-dsp-runtime from mq_k2x to develop_1q17
MCT-543.
* commit 'f1a1340eb0a4a38bfa59646abb4160ff2a529aba':
Switched to software queues for K2x
MCT-543.
* commit 'f1a1340eb0a4a38bfa59646abb4160ff2a529aba':
Switched to software queues for K2x
Switched to software queues for K2x
Merge tag 'v02.04.00.02' into develop
v02.04.00.02
v02.04.00.02
Merge branch 'hotfix/v02.04.00.02'
Update PSDK
Update version to v02.04.00.02
Merge branch 'hotfix/v02.04.00.01' into develop
Merge branch 'hotfix/v02.04.00.01'
MCT-609: Uniitialized variable causing assertion failure
In parallel regions without worksharing constructs, the use of an
uninitialized variable (dummy_ws->event) led to assertion failures from
GOMP_parallel_end due to an extra free.
[core 0] INTERNAL ERROR: รนรพ - src/tomp_queues.h, 121
In parallel regions without worksharing constructs, the use of an
uninitialized variable (dummy_ws->event) led to assertion failures from
GOMP_parallel_end due to an extra free.
[core 0] INTERNAL ERROR: รนรพ - src/tomp_queues.h, 121
Merge tag 'v02.04.00.00' into develop
Tagged v02.04.00.00 for Processor SDK 3Q release
Tagged v02.04.00.00 for Processor SDK 3Q release
Merge branch 'release/v02.04.00.00'
Updated version number
Updated version number
add k2l platform file and support for k2l in examples
Update PSDK
Merge tag 'v02.03.01.00' into develop
v02.03.01.00
v02.03.01.00
Merge branch 'release/v02.03.01.00'
Check for BUILD_AM57 == 0
Replace:
if (java.lang.System.getenv("BUILD_AM572"))
With:
if (parseInt(java.lang.System.getenv("BUILD_AM572")) == 1)
The first check return true even if BUILD_AM572 is set to 0 because
getenv return a string.
This problem was exposed by the yocto build because the recipe does the
following:
export BUILD_K2H = "0"
export BUILD_AM572 = "0"
export BUILD_K2G = "0"
And then sets the approproiate target to 1.
Replace:
if (java.lang.System.getenv("BUILD_AM572"))
With:
if (parseInt(java.lang.System.getenv("BUILD_AM572")) == 1)
The first check return true even if BUILD_AM572 is set to 0 because
getenv return a string.
This problem was exposed by the yocto build because the recipe does the
following:
export BUILD_K2H = "0"
export BUILD_AM572 = "0"
export BUILD_K2G = "0"
And then sets the approproiate target to 1.
Check for BUILD_AM57 == 0
Replace:
if (java.lang.System.getenv("BUILD_AM572"))
With:
if (parseInt(java.lang.System.getenv("BUILD_AM572")) == 1)
The first check return true even if BUILD_AM572 is set to 0 because
getenv return a string.
This problem was exposed by the yocto build because the recipe does the
following:
export BUILD_K2H = "0"
export BUILD_AM572 = "0"
export BUILD_K2G = "0"
And then sets the approproiate target to 1.
Replace:
if (java.lang.System.getenv("BUILD_AM572"))
With:
if (parseInt(java.lang.System.getenv("BUILD_AM572")) == 1)
The first check return true even if BUILD_AM572 is set to 0 because
getenv return a string.
This problem was exposed by the yocto build because the recipe does the
following:
export BUILD_K2H = "0"
export BUILD_AM572 = "0"
export BUILD_K2G = "0"
And then sets the approproiate target to 1.
Update PSDK
Update PSDK
Update version to v02.03.02.00
Updates to configure #cores dynamically from OpenCL
* Enables number of DSP cores to be dynamically configured from OpenCL. On
AM57, tomp_initOpenMPforOpenCL is called once per OpenCL application
instead of once per boot.
Renamed tomp_initOpenMPforOpenCL to tomp_initOpenMPforOpenCLPerApp to
avoid inadvertent link against older OpenMP runtime.
* Added -DTI_AM572 to ompbios library builds
* Added an extra heap index to avoid conflicts between openmp runtime and
user defined DDR heaps
* Moved need_mem_init initialization to OpenCL monitor since it must be
done once per monitor invocation.
* Updated version number to 2.3.1
Removed comment
* Enables number of DSP cores to be dynamically configured from OpenCL. On
AM57, tomp_initOpenMPforOpenCL is called once per OpenCL application
instead of once per boot.
Renamed tomp_initOpenMPforOpenCL to tomp_initOpenMPforOpenCLPerApp to
avoid inadvertent link against older OpenMP runtime.
* Added -DTI_AM572 to ompbios library builds
* Added an extra heap index to avoid conflicts between openmp runtime and
user defined DDR heaps
* Moved need_mem_init initialization to OpenCL monitor since it must be
done once per monitor invocation.
* Updated version number to 2.3.1
Removed comment
update to documentation for SDK 2.0.2
update intro section of documentation
Update PSDKs
fix patch verion # on develop
Merge branch 'hotfix/v02.02.01.03'
fix am57x NOLOAD auto-init and omp atomic race bugs
update version to 02.02.01.03
Merge tag 'v02.02.01.02' into develop
v02.02.01.02
Conflicts:
utils/eclipse/Product.xdc
utils/product/version.txt
v02.02.01.02
Conflicts:
utils/eclipse/Product.xdc
utils/product/version.txt
Merge branch 'hotfix/v02.02.01.02'
Fix K2G .tomp_svNcMem initialization
Update version to v02.02.01.02
Merge tag 'v02.02.01.01' into develop
v02.02.01.01
Conflicts:
utils/product/version.txt
v02.02.01.01
Conflicts:
utils/product/version.txt
Merge branch 'hotfix/v02.02.01.01'
Fix task barrier at end of parallel region with num_threads(1)
Avoid unused QMSS dependency on K2G
Update version to v02.02.01.01
Merge tag '2.02.01.00' into develop
Tag 2.02.01.00
Tag 2.02.01.00
Merge branch 'release/2.02.01.00'
Update version to 02.03.00.00
Update changelog
Add K2G support
Update PSDK
Update Makefile.inc
Update SDKs
Merge tag 'v02.02.00.00' into develop
Tag for Processor SDK 4Q
Tag for Processor SDK 4Q
Merge branch 'release/v02.02.00.00'
Merge branch 'release/v02.02.00' of gitorious.design.ti.com:openmp/ti-openmp-dsp-runtime into release/v02.02.00
barrier and taskwait bug fixes
Updated documentation to remove modes
RTSC mode is now the default. Removed the notion of modes from the
documentation.
RTSC mode is now the default. Removed the notion of modes from the
documentation.
Fixed a makefile issue with duplicated source files
Build system changes required by new KeyStone SDKs
* Ability to build any one of C6678, C6670, C6657 or C6636 using the
BUILD_XXX environment variables:
BUILD_AM572=1 make -f utils/product/Makefile .zipfile
BUILD_C6678=1 make -f utils/product/Makefile .zipfile
BUILD_C6657=1 make -f utils/product/Makefile .zipfile
BUILD_K2H=1 make -f utils/product/Makefile .zipfile
* Cleaned up examples, all can be build via a top level Makefile
* Updated qmss global object for Keystone to sync with PDK changes
* Added device name into OpenMP package. There are 4 supported devices,
each with its own package. The k2x package can be used with K2H, K2L
and K2E.
openmp_dsp_c667x_2_<version>
openmp_dsp_c657x_2_<version>
openmp_dsp_am57xx_2_<version>
openmp_dsp_k2x_2_<version>
* Ability to build any one of C6678, C6670, C6657 or C6636 using the
BUILD_XXX environment variables:
BUILD_AM572=1 make -f utils/product/Makefile .zipfile
BUILD_C6678=1 make -f utils/product/Makefile .zipfile
BUILD_C6657=1 make -f utils/product/Makefile .zipfile
BUILD_K2H=1 make -f utils/product/Makefile .zipfile
* Cleaned up examples, all can be build via a top level Makefile
* Updated qmss global object for Keystone to sync with PDK changes
* Added device name into OpenMP package. There are 4 supported devices,
each with its own package. The k2x package can be used with K2H, K2L
and K2E.
openmp_dsp_c667x_2_<version>
openmp_dsp_c657x_2_<version>
openmp_dsp_am57xx_2_<version>
openmp_dsp_k2x_2_<version>
Bumped up version to 2.02.01.00
Added 6636 to device names tested for K2H
add tomp_dispatch_finish for am57x accelerator model
Moved RTSC mode init function back into app cfg, added example
* Added an example to illustrate initializing QMSS in the application
* Moved adding __TI_omp_initialize_rtsc_mode to Startup.lastFxns back into
the application config file. The flexibilty is required to ensure a QMSS
init function inthe application can be added to lastFxns before
__TI_omp_initialize_rtsc_mode
* Updated documentation to indicate that caching for the memory ranges must
be set up correctly when the application initializes QMSS. It is important
to ensure that the non-cached section of MSMC is set up before the
application QMSS initialization function is called.
* Added an example to illustrate initializing QMSS in the application
* Moved adding __TI_omp_initialize_rtsc_mode to Startup.lastFxns back into
the application config file. The flexibilty is required to ensure a QMSS
init function inthe application can be added to lastFxns before
__TI_omp_initialize_rtsc_mode
* Updated documentation to indicate that caching for the memory ranges must
be set up correctly when the application initializes QMSS. It is important
to ensure that the non-cached section of MSMC is set up before the
application QMSS initialization function is called.
Cleaned up build process
* Added Makefile.inc in utils/product to set up paths for K2x builds.
* Dropped the /package suffix from environment variables such as
BIOS_DIR, IPC_DIR. Updated Makefile.libs correspondingly.
* Added Makefile.inc in utils/product to set up paths for K2x builds.
* Dropped the /package suffix from environment variables such as
BIOS_DIR, IPC_DIR. Updated Makefile.libs correspondingly.
Set CSL deviceType appropriately for K2H/L/E
chmod +x .csh scripts
add sitara am572 support
Fix "Disabled latex based user guide generation"
Disabled doxygen builds in error, re-enable. Disable user guide build
from latex source.
Disabled doxygen builds in error, re-enable. Disable user guide build
from latex source.
Disabled latex based user guide generation
The OpenMP runtime has switched to using Sphinx for documentation. The
latex -> pdf build to generate the user guide has been disabled.
The OpenMP runtime has switched to using Sphinx for documentation. The
latex -> pdf build to generate the user guide has been disabled.
Add SOC_K2H flag for CSL changes
Merge tag 'v02.01.17.02' into develop
v02.01.17.02
v02.01.17.02
Merge branch 'hotfix/v02.01.17.02'
Configuring the OpenMP runtime in RTSC mode to use a subset of the cores starting with a non zero master core index (OpenMP.masterCoreIdx) does not work as expected. This is fixed in OpenMP Runtime version 2.01.17.02.
Configuring the OpenMP runtime in RTSC mode to use a subset of the cores starting with a non zero master core index (OpenMP.masterCoreIdx) does not work as expected. This is fixed in OpenMP Runtime version 2.01.17.02.
Defect fix - runtime configuration with non zero master core
Configuring the OpenMP runtime in RTSC mode to use a subset of the cores
starting with a non zero master core index (via OpenMP.masterCoreIdx) does
not work as expected. This is fixed in OpenMP Runtime version 2.01.17.02.
Configuring the OpenMP runtime in RTSC mode to use a subset of the cores
starting with a non zero master core index (via OpenMP.masterCoreIdx) does
not work as expected. This is fixed in OpenMP Runtime version 2.01.17.02.
Merge branch 'feature/port-k2el' into develop
Merge branch 'develop' into feature/port-k2el