Andrew Scheller

Don't these normally end up being created inside the `build` folder anyway?

@protik09 See also https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf

Is this the same thing as #111 and #442 or are those slightly different?

As I might have mentioned before, I only provide "(hopefully) helpful comments", it's not my decision whether to merge PRs in `pico-sdk` or `pico-examples`. But my first helpful comment would...

> As I might have mentioned before, I only provide "(hopefully) helpful comments", it's not my decision whether to merge PRs in `pico-sdk` or `pico-examples`.

I think GitHub just treats _any_ comment on the code as a "review" :facepalm:

Is this a duplicate of #447 ?

It's possible that https://github.com/raspberrypi/pico-examples/issues/423#issuecomment-1742244505 also applies here?

Looks like the same thing affects https://github.com/raspberrypi/pico-examples/blob/develop/pico_w/wifi/iperf/picow_iperf.c#L98 too? Some of the other picow examples use `cyw43_arch_gpio_put` rather than `cyw43_gpio_set` - most of them use `CYW43_WL_GPIO_LED_PIN` but https://github.com/raspberrypi/pico-examples/blob/develop/pico_w/wifi/freertos/iperf/picow_freertos_iperf.c#L53 uses a hardcoded...

> It looks like FreeRTOS is looking for `configNUMBER_OF_CORES` but the SDK and example code is using `configNUM_CORES`. A quick workaround is to define them to be the same thing....