[En-Nut-Discussion] Ethernut not running stable
Ulrich Prinz
uprinz2 at netscape.net
Wed Nov 17 21:47:03 CET 2010
Hi!
I didn't check Version 4.8.x and I cannot see from your mail if httpd
itself works but the nut crashes with ping only.
In 4.9.x (trunk) there is a bug that shows up if you start the httpd
example and ping it without having at least done one http request. It
crashes with the first ping.
If you had already done at least one http request, it withstands some
30..60 seconds of adaptive ping (a bit calmer than floodping) and
crashes then.
But if you do not ping the nut, http works.
I am actually searching for that bug while I rewrite parts of the
at91_emac.c. I tested against the EIR which uses a different (external)
MAC and it does not show the problem after several minutes of adaptive
ping. It didn't even give any hichup in the sound even the interface is
flooded:
138204 packets transmitted, 138203 received, 0% packet loss, time 171703ms
rtt min/avg/max/mdev = 0.433/0.741/6.437/0.973 ms, ipg/ewma 1.242/0.539 ms
There is already a thread in the list here, where I talked about that
problem: "Detecting unplugged network cable" is the thread you might
like to join and see how it grows.
Best regards
Ulrich
Am 17.11.2010 21:07, schrieb Erich:
> Hi,
>
> C:\Programme\yagarto\bin>arm-elf-gcc -v
> Using built-in specs.
> Target: arm-elf
> Configured with: ../gcc-4.4.2/configure --target=arm-elf
> --prefix=/home/yagarto/
> install --disable-nls --disable-shared --disable-threads --with-gcc
> --with-gnu-l
> d --with-gnu-as --with-dwarf2 --enable-languages=c,c++
> --enable-interwork --enab
> le-multilib --with-newlib
> --with-headers=../newlib-1.18.0/newlib/libc/include --
> disable-libssp --disable-libstdcxx-pch --disable-libmudflap
> --disable-libgomp -v
>
> Thread model: single
> gcc version 4.4.2 (GCC)
>
> C:\Programme\yagarto\bin>
>
>
> Nut Os 4.8.7 and 4.8.8 show same behavior. When i statt a flood ping on
> the devices
> it crashes immediatly.
>
> #define NUT_THREAD_NICRXSTACK 384
>
>
> didnt help so far
>
> Harald Kipp schrieb:
>> Hi Erich,
>>
>> On 17.11.2010 18:35, Erich wrote:
>>
>>
>>> i have a ethernut 3 board 3.0 rev e and when i try the httpd sample or
>>> any other
>>> programm that uses ethernet the board crahes and does not reply to ping
>>> or anything
>>> else. we tried nut os 4.8.8 and 4.8.7
>>> suggestions?
>>>
>>
>> If you installed the Nut/OS 4.8.8 distribution on Windows, you'll find
>> binaries in subdirectory
>>
>> bin\boards\ethernut30e\arm-gcc\
>>
>> I just tested the httpserv.bin and it works.
>>
>> Note, that the default is to run in RAM, using TFTP as explained at
>>
>> http://www.ethernut.de/nutwiki/Ethernut_3.0_E
>>
>> Unfortunately the Linux distri comes without binaries.
>>
>> In Nut/OS 4.9 beta I recently had the problem, that the receiver thread
>> stack in arch/arm/dev/at91_emac.c overflowed. It worked before and I
>> assume that this appeared after updating the compiler.
>>
>> May be it helps to increase
>>
>> #define NUT_THREAD_NICRXSTACK 384
>>
>> Please let us know if it helps and what compiler version you are using.
>>
>> arm-elf-gcc --version
>>
>> Regards,
>>
>> Harald
>> _______________________________________________
>> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>>
>>
>
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
More information about the En-Nut-Discussion
mailing list