[En-Nut-Discussion] Ethernet Reboot Issue

[Tim DeBaillie]

On Tue, 17 Oct 2006, Harald Kipp wrote:

> Can you please try again with 4.1.99 or 4.2, which will be available
> shortly. There had been several fixes.
>
> Your assumption about stack problems might be correct. By default
> the following sizes are set for the thread stacks:
>
> dev.h:#define NUT_THREAD_NICRXSTACK 768
> dhcp.h:#define NUT_THREAD_DHCPSTACK 768
> os.h:#define NUT_THREAD_IDLESTACK 512
> os.h:#define NUT_THREAD_MAINSTACK 768
> sntp.h:#define NUT_THREAD_SNTPSTACK 768
> tcp.h:#define NUT_THREAD_TCPSMSTACK 768
>
> These may be increased, specifically NUT_THREAD_MAINSTACK,
> NUT_THREAD_NICRXSTACK and NUT_THREAD_TCPSMSTACK.

Thanks,

I installed the 4.1.99, which appeared to fix the problem on the 
Evaluation Kit.  Then I installed it on our model and since you have hard 
coded the PHY_IDs in the NIC Driver (EmacReset), it would not link the PHY 
with the SAM.  So I would suggest putting the PHY_ID1 and PHY_ID2 defines 
in the configurator so others can configure the OS for their PHY.

After changing the PHY_ID checks to our PHY ID the software worked without 
any trouble.

Also, I see where you have added a timeout for the PHY Autonegotiation, I 
would suggest putting a small NutSleep or a NutThreadYield, so the OS can 
continue to operate if you are waiting on a link.  I know the timeout 
should resolve this issue, but it does a few seconds for the timeouts to 
occur.

Tim