From 9d3ca0d0f9517c98621e559d0ba6412c02b3fd1b Mon Sep 17 00:00:00 2001
From: geeksville <kevinh@geeksville.com>
Date: Fri, 10 Jul 2020 18:46:33 -0700
Subject: [PATCH] fix esp32 build

---
 .vscode/settings.json       | 3 ++-
 docs/software/nrf52-TODO.md | 7 ++++++-
 src/{ => nrf52}/alloc.cpp   | 0
 3 files changed, 8 insertions(+), 2 deletions(-)
 rename src/{ => nrf52}/alloc.cpp (100%)

diff --git a/.vscode/settings.json b/.vscode/settings.json
index 87c760c8c..e6f1d49e1 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -47,7 +47,8 @@
         "memory_resource": "cpp",
         "optional": "cpp",
         "string_view": "cpp",
-        "cassert": "cpp"
+        "cassert": "cpp",
+        "iterator": "cpp"
     },
     "cSpell.words": [
         "Blox",
diff --git a/docs/software/nrf52-TODO.md b/docs/software/nrf52-TODO.md
index 26d03a3b1..76b5fd5f6 100644
--- a/docs/software/nrf52-TODO.md
+++ b/docs/software/nrf52-TODO.md
@@ -3,7 +3,12 @@
 ## RAK815
 
 TODO:
-This board has a TCXO, which is uncommon. For better RF performance it should be enabled P0.05 (RF95_TCXO) high. And then tell the RF95 to use it.
+* P0.23 is for PABOOST? see page 2 in RAK813 sechematic  P0.22 is for HF_RF_CPS?  Look up datasheet for PE4259  Until this is fixed I bet the range is quite poor.  DIO2 is not 
+controlling PABOOST on this board!
+* i2c gps
+* BLE link
+* measure power draw
+
 
 ### Bootloader
 
diff --git a/src/alloc.cpp b/src/nrf52/alloc.cpp
similarity index 100%
rename from src/alloc.cpp
rename to src/nrf52/alloc.cpp