RTOS/TDA3XEVM: when modify ti_component's code in TDA3X SDK, how to accelerate

gzz

Part Number: TDA3XEVM

Tool/software: TI-RTOS

We are developing our project based TDA3X SDK , we will change some code and debug in your sdk directory ti_componets, not vision_sdk

for example, add one debug_trace() in one c source file, then we must do: build make -j8 depend, if ok, build make -j8., then make AppImage.

but we find the build time to finish all step is so so long, and the efficiency is so low for debug and evaluate.

so what good suggestion for us to accelerate the total build time after modify the ti_component's code.

over 8 years ago

0 Chetan Matad over 8 years ago

TI__Expert 3970 points

Hi ,

Unfortunately we cannot do much here as the changes in ti_components changes the libs ,
In sdk we statically link the libraries ( no dll) hence for the changes to be reflected in sdk you will have to do a depend and make and then create a appimage .

If your debug is at driver or component you can try using the standalone app from the component and then once done try it with SDK.

Regards
Chetan.M

0 gzz over 8 years ago in reply to Chetan Matad

Intellectual 765 points

Hi.
thanks for your reply.
I find some example or testcase under ti_components, so you means We can only build one separated domain application to test some changed driver module, then i can debug this app bin on CCS? is that right?
for our project, we reconstruct the hardware of evm and want to change or add one new camera sensor and lcd-panel drivers.
could you give me some idea to check this two new driver, do you know which application i can use in ti_components?
Thank you.

0 Chetan Matad over 8 years ago in reply to gzz

TI__Expert 3970 points

which driver in ti-components are you modifying .

So if its PDK drivers , you will have sample app for most of drivers .
You can modify the driver and test the functionality of the driver using the sample app.
While building the standalone you will have to build it from the ccomponents make file. you will not be able to build it directly from top level make . Also make sure you set all the paths to the component make .
Later integrate the same changes to SDK and test your usecase.

Regards
Chetan.M