• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 2320 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.

C6678 - Client example app never connects

Dan Skehan7
Intellectual 560 points

I have been attempting to use the client example program for some time now, but with no luck yet.  I have followed every user guide and read through many TI forum posts, but I have not seen this issue discussed anywhere.

The program never seems to connect, either by means of static IP (which I would prefer) or DHCP. I am using C6678, CCS v5.1.1.00031, mcsdk 2_00_06_18, NDK 2_21_02_43. I have the board currently starting up with the "no boot" configuration and loading the general GEL file that came with the software install. Any suggestions? A sample output can be seen below:

[C66xx_0] QMSS successfully initialized

[C66xx_0] CPPI successfully initialized

[C66xx_0] PA successfully initialized

[C66xx_0]

[C66xx_0] TCP/IP Stack Example Client

[C66xx_0] Configuring DHCP client

[C66xx_0] PASS successfully initialized

[C66xx_0] Ethernet subsystem successfully initialized

[C66xx_0] Ethernet eventId : 48 and vectId (Interrupt) : 7

[C66xx_0] Registration of the EMAC Successful, waiting for link up ..

[C66xx_0] Service Status: DHCPC : Enabled : : 000

[C66xx_0] Service Status: Telnet : Enabled : : 000

[C66xx_0] Service Status: HTTP : Enabled : : 000

[C66xx_0] Service Status: DHCPC : Enabled : Running : 000

  • 0
    TI__Guru* 95265 points

    Dan,

    mcsdk 2_00_06_18 is a very old release, can you upgrade to the latest MCSDK 2.1.2.6? Under ti\mcsdk_2_01_02_06\examples\ndk there are pre-built client and hello world for C6678, can you try if that worked?

    Regards, Eric

  • 0 in reply to lding
    Intellectual 560 points

    I have just updated the software to CCS v5.2, MCSDK 2.1.2.6 (w/ patch01), NDK 2.21.2.43.
    The pre-built client still had the same output, no conection was made.

    Previously when I attempted to set it up as a static IP I could not ping the DSP either. Although I saw the lights on the ethernet connectors blinking which would indicate network activity.

    Any thoughts?

  • 0 in reply to Dan Skehan7
    Intellectual 475 points

    Hi Dan,

    I am not able to connect to the DSP using DHCP, but I have been using the static IP mode without problems for a long time. Since it is simpler, I would give it another try. Here are some ideas:
    - You should check that the IP/mask on your PC are well configured. If I recall correctly, when running in static IP mode, the DSP tells you (via console) what IP you have to use.
    - Also be sure that you have no firewall running on your PC.
    - If you are connecting through a switch/router, try connecting directly instead.
    - Finally, you should try to use a tool like Wireshark to monitor all your Ethernet activity. This may help you know whether the connection problem is on the DSP or the PC.

    Best regards,
    Alejandro

  • 0 in reply to Alejandro Gimeno
    TI__Guru* 95265 points

    Dan,

    With the pre-built client example, you can choose DHCP or static IP via the setting of user switch SW9, pin 2 on the 6678 EVM board. 

    In DHCP case, the EVM sends DHCP discover packet first, then DHCP server replies DHCP offer; then EVM sends DHCP request; finally server replies with DHCP ACK. You can monitor those via Wireshark.

    In static IP case, the EVM is configured as 192.168.2.100 (below from my CCS console):

     ======

    TCP/IP Stack Example Client

    PASS successfully initialized

    Ethernet subsystem successfully initialized

    Ethernet eventId : 48 and vectId (Interrupt) : 7

    Registration of the EMAC Successful, waiting for link up ..

    Network Added: If-1:192.168.2.100 ==========================> Did you have this printed out?

    Service Status: Telnet : Enabled : : 000

    Service Status: HTTP : Enabled : : 000

    =====

    Your PC (which is going to connect to the EVM) needs to have the same subnet as the EVM. For example, you can have it an IP as 192.168.2.101.

    I feel the problem is not the DSP code, but the setup.

    Regards, Eric

  • 0 in reply to lding
    Intellectual 560 points

    Everything was configured fine. The problem was indeed the SW9 switch needed to be set.

    Where does this switch come into play in the code? Could you tell me a bit more about it?

    Thanks!

  • 0 in reply to Dan Skehan7
    TI__Guru* 95265 points

    It is in client.c:

    if (!platform_get_switch_state(1))

    DHCP or static IP depends on this.

    Regards, Eric