I started looking into Jacob's bootloader as he commented me about it on one of my topics on Raspberry forum. Instead of the application uploading from a fixed server address, I'd like to instead have the Pico application be the server to receive the BIN file so I can upload it from any client, regardless of the IP of the client.
Of course you can do it that way. Jakob's library doesn't handle the transfer of the BIN over the network, so you are free to do as you please. LWIP does include a webserver with post capability you could use. Though it isn't an easy library to use. There are some other embedded http server out there too as open source projects. I'd probably recommend looking at mongoose.ws/.
I don't think you need RTOS to provide an HTTP platform. It already exists in LWIP application, though what exists in Pico SDK inclusion of LWIP library may be stripped down. Does RTOS expand on what Pico SDK LWIP provides?
Your are quite right you can provide HTTP using just LWIP as client and server. You need to manage the network connection using interrupts or polling through. By using a RTOS LWIP can provide a Posix style socket. It also takes away the need to poll the network.
I started looking into Jacob's bootloader as he commented me about it on one of my topics on Raspberry forum.
Instead of the application uploading from a fixed server address, I'd like to instead have the Pico application be the server to receive the BIN file so I can upload it from any client, regardless of the IP of the client.
Of course you can do it that way. Jakob's library doesn't handle the transfer of the BIN over the network, so you are free to do as you please.
LWIP does include a webserver with post capability you could use. Though it isn't an easy library to use. There are some other embedded http server out there too as open source projects. I'd probably recommend looking at mongoose.ws/.
I don't think you need RTOS to provide an HTTP platform. It already exists in LWIP application, though what exists in Pico SDK inclusion of LWIP library may be stripped down. Does RTOS expand on what Pico SDK LWIP provides?
Your are quite right you can provide HTTP using just LWIP as client and server. You need to manage the network connection using interrupts or polling through.
By using a RTOS LWIP can provide a Posix style socket. It also takes away the need to poll the network.