• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 725 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.

EK-TM4C1294XL: uIP not working with UARTStdioIntHandler()

Goran Pufler
Prodigy 100 points
Part Number: EK-TM4C1294XL

Hi,

I create simple uIP project that call as web client REST API request to the server (myserver.com:8080/.../somedata). I use example enet_uip project and replace httpd with webclient lib, and it works fine. Now, I want to add some UART functions, so I use standard command example (with uartstdio and ustdlib).

After enabling interrupt in startup_ccs uIP stop working, it even won't collect IP address from DHCP.

Is this not working together or is there any way to avoid this?

THX

Goran

  • 0
    TI__Guru*** 135355 points
    Hello Goran,

    When configured correctly those APIs should work together just fine. Have you verified the that the UART APIs you have integrated are operating as expected, including the interrupt(s), in a separate project first?

    If the uIP project was working fine until you added UART, it is likely something with the UART configuration, interrupts, etc. is not setup correctly and thus causing the issue.

    Posting source code for the UART configurations, interrupt, interrupt enables, ISR etc. would be helpful too. You can do this by clicking "Use Rich Formatting" and using the Syntax Highlighter in the toolbar above the E2E post box - look for a symbol that looks like "< / >".
  • 0 in reply to Ralph Jacobi
    Prodigy 100 points
    Hi Ralph,

    thank you for swift answer.
    late tonight I figure out what's going on - it was on me :)

    I forget to increase stack size and I always end up on FaultISR. I'm a new one to TIVA C and I need time to get used on CCS and TiwaWare. I have the same problem with lwIP, and also stack size was a problem.
    Maybe, adding some reference in uIP and lwIP documentation to state how much stack size they will need, will not be a bad idea.

    Any how, thank you for replay

    regards
    Goran