build: Descoping C64x and C66 big endian The C64x and c66 big endian platform are no longer supported and hence getting removed from the build files . Signed-off-by: Sam Nelson <sam.nelson@ti.com>
tests: R5F Split mode support Add code to build separate test images for R5F0, R5F1. R5F0 images can be used AS-IS with R5F cores in Lock step mode Note the DDR memory is partitioned according to the Linux device tree nodes for r5f-0 and r5f-1 Signed-off-by: Sam Nelson <sam.nelson@ti.com>
K3: Add support for K3 AM65XX device - Adds support for A53 and R5F cores - Adds IPC VirtQueue, Interrupt & Notity drivers for AM65XX platform. - gates: Add V7R and v8A support Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Build scripts: Add far model for ipc data This helps to relocate and place data sections without any restrictions. Signed-off-by: Sam Nelson <sam.nelson@ti.com>
ipc-bios.bld: Add building of smp libraries for A15 Previously smp was supported for M4 targets only. Adding A15 support now. Signed-off-by: Sam Nelson <sam.nelson@ti.com>
ipc-bios.bld: Update default platform for C6678 - Also update print string for unknown platform Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Initial Keystone 2 Galileo build support on DSP Add new device name 66AK2G to top-level products.mak file. Add device TCI66AK2G02 alias to ti.sdo.ipc.family.Settings.
c28: remove c28 support Delete C28-related packages, and remove build-related support. Signed-off-by: Chris Ring <cring@ti.com>
Added new TDA3xx platform.
Create Keystone platform instances with no external DDR defined On MAR-based cores (i.e., C6x), SYS/BIOS will, by default, set the "cacheable" bit for any external memory that it "sees", i.e., any external memory that is defined for the platform. This happens regardless of whether or not that memory is used for program placement. This cacheable-ness is somewhat hidden to the programmer. In order to offer better control of this, Keystone platform instances are created with no external memory defined. This allows all MAR pages to be tagged "non-cached" by default, and the programmer is free to set MAR bits to their liking.
66AK2E: BIOS: Remove leading 'C' in device name The initial support for 66AK2E (commit 867efc6fa15f91639820614f6f9ca6ee6751ffa6) went in with the 'C66AK2E' identifier. After review by the MCSDK team, the leading 'C' was incorrect and removed. The XDC platform and catalog includes this leading 'C', so most of the internal config-related support did not require changes. Finally, this is only the BIOS-side changes. The Linux-side changes will be done in a subsequent commit.
BIOS: Enable xdc__strict and fix issues XDC provides a xdc__strict feature. Defining that pre-processor variable prior to #including <xdc/std.h> will disable deprecated data types (e.g. Uint32 - note the lowercase 'i') and change NULL from '0' to '(void *)0'. This commit throws that xdc__strict definition when building the BIOS-side code, and fixes issues that were found enabling it. Interestingly, there were a few bugs that turned up during this exercise (rare in the wild, but still good cleanup).
C66AK2E: BIOS: Introduce support for C66AK2E The C66AK2E device is an A15 + C66 DSP, similar in hardware to the TCI663X family of devices. This commit adds BIOS-side support.
TCI6630: BIOS: Introduce support for TCI6630K2L The TCI6630K2L device is an A15 + 4 C66 DSPs, very similar to TCI6638K2K (A15 + 8 C66 DSPs). This commit adds BIOS-side support.
SDOCM00099002 Make LibType_Debug build profile same as custom. Merged updates in ti.sysbios.Build module into ti.ipc.sdo.Build. Turn off package library builds when building IPC for product release. Added ti.sdo.ipc.Build.libType config param. Added source files to Pkg.otherFiles for source only release. Added package debug library build support. Removed package ti.sdo.utils from ti.sdo.ipc.Build file list, it builds separately now.
Build: Align products.mak variables across OS's The make variable to indicate a platform is now consistent between BIOS, QNX and Linux, and only needs to be set once. Note that this is a compatibility break for consumers (e.g. SDKs) which automate the consumption/build of IPC. This is consciously being introduced in a new Major.minor release (3.20) to keep from breaking 3.00 and 3.10 users. This resolves SDOCM00103415.
Build: Enable builds without SMP support Some customers (including the TI RTOS SDK) do not use SMP BIOS and therefore don't require the libraries. To improve build times and reduce the disk size for these users, a new variable, BIOS_SMPENABLED, was created in products.mak. Its default value is 1 (enabled), which maintains the behavior of previous releases. Setting it to 0 disables the build of SMP-enabled libraries. Note that some platforms require SMP libraries to be built, otherwise their test executables may fail to build. This resolves SDOCM00103413.
Vayu: Tests: Add support for IPU1 and DSP2 - Resource Table: Vring physical addresses are made unique depending on VAYU core, and need to match CMA base addresses; given both DSP and IPU have IOMMU's, the device addresses otherwise remain the same. - Adjust test image memory maps to fit in 6MB footprint for initial testing. - Add support to build tests for IPU1 and DSP2 platform instances. Signed-off-by: G Anthony <a0783926@ti.com> [s-anna@ti.com: add dsp2 and ipu1 build targets] Signed-off-by: Suman Anna <s-anna@ti.com> Vayu: Tests: Adjust memory maps for IPU1 and DSP2 Retain the memory map for IPU2 while creating a newer memory map for IPU1. Also fix some of the other sizes. Signed-off-by: Suman Anna <s-anna@ti.com>
Build: Entry point alignment to ti.ipc.remoteproc Move the logic ensuring entry point alignment from ipc-bios.bld into ti.ipc.remoteproc. This is a commonly used package in environments where these alignment constraints exist. This also enables customer executables to 'freely' meet the necessary entry point alignment requirements without explicitly doing anything. Note that because of the clever technique employed to ensure alignment, namely setting the entry point to BIOS's already-aligned HWI vector table, we only override the entry point this flag if BIOS is used. If BIOS is not used, it becomes the application's responsibility to ensure any device-specific entry point alignment constraints are met. A nice side effect is that ipcdev can now build executables that don't have a BIOS dependency.
C64T: use common C6x compiler opts The compiler options IPC throws for the C64T target should be the same as other C6x targets; there's no need for them to be different. Note that these C64T-specific flags were introduced in 8f8201d89c330e1776645b572b9151ea9b5e99ce. This commit reverts that.