[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] LwIP V1.3.2 + FreeRTOS V8.2.1 + STM32F107 strange failu
|
From: |
Sergio R. Caprile |
|
Subject: |
Re: [lwip-users] LwIP V1.3.2 + FreeRTOS V8.2.1 + STM32F107 strange failure |
|
Date: |
Mon, 18 Jan 2016 09:53:55 -0300 |
|
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
You are debugging an embedded application on an embedded system. The
usual techniques for debugging embedded applications on embedded systems
still apply.
If you can't use a UART to log messages, you can surely use Cortex-M's
SWD or put breakpoints or use any other debugging resources you surely
reserved for your application at design time.
lwIP provides statistics you can enable to be compiled in. You should
check them for memory loss and things like that.
Is there any reason why you are using lwIP 1.3.2 ? I know 1.4.1 is
stable and git head seems to be rock solid, but I can't bet on 1.3.2 and
don't know if anyone here (besides the maintainers) will be able to help
you in case you do find something that is lwIP's fault. I would check
your driver and port if I was in your shoes.