#So I tried, after many experiments, I

1 messages · Page 1 of 1 (latest)

candid holly
#

It sounds like you're learning new skills and doing several things at the same time, which could each independently (or in combination) be the source of a problem. I'd recommend trying to reduce the number of variables in play by ruling things out step by step. For example:

  1. It's fairly common for people to report having problems with Thonny, and those sometimes turn out to be related to the way that Thonny communicates with the CircuitPython board. You can rule out that possibility by trying different a different editor or IDE, perhaps https://code.circuitpython.org/
  2. You could try practicing making builds with small configuration changes to one of Adafruit's officially supported boards, or to a popular actively maintained board by some other vendor. Sometimes the code for boards that aren't used as much will have problems that don't get noticed quickly.
  3. Make sure you understand how to ensure the nRF52840 bootloader is properly updated. For example, see https://learn.adafruit.com/introducing-the-adafruit-nrf52840-feather/update-bootloader
  4. Check if the board you are using has a different clock crystal than what's specified in the build configuration you're using (see BOARD_HAS_32KHZ_XTAL)
  5. Check if the board you're using has a different flash chip (no flash chip?) than what's specified in the build configuration you're using
  6. Try building 10.0.3 instead of 10.1.0-beta.1
wide iron
#

re 6. The difference between 10.0.3 and 10.1.0-beta.1 for nrf52840 should be pretty much nothing (that is not always the case)

#

I endorse 1. Try a plain terminal instead of Thonny. Thonny does a lot of invisible stuff when talking to the REPL. It is NOT just a terminal. It uses invisible REPL commands to read and write files and run some code.

errant silo
candid holly
#

have you read about "git bisect"? It's a technique assisted by git to do a binary search over a series of commits where you know one that's good and one that's bad. Using git bisect can help you find a specific commit that takes you from a good build to a bad build.