Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

Hi, I notice that in the board definition files, you have defined the external flash size as 16 MByte.

However, my understanding was that the flash size is the same as the W5500-EVB-pico, i.e. 2MByte. Also the schematic for the W5500-EVB-Pico2 (see https://docs.wiznet.io/Product/iEthernet/W5500/w5500-evb-pico2#schematic) shows the flash to be a W25Q16JV, a 16Mbit part, i.e 2MByte.

Dear byzantic,

Thank you for your advice and for pointing out the issue with the flash size definition. You are absolutely correct, and I sincerely apologize for the oversight.

The flash size for the W5500-EVB-Pico2 / W5100S-EVB-Pico2 is indeed 2MByte, as the schematic indicates with the W25Q16JV flash, which is a 2MByte(16Mbit ). I have updated the mpconfigboard.h files to reflect the correct flash size.
and I’ve also completed the testing after the modification.

I truly appreciate your attention to detail and for bringing this to my attention. Thanks again for your help in ensuring the accuracy of the board configuration.

Best regards
Grace

Hi, I notice that in the board definition files, you have defined the external flash size as 16 MByte.

However, my understanding was that the flash size is the same as the W5500-EVB-pico, i.e. 2MByte. Also the schematic for the W5500-EVB-Pico2 (see https://docs.wiznet.io/Product/iEthernet/W5500/w5500-evb-pico2#schematic) shows the flash to be a W25Q16JV, a 16Mbit part, i.e 2MByte.

I may be a bit confused, but are there remaining changes needed for this PR? Looking forward to getting this board supported!

I may be a bit confused, but are there remaining changes needed for this PR? Looking forward to getting this board supported!

Sorry for the late reply, and thank you so much for your interest!

This PR is still active and there are no pending changes at the moment.
If there's anything that needs to be fixed or adjusted, we’d really appreciate your feedback.

Thanks again for checking in — we really appreciate the support!
Grace

Well, FWIW, I've been testing this PR in the wild.

I picked up a W5100S-EVB-Pico2 a few weeks ago wth the add-on PoE module. I built a Micropython install for it using this PR and the v1.25 release tag. Flashed it and deployed my code on top.

It has been running 24x7 monitoring a half dozen sensors every 10 seconds or so and sending the results over a TLS encrypted websocket to a central server. It seems pretty solid.

Thanks for the work @wiznet-grace and I'm looking forward to this being merged.

Well, FWIW, I've been testing this PR in the wild.

I picked up a W5100S-EVB-Pico2 a few weeks ago wth the add-on PoE module. I built a Micropython install for it using this PR and the v1.25 release tag. Flashed it and deployed my code on top.

It has been running 24x7 monitoring a half dozen sensors every 10 seconds or so and sending the results over a TLS encrypted websocket to a central server. It seems pretty solid.

Thanks for the work @wiznet-grace and I'm looking forward to this being merged.

Thanks a lot for testing and sharing your results!
Happy to hear it’s working well for you.
If you spot anything that needs improvement, feel free to let me know. 😊

Grace

Hello ! any reason for not merging it yet?

Hi, just following up on this PR. It’s been a few months since submission,
and we’ve seen some community users testing these WIZnet Pico2 boards with good results.

I’d be happy to rebase or make any changes needed to get this merged. Let me know if there’s anything I can help with!

Thanks again for maintaining MicroPython.

cc @dpgeorge

Hello @dpgeorge ,

This PR looks great, builds are passing and tests are conclusive, please advise on the reason of not approving yet. Thanks!

@wiznet-grace can you please share the uf2 generated from this PR? or how to do it? would like to proceed cause 7 months are way too much for a PR 😄

Hello @dpgeorge ,

This PR looks great, builds are passing and tests are conclusive, please advise on the reason of not approving yet. Thanks!

@wiznet-grace can you please share the uf2 generated from this PR? or how to do it? would like to proceed cause 7 months are way too much for a PR 😄

Sure! You can generate the .uf2 from this PR by cloning my fork directly:

1. Clone the repo and checkout the branch:

git clone https://github.com/wiznet-grace/micropython.git
cd micropython
git checkout WIZnet-EVB-Pico2

2. Initialize submodules:
   git submodule update --init
3. Build for the W5500-EVB-Pico2 board:

make -C mpy-cross
cd ports/rp2
make BOARD=W5500_EVB_PICO2
(or make BOARD=W5100S_EVB_PICO2)

4. After build completes, you'll find:
   build-W5500_EVB_PICO2/firmware.uf2

Let me know if you need help flashing the .uf2 to your board 😄

Thank you for the reviews and discussions.
All changes from this PR have now been included in #18035.
To keep things clean, I will close this PR and continue the work in #18035.