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

TI RTOS Help needed

joshua ivaldi
Intellectual 300 points

Hi,

I am having a problem running the dual-core example for TI RTOS.  I will provide the steps I've followed, and what issues I am having.  This may be difficult to solve because I believe it is a driver or hardware issue, not code.  I am using a TMDXDOCKH52C1.

1.  I followed the detailed board modifications in the 2 RTOS related PDFs. I am using CCS v5.4.1 or something..

     - J1-15 B-C, J20-21 A-B-C (The PDF says 20-21 B-C, the .txt document within the code says 20-21 A-B), J22-25 B-C, J30-31 B-C, R230 (Shorted), J6 2-3. Have all been shorted.  SW1 is in boot-from-flash (0) position.

2. I installed TI RTOS Software and USB host drivers.  The USB host driver, I am not sure if i chose the correct one, but when connected via micro USB cable, my network devices displays a virtual COM port corresponding to it.  My connections are by Mini USB and Micro USB- not the connection at JP2 where the JTAG is.

3. I changed the MAC address within the code to my board's MAC address.

4.  I do NOT have an SD card in the slot, nor do I have a temperature circuit set up. 

5.  I compiled the code, and there are no mistakes.  I've connected my board by a cat 5e cable.  I uploaded the code on to its respective cores and ran it.

6. LD2 lights up, as it should when it enters the main section of the code.  The ethernet LED's flash.  When I go to my network devices, however, it shows a network device that receives packets, but sends nothing back.  Obviously if i try to point a browser to its IP address, it does not connect to anything.

There are a few mistakes I could have made here.  Either the driver i chose for the micro USB virtual com port could be wrong, I made an incorrect board modification, or my computers network adapter settings aren't what they should be.  Sorry if this problem is difficult to solve, I've been having quite some trouble figuring out what the issue is.

Thanks,
Josh

  • 0
    Intellectual 300 points

    Hi everyone,

    Is there any chance someone could take a look at this?  All I need is someone to check my steps or give advice as to what they think the problem might be.  I am certain that it's nothing to do with code.

    Thank you,
    Josh

  • 0 in reply to joshua ivaldi
    TI__Guru* 96960 points
    Hi Josh, I'll get this thread moved to the TI-RTOS forum. Which version of TI-RTOS are you using? Todd
  • 0 in reply to ToddMullanix
    Intellectual 300 points

    Hey Todd,

    Thanks for your reply,  I believe I am using v. 1 10 00 23.  Are there any known compatibility issues with ethernet connectivity? 

  • 0 in reply to joshua ivaldi
    TI__Guru* 96960 points

    Hi Josh,

    I have not heard of any issues. Which example are you using? The examples by default use DHCP. Do you have a DHCP server on your network? Can you install Wireshark on your host? You should be able to see the DHCP discovery request from the target with Wireshark.

    Todd

  • 0 in reply to ToddMullanix
    Intellectual 300 points

    Ahh, this is the stuff I don't know enough about, which is why it's been hard for me to troubleshoot this. I'll download and install wireshark and post my results ASAP. How will I be able to see DHCP server settings on my network? Is this something that I can adjust with my LAN network adapter (since it is connected by ethernet cable)? I'm using the Demo M3/C28 RTOS. The temperature conversion + HTTP NDK server + SDSPI example.

    Thank you so much, Todd!

    Josh

  • 0 in reply to ToddMullanix
    Intellectual 300 points

    Todd,

    I've installed Wireshark and sniffed packets.  0.0.0.0 sends DHCP discovery packets to 255.255.255.255 - I assume this is going from computer to MCU, but I am not getting any packets back from the MCU.  I took a few screenshots.. I'll be honest, I'm not well versed in protocols / ethernet connectivity in any way shape or form.  How can I tell why the MCU isn't sending packets?

    From CCS,

    "[Cortex_M3_0] Demo with HTTP, I2C, and SD
    System provider is set to SysMin, halt the target and use ROV to view output.
    Service Status: DHCPC    : Enabled  :          : 000
    Service Status: HTTP     : Enabled  :          : 000
    Service Status: DHCPC    : Enabled  : Running  : 000
    Start the main loop
    Service Status: DHCPC    : Enabled  : Fault    : 002
    "


    Thank you for your help,

    Josh

  • 0 in reply to joshua ivaldi
    TI__Guru* 96960 points

    Josh,

    What is the Ethernet cable from the board connected to?

    If it is to a network, either you don't have a DHCP server on your network or possibly do you have two boards with the same MAC address?

    If it is connected to your PC, you'll probably need to give the board a static IP address (it does not look like you have a DHCP server running on your PC). You can set an IP address via the following config page. Of course, you will need to adjust accordingly based on your PC's settings.

    Todd

  • 0 in reply to ToddMullanix
    Intellectual 300 points

    Hi Todd,

    This is going to my PC.  I changed my IP - General Settings to match yours, but it's still not working. How do I provide a DHCP server? What settings should I be looking at on my computer?

    I am looking online and I've seen a few DHCP programs that require configuration of IPv4 settings before installation / lease options can be set.  I also saw the DHCP module in the demo.cfg file in the M3 project - I turned the DCHPClient module on and rebuilt my code after I set my computer's IPv4 settings to,

    IP Address: 192.168.0.2

    Subnet Mask: 255.255.255.0

    Default Gateway: 0.0.0.0

    The TMDXDOCKH52C1 is set to,

    IP Address: 192.168.1.2

    IP Mask: 255.255.254.0

    Gateway IP: 0.0.0.0

    In the IP-General Settings tab.  The Console window now says,

    [Cortex_M3_0] Demo with HTTP, I2C, and SD
    System provider is set to SysMin, halt the target and use ROV to view output.
    Network Added: If-1:192.168.1.2
    Service Status: HTTP     : Enabled  :          : 000
    Demo with HTTP, I2C, and SD
    System provider is set to SysMin, halt the target and use ROV to view output.
    Network Added: If-1:192.168.1.2
    Service Status: HTTP     : Enabled  :          : 000
    Demo with HTTP, I2C, and SD
    System provider is set to SysMin, halt the target and use ROV to view output.
    Network Added: If-1:192.168.1.2
    Service Status: HTTP     : Enabled  :          : 000

    No mention of DHCP anymore!???!

    After running for awhile, the Console said:

    Cortex_M3_0: JTAG Communication Error: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 5.1.232.0)
    C28xx_0: Error: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.1.232.0)
    Cortex_M3_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
    C28xx_0: Unable to determine target status after 20 attempts
    C28xx_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

    Is this a timeout, or critical error?



    Thank you for all of your help. I really appreciate this,

    Josh

  • 0 in reply to joshua ivaldi
    TI__Guru* 96960 points

    Your setting are not going to work. Do the following

    PC

    IP Address: 192.168.1.1

    Subnet Mask: 255.255.255.0

    Default Gateway: 0.0.0.0

    The TMDXDOCKH52C1 is set to,

    IP Address: 192.168.1.2

    IP Mask: 255.255.255.0

    Gateway IP: 0.0.0.0

    Do not use DHCP anywhere. You are now using static IP addresses. The two can talk to each other now.

    Todd

  • 0 in reply to ToddMullanix
    Intellectual 300 points

    Awesome!  That's all it needed.  Thank you so much, Todd!