sample_embedding_folder2/0724271.txt

Ticket Name: Linux/TDA2: A15 (Linux) EVE chain. How does it works?

Query Text:
Part Number: TDA2 Tool/software: Linux Hi, I have read in manual that A15 can't get acsess directly to EVE cores, and using IPU is recomended to organize link to EVE. When I set chain from A15 to EVE, vision sdk (I use 3.4) automatically connect cores throw IPU or I should do this manually? And I have quenstion about EVE configuration under Linux. In manuals is next steps: 1. Get .xearp32F 2. Convert .xearp32F -> .h (bin to hex converter utility was used). It means convert binary to header file like for TI Logo is used in sample app? bin to hex converter utility was used is uncluded in vision sdk? 3. What finction I should call to load program to EVE from IPU?

Responses:
Hello For "vision SDK Bios only" version EVE cores are handled same as any other cores like DSP or M4. With "vision SDK Linux" EVE loading and all inter processor communication between A15 and EVE are automatically taken care by EVE loader of VSDK, Its routed via IPU, Integreator/App need not to do anything special to address this. EVE firmware .xearp32F is embedded in IPU2 binary, yes, you are correct, SDK had tools to Convert .xearp32F -> .h (bin to hex converter utility used). you do not need to do anything special on IPU to program EVE, just port your Algos to EVE, create the UC on A15 as usual and build VSDK Linux, rest all are taken care in VSDK regards, Shiju