Skip to the content
4 layers58.4 × 54 mmTempo bt, the printed circuit board in 3D

A Bluetooth LE version of the Tempo Skydiving data logger

Size
58.4 × 54 mm
Copper layers
4
Thickness
1.6 mm
Parts
69
Nets
106
Pads
358
Tracks, vias
876, 99
Pours
1
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
18 Oct 2025
Updated
27 Sep 2026

Overview

Tempo bt is an open-source printed circuit board by rrainey, from the rrainey/tempo-bt repository on GitHub, published under the GPL-3.0 licence. It is a 4-layer board of 58.4 × 54 mm with 69 parts on 106 nets, routed with 876 tracks and 99 vias.

It is built around the NORA-B106-00B, SAM-M10Q-00B and BMP390, with the MMC5983MA, MX25R6435FZNIL0-TR and MEM2061-01-188-00-A among its other parts. Its parts include 16 resistors, 14 capacitors, 8 ICs, 7 diodes and 5 connectors.

Main components

12

README

hardware/tempo-bt/README.md

tempo‑bt V1 board — Peripheral IC Connections

Core MCU/Module: u‑blox NORA‑B106 (nRF5340) OS: Zephyr RTOS Goal: Provide a canonical, test‑ready mapping of logical nets from the NORA‑B106 to each peripheral IC for driver bring‑up and HW connectivity tests.

High‑level digital interconnect

mermaid
flowchart LR
  subgraph Core [NORA‑B106 (nRF5340)]
    QSPI[QSPI: SCK, CSN, IO0..IO3]
    SPI4[SPI (SPIM4): SCK, MOSI, MISO, CSN]
    I2C[I²C: SCL, SDA]
    UART_A[UART A: NET_NORA_TX/RX]
    UART_B[UART B: APP_NORA_TX/RX, RTS/CTS]
    VCOM[USB‑UART: VCOM1_TX/RX]
  end

  QSPI --> Flash[MX25R6435F 64Mbit QSPI NOR]
  SPI4 --> IMU[ICM‑42688‑V 6‑axis IMU]
  I2C --> Press[BMP390 Baro]
  I2C --> Mag[MMC5983MA Mag]
  UART_A --> GNSS[SAM‑M10Q GNSS]
  UART_B --> TestApp[App/aux interface]
  VCOM --> HostPC[USB‑UART Console]

Notes • Net names and bus roles mirror the labels present on the schematic (e.g., SPIM4_SCK, QSPI_IO0, SCL, SDA, NET_NORA_TX, APP_NORA_RTS/CTS, VCOM1_RX/TX). • Where interrupts or extra control pins exist but were not explicitly net‑labeled to the MCU on the sheet, they’re called out as TBD/verify so you can tag them to specific GPIOs during bring‑up.


User Outputs / Inputs

SignalB106 connectionDescription
LED1P1.06
LED2P0.12
BTN1P0.23Pushbutton 1 (with hardware debounce)
BTN2P0.24Pushbutton 2 (with hardware debounce)

Connectivity tables (by peripheral)

1) External QSPI NOR flash — MX25R6435F (64 Mbit)

BusPCB logical netB106 PortFlash pin/functionNotes
QSPIQSPI_SCKP0.17/SCKSCLKPrimary quad SPI clock
QSPIQSPI_CSNP0.18/CSNCS#Chip select
QSPIQSPI_IO0P0.13/IO0IO0 (MOSI/SI)Data/IO0
QSPIQSPI_IO1P0.14/IO1IO1 (MISO/SO)Data/IO1
QSPIQSPI_IO2P0.15/IO2IO2 (WP#)Quad IO2 / Write Protect when legacy
QSPIQSPI_IO3P0.16/IO3IO3 (HOLD#/RESET#)Quad IO3 / Hold# when legacy

Additional compatibility labels seen on sheet:

  • FLASH_MOSI, FLASH_MISO, FLASH_SCK appear alongside the QSPI_* set; treat as alternative/legacy SPI naming used at fan‑out or test points.

Zephyr tips: Use jedec,spi-nor with qspi child and 4‑line mode; map io0..io3 and cs-gpios to the same nets as above.


2) 6‑axis IMU — ICM‑42688‑V

BusPCB netB106 PortIMU pin/functionNotes
SPI (SPIM4)SPIM4_SCKP0.08/SCKSCLKIMU serial clock
SPI (SPIM4)SPIM4_MOSIP0.09/MOSISDIMaster‑out / IMU SDI
SPI (SPIM4)SPIM4_MISOP0.10/MISOSDOMaster‑in / IMU SDO
SPI (SPIM4)SPIM4_CSNP0.11/CSNCSBChip select, active low
GPIOD6P1.07INT1Interrupt to NORA GPIO
NCNCINT2/FSYNC/CLKINOptional secondary INT/FSYNC (unconnected)

What’s explicit vs. to‑confirm: The SPIM4_* nets are explicit on the sheet and should route to the IMU serial pins. Interrupt lines are present on the symbol but aren’t labeled to a specific net name at the MCU in the text export I parsed—please tag to the intended GPIOs during DTS authoring.


3) Barometric pressure — BMP390

BusPCB netB106 portBMP390 pin/functionNotes
I²CSCLP1.02/TWISCLI²C clock
I²CSDAP1.03/TWISDAI²C data
GPIOD11P1.11INT

4) Magnetometer — MMC5983MA

BusPCB netB106 portMMC5983MA pin/functionNotes
I²CSCLP1.02/TWISCLShared I²C clock
I²CSDAP1.03/TWISDAShared I²C data
GPIOD9P1.09INT

5) GNSS module — u‑blox SAM‑M10Q

Note: V1 board has GNSS UART connections only. V2 board will connect PPS TIMEPULSE to a GPIO line (line to-be-determined).

InterfaceNORA‑B106 logical netSAM‑M10Q functionNotes
UARTNET_NORA_TX → GNSS RXRXDPrimary GNSS serial in
UARTNET_NORA_RX ← GNSS TXTXDPrimary GNSS serial out
UART (alt/app)APP_NORA_TX/RX, APP_NORA_RTS/CTSTX/RX/RTS/CTSA second NORA UART is brought out as “APP_NORA_*”; use if the GNSS is wired to the app port or for auxiliary host/debug depending on stuffing
USB‑UART (console)VCOM1_TX/RXTX/RXLabeled console link to host PC/bridge; useful for test logging

The schematic contains NET_NORA_TX/RX and also APP_NORA_* plus VCOM1_*. Use the pair that terminates on the SAM‑M10Q in your assembled option. For Zephyr, declare the chosen UART instance as gps0 with ubx,m10 (or use NMEA‑compatible driver) and disable the unused one(s).


Zephyr bring‑up checklist (how to use this map)

  1. Pick instances

    • QSPI: enable nRF QSPI controller, bind cs-gpios and io0..io3 to QSPI_*.
    • SPI: enable spi4 (SPIM4) and bind to IMU.
    • I²C: enable the I²C controller feeding SCL/SDA bus; add BMP390 + MMC5983MA as children with proper addresses.
    • UART: choose either NET_NORA_* (GNSS) or APP_NORA_* based on your assembly; reserve VCOM1_* for console.
  2. GPIOs/interrupts

    • Assign IMU INT1 and the magnetometer INT to listed GPIOs
    • Add interrupts = <&gpioX pin IRQ_EDGE_RISING>; in each child node.
  3. Testing hooks

    • Flash: probe with JEDEC ID over QSPI, read SFDP.
    • IMU: WHO_AM_I on SPIM4; read INT on motion.
    • Baro/Mag: ID registers over I²C; poll data‑ready.
    • GNSS: open UART, request UBX‑MON‑VER, check NMEA stream.
    • Console: ensure VCOM1_* maps to the chosen Zephyr console.

Appendix — Signal name index (as found on the sheet)

From the schematic net labels (selection): QSPI_SCK, QSPI_CSN, QSPI_IO0, QSPI_IO1, QSPI_IO2, QSPI_IO3, FLASH_MOSI, FLASH_MISO, FLASH_SCK, SPIM4_SCK, SPIM4_MOSI, SPIM4_MISO, SPIM4_CSN, SCL, SDA, NET_NORA_TX, NET_NORA_RX, APP_NORA_TX, APP_NORA_RX, APP_NORA_RTS, APP_NORA_CTS, VCOM1_TX, VCOM1_RX, SWDIO, SWDCLK, ~RESET, BTN1, BTN2, BTN3, BTN4, D5, D6, D7, D9, D10, D11, D12, D13, P0.31, XL1, XL2, VDDIO, VBACKUP.

D* lines (D5 .. D13) were selected to correspond the the nRF8340 Arduino developement kit board definition.

Parts

69
QtyValueFootprintReferences
310KOHM-0603-1/10W-1%peakick:0603R11, R13, R14
310uFCapacitor_SMD:C_0603_1608MetricC2, C4, C8
32.2KResistor_SMD:R_0603_1608MetricR5, R9, R10
3STAND-OFFTIGHTpeakick:STAND-OFF-TIGHTH1, H2, H3
2100nFCapacitor_SMD:C_0603_1608MetricC1, C3
22.2KOHM-0603-1/10W-1%peakick:0603R3, R4
2220OHM-0402Resistor_SMD:R_0402_1005MetricR7, R8
24.7UF-0603-6.3V-(10%)Capacitor_SMD:C_0603_1608MetricC12, C15
25.1kResistor_SMD:R_0402_1005MetricR1, R2
2LTST-S270KGKTLED_SMD:LED_0603_1608MetricLED1, LED3
2PTS850peakick:PTS850-with-bossesSW2, SW3
2UBXH07-0000034Diode_SMD:D_SOD-923D1, D2
10.1uFCapacitor_SMD:C_0603_1608MetricC5
11.0UF-0603-16V-10%-X7RCapacitor_SMD:C_0603_1608MetricC10
1100nFCapacitor_SMD:C_0402_1005MetricC9
110nFCapacitor_SMD:C_0603_1608MetricC6
11A/23V/620mVpeakick:SOD-323D5
11Kpeakick:0603R15
12.0kpeakick:0603R16
12.2UF-0603-10V-20%Capacitor_SMD:C_0603_1608MetricC11
12.2uFCapacitor_SMD:C_0603_1608MetricC7
12x5 PTH ARM CORTEX DEBUGpeakick:2X5-PTH-1.27MM-NO_SILKJ5
132.768kHzpeakick:CRYSTAL-SMD-3.2X1.5MMY1
14.7UF-0805-10V-10%peakick:0805C13
1470KOHMResistor_SMD:R_0402_1005MetricR12
1499OHM-0402Resistor_SMD:R_0402_1005MetricR6
1500mA, 6VFuse:Fuse_0805_2012MetricF1
1BMP390peakick:LGA10_BMP390_BOSU1
1CR1220peakick:CR1220-2B1
1DMP3125L-7peakick:SOT23-3@1Q1
1FRAME-LETTERpeakick:CREATIVE_COMMONSFRAME1
1ICM-42688-Vpeakick:PQFN50P300X250X97-14NU4
1IMU_INT1TestPoint:TestPoint_THTPad_1.0x1.0mm_Drill0.5mmTP3
1IO InterfacesConnector_PinHeader_1.27mm:PinHeader_1x08_P1.27mm_VerticalJ3
1JS102011SAQNpeakick:JS102011SAQNSW1
1JSTPHpeakick:JSTPH2J1
1LTST-C19HE1WTpeakick:LTST-C19HE1WTRGB1
1LTST-S270KRKTLED_SMD:LED_0603_1608MetricLED2
1MCP73831peakick:SOT23-5U8
1MEM2061-01-188-00-Apeakick:MICROSDX1
1MMC5983MApeakick:MMC5983MA_MEMU3
1MX25R64Package_SON:WSON-8-1EP_6x5mm_P1.27mm_EP3.4x4mmU5
1NET_NORA_RXTestPoint:TestPoint_Pad_1.0x1.0mmTP2
1NET_NORA_TXTestPoint:TestPoint_Pad_1.0x1.0mmTP1
1NORA-B106-00Bpeakick:XCVR_NORA-B106-00BU7
1OSHW-LOGOSpeakick:OSHW-LOGO-SLOGO1
1QWIIC_CONNECTORJS-1MMpeakick:JST04_1MM_RAJ4
1RESETButton_Switch_SMD:SW_Push_1P1T_NO_CK_KMR2SW4
1SAM-M10Qpeakick:MODULE_SAM-M8Q-0-10U2
1SPX3819M5-L-3-3/TRpeakick:SOT23-5U6
1USB_C_Receptacle_USB2.0peakick:GCT-USB4105-GF-A modified-USB-C 16PJ2
1VBATTTestPoint:TestPoint_THTPad_1.0x1.0mm_Drill0.5mmTP4
1Yellowpeakick:LED-0603LED4

Similar boards

  • 2 layers44.5 × 50.8 mmDropkick, the printed circuit board in 3D

    Dropkick

    rrainey/dropkick

    A data logger designed for skydivers

    50 parts7
  • 8 layers90.5 × 49.5 mmOpen race v2, the printed circuit board in 3D

    Open race v2

    teehee567/Aevia

    gnss module collecting track data

    337 parts5
  • 4 layers92.5 × 101.6 mmVCU, the printed circuit board in 3D

    VCU

    formulaslug/fs-4-schematics

    Electrical Design Repository for fs-4 schematics and PCBs

    225 parts7
  • 4 layers100 × 70 mmZSWatch Watch DevKit, the printed circuit board in 3D

    ZSWatch Watch DevKit

    ZSWatch/Watch-DevKit-HW

    The hardware repo for the ZSWatch Development Kit.

    132 parts188GPL-3.0
  • 2 layers40.5 × 49.5 mmNora minimal, the printed circuit board in 3D

    Nora minimal

    rain-1/nora-b106

    Minimum assembly is still U1 plus C1 (4.7 µF) and C2 (100 nF), with external regulated 3.3 V and SWD wires. Headers are optional. The module's 82 hidden LGA pads need controlled reflow/hot-plate assembly.

    18 parts
  • 8 layers90.2 × 101.1 mmRevC fm, the printed circuit board in 3D

    RevC fm

    Sierra-Lobo/mainboard-hardware

    PyCubed mainboard v5 fork by Sierra Lobo for Foras Promineo CubeSat

    644 parts1
  • 4 layers80 × 50 mmPCB LoRa+GPS, the printed circuit board in 3D

    PCB LoRa+GPS

    ChrisKlein01/ArrozPCB

    LoRa-based GPS PCB design with KiCad

    84 parts
  • 4 layers32 × 63.8 mmFpga play, the printed circuit board in 3D

    Fpga play

    electronut/fpga.play.pub

    Low cost open source Lattice iCE40UP5k FPGA board.

    74 parts21

Questions

How big is the Tempo bt PCB?

It measures 58.4 × 54 mm and has 4 copper layers, 1.6 mm thick.

What parts does the Tempo bt use?

69 parts, built around the NORA-B106-00B, SAM-M10Q-00B, BMP390 and MMC5983MA. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Tempo bt KiCad files?

From the rrainey/tempo-bt repository on GitHub, at the commit this page was made from: the board is hardware/tempo-bt/tempo-bt.kicad_pcb and its schematic hardware/tempo-bt/tempo-bt.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Tempo bt design in my own project?

Its repository publishes it under the GPL-3.0 licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).