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.

NDK 2.00 on TMS320C6412 + DSPBIOS 4.9 - latency issue

team,

we have a system level issue that could be related to NDK2. Can you please suggest debug points to help us narrow down?

The 6412/NDK2/DSPBIOS acts as webserver host webpages accessed by client over a busy network :

the web pages hosted on 6412 displays correctly on host in

        - 80 % with recent version of web browser  (FIREFOX >10 ou IE >8)

        - <50 % other browser (Chrome Opéra)

adding a simulator capable of injecting jitter, Ip errors, and delay, we see that pasted 2sec delay the pages are never displayed.

we have wireshark traces available on request.

  • Let's start with some background questions and clarifications. 

    1. What versions of DSP/BIOS and NDK are you using?

    2. Are there two separate problems here? 1) general inter-op of the NDK HTTP server with various HTTP clients? 2) Performance in the face of network degradation?

    3. What happens when the network simulator is inserted between the server and client? Have you tried using a Windows or Linux HTTP server with the same network simulator? How does that behave? I got the wireshark capture but it's not clear to me (yet) what the failure is - I'm assuming the NOK capture file is the failure scenario?

    Mark

  • 1. What versions of DSP/BIOS and NDK are you using?

    >> stated in the title of the post :) NDK 2 DSPBIOS 4.9

    2. Are there two separate problems here? 1) general inter-op of the NDK HTTP server with various HTTP clients? 2) Performance in the face of network degradation?

    >> Yes

    3a. What happens when the network simulator is inserted between the server and client? Have you tried using a Windows or Linux HTTP server with the same network simulator? How does that behave?

    >> I can ask

    3b.I got the wireshark capture but it's not clear to me (yet) what the failure is - I'm assuming the NOK capture file is the failure scenario?

    >> shall we have a call with the customer? I'll ask in the meantime

  • Olivier,

    1. Ok, that's a "Doh" on me for the versions :)

    2. HTTP server issue - could you get some of the specific browsers that fail? Are you sure it's not the HTML content that's failing? Any error messages to report?

    3. I would like to see the results of using the network simulator with a Linux or Windows HTTP server and if that's the expected result.

    Mark