Implement Hard Coded Bootloader Options about adafruit_nrf52_arduino HOT 8 CLOSED

Since we may need an option for force OTA boot mode instead of the more common SERIAL mode, but we don't have a free pin dedicate for this, I propose to use the F.RST pad which is located on a test point on the bottom of the PCB. It won't happen commonly anyway.

We can still keep factory reset behaviour like normal (when only FRST is asserted), but asserted both DFU and FRST pins at the same time will enter OTA bootloader mode, which at least keeps the possibility even if it's more trouble than entering SERIAL bootloader mode.

from adafruit_nrf52_arduino.

What is the factory reset pin though. I don't see it in the schematics .

from adafruit_nrf52_arduino.

See P0.22 here: #1

It doesn't have a 0.1" pin, it's only available as a test pad on the bottom of the PCB.

from adafruit_nrf52_arduino.

Ah I see P0.22. Forget about factory reset, will it erase the memory application as well application data right ?

from adafruit_nrf52_arduino.

Btw, I forgot about the factory reset. Let's review the memory flash a bit.

• Our bootloader is larger starting from 0x78000 with 32KB + 8KB bootloader data ~ 40KB.
• Softdevice + MBR currently is 104 + 4 = 108
• Application + data is 512 - (40+104+4) = 364 KB

How much did we partition the application data, I would suggest 32KB, that leave 332 KB for dual bank --> an image is limited at 332/2 = 166KB

PS: SD 3.0.0 is larger with 120KB

from adafruit_nrf52_arduino.

I think 166KB is fine for a SD based image with OTA update support. That's still WAY more than we have for Bluefruit on the nRF51.

from adafruit_nrf52_arduino.

ok let give 32KB for user than. Factoryreset will cause bootloader to erase

• application code region
• applicaticon data region

Let's wait for this, we will dot it later when having something solid.

from adafruit_nrf52_arduino.

move discussion to bootloader repo adafruit/Adafruit_nRF52_Arduino_Bootloader#1

from adafruit_nrf52_arduino.