#Release 0.7.0 · adafruit/Adafruit_nRF52_...
hardy dust
this will get you the files:
curl -O -L "https://github.com/adafruit/Adafruit_nRF52_nrfutil/releases/download/0.5.3.post17/adafruit-nrfutil--0.5.3.post17-macos.zip"
unzip "adafruit-nrfutil--0.5.3.post17-macos.zip"
chmod +x adafruit-nrfutil
curl -O -L "https://github.com/adafruit/Adafruit_nRF52_Bootloader/releases/download/0.7.0/circuitplayground_nrf52840_bootloader-0.7.0_s140_6.1.1.zip"
from the same command line, you can look for the port with:
ls /dev/cu.usbmodem*
which should have only the current CPB in bootloader mode unless you have other things connected
once you find the port, you can save it, that helps keeping it:
PORT="/dev/theport" # replace with the actual port from above
and then from the same command line you can flash a board with:
./adafruit-nrfutil --verbose dfu serial --package "circuitplayground_nrf52840_bootloader-0.7.0_s140_6.1.1.zip" -p "$PORT" -b 115200 --singlebank --touch 1200
past bluff
OK - thx. Am following these steps. When I run the step to get the port, this is returned:
/dev/cu.usbmodem311401
When I run the save command, is 'theport' the whole cu.usbmodem311401 or usbmodem311401 or just 311401? I currently have a USB hub working from home, but if I head into work tomorrow I'll direct-connect to my Mac. Should I assume I need to rerun the command to get the port & then save the port to get anything that may have a different USB setup?
past bluff
OK! So I think I may have had success. I ran the steps above. Got lots of terminal activity. ended in "upgrade took... device programmed". Then when I look at the CPLAYBOOT still mounted I see:
UF2 Bootloader 0.7.0 lib/nrfx (v2.0.0) lib/tinyusb (0.12.0-145-g9775e7691) lib/uf2 (remotes/origin/configupdate-9-gadbb8c7) which I assume means I've now got the v.0.7 bootloader. Is this correct? And if so. Do I eject my current CPB & just put in any additional ones, up arrow ,and rerun the command:
./adafruit-nrfutil --verbose dfu serial --package "circuitplayground_nrf52840_bootloader-0.7.0_s140_6.1.1.zip" -p "$PORT" -b 115200 --singlebank --touch 1200?
hardy dust
yeah that should work
if the port is wrong there should be no harm, you'll just have to check it again
past bluff
This is a big help. I'm noticing one more thing. So I updated my first board. While it was still plugged into the USB port, I dragged over the latest CIRCUITPY & the board seemed to update properly. Double tap on the RESET is a ring of green, not green then red as we got before. I dragged over the latest .uf2 for the CPB and the board seemed to update properly.
Next I enjected the CPB, then plugged a new board into my Mac.
New board mounts as CIRCUITPY
Then I double-tap the RESET button on this new board. It mounts as CPLAYBOOT, but I get the green lights followed by solid red lights, which I thought indicated that we had the bootloader issue.
I look in the INFO_UF2.TXT file & see:
UF2 Bootloader 0.7.0 lib/nrfx (v2.0.0) lib/tinyusb (0.12.0-145-g9775e7691) lib/uf2 (remotes/origin/configupdate-9-gadbb8c7) which, if I'm reading properly, suggests this has the proper bootloader (0.7). Is this correct and if so, why would I get green ring then red ring? Or is there some sort of legacy cache that's not clearing on this? Again, thx for tolerating me as I try to figure this all out.
BTW: up-arrowing in the Terminal & re-running the command:
./adafruit-nrfutil --verbose dfu serial --package "circuitplayground_nrf52840_bootloader-0.7.0_s140_6.1.1.zip" -p "$PORT" -b 115200 --singlebank --touch 1200 seems to have done a proper update with the CPB lights showing solid green, the CPB mounted as CPLAYBOOT, and ready to receive a new .uf2 file.
hardy dust
uh that's weird, red normally means that the bootloader can't connect to the computer (or is in some error state I guess), maybe it's doing weird things between Ventura and the old bootloader
past bluff
OK. This was HUGELY helpful. I'll copy the text from this thread & run this in the work lab tomorrow. Hopefully I can update all of our CPBs. I think they're all in a single box - will mark the back just in case & I'll keep this thread handy in case things need repeating. This whole bootloader business only applies to nRF52840, correct? We don't use any other boards in class that have this chip, save for the CPB. The old CPXs shouldn't be impacted, right? Nor any Raspberry Pi Pico Ws, Arduino Nano RP2040 Connects (those are the other boards we have a lot of). Thanks again! If we ever meet I will be most happy to buy you a beverage of your choice!