I just pushed the current version of ENCX24J600 code to the feature-encX24J600-wip branch: https://github.com/Ell-i/Runtime/commit/b865fb534276b400ec272d3f9cc9a196061b9e34 That contains three test cases: https://github.com/Ell-i/Runtime/tree/feature-encX24J600-wip/stm32/tests/test_ENCX24J600_begin https://github.com/Ell-i/Runtime/tree/feature-encX24J600-wip/stm32/tests/test_ENCX24J600_receive https://github.com/Ell-i/Runtime/tree/feature-encX24J600-wip/stm32/tests/test_ENCX24J600_send The begin and receive test cases should work as such. The send test case works almost, sending garbled packets. But you can still see them with tcpdump. When I have more time (maybe only mid November), I will continue from this. Of course, if someone wants to continue earlier, feel free to work and start working. I'd be more than happy to merge. For the next stage of work, the most important thing is to move the ENCX24J600 and ENC28J60 libraries into separate libraries, out from the CoAP code base. That will also help us when we'll start unifying them with the RIoT driver interfaces. --Pekka On 2014–10–21, at 15:11 , Pekka Nikander <pekka.nikander@xxxxxx> wrote: > No, no proper code yet. I think we agreed that I will work on that on the > 30th. > > I will be committing some existing code any day now once I get an urgent > larger task out of my hands. > > --Pekka > > On 2014–10–21, at 13:03 , otso@xxxxxxxxxxxx wrote: > >> Hi all, >> >> Is there a code I could flash to Nucleo to verify the communication over >> ethernet? >> >> I've tested that PoE negation succeeds, DC/DC operates properly and "link" >> and "act" LEDs operate, but I'd be interested in seeing how many packets >> get corrupted, does loading of DC/DC affect transmission reliability and >> so on. >> >> -Otso >> >
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
