sample_embedding_folder2/0699186.txt

Ticket Name: RTOS/TDA2: Problems with integrating existing framecopy algorithm into existing NetworkRxDecDisplay UseCase

Query Text:
Part Number: TDA2 Tool/software: TI-RTOS Hello, We are working on a TDA2xx EVM with Bios (tda2xx_evm_bios_all) We tried to integrate the framecopy algorithm into the NetworkRxDecDisplay UseCase. (See picture) The defaul unedited NetworkRxDecDisplay UseCase is working fine, but the new edited UseCase doesn't work. It starts, but when we start to stream the data from the pc to the Board, this error occurs: PC side: Does anyone know, how we can fix that? Kind Regards

Responses:
Hi , On which core are you running networking .? A15 or ipu1_1 From figure it shows a15 but from log it says ipu1_1 Regards Chetan.M

Hello, we set NDK_proc_to_use to ipu1_1 in build-config Regards

but the usecase you have generated network rx on A15 . ? Can you try changing it on ipu ( core where you have networking enabled) . ? Regards Chetan.M

But the standard NetworkRxDecDisplay UseCase (without the framecopy) works fine. We can send video data with the network tx tool and it's displaying on the display without an error Regards

Sorry this use case is a bit confusing... In the use case Picture, it seems to indicate the NetworkRx is running on A15 but it will actually be overwritten in chains_networkRxDecDisplay_SetAppPrms() depending on where the NDK_proc_to_use is set. So, in reality, since NDK_proc_to_use=ipu1_1, the NetworkRx link will be running on IPU1_1. We do that because we want to make the same use case code working wherever NDK resides. When you create your own use case, you have to create NetworkRx Link on the same core as the NDK_proc_to_use is set.

Hello, ok, thanks for the explanation . We will try it with the NetworkRx link created on ipu1_1 and let you know if it works then. Thanks and regards

Did it solve the issue , Please close the thread if the issue is solved Regards Chetan.M