Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Driver: Improve W5X00 ethernet shield/device detect #471

Open
mikaelpatel opened this issue Jan 7, 2016 · 3 comments
Open

Driver: Improve W5X00 ethernet shield/device detect #471

mikaelpatel opened this issue Jan 7, 2016 · 3 comments

Comments

@mikaelpatel
Copy link
Owner

No description provided.

@dansut
Copy link
Contributor

dansut commented Jan 8, 2016

I'm likely going to spend some time in the next couple of weeks following your lead with the work you did on the W5200 integration replicating for the W5500, as it is what I'm using on my project, so if you add any ideas you have or direction you'd like to take to this issue then I'll do anything I can to help.

Cheers
/dan

@mikaelpatel
Copy link
Owner Author

@dansut

After reading a number of forum topics on the Ethernet Shield and library it seems like there are some basic validations missing.

  1. Is a shield with the Ethernet controller available?
  2. Is the Ethernet controller cable connected (link working)?

Both these should (if possible) be validated with the device driver is started. The first seems easiest to do by checking an SPI read as the return values are very specific (at least what I have seen for the W5100). The second issue is a bit trick as this is not available in a status register (what I know) and without a mod of the board it is difficult to "read the link status". Worst case this has to be ignored and higher level protocol has to detect that the network (link) is not available. Do you have any ideas on this?

Cheers! Mikael

@dansut
Copy link
Contributor

dansut commented Jan 15, 2016

Good info, thanks - it strikes me using this type of technique it would perhaps be possible to automatically select the correct wiznet chip dynamically, although this is probably not so desirable with limited memory and no desire for binaries to contain stuff they will never use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants