error connecting two w5500s at the same time

[cyber-bat]

Callback function don't work with second module

[cyber-bat]

callback function doesn`t depend on the instance of the class?

[seok930927]

If you are trying to control two or more W5500 chips from a single host MCU or system using the ioLibrary,
it is expected that the library does not work correctly when used without modification.

The ioLibrary is originally designed to control only one WIZnet chip.
Several core resources are implemented as global variables or preprocessor macros,
which means the driver assumes that only one WIZnet device exists on the host system.

In addition, the ioLibrary controls the Chip Select (CS) signal internally.
Therefore, if you want to use multiple W5500 devices, you will need to make one of the following modifications.

---

✔ Minimal Modification

• Remove the internal CS control code from the ioLibrary.

• Multiple W5500 chips should

  • share the same CLK, MOSI, and MISO lines,

  • while each device uses its own CS pin.

• When accessing a specific W5500,

  • manually pull its CS pin LOW before SPI access,

  • and set it HIGH after access, to ensure only the intended chip responds.

---

✔ Larger Modification (Proper Multi-Device Support)

To fully support multiple W5500 chips, the ioLibrary must be restructured so that each device can be handled as an independent instance.

• This requires converting key global variables into dedicated C structures, or C++ classes,

• so that each W5500 can have its own independent state.
  With this approach, you can instantiate multiple objects and manage each chip separately.