• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 98 subscribers
  • Views 1584 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux: Do we have support of networking tools such as "Network_Control_Tool" , "Network TX/RX" and "Network_CONS" Tool on "LINUX+BIOS" Build?.

Anshul Jain96
Intellectual 320 points

Tool/software: Linux

Hi There,

I am using VSDK_03_01_00_00 with TDA2XX SOC and want to execute some networking related use cases . So I have referred  "VisionSDK_UserGuide_NetworkTools.pdf" PDF for primary setup such as setting the static IP but in this document they have mentioned a "Note" under the Introduction section as "these tools can be used only when BIOS based NDK/NSP runs on target".

So please confirm do we have support of these tools with "Linux+ Bios" too or it is only for "BIOS".

@NOTE:- If these tools are only for "BIOS" then how the "HOST" and "EVM" board will establish the communication, if the build is "Linux+Bios"?.

Regards,

Anshul Jain.

  • 0
    TI__Mastermind 42515 points
    Hi Anshul,

    You can use the tools with Linux+BIOS too, please check the document PROCESSOR_SDK_VISION_03_01_00_00/vision_sdk/apps/tools/network_tools/docs/VisionSDK_UserGuide_NetworkTools.docx

    The note there is:
    NOTE: These tools can be used for both BIOS and Linux usecases. For BIOS
    usecases, make sure that the NDK/NSP is enabled and runs on the target. For Linux
    usecases, make sure that Ethernet is enabled and correct ip address is provided in u-boot
    boot arguments.

    It seems VisionSDK_UserGuide_NetworkTools.pdf in not updated.

    Regards,
    Yordan
  • 0 in reply to Yordan Kamenov
    Intellectual 320 points
    Hi Yordan,

    Thank you for your response.

    Yes, the document is not updated yet. Can you please suggest, is there any document that tell us how to enable Ethernet and which IP needs to be pass through the u-boot as a argument and how to pass.

    Regards,
    Anshul Jain.
  • 0 in reply to Anshul Jain96
    TI__Mastermind 42515 points
    Hi Anshul,

    you can edit you uenv.txt and change "ip=" boot parameter in your kernel command line (that is the "bootargs" variable).
    You can have ip=dhcp for dynamic ip (if your PC is running DHCP server) or something like ip=192.168.0.2 for a static IP.
    You can check here for more info:
    www.kernel.org/.../nfsroot.txt

    Also once the Linux has booted on the device you should be able to check or change the network configuration with standard ifconfig/ifup/ifdown commands.

    Regards,
    Yordan
  • 0
    TI__Mastermind 27743 points
    Hello Anshul,

    In addition to what Yordon has mentioned below are some details for using network tools with Linux+Bios
    1. The tools are supported only when networking stack (NDK) is running on BIOS
    2. If you are using networking stack on linux then these tools wont work as BIOS would see networking (null source and null links with network) disabled.
  • 0 in reply to Prasad Jondhale
    Intellectual 320 points

    Hi Prasad,

    That means for supporting the networking tools on "LINUX+BIOS" we should have the below configuration in cfg.mk file which is present under the "\vision_sdk\$(MAKEAPPNAME)\configs\$(MAKECONFIG)\" directory.

    A15_TARGET_OS := Linux and NDK_PROC_TO_USE=BIOS

     

    Note:- But as written in the section no. "3.2" of "VisionSDK_Linux_UserGuide.pdf" for building the  Linux VSDK for AVB Capture, Decode and Display UCs the following configuration should be in cfg.mk as mentioned below.

    A15_TARGET_OS := Linux and NDK_PROC_TO_USE=ipu2

    Please confirm if my understating is correct or not.

    Regards,

    Anshul Jain.

  • 0 in reply to Anshul Jain96
    TI__Mastermind 27743 points
    Anshul,

    You cant set NDK_PROC_TO_USE to BIOS. It is not valid param. The one you are setting (ipu2) is correct.
    With this you should be able to use network tools.
    Network console needs to be enabled explicitly using ENABLE_NETWORK_LOG=yes in .cfg file.
    Network Rx/Tx can be used with Null/null source links
    Network control can be used any time.