This.PIO.Enable is missing.

[krischik]

I hope this is the correct place. Thanks for you patience.

[JeremyGrosser]

This would reset the whole PIO peripheral, breaking any other programs that are already loaded into other SMs. It’s the caller’s responsibility to enable the peripheral before calling WS2812.Initialize.

The driver behavior is correct, albeit poorly documented.

[krischik]

@JeremyGrosser

The driver behavior is correct, albeit poorly documented.

Poorly documented indeed as your sample code (https://github.com/JeremyGrosser/pico_examples/blob/master/ws2812_demo/src/ws2812_demo.adb) isn't calling RP.PIO.Enable; and you sample code is the only documentation available. That means that currently documentation and implantation are at odds and one of the two needs to be fixed.

Note that I have wasted 2 days on this because the sample code isn't working.

[JeremyGrosser]

A quote from the LICENSE file:

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.