-
Notifications
You must be signed in to change notification settings - Fork 1.3k
CP drive does not appear with Particle Boron #10096
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
Comments
If you connect to the REPL via a terminal program, and press reset, does it say you are in safe mode because it couldn't create CIRCUITPY? This could be because the external flash on the board is not an expected part number. What does the printing on the external flash chip say? |
Nothing comes up on the serial terminal when I reboot, it seems to be unable to connect. Yet, the LED still has the characteristic 3 white blinks. I don't know which chip is the flash chip (it's not called out in their datasheet), and it could be under either of the two large metal shields. In the meantime, I'll see if I can deceiver any of the marking on the chips that are visible. |
There was one chip with markings visible that might be the flash. The complete set of markings are: When I googled this, I noticed there were a couple links to forum posts related to issues using this flash in other devices (STM32U5 and nRF9160). |
The build has support for only "MX25L3233F", which is half the size Maybe they changed the flash chip at some point.
I'll submit a PR to add that flash chip. I'll tag you when that's done. BTW, I know of no CircuitPython support for the LTE hardware. |
Success! Boot_out.txt reads: |
OK! We'll merge it and it will be in 9.2.5. |
Adafruit CircuitPython 9.2.4 on 2025-01-28; Particle Boron with nRF52840.
I'm struggling to get a Particle Boron (https://www.adafruit.com/product/3994) to display the CircuitPython drive. In case it's helpful, the version printed on the PCB is v1.5.0, the model number on the sticker is BRN404X, FCC ID is 2AEMI-BRN404X, and the IC is 20127-BRN404X.
I used a J-Link Edu to replace the stock bootloader with the Boron's UF2 bootloader, but when I copied the .uf2 file for CP to the Boron, no CircuitPython drive appeared. This appears to be a Boron-specific thing because, I was able to perform the same sequence of operation on the Partilce Argon (with Argon appropriate files of course) and did get the CircuitPython drive to appear.
I checked the common issues and I don't have any of the offending programs like anti-virus software or Samsung Magician that are known to cause this issue. I also found an old forum post where someone said they had to uninstall the device drivers in windows to get it to show up as a drive-type-device, and I tried that, but no joy.
In case it's helpful I've tried CP 9.2.4 with the following bootloaders:
Boron (I also tried CP 9.2.4, 9.2.2, 8.2.9, 7.2.0, and 6.3.0 on this one)
Argon
Xenon
Generic NRF52480
All showed up as USB drives until I copied over the .uf2 file for CP.
Based on the blinking pattern of the RGB LED (3 white blinks every once in a while), I have inferred that CP appears to be running in safe mode, and was able to connect to the REPL using Putty. I tried sending
import storage
followed bystorage.erase_filesystem()
, but this just caused the device to crash and reboot. I've attached a screen shot showing that the boot loader appears as a drive and the contents of the REPL.If it helps with diagnosis, I'd be happy to try loading a version of CP that doesn't attempt to use external flash, but I don't have the skills to compile this myself.
The text was updated successfully, but these errors were encountered: