Daniel Blendea

Important changes to forums and questions

All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.

9 years, 2 months ago.

RDY, INTn pins

Hi,

I'm trying to connect WIZ550io (http://developer.mbed.org/components/WIZ550io/) to the F411RE. I was able to map all the pins on the WIZ550io except for the RDY and INTn pins.

From their documentation I'm guessing that RDY and INT are output pins for WIZ550io so they must be connected to input pins of F411. But, should they be analog or digital inputs?

And, please correct me if I'm wrong.

Thanks.

Question relating to:

Last updated: 20 Apr 2021
Affordable and flexible platform to ease prototyping using a STM32F411RET6 microcontroller.

Apparently, the WIZ550io doesn't like the NUCLEO pins. I connected the shield to the Arduino pins and it works.

SPI spi(D11, D12, D13); // mosi, miso, sclk
EthernetInterface eth(&spi, D10, D7); // spi, cs, reset

However I had to initialize eth with hardcoded IP, mask and gateway. It didn't initialize from dhcp. But at least now I can move on with the project.

posted by Daniel Blendea 15 Feb 2015

1 Answer

Phillip B.
9 years, 2 months ago.

Hi Daniel. I figure you've solved your problem already, but I thought I'd answer in case you hadn't.

The WIZNET5500io's hardware wiki page describes the RDY pin in digital terms:

Quote:

READY

This pin is asserted to low after power on.

When RSTn is activated, WIZ550io does auto configuration with embedded MAC and default IP address. After configuration gets completed, WIZ550io raises this pin to HIGH in order to inform about the completion of WIZ550io’s configuration.

Host processor can only control WIZ55oio when RDY pin is HIGH.

The low and high suggest a digital connection.

The INTn pin is described on the W5500 chip's datasheet like so:

Quote:

Interrupt output (Active low)

Low: Interrupt asserted from W5500

High: No interrupt

Again, the low and high references imply digital connections. The datasheet has more to say about using the INTn than the wiki.

Good luck. If you get a chance, post a comment on your progress.

Accepted Answer

Thanks,

Eventually I connected the two WIZ pins to D2 and D4. What I don't understand is how the host should use those pins. I couldn't find anywhere here how the EthernetInterface and the SPI should use those pins.

Anyway, after all pins are connected, WIZ is still not getting an IP although the green LED is on and the orange LED is flickering irregularly. I'm getting strange results when I'm initializing eth explicitly with IP 10.0.0.30

F411RE Listening
Initializing eth
Error eth.init() - ret = 0
Initialized, MAC: 04:06:01:81:50:02
Connected, IP: 57.84.2.4, MASK: 255.255.254.0, GW: 4.6.1.129
F411RE Listening
Initializing eth
Error eth.init() - ret = 0
Initialized, MAC: 08:10:18:06:05:40
Connected, IP: 32.0.64.1, MASK: 4.0.8.0, GW: 4.6.1.129

And when requesting an IP from dhcp:

F411RE Listening
Initializing eth
Error eth.init() - ret = 0
Initialized, MAC: 04:06:3A:00:00:0E
Connected, IP: 0.64.128.1, MASK: 4.8.12.116, GW: 0.0.0.0
F411RE Listening
Initializing eth
Error eth.init() - ret = 0
Initialized, MAC: 20:30:0C:0A:80:10
Connected, IP: 255.255.254.0, MASK: 4.6.1.129, GW: 4.6.1.129
posted by Daniel Blendea 14 Feb 2015

I haven't seen them used in the few examples I looked through either. Based on the datasheet, I think INTn can be ignored for now (it's used for timeouts and Wake On Lan interrupts). The RDY will read as LOW while the WIZ is not yet usable. I think the code examples should be using it for correctness, but the wait(1) calls probably make up for it. Still, consider waiting for RDY to go HIGH before calling eth.init(). At least you'll be able to rule that out as a problem.

If still nothing works, consider posting a new question under the WIZ550io component, since it looks like it has active followers who know the component well.

posted by Phillip B. 14 Feb 2015