TMS320C6657: porting from C6678 to C6657 PDK

Kannan Sockalingam

Intellectual 1905 points

Part Number: TMS320C6657
Other Parts Discussed in Thread: SYSBIOS

Tool/software:

Hi team,

A customer is working on is the port of PDK for C6678 changing to a PDK targeted for C6657.

These are the current build errors:

Building file: "../Pluto_C6657_Core1.cfg"

Invoking: XDCtools

"C:/ti/xdctools_3_55_02_22_core/xs" --xdcpath="C:/ti/bios_6_76_03_01/packages;C:/ti/pdk_c665x_2_0_16/packages;C:/ti/uia_2_30_01_02/packages;C:/ti/bios_6_76_03_01/packages/ti/posix/ccs;C:/ti/ndk_3_61_01_01/packages;C:/ti/ipc_3_50_04_08/packages;C:/ti/edma3_lld_2_12_05_30E/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6657 -r debug -c "C:/ti/ccs930/ccs/tools/compiler/ti-cgt-c6000_8.3.5" "../Pluto_C6657_Core1.cfg"

making package.mak (because of .xdcenv.mak) ...

configuring Pluto_C6657_Core1.xe66 from package/cfg/Pluto_C6657_Core1_pe66.cfg ...

subdir_rules.mk:12: recipe for target 'build-8928465-inproc' failed

js: "C:/Users/M45567/OneDrive - NGC/Home/Programs/NextGen_ServoDSP/PlutoServoDSP_2023/latest/Pluto_DSP/C6657_Master_CPU/Pluto_C6657_Core1/Pluto_C6657_Core1.cfg", line 115: xdc.services.global.XDCException: xdc.PACKAGE_NOT_FOUND: can't locate the package 'ti.drv.pa' along the path: 'C:/ti/bios_6_76_03_01/packages;C:/ti/pdk_c665x_2_0_16/packages;C:/ti/uia_2_30_01_02/packages;C:/ti/bios_6_76_03_01/packages/ti/posix/ccs;C:/ti/ndk_3_61_01_01/packages;C:/ti/ipc_3_50_04_08/packages;C:/ti/edma3_lld_2_12_05_30E/packages;C:/ti/xdctools_3_55_02_22_core/packages;..;'. Ensure that the package path is set correctly.

"./package/cfg/Pluto_C6657_Core1_pe66.cfg", line 196

gmake.exe: *** [package.mak:204: package/cfg/Pluto_C6657_Core1_pe66.xdl] Error 1

js: "C:/ti/xdctools_3_55_02_22_core/packages/xdc/tools/Cmdr.xs", line 52: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.

gmake[1]: *** [build-8928465-inproc] Error 1

gmake: *** [build-8928465] Error 2

subdir_rules.mk:9: recipe for target 'build-8928465' failed

**** Build Finished ****

6 months ago

0 Praveen Rao 6 months ago

TI__Mastermind 48243 points

Hi,

Can you ask the customer to share the TI SDK version and the complete code changes done along with the build environment and steps followed?

Thanks.

0 Kannan Sockalingam 6 months ago in reply to Praveen Rao

TI__Intellectual 1905 points

Praveen, still ongoing on this issue. Moved along a bit. I will get you the SW version tmrw.

Engineer was able to get the project to build for C6657, but then had issues that CCS could not load and debug the project because most all of the memory was mapped for DDR3 that had previously been available and configured on the C6678 dev board.

Next, he was able to move all the memory segments into L2SRAM and MSMCSRAM. Also, had to reduce the size of the heap to get all the memory mapping to fit into those two segments, but the NDK initializations are failing.

They have 3 DDR3 ram chips which are Micron MT41K128M16JT-125 IT:K. These are 16-bit wide memory which we expect now requires some gel file or run-ime C code to initialize CPU registers properly to access those DDR3 memory.

I would appreciate support for configuring this DDR3 memory and next steps porting the SysBios NDK for C6657. Are you able to help provide the gel file?

0 Praveen Rao 6 months ago in reply to Kannan Sockalingam

TI__Mastermind 48243 points

Kannan,

Thanks for updating with the latest status. Good to know that they were able to build successfully.

Just to set the expectation, we can only provide support for what is in the SDK. Providing support for any custom work on their platform will be challenging. Please note that our Apps team is lean and thin and has limited expertise on these K2 devices, as most experts are no longer with the company.

One option is that we can provide some 3P contacts whom the customer can engage for support.

Let us know,

Thanks.

0 Bryan Fredrickson 5 months ago in reply to Praveen Rao

Prodigy 10 points

Praveen,

We are currently stuck in that our custom board design is using a DDR3 memory part (Micron MT41K128M16JT-125 IT:K) which we are unable to load via JTAG debugger nor initialize at run-time.

Our thinking is that we need to modify a gel file for this DDR3 memory access to be loadable by the JTAG debugger. Long term, we would need this DDR3 to be initialized at startup for boot from EMIF flash option.

Previous to have a custom hardware board, we went down a path of maturing our software project on a C6678 development board. Now that we have finally received our custom board with C6657, the project build memory footprint does not fit into internal RAM (L2SRAM and MSMCSRAM). We do need to allocate some segments in the DDR3 to load and execute.

At this point we are unsure if we have a DDR3 circuitry issue or just need proper DDR3 initialization (gel file or run-time c code). Our software project is stopped until we can load and run a project software build on the custom hardware.

If we could get some help customizing a gel fil to allow JTAG load and debug of memory in the DDR3, that would be appreciated and keep our project moving.

Thank you