That you for reply. I know about asserts. In debug version I use them to catch
critical errors, and non-critical too. And I always enable all asserts in
submodules. I also know about that article and had implemented most of their
suggestions. That did not help this time.
I fixed the problem
#define MEMP_MEM_MALLOC 0 //was 1
I prefer dynamic memory allocation. But this time it doesn't work fine....
=======
SOLVED.
=======
--
Ivan Kuvaldin
08.06.2016, 16:05, "Sergio R. Caprile" <[email protected]>:
> > hard fault. I think it because of NULL pointer exception
>
> Insted of thinking, put an assertion to verify that, and follow your
> processor debugging instructions to understand the actual reason of the
> hard fault.
> Even your OS has a guide on that:
> http://www.freertos.org/Debugging-Hard-Faults-On-Cortex-M-Microcontrollers.html
>
> PS: I would honor and follow advice regarding memory allocation
> functions, if I was you and I was chasing a fault on some error that
> depends on the number of data being processed.
>
> _______________________________________________
> lwip-users mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users
