Well, to clarify, I send whole Ethernet frames via SPI. ARP should be
handled by the external chip, though, as it does not let any ARP packages
through and responds to ARP queries without the TCP/IP stack. I stumbled
upon a problem with ARP, however - everytime I try to turn it off in
lwipopts.h,
Hi,
On Thu, Aug 23, 2012 at 04:21:30PM +0200, Tomás Svec wrote:
Well, to clarify, I send whole Ethernet frames via SPI. ARP should be
handled by the external chip, though, as it does not let any ARP packages
through and responds to ARP queries without the TCP/IP stack.
Maybe you should tell
The problem is, the external chip is a prototype, so this would not help
the cause. I am currently in contact with the manufacturer to clarify the
ARP packages. But I am sure it does not have an embedded stack, just ARPs.
2012/8/23 Sylvain Rochet grada...@gradator.net
Hi,
On Thu, Aug 23, 2012
Thank you for the quick answer. By ISR you mean an interrupt routine? In
that case it is correct, since the event polling kind of replaces
interrupts. I also implemented low_level_output, but it seems to be called
only from the etharp.c file. Is it necessary to implement a function like
Tomáš Švec tomas.sve...@gmail.com wrote:
Thank you for the quick answer. By ISR you mean an interrupt routine? In that
case it is correct, since the event polling kind of replaces interrupts.
Yes.
I also implemented low_level_output, but it seems to be called only from the
etharp.c file.
Hello,
I am implementing lwip 1.4.0 on quite a specific configuration. The stack
itself is running on an STM32 chip, which is connected through SPI to
another one, which handles Ethernet traffic (I just send the right data on
SPI and the other chip takes care of the rest). There is an issue,
Tomáš Švec wrote:
The problem is, in that case, I need to call ethernetif_input
manually when I receive the package, right? In case it is right,
ethernetif_input is a static function, which does not allow me to use it
outside its translation unit. Is it safe to remove the static attribute,
