I suspect I know the answer in advance, but recent events have encouraged me to check first....
As part of my on-going self-education, I am looking at redeveloping some existing firmwares I have, that are currently on ESP8266 and ESP32 hardware for the Pico (mainly Pico W). The idea of a wired connection is also compelling, and I do have a W5100S-EVB-Pico board, as well as a number of WizNet SPI modules which could be connected to regular Pico or Pico W boards.
I know from Wiznet's webside that there is RP2040-HAT-LWIP-C available from github, which will give me (allegedly) an SDK environment including the relevant lwip port components.
I see that in the latest standard Pico SDK, there is a wiznet_w5100s_evb_pico.h in in the ${SDK}/src/boards/include/boards folder.
Is support for board baked into the standard SDK, or do I need to pull down the WizNet stuff and use that?
Ideally for my dev system, I'd only have the one copy of the pico SDK, and use the same basic CMake stuff (barring a few definitions, to specify board type, of course) for the variants I'm writing.
I assume that the WizNet stuff uses the pico SDK as a submodule, but I haven't yet had time to start looking at it in detail, as I have been busy asking PlatformIO why RP2040 isn't supported if you're developing on a Pi. I understand that some community members have done a lot of work on it, but this is being held back (or ignored) by the PlatformIO guys - I guess when you consider that they may well be in a war zone (or special military operation zone, depending on where you get your news from) this isn't a surprise.
Anyway, it would be nice to just have a (relatively) simple, single environment to do my Pico related stuff on.
As part of my on-going self-education, I am looking at redeveloping some existing firmwares I have, that are currently on ESP8266 and ESP32 hardware for the Pico (mainly Pico W). The idea of a wired connection is also compelling, and I do have a W5100S-EVB-Pico board, as well as a number of WizNet SPI modules which could be connected to regular Pico or Pico W boards.
I know from Wiznet's webside that there is RP2040-HAT-LWIP-C available from github, which will give me (allegedly) an SDK environment including the relevant lwip port components.
I see that in the latest standard Pico SDK, there is a wiznet_w5100s_evb_pico.h in in the ${SDK}/src/boards/include/boards folder.
Is support for board baked into the standard SDK, or do I need to pull down the WizNet stuff and use that?
Ideally for my dev system, I'd only have the one copy of the pico SDK, and use the same basic CMake stuff (barring a few definitions, to specify board type, of course) for the variants I'm writing.
I assume that the WizNet stuff uses the pico SDK as a submodule, but I haven't yet had time to start looking at it in detail, as I have been busy asking PlatformIO why RP2040 isn't supported if you're developing on a Pi. I understand that some community members have done a lot of work on it, but this is being held back (or ignored) by the PlatformIO guys - I guess when you consider that they may well be in a war zone (or special military operation zone, depending on where you get your news from) this isn't a surprise.
Anyway, it would be nice to just have a (relatively) simple, single environment to do my Pico related stuff on.
Statistics: Posted by SteveSpencer — Sat Mar 16, 2024 4:30 pm