John Maloney

Here is a test program that fails: void setup() { pinMode(LED_BUILTIN, OUTPUT); } void loop() { digitalWrite(LED_BUILTIN, HIGH); delay(250); digitalWrite(LED_BUILTIN, LOW); delay(250); } With this platformio entry: [env:test] platform =...

Yes, I'm guessing this is a bootloader. The board has a bootloader but the bootloader has a SoftDevice which may be conflicting with NimBLE. Here is the info file: UF2...

The problem may be this (from the README): "The provided Adafruit bootloaders have no softdevice, if you currently are using the softdevice based Adafruit bootloader on your nRF52 board you...

The Adafruit bootloader may have changed since you last tested n-able-arduino on Adafruit boards. The current bootloader apparently prevents replacing itself or the built-in softdevice. I tried replacing the bootloader...

The suggested change would also address issues #11 and #20.

I don't think I have the expertise to do a PR for this, but I'd be happy to advise. I don't fully understand what the gcc_startup_nrf52840.S must do or how...

The Adafruit memory maps [here](https://learn.adafruit.com/bluefruit-nrf52-feather-learning-guide/hathach-memory-map) may help. I think both the "user data" and, of course, the "bootloader" sections are reserved. However, the nRF52840 has 1024k of Flash, so even...

I also ran into this issue. You can also disable the watchdog timer by adding: `-DCONFIG_WDT_TIMEOUT_SECONDS=0` to your compiler flags. It would be nicer for newcomers to n-able-Arduino if the...

Thanks! (You might not have noticed that the resets were happening. I didn't notice at first. What brought it to my attention was that variables were getting reset to their...

I just submitted a tiny PR to make CONFIG_WDT_TIMEOUT_SECONDS default to zero (WDT disabled).