From aefabc5353cf8507b15f77a17ab38023324f3040 Mon Sep 17 00:00:00 2001 From: Josh Klar Date: Sat, 20 Oct 2018 03:29:20 -0700 Subject: [PATCH] Update docs to reflect proper size of device --- ports/nrf/boards/makerdiary_nrf52840_mdk/README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/ports/nrf/boards/makerdiary_nrf52840_mdk/README.md b/ports/nrf/boards/makerdiary_nrf52840_mdk/README.md index 826b930512..f1ba8151ac 100644 --- a/ports/nrf/boards/makerdiary_nrf52840_mdk/README.md +++ b/ports/nrf/boards/makerdiary_nrf52840_mdk/README.md @@ -4,10 +4,12 @@ Refer to https://github.com/makerdiary/nrf52840-mdk or https://wiki.makerdiary.com/nrf52840-mdk/ for more details about the device. Notably, CircuitPython does not currently support QSPI external flash on NRF -devices, so neither does this port. Don't store anything you care to read in -Python on that giant 64MB flash device for now - the 64MB drive that shows up on -your computer is actually part of the MSC driver provided by the DAPLink -debugger. You'll still have access to 256KB of the onboard flash, however, for +devices, so neither does this port - the 64Mb flash device is not used for +anything. Also, don't confuse this with the 64MiB drive that shows up on your +computer - it's actually part of the MSC driver provided by the DAPLink +debugger, and is inaccessible at all from Python land (this drive is where you +can copy `firmware.hex` if you'd prefer to flash that way as opposed to with +`pyocd`. You'll still have access to 256KB of the onboard flash, however, for storing your Python files, cat pictures, or whatever. It's also interesting to note that all three LEDs and the "user button" on this