Arduino guide

Papyr can be used with Arduino! this section contains how to use arduino IDE for development on papyr. The Arduino core is based on Adafruit's nRF52 core, which is forked from Sandeep Mistry's Arduino core for Nordic Semiconductor chips.


  1. Download and install Arduino IDE (at least v1.6.12) from Arduino website.
  2. Start the IDE
  3. Go into preferences
  4. Add as an "Additional Board Manager URL"
  5. Open the Boards Manager from the Tools -> Board menu and search/install "Electronut labs nRF52840 Boards"
  6. Select 'Electronut labs Papyr' from the Tools -> Board menu
  7. Select 'Black Magic Probe (GDB)' from the Tools -> Programmer menu

Upload code with Bumpy

For Programming perpose, you can use Bumpy (blackmagic probe compatible SWD debugger). You can buy bumpy from here.

Connect Bumpy with Papyr:

Bumpy Papyr

Bumpy will show up as two serial ports. The first one of these is the GDB serial port, and is used for programming only. The second one is connected to UART pins of nRF52840 (pins are reconfigurable on the chip).

Any code compiled right now requires Nordic Semiconductor's BLE stack binary, called the Softdevice to be present on the nRF52840 chip. This needs to be programmed only once while using arduino. To do this, click on Tools -> Burn bootloader menu option. (There is no bootloader in this port of arduino, we upload only the softdevice.)

Note about serial ports: In this arduino core, Serial is the serial port that comes up when you plug in the USB port of papyr to your computer. This one is USB device peripheral of the nRF52840 chip. Serial1 is the actual UART peripheral of nRF52840 SoC, and it is connected to the Debugger's serial port (which comes up as the second serial port on your computer). In Arduino IDE, you have to select the first port for programming; this means serial montor will not work with that one. To use serial monitor, you can switch to the second port temporarily. We prefer to use a separate serial monitor program like putty, or picocom. For example, if you are on linux and have installed picocom, you can use the following command in a terminal to keep the port open (at 115200 baud rate):

picocom -b 115200 /dev/ttyACM1


You can find papyr arduino examples here.

For e-paper, GxEPD2 and Adafruit-GFX libraries are used, so make sure to install these before compiling the code.

Here is the video of arduino code running on Papyr.

Pin mapping

Pin mumbers are directly connected to the nRF52840 port/pin numbers. Pin numbers 0-31 are on the chip's Port0. Pin numbers above 32 are on Port1. For example, pin 16 corresponds to Port0, pin 16; pin 40 correseponds to Port1 pin 8 (i.e. 40-32).

You can use the following symbols in your code:


PIN_LED1             pin 14
PIN_LED2             pin 13
PIN_LED3             pin 15

LED_CONN             PIN_LED2

LED_GREEN            PIN_LED1
LED_RED              PIN_LED2
LED_BLUE             PIN_LED3


This serial port is connected to the Black Magic Probe debugger's USB to serial pins.



The SPI pins are connected to the e-Paper display. The pin mapping is as follows:

MISO         pin 33
MOSI         pin 29
SCK          pin 31
SS           pin 30


These pins can be used for interfacing I2C sensors. The pin mapping is as follows:

SDA         pin 5
SCL         pin 6


Analog pins are mapped as follows:

PIN_A0       pin 3
PIN_A1       pin 4
PIN_A2       pin 28
PIN_A3       pin 29
PIN_A4       pin 30
PIN_A5       pin 31


A known issue with bumpy is that sometimes the debugger is not able to detect the nRF52840 chip when it scans. This happens rarely, and there is a manual fix for that.

Option 1: One can either repeatedly try uploading (which takes time if compiling), or by trying 'Burn bootloader' (Alt+T, then Up, then enter). If you can run arm-none-eabi-gdb directly, you can run it like in the following terminal capture. First we specify the GDB serial port (which is the first port detected when Papyr is connected to your computer) using tar ext <GDB port>. Next, try scanning using the command mon swdp_scan. Keep on pressing enter till the chip is detected:

Following is output when chip is not detected:

$ arm-none-eabi-gdb
GNU gdb (GNU Tools for Arm Embedded Processors 7-2018-q3-update)
>>> tar ext /dev/ttyACM0
Remote debugging using /dev/ttyACM0
>>> mon swdp_scan
Target voltage: unknown
SW-DP scan failed!

Following is output when it gets detected:

>>> tar ext /dev/ttyACM0
Remote debugging using /dev/ttyACM0
>>> mon swdp_scan
Target voltage: unknown
Available Targets:
No. Att Driver
 1      Nordic nRF52
 2      Nordic nRF52 Access Port