TDA4VM: Fail to apply tuning results to target environment

Hi,

Could you please tell me how you are doing last step ie building vision apps?

Since there is a change in the imaging component, could you please rebuild imaging and then vision apps, as shown below?

1, make imaging_scrub

2, make imaging

3, make sdk

Regards,

Brijesh

Hello Brijesh,

Thanks for your reply. I only run "make sdk type=a PROFILE=debug -j12" to rebuild vision_apps before.

But after I use the command you provided, the changes in the .h file still fail to take effect successfully. And I don't see any errors during compilation.

Is there anything else I'm missing?

One more thing, the files I copied from sdk to TDA4 board are:

folder: /targetfs/lib/firmware/pdk-ipc; folder: /targetfs/lib/firmware/vision_apps_evm; files: /targetfs/lib/firmware/j7-c66_0-fw, j7-c66_1-fw, j7-c71_0-fw, j7-main-r5f0_0-fw, j7-main-r5f0_1-fw, j7-mcu-r5f0_0-fw, this folders and files in sdk are copied to /lib/firmware/ in TDA4 board.

folder: /targetfs/opt/vistion_apps is copied to /opt/vision_apps/ in TDA4 board.

Is there anything else that needs to be copied into the TDA4 board?

Hi wang zhill,

Instead of manually copying the firmware images, can you please run "make linux_fs_install_sd" command to copy all required firmware and binaries to the SD card?

Regards,

Brijesh 

Hi Brijesh,

The TDA4 board I use is customer hardware instead of TDA4 EVM, I can not connet the TDA4 board to the environment of SDK compilation. That is to say, I can only manually copy the firmware files to the board.

Is there any problem with manual copying?

Hi Wang Zhili,

no, no issues in manual copy, as long as the copy and rename of the files is done correctly..  In fact, here, you just need to update firmware for mcu2_0, because DCC code is running on mcu2_0 only.. 

So can you rebuild imaging "make imaging_scrub && make imaging", rebuild sdk "make sdk", then copy just mcu2-0 firmware ie j7-main-r5f0_0-fw in the /lib/firmware folder and try it again?

Also please confirm that above step #4 is performed correctly, ie generated_dcc.sh file is run to convert binary dcc file to header file, generated header file is copied to sensor_drv/include folder and then this header file is included in the vision_apps\utils\iss\src\app_iss_common.c, so that it can be used in the vision apps.. 

Regards,

Brijesh

Hi Brijesh,

Brijesh Jadav said:

So can you rebuild imaging "make imaging_scrub && make imaging", rebuild sdk "make sdk", then copy just mcu2-0 firmware ie j7-main-r5f0_0-fw in the /lib/firmware folder and try it again?

I have tried this way, the change in header files still fail to take effect successfully.

I made an extreme test: In dcc_viss_ar0820_wdr.h, I deleted almost all the data to see what would happen, I found that it still didn't work, there is nothing changed in image.

It seems that the header files do not compile successfully in SDK, I have checked that the header files generated by generate_dcc.sh are different from the old one, and the header files are included in app_iss_common.c, there is no error during the compiling, which makes me very confused.

Do I need to modify or add content to the Makefile to apply the changes in header files?

Hi Brijesh,

Do you have any idea of this problem?

Regards,

Zhili