Integration Manual
Table Of Contents
- Document information
- Contents
- 1 System description
- 1.1 Overview
- 1.2 Applications
- 1.3 Architecture
- 1.4 Pin assignments
- 1.5 Supply interfaces
- 1.6 System function interfaces
- 1.7 Debug
- 1.8 GPIO pins
- 1.9 Analog interfaces
- 1.10 Serial interfaces
- 1.10.1 Universal Asynchronous Receiver/Transmitter (UART)
- 1.10.2 Serial Peripheral Interface (SPI)
- 1.10.3 Quad Serial Peripheral Interface (QSPI)
- 1.10.4 Inter-Integrated Circuit (I2C) interface
- 1.10.5 Pulse Width Modulation (PWM) interface
- 1.10.6 Inter-IC Sound (I2S) interface
- 1.10.7 Pulse Density Modulation (PDM) interface
- 1.10.8 USB 2.0 device interface
- 1.11 Antenna interface
- 1.12 Reserved pins (RSVD)
- 1.13 GND pins
- 2 Software
- 3 Flashing application software
- 4 Design-in
- 5 Handling and soldering
- 6 Regulatory information and requirements
- 6.1 ETSI – European market
- 6.2 FCC/ISED – US/Canadian markets
- 6.3 MIC - Japanese market (pending)
- 6.4 NCC – Taiwanese market (pending)
- 6.5 KCC – South Korean market (pending)
- 6.6 ANATEL Brazil compliance (pending)
- 6.7 Australia and New Zealand regulatory compliance (pending)
- 6.8 South Africa regulatory compliance (pending)
- 6.9 Integration checklist
- 6.10 Pre-approved antennas list
- 7 Technology standards compliance
- 8 Product testing
- Appendix
- A Glossary
- B Antenna reference designs
- Related documents
- Revision history
- Contact
NORA-B1 series - System integration manual
UBX-20027617 - R04 Software Page 21 of 61
C1-Public
Having a copy of the Bluetooth device address stored in a file is useful when reprogramming each
core after a chip erase or recovery.
The entire UICR memory area can hold other valuable information. Use the following command to
save the entire UCIR memory area:
nrfjprog.e– --readuicr uicr.hex
The Bluetooth device address can only be written to the UICR of each core after a recovery or full
chip erase. See Flashing application software for recovery and erasing details. If an electronic copy
of the address is not saved, the address may be recovered by scanning the 2D data matrix on the
NORA-B1 label. See also the NORA-B1 data sheet [1].
Writing the Bluetooth device address may be done through the following nrfjprog commands
following a chip erase or recovery.
c:\ubx>nrfjprog -f nrf– --memwr 0x00ff81– --val 0xddccbbaa
c:\ubx>nrfjprog -f nrf– --memwr 0x00ff81– --val 0xffffffee
c:\ubx>nrfjprog -f nrf– --coprocessor CP_NETWO– --memrd 0x01ff83– -–val 0xddccbbaa
c:\ubx>nrfjprog -f nrf– --coprocessor CP_NETWO– --memrd 0x01ff83– -–val 0xffffffee
J-Link may also be used. For the application core:
J-Link>loadbin bdaddr.bin, 0x00ff8100
For the network core:
J-Link>loadbin bdaddr.bin, 0x01ff8300
☞ The Bluetooth device address is provided in both cores for convenience. If only one core
accesses the address, the other core does not need to be rewritten.
☞ Example programs provided with NCS do not use the programmed public Bluetooth device
address. A static random address is used which is derived from the FICR registers. An
application must read the public address and set the address with
bt_ctlr_set_public_addr() in Zephyr or sdc_hci_cmd_vs_zephyr_write_bd_addr() in nrfxlib.