Spaces:
Sleeping
Sleeping
| Ticket Name: Linux/TDA2: Can network_tx.out in network tool be set to TCP/IP mode, not using TFDTP, how to set | |
| Query Text: | |
| Part Number: TDA2 Tool/software: Linux Create a Vision SDK use-case on target side. Specify the source of data as “Network_rx” link. NDK runs on A15 CPU. NDK_PROC_TO_USE=a15_0. Set NetworkRxLink_CreateParams.dataRxMode as NETWORK_RX_LINK_DATA_RX_MODE_TCPIP I use the network tool to send image data on the pc side, Network Tx: Connecting to server 172.18.0.205:29171 ... # ERROR: NETWORK: Server connect Failed (172.18.0.205:29171)!!! # INFO: Closing connection to Server | |
| Responses: | |
| Hi Hua Liu Liu, Do you want to send the captured data to the PC via the network (network_rx) or File from PC to the evm for HDMI Display (network_tx) ? These are the commands you should use respectively Network Tx ---------------- network_tx.out --target_ip <TARGET_IP> --host_ip <HOST_IP> --files <YOUR_FILE_IN_PC> Network_Rx ---------------- network_tx.exe --target_ip <TARGET_IP> --host_ip <HOST_IP> --files <FILE_PATH_IN_PC_WHERE_THE_CAPTURE_IS_TO_BE_SAVED> If you don't use --usetfdtp in the command, it'll use tcp/ip for default. Regards, Anand | |
| Hi Anand, I want to sent File from PC to the evm for HDMI Display (network_tx) , Network TX ----------------------- root@ubuntu:/home/ti/vision_sdk/apps/tools/network_tools/bin# ./network_tx.out --target_ip 172.18.0.200 --host_ip 172.18.0.156 --files airshow_1280x720_5frs.yuv # Network Tx: Connecting to server 172.18.0.200:29171 ... # ERROR: NETWORK: Server connect Failed (172.18.0.200:29171)!!! # INFO: Closing connection to Server # Network Tx: Connecting to server 172.18.0.200:29171 ... | |
| Hi Hua Liu Liu, Please try the ping and make sure it works before trying out a network usecase. I'm assuming you're using dynamic IP here. Regards, Anand | |
| Hi Anand, Thanks, In the windows environment,I sent File from PC to the evm for HDMI Display (network_tx) ,is ok. I ported the networ_rx code to Linux and it is a bit of a problem. Let me check the code myself. | |
| Sure, Hua Liu Liu. Let me know of any updates! Regards, Anand | |
| Hi Anand, NDK_PROC_TO_USE=a15_0, #define VIDEO_SENSOR_NUM_LVDS_CAMERAS (4) Camera 1, Camera 2, Camera 3 and Camera 4 are used for 4 channel LVDS use-case I joined NetworkRx (A15) in lvds_vip_sv_standalone, there is no image output in the loop, and there is a conflict when the camera is used with the network. | |
| Hi, What exact changes did you make when you ported the code to linux? I suppose the usecase was working for you in Windows. Have you made any additional changes? Regards, Anand | |
| No code changed during the migration process。I am running under windows, no problem, I am transplanted to linux to run the following problems ASSERT (chains_lvdsVipSurroundViewStandalone_priv.c|chains_lvdsVipSurroundViewStandalone_Create|332) line332：status = System_linkCreate(pObj->NetworkRxLinkID, &pObj->NetworkRxPrm, sizeof(pObj->NetworkRxPrm)); UTILS_assert(status == SYSTEM_LINK_STATUS_SOK); | |
| Hi Hua Liu Liu, I am not sure how these changes would affect the 'TCP/IP or TFDTP' parameter. So the System_linkCreate is not successful in your linux code? I mean the assert is failing? Regards, Anand | |
| Hi Hua Liu Liu, It's been a while since I've heard from you. Were you able to resolve the issue? :) Regards, Anand | |