Linux Desktop SDK to MCSDK-HPC

PhilM5

Other Parts Discussed in Thread: 66AK2H12

Hi,

running a C6678 App from the X86 form the Linux desktop SDK shouldn't be much different from running the app on the 8x C66x from the A15 cluster on a 66aK2H12 .

Do we have recommendation/wikis/… for making this conversion ?

Thanks & Regards

over 9 years ago

0 Raja over 9 years ago

TI__Guru* 81335 points

Hi,

The target usage of Linux Desktop SDK and MCSDK-HPC are different. Please review the release page for more information.

Could you please elaborate your query?

Thank you.

0 PhilM5 over 9 years ago in reply to Raja

TI__Intellectual 1680 points

Hi Raja,

Prototyping was done on C6678 with its AMC PCIe adapter to fit into a host PC. Great results were achieved and now the plan is to migrate this into a Keystone-2 66aK2h12 device at minimum SW redesign cost/efforts.

Could you please elaborate on steps to achieve this ? (common APIs, shared memory instead of PCIe , etc ...)

Thanks & Regards

0 lding over 9 years ago in reply to PhilM5

TI__Guru* 95265 points

Assuimg when developed on C6678, you used Linux desktop to download the DSP code from Host to DSP and run, through the PCIE bus. Now, you also want to run the same code on K2H DSP cores, an easier way is to use MPM. Here the K2H ARM core running Linux is your host, through shared memory, not PCIE. See: http://processors.wiki.ti.com/index.php/MCSDK_UG_Chapter_Developing_System_Mgmt#Multiple_Processor_Manager

Regards, Eric

Processors

Processors forum

Linux Desktop SDK to MCSDK-HPC