CircuitPython 3.0.1 breaks built in NeoPixel on Feather M4 Express

[ash0x1b]

After upgrading to CP 3.0.1, built in NeoPixel does't work anymore. It doesn't indicate the CP state with green/white and driving it with code has no effect.

Code below works in 3.0.0, doesn't work in 3.0.1

import time
import board

import neopixel
led = neopixel.NeoPixel(board.NEOPIXEL, 1)
 
led.brightness = 0.3
 
while True:
    led[0] = (255, 0, 0)
    time.sleep(0.5)
    led[0] = (0, 255, 0)
    time.sleep(0.5)
    led[0] = (0, 0, 255)
    time.sleep(0.5)

[jerryneedell]

I have also reproduced this issue on a feather_m4_express and on a metro_m4_express :-(

[jerryneedell]

This is likely a result of PR #1132 -- I will experiment with the timing to try to resolve it.

[deshipu]

Perhaps at some point we will need to add a parameter telling the neopixel code whether they are powered with 3.3V or 5V.

[jerryneedell]

submitted PR #1141 - this seems to work.

[dhalbert]

@ash0x1b could you try this build, which includes #1141, and see if it works on your board? Thanks.

https://adafruit-circuit-python.s3.amazonaws.com/bin/feather_m4_express/adafruit-circuitpython-feather_m4_express-20180824-caa2328.uf2

[ash0x1b]

@dhalbert I can confirm, build from caa2328 fixes the problem on both Feather M4 Express and Metro M4 Express.

I have 2 Metros M4 Express and 2 Feathers M4 Express. Yes, I always buy my boards in pairs due to magic white smoke being so eager to escape.

While both Feathers had the same issue with 3.0.1, Metros didn't. One worked fine but the other one presented the same issue. Both Metro boards were purchased at the same time from Mouser so I assume they were from the same batch.

[dhalbert]

@ash0x1b Thanks! We'll do another release relatively soon.

[dhalbert]

Fixed by #1141.