[En-Nut-Discussion] Design based around the ethernut1.3g

[Richard Dawodu]

I am currently using 74HC373 because I have large stock. If speed is the
issue can it be slowed down by adding wait state, which I have tries with
the following within main thread.
	sbi(XMCRA, SRW00);
	sbi(XMCRA,SRL2);

Does the fact that my hardware sending out bogus packet similar to ethernut
hardware mean that the interation between the processor and the RTL is ok ?

Yes I did say my hardware hangs at function call
Nutregisterdevice(&devEth0,,) with "basemon.c" but it goes beyond the device
registration point and hangs somewhere else with the "tcp.c" because my
hardware sends out valid packet for a moment. It is with this "tcp.c" that
my hardware responds to a ping.

-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de]On Behalf Of Harald Kipp
Sent: 11 June 2005 20:20
To: Ethernut User Chat (English)
Subject: RE: [En-Nut-Discussion] Design based around the ethernut1.3g


Rich,

Yes, Basemon option B sends bogus packets.

Basemon's RAM test is not very versatile. It may not detect
timing problems. It's main purpose is to find shorted or open
wires and the last RAM address as well as the number of banks.

We have also used 70 ns RAMs without problems. However, we do
extensive test before selecting new chips. RAM timing on
Ethernut is indeed highly critical.

You may also check the HC573, optionally replace it with an
AHC type. However, these chips are typically very noisy,
regarding EMC.

Harald

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion