• Re: Anyone familiar with PICO Pi SDK and networking?

    From scott@alfter.diespammersdie.us@3:770/3 to Theo on Wed Sep 6 18:47:02 2023
    Theo <theom+news@chiark.greenend.org.uk> wrote:
    Every vendor has some degree of proprietary libraries and/or toolchain, and each vendor has a relatively small community of users. Some of whom have a hotline to the vendor's support staff which the rest of us don't.

    So the platform is much less well tested than the standard Linux/glibc/gcc flow. Troubles like this aren't unusual in this environment.

    Arduino on Atmega is probably the most beaten path in the embedded space - but less popular Arduino platforms suffer from similar creakiness.

    I've had pretty good luck with VSCodium and PlatformIO. They manage to abstract away most of the unpleasantness involved in dealing with yet
    another toolchain. With it, I've been able to wrangle different bits of
    code targeting microcontrollers with AVR, ARM, and RISC-V cores. Some have been a little easier to set up than others (the programmer dongle for some
    of the RISC-V dev boards I have needed its firmware updated with another
    tool first), but once it's sorted, writing code for any of them isn't too
    much different.

    --
    _/_
    / v \ Scott Alfter (remove the obvious to send mail)
    (IIGS( https://alfter.us/ Top-posting!
    \_^_/ >What's the most annoying thing on Usenet?

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
  • From The Natural Philosopher@3:770/3 to scott@alfter.diespammersdie.us on Thu Sep 7 12:04:30 2023
    On 06/09/2023 19:47, scott@alfter.diespammersdie.us wrote:
    Theo <theom+news@chiark.greenend.org.uk> wrote:
    Every vendor has some degree of proprietary libraries and/or toolchain, and >> each vendor has a relatively small community of users. Some of whom have a >> hotline to the vendor's support staff which the rest of us don't.

    So the platform is much less well tested than the standard Linux/glibc/gcc >> flow. Troubles like this aren't unusual in this environment.

    Arduino on Atmega is probably the most beaten path in the embedded space - >> but less popular Arduino platforms suffer from similar creakiness.

    I've had pretty good luck with VSCodium and PlatformIO. They manage to abstract away most of the unpleasantness involved in dealing with yet
    another toolchain. With it, I've been able to wrangle different bits of
    code targeting microcontrollers with AVR, ARM, and RISC-V cores. Some have been a little easier to set up than others (the programmer dongle for some
    of the RISC-V dev boards I have needed its firmware updated with another
    tool first), but once it's sorted, writing code for any of them isn't too much different.


    As the OP on this thread, I can say that once the documentation has been
    found, and its ambiguities tested against real life code, the code
    itself appears to be robust, as does the hardware. Unlike the somewhat flakiness of microPython, documented in other threads.

    e.g. timeouts do not work reliably, but watchdog timers seem to, so I implemented a 'i cant connect in 5 seconds, so abort and try again'
    sequence to at least not brick the code if the server goes off line.

    I have yet to test the wifi point going off line. That may requires some further delving.

    It's been uphill and a struggle all the way, but I now have some minimal
    code that runs very well.

    I have, in short, solid foundations on which to build any wifi connected gadgets around the place.

    I might well have done it with Arduinos etc. but faced with zero
    knowledge of either platform software wise, I picked the Pi.


    --
    "First, find out who are the people you can not criticise. They are your oppressors."
    - George Orwell

    --- SoupGate-Win32 v1.05
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)