[En-Nut-Discussion] no source in debugger solved, next step
Klaus Kloos
klaus.kloos at gmx.de
Sun Oct 2 22:27:06 CEST 2011
hello
The first problem is solved. After I found the switch for arm-gccdbg in the configurator settings everything was much easier... Sorry for the wasted bandwidth.
the gcc option -Werror has to be replaced with -Wunused-but-set-variable, and 'c:\ethernut-4.8.9\nut\tools\win32' has to be added to the PATH.
Now in debug mode the httpd-sample works much better than using the arm-gcc variant. DCHP is now finished successful, an IP address is there and ping is working.
the arm-gcc variant hangs while asking the dhcp-server. (im using the AT91SAM7x-EK board).
Connecting with a web-browser does not work. No page is shown and the following output can be seen on the debug port:
[4] Connected, 1444 bytes free
[4] Low mem
[4] Low mem
..... and so on.
Do I have to adjust the memory somewhere?
Greeting Klaus
More information about the En-Nut-Discussion
mailing list