-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Nano 33 BLE #407
base: master
Are you sure you want to change the base?
WIP: Nano 33 BLE #407
Conversation
thanks! this is cool, and we want to make sure we match folk's expectations. |
Glad you like it! I've pushed my latest commits, which include a README in the bootloader directory. I also tested flashing back to the original bootloader, which worked great with my Atmel-ICE - flashing the Adafruit bootloader also worked great, so those are the instructions I used. Pretty sure there are some open-source CMSIS-DAP programmer firmwares out there, so should be accessible for those with the technical skills. I do have some photos of my (hacky) pogo pin jig that I haven't added yet, let me know if you think they'd be useful. (You can put a mechanical-only pogo pin 2 holes away from either side of the electrically-useful ones to go into the actual header holes for alignment, which is handy if you have a no-header version of the board. Today I didn't even clamp it when doing the bootloader since I had it down to a single command I could send with one hand.) |
yeah add any pics you like :) when you're done we'll do a final review |
@rpavlik Hi Ryan, I was taking a look at the Nano 33 BLE board, but it appears that the official docs disagree on D7 and D8. Specifically, the official board pinout diagram shows D7 is P0.09, and D8 is P0.10. However, the official Arduino BSP v1.1.3 variant.cpp says they are 0.23 and P0.21, respectively: Your commits appear to follow the BSP. Can you verify that D7 and D8, when mapped to P0.23 and P0.21 respectively as in your commits, will work in blink sketch targeting D7 / D8? If an LED doesn't blink on D7/D8 as-is, can you try again after adjusting Thanks! |
Good catch! I'll have to solder in the headers and try that one out. Pretty sure it's not the first inconsistency I've seen in the docs. |
@rpavlik -- Well, they updated the picture to match the variant files. So, no need to change pins at this point. :) |
Any updates on this? Hoping to use an SDK built on top of this with the nano sense :) |
This is very cool contribution. Does OTA also work with the bootloader? |
Oh that's a nice tool! Kind of like the one I built myself from perf board. I have never tried the ota stuff on an nrf chip so I don't know, sorry. I suspect that if it works on an Adafruit board, it probably will work with this conversion, but I am not sure. Recently I've been using mine not for BLE at all, but just as a fast processor with an attached imu. |
I am wondering what is missing for the pull to be accepted? |
Per adafruit/Adafruit_nRF52_Bootloader#94 and adafruit/Adafruit_nRF52_Bootloader#97 I'm interested in using the UF2 bootloader on my Nano 33 BLE. I got it working, though the stock Arduino board def uses bossac, which doesn't work with the adafruit NRF52 bootloader. To adjust for this, I added a new board in this board collection to use nrfutil dfu. The pin definitions are based on the original (though ported to this repo's technique), most everything else is related to or based on the Itsy or Feather nrf52832 definitions.
I have successfully run several Adafruit BLE demos, including the "Controller" example where adding these lines to the color packet handler lets you control the onboard RGB LED using the Bluefruit app:
No idea if there's appetite for merging this, but I figured I'd share and submit it at the very least.