This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-TDA4VM: Folders deleting with RTOS SDK

Part Number: SK-TDA4VM

Hello team, 

Customer still has some outstanding questions on the SDK. Please refer below. Thanks!

~~~~~~~~~~~~~~~~~

In the plain untarred ti_rtos SDK I see several file in this particular folder which gets deleted when I run a "make sdk_scrub" without even doing an initial make , "pdk_jacinto_08_01_00_36/packages/ti/binary" . This makes a bit tough to judge what needs to be pushed as the base codebase. Is there a possibility to get a fully cleaned SDK or a README on what are the generated packages vs builtin packages

Example

Plain unmodified SDK

~/ti/tirtos/ti-processor-sdk-rtos-j721e-evm-08_01_00_13/pdk_jacinto_08_01_00_36/packages/ti/binary/ti/csl/obj/j721e/c7x-hostemu/debug$ ls -la
total 222944
drwxrwxr-x 3 anantha anantha    4096 Feb  3 23:02 .
drwxrwxr-x 4 anantha anantha    4096 Feb  3 23:02 ..
-rw-rw-r-- 1 anantha anantha  152920 Feb  3 23:02 adc.obj
-rw-rw-r-- 1 anantha anantha  110240 Feb  3 23:02 crc.obj
-rw-rw-r-- 1 anantha anantha  108744 Feb  3 23:02 csl_cbass_error.obj
-rw-rw-r-- 1 anantha anantha  104504 Feb  3 23:02 csl_cbass_qos.obj

 

After running make sdk_scrub

anantha@anantha:~/ti/tirtos/ti-processor-sdk-rtos-j721e-evm-08_01_00_13$ ls -la pdk_jacinto_08_01_00_36/packages/ti/
total 56
drwxrwxr-x 14 anantha anantha 4096 Mar 19 00:30 .
drwxrwxr-x  5 anantha anantha 4096 Feb  3 22:30 ..
drwxrwxr-x  7 anantha anantha 4096 Mar 19 00:30 board
drwxrwxr-x  4 anantha anantha 4096 Feb  3 22:30 boot
drwxrwxr-x  6 anantha anantha 4096 Feb  3 22:30 build
drwxrwxr-x  9 anantha anantha 4096 Mar 19 00:30 csl
drwxrwxr-x  4 anantha anantha 4096 Feb  3 22:30 diag
drwxrwxr-x 21 anantha anantha 4096 Feb  3 22:30 drv
drwxrwxr-x  3 anantha anantha 4096 Feb  3 22:30 fs
drwxrwxr-x  5 anantha anantha 4096 Mar 19 00:30 kernel
drwxrwxr-x  7 anantha anantha 4096 Feb  3 22:30 lpm
drwxrwxr-x  8 anantha anantha 4096 Mar 19 00:30 osal
drwxrwxr-x  4 anantha anantha 4096 Feb  3 22:30 transport
drwxrwxr-x  3 anantha anantha 4096 Feb  3 22:30 utils
anantha@anantha:~/ti/tirtos/ti-processor-sdk-rtos-j721e-evm-08_01_00_13$ 

 

I see the binary/ folder gets completely deleted with a make sdk_scrub command and regenerated on a make command again and no .gitignore files found inside pdk_jacinto_08_01_00_36/packages/ti/.

Please confirm the behavior and suggest some way around this to get a clean SDK to start with. I would like to if this was the only exception or similar regeneratable objects could be 

  • If you want a clean SDK, then make sdk_scrub is the way to go.  The SDK comes with prebuilt component libraries (not executables).  This has been convention for many SDKs.  I think it is meant to save time for customers who don't want to wait for the full SDK build.

  • Hi Jesse,

    Thanks for the update. Is there any Doc defining what are the prebuilt vs generated folders/files in each folder so that I can prepare proper gitignore files as I see .gitignore files in few folders where as not available in others. And at times its confusing as in some folders the prebuilts are kept in out folder ifself .

    Example

    ~/ti/tirtos/ti-processor-sdk-rtos-j721e-evm-08_01_00_13/tidl_j7_08_01_00_05/ti_dl/onnxrt_EP

    Even after the sdk_scrub , the files inside the out/ of onnxrt_EP are not deleted and it doesnt get build as part of "make sdk" as well.

    Thanks,

    Anantha

  • We do not currently have a document that indicates this.  In general, some packages, like TIDL and MMALIB are integrated into the SDK from a prebuilt standalone package that do not have source, so the "make sdk" can not build from source, so this is why it also doesn't remove it when "make sdk_scrub" is run.  Basically "make sdk_scrub" cleans all of the binaries that "make sdk" can build from source.  Is that consistent with what you are seeing? 

    The concerto make system generally adds .gitignore files to the projects that use concerto to build.  Not all the components use concerto.  vision_apps, tiovx, imaging, ethfw, remote_device, vxlib, all use concerto.  pdk, mcusw do not.  Perhaps that is the difference.