notes on using the arduino ide with the adafruit feather nrf52 bluefruit le

Adafruit Feather nRF52 Bluefruit LE – nRF52832

All of this work is done on my MacBook Pro with macOS Mojave 10.14.6 (I haven’t upgraded beyond Mojave yet because I don’t see the need on the MacBook, and if I need macOS 10.15 it’s installed on my Mac Mini).

First, let’s sort out my (miss) adventures with Arduino IDE. It started a few days ago when I decided to do something with the Feather, a device I’d purchased nearly a year prior. I’d plugged it in several times when it first arrived and I’d used the Arduion IDE’s Serial Monitor (Tools > Serial Monitor) to check it. It shipped with the StandardFirmataBLE sketch compiled and installed, so I was able to see the device’s internal configuration on the Serial Monitor as well as test it with Adafruit’s Bluefruit LE Connect app. I then put it aside and wound up forgetting about it until just recently. Adafruit still sells the device today, which is good.

It was during this restart I noticed that my version of the Arduino IDE was at 1.8.7, but the website had released 1.8.10. So I downloaded the latest IDE software and installed it.

After the IDE updated I updated the Feather’s bootloader software. That went off without a hitch. Then I started to look at the sample sketches for the board that Adafruit provides. Since it already came with the Firmata sketch installed and running, I found the source in the samples and attempted to recompile and upload. That’s when everything went screwy. Here’s an example of the error output.

Arduino: 1.8.10 (Mac OS X), Board: "Adafruit Bluefruit Feather nRF52832, 0.2.13 SoftDevice s132 6.1.1, Level 0 (Release)"

/Users/wbeebe/Git/arduino/libraries/Servo/src/nrf52/Servo.cpp: In member function 'void Servo::writeMicroseconds(int)':
/Users/wbeebe/Git/arduino/libraries/Servo/src/nrf52/Servo.cpp:92:12: error: 'g_APinDescription' was not declared in this scope
  instance=(g_APinDescription[pin].ulPWMChannel & 0xF0)/16;
/Users/wbeebe/Git/arduino/libraries/Servo/src/nrf52/Servo.cpp: In member function 'int Servo::readMicroseconds()':
/Users/wbeebe/Git/arduino/libraries/Servo/src/nrf52/Servo.cpp:123:12: error: 'g_APinDescription' was not declared in this scope
  instance=(g_APinDescription[pin].ulPWMChannel & 0xF0)/16;
Multiple libraries were found for "Firmata.h"
 Used: /private/var/folders/d9/n152_yx519121c0nlmlds71c0000gn/T/AppTranslocation/2101D1AD-76B6-4A4E-A36D-936C2672D030/d/
Multiple libraries were found for "Adafruit_LittleFS.h"
 Used: /Users/wbeebe/Library/Arduino15/packages/adafruit/hardware/nrf52/0.14.6/libraries/Adafruit_LittleFS
Multiple libraries were found for "InternalFileSystem.h"
 Used: /Users/wbeebe/Library/Arduino15/packages/adafruit/hardware/nrf52/0.14.6/libraries/InternalFileSytem
Multiple libraries were found for "bluefruit.h"
 Used: /Users/wbeebe/Library/Arduino15/packages/adafruit/hardware/nrf52/0.14.6/libraries/Bluefruit52Lib
Multiple libraries were found for "Servo.h"
 Used: /Users/wbeebe/Git/arduino/libraries/Servo
 Not used: /private/var/folders/d9/n152_yx519121c0nlmlds71c0000gn/T/AppTranslocation/2101D1AD-76B6-4A4E-A36D-936C2672D030/d/
 Not used: /Users/wbeebe/Library/Arduino15/packages/adafruit/hardware/nrf52/0.14.6/libraries/Servo
Multiple libraries were found for "Wire.h"
 Used: /Users/wbeebe/Library/Arduino15/packages/adafruit/hardware/nrf52/0.14.6/libraries/Wire
exit status 1
Error compiling for board Adafruit Bluefruit Feather nRF52832.

Lots of error messages. The key to a solution is line 20, but I’ll get to that. In the meantime I went slumming on the Internet for solutions, none of which really worked, so that don’t bear repeating here. What finally got me out of this mess and allowed the sketch to compile is the removal of the libraries folder pointed to in line 20 (which none of the on-line experts never mentioned). I don’t know what happened except that something got out of sync in the upgrade to Arduino IDE 1.8.10, and that caused a cascade effect in the error messages. When I removed the libraries folder and then reloaded the Adafruit nRF52 specific libraries again, everything was just fine. The libraries folder was recreated by the IDE.

In the mean time I decided to try to run a sketch that simply flashed the LEDs on the Feather board. The listing follows.

#include <Arduino.h>

 * Sketch demonstrates mutli-tasking using the Scheduler.
 * Demo creates a loop2() that runs in 'parallel' with loop().
 * - loop() toggles LED_RED every 1 second
 * - loop2() toggles LED_BLUE every 300 milliseconds

void setup() {
    // whb Nov 2019
    // This must be performed first or else nothing else will work.
    // No, I don't know exactly why.

    // LED_RED & LED_BLUE pins are already initialized outputs.
    // Create loop2() using Scheduler to run in 'parallel' with loop()

 * Toggle the Red LED every second
void loop() {
    digitalToggle(LED_RED); // Toggle LED 
    delay(1000);            // wait for a second

 * Toggle the Blue LED every 300 milliseconds
void loop2() {
    digitalToggle(LED_BLUE); // Toggle LED 
    delay(300);              // wait for a half second  

There’s far more comments than code, and that’s after not including the boilerplate block comment at the start of the code. This is from an example sketch provided when you install the Adafruit libraries. So I compiled and uploaded it, and the lights didn’t flash. Ok. I went online to Adafruit’s Feather documentation and copied an even simpler sketch that just flashed the red LED. Again, compiled and uploaded and nothing happened. The red LED just glimmered, like it did while the upload to the Feather was taking place.

I went back and looked at the major Firmata sketch, and at setup specifically, and that’s when the light went off. So I added line 15 above, and bingo, the lights started to flash like they’re supposed to. I played with a number of other sketches like this one. Load them without the Serial.begin() and nothing worked. Add that single line and it worked as advertised.

I also like this sketch because it points to the use of freeRTOS in the code. Keep in mind that the processor in the feather is a 32-bit ARM Cortex M4 processor running at 64MHz with 64K of RAM and 256K of Flash. It’s more than enough for basic embedded work, including freeRTOS. When I think back to the late 1970s and early 1980s I would have given anything to have this back when all that was available were Commodore 64s and Apple ][s and TRS-80s and the original IBM PC. This even blows the original Macintosh away with its 8MHz Motorola 68000. And here it all is now, on a board not much bigger than a stick of chewing gum and all for just $25 instead of the hundreds to thousands back then. Anyway…

The Arduino and its environment are now stable again, and I can build (in C, and possible C++) “sketches” for the Feather. This goes along with my Circuit Playground and my little Adafruit 32U4 powered robot. All of my code is checked into my Github location,

a comparison of three mobile browsers on ios 13.2.2

I’ve grown increasingly paranoid, at an accelerated rate since 2016. I’m dependent upon the open Internet for communication and general iOS app functionality, since nearly all of my apps are useless without connecting to some service on the Internet. Whether it’s via WiFi or using AT&T, my current wireless provider, nearly everything I send mobily is in the clear. The notable exception is my use of ProtonMail, which encrypts and decrypts locally for email, and Signal, providing the same capabilities for chat.

A good portion of my “stuff” that flows across the wireless network is from my browsers. Visiting sites using HTTPS is nice and all, but that’s just the tip of the iceberg with regards to data security. There’s all the JavaScript libraries attached to all those web pages that are now absolutely required, and they’re doing everything to fingerprint and help track you. I really don’t care to be tracked. Where I go is none of anybodies business. So no matter if you’re running encrypted or unencrypted to your service, it’s trivial to invade your privacy, just at a different level. That led me to investigate how the basic mobile browsers, just on their on, help or hinder how you’re tracked. For that kind of initial measuring I turned to EFF’s Panopticlick web page.

These following screenshots are Google Chrome, Firefox, and Safari running the Panopticlick web page. The browser apps are all up to date.

The worst of the browsers as far as Panopticlick is concerned is Chrome, the first screen capture. It got no green checks, only warnings (partial protection) and outright red cross marks, an indication of no protection. I don’t use Chrome on my iPhone, so that’s not an issue.

The next entry is Firefox. I had it configured for night mode so I could attempt to match the dark mode I have my phone in. It faired much better than Chrome in this test.

Finally there’s Safari at the bottom. Like Firefox it faired much better than Chrome, and it managed to fair a bit better than Firefox fingerprinting, which was deemed a partial.

I’ve been looking at moving over to Firefox on mobile for a long time, but it has a number of operational issues that keep me from using it on my iPhone. For all practical purposes I’m happy with Safari (although its lack of dark mode is a bit strange), and trust it more than the other two. If I didn’t have Safari (meaning I was using an Android handset) I’d be using Firefox in a cold New York minute before I would ever fire up mobile Chrome. And if anything ever goes sideways with Safari, I’m pretty certain I could live with some of the quirks I found using Firefox.

But for now, it’s still Safari for me.