Skip to content

User Guide🔗

Introduction🔗

The PAN1783 evaluation board (ENW89860AXKF) features a PAN1783 Bluetooth® Low Energy (LE) module (ENW89860A1KF) which is based on the Nordic Semiconductor nRF5340 single-chip controller.

Introduction

The PAN1783A evaluation board (ENW89860CXKF) features a PAN1783A Bluetooth® Low Energy (LE) module (ENW89860C1KF) which is based on the Nordic Semiconductor nRF5340 single-chip controller. Also the certified antenna GW.34.5153 from Taoglas and a micro coax cable from TE connectivity are included.

Introduction

The PAN1783A-PA evaluation board (ENW89860CYKF) features a PAN1783A Bluetooth® Low Energy (LE) module (ENW89860C1KF) which is based on the Nordic Semiconductor nRF5340 single-chip controller. An additional Skyworks SKY66407-11 power amplifier is mounted on the evaluation board. A PULSE W1030 antenna and a micro coax cable from TE connectivity are included.

Note

The PAN1783A-PA evaluation board is not available as a mass market product.

If you are interested, contact your local Panasonic Sales representative.

You can access all the different module interfaces like USB, UART, NFC, and GPIOs easily, which makes the evaluation board ideally suited for the evaluation of the module and rapid prototyping of products.

Warning

During development, module-specific information, which also includes the Bluetooth Device Address, may get lost. Before you start any development, it is recommended to save module-specific information.

Please refer to Bluetooth Device Address Safeguard.

Features🔗

  • 8 MB external flash memory
  • Arduino interface configurable as shield or board
  • mikroBUS™ interface
  • All GPIOs accessible via pin headers
  • Power measurement interface
  • Segger J-Link on-board debugger
  • Virtual COM port over Segger J-Link on-board debugger
  • Peripherals can be deactivated for low power applications
  • 4x user buttons, 4x user LEDs
  • Module native USB interface
  • FPC connector for NFC antenna (antenna is included)
  • Compatible to nRF Connect SDK projects
  • Skyworks SKY66407-11 power amplifier (PAN1783A-PA EVB only)

Block Diagram🔗

Board Overview🔗

1 Reset Button - RST
You can use the reset button to reset the board to a known-good state.

2 USB connector - X1
You can use the USB connector to power the board and gain access to the UART communication and debugging capabilities. Also see Powering Options

3 User buttons - SW
You can use the user buttons to interact with the running application if the application supports it.

4 Current measurement pin header - P4
You can use the current measurement pin header to measure the current consumption of the currently running application. Also see Powering Options and Current Consumption Measurement

5 Module native USB connector - X5
You can use the module native USB connector to interact with the USB interface of the module. It is directly connected to module's USB pins. Also see Powering Options

6 Power configuration pin header - P7
You can use the power configuration pin headers to choose between 3.3 V and 5 V voltage levels. Also see Module Power Options and Powering Options

7 UART module connection pin header - P1
This pin header allows you to disconnect the connection between the virtual COM port of the Segger J-Link on-board debugger and the module. This can be useful in order to isolate the module for Current Consumption Measurement.

8 Breakout pin headers - P21 and P22
You can use the breakout pin headers to access all the module GPIO pins directly. Also see GPIO Pin Access

9 Arduino pin headers - P9, P10, P11 and P13
You can use Arduino pin headers to attach to Arduino shields or boards. Also see Arduino Interface

10 Power pins on breakout pin header - P22
You can use these power pins on the breakout pin header to power the board. Also see Powering Options

11 Power LED - PWR
You can observe the power LED to verify that the board is correctly powered.

12 mikroBUS™ pin headers
You can use the mikroBUS™ pin header to attach a Click™ board. Also see mikroBUS Interface

13 NFC antenna connector - NFC / P19
You can use the NFC antenna connector to connect an NFC antenna.

14 The module

15 U.FL antenna connector - X4
You can use the U.FL antenna connector to connect an external antenna.

16 Arduino UART direction pin header - P16
You can use the Arduino UART direction pin headers to choose the configuration when running in shield or board mode. Also see Arduino Configuration

17 Segger J-Link LED
You can use the Segger J-Link LED to verify that the Segger J-Link on-board debugger is correctly powered.

18 Peripheral disable pin header - P6
You can use the peripheral disable pin header to control the connection of the Segger J-Link on-board debugger to the power supply. This is useful to disconnect certain peripherals for power consumption measurements. Also see Peripheral Configuration

19 User LEDs pin header - P20
You can use the user LED pin header to control the connection of the LEDs to the module pins.

20 User LEDs
You can use the user LEDs from the application to interact with the user.

21 Power pins on Arduino pin header - P10
You can use these power pins on the Arduino pin header to power the board. Also see Powering Options

22 Power pins on MikroBus pin header
You can use these power pins on the MikroBus pin header to power the board. Also see Powering Options

Initial Preparations🔗

Before you can work with the evaluation tool (again) you may have to check (or restore) the default jumper configuration or install device drivers, depending on the operating system you are using.

Default Jumper Configuration🔗

You can check the default jumper configuration easily because it is imprinted with white (or blue) line markings on the silkscreen of the PCB.

For example, the default jumper configuration in the following picture is:

  • One jumper put on the lower left two pins
  • One jumper put on the lower right two pins

When you install one of the Development Tools from Nordic Semiconductor a driver for the Segger J-Link on-board debugger is automatically installed as well.

First Steps🔗

You can use a USB-C cable to connect the evaluation board to your computer using the USB connector X1 2.

The PAN1783 module is pre-programmed with a test application that is used during the production of the evaluation board.

You can observe the following behavior of the evaluation board after the very first start:

You can also use a USB-C cable to connect the evaluation board to your computer using the module native USB connector X5 5. If you do this you can notice an additional USB-HID keyboard appearing. If you now press the user buttons SW 3 labelled SW1 the message PAN1783 EVB is inserted where the focus of the cursor is currently located.

You can now start to set up a software development environment and then build and run your own application, check out the dedicated Getting Started guide.

Warning

During development, module-specific information, which also includes the Bluetooth Device Address, may get lost.

So before you start right now, it is recommended to save module-specific information first.

Please refer to Bluetooth Device Address Safeguard.

Pin Map🔗

Header Item Function Module Footprint Module Pin
P1 7 UART Rx B9 P0.22
UART Tx E9 P0.20
UART CTS F1 P0.10
UART RTS G8 P0.11
NFC / P19 13 NFC 1 A9 P0.02
NFC 2 A8 P0.03
P20 19 LED 1 A3 P0.28
LED 2 A1 P0.29
LED 3 F9 P0.30
LED 4 F8 P0.31
SW 3 SW 1 E4 P0.23
SW 2 B6 P0.24
SW 3 E2 P0.08
SW 4 F2 P0.09

Powering Options🔗

You can power the evaluation board in different ways:

Risk of damaging board components

Do not supply 5 V on the 3.3 V pin of the power pins on Arduino pin header P10 21, the power pins on MikroBus pin header 22 or the power pins on breakout pin header P22 10.

USB Connector🔗

You can power the whole evaluation board using the USB connector X1 2.

Note

Please note that the module is still powered if the peripherals are deactivated using peripheral disable pin header P6 18.

Module Native USB Connector🔗

You can power the whole evaluation board using the module native USB connector X5 5.

Note

Please note that the module is still powered if the peripherals are deactivated using peripheral disable pin header P6 18.

Current Measurement Pin Header🔗

You can power the module by attaching VCC to the current measurement pin header P4 4.

You have to attach GND to the breakout pin headers P21 and P22 8 accordingly.

Arduino Pin Header🔗

You can power the whole evaluation board using the power pins on Arduino pin header P10 21.

Both the 3.3 V and the 5 V pins can be used.

mikroBUS™ Pin Header🔗

You have the option to power the evaluation board using the power pins on MikroBus pin header 22.

Both the 3.3 V and the 5 V pins can be used.

Breakout Pin Header🔗

You can power the whole evaluation board using the power pins on breakout pin header P22 10.

Both the 3.3 V and the 5 V pins can be used.

Module Power Options🔗

You can power the module by two different supply voltage modes.

  • Normal Voltage Mode using 3.3 V
  • High Voltage Mode using 5 V

The mode setting depends on which voltage levels are connected to VCC and VDDH pins on the power configuration pin header P7 6.

Normal Voltage Mode🔗

You can configure the supply voltage mode to Normal Voltage Mode using the power configuration pin header P7 6 as follows:

  • Connect 3.3 V to VCC pin
  • Connect 3.3 V to VDDH pin

High Voltage Mode🔗

Note

When you use the High Voltage Mode, a current measurement using the current measurement pin header P4 4 is not possible anymore.

You have to use a separate power supply and connect it directly to the VDDH pin of the power configuration pin header P7 6 instead.

You can configure the supply voltage mode to High Voltage Mode using the power configuration pin header P7 6 as follows:

  • Connect 5 V to VDDH pin
  • Leave VCC pin unconnected

For further information please refer to section 5.3.1 Main Supply in chapter 5.3 POWER - Power Supply in the nRF5340 Product Specification.

GPIO Pin Access🔗

You can access every GPIO pin of the module through the breakout pin headers P21 and P22 8.

External flash memory

P0.13, P0.14, P0.15, P0.16, P0.17 and P0.18 are used to interface the external flash memory.

If you don't need the external flash memory and want to make the GPIOs accessible please see Deactivate External Flash Memory

You can check the details of the pin mappings between the evaluation board, the module and the nRF5340 in the following table.

Pin Module Footprint Module / nRF5340 Pin
3.3 V 1
5 V 2
0.00 C2 P0.00
0.01 B2 P0.01
0.02 A9 P0.02
0.03 A8 P0.03
0.04 A5 P0.04
0.05 A4 P0.05
0.06 B3 P0.06
0.07 B4 P0.07
0.08 E2 P0.08
0.09 F2 P0.09
0.10 F1 P0.10
0.11 G8 P0.11
0.12 D3 P0.12
0.13 C6 P0.13
0.14 C7 P0.14
0.15 C8 P0.15
0.16 C9 P0.16
0.17 D8 P0.17
0.18 D7 P0.18
0.19 B7 P0.19
0.20 E9 P0.20
0.21 D2 P0.21
0.22 B9 P0.22
0.23 E4 P0.23
0.24 B6 P0.24
0.25 B5 P0.25
0.26 A7 P0.26
0.27 A6 P0.27
0.28 A3 P0.28
0.29 A1 P0.29
0.30 F9 P0.30
0.31 F8 P0.31
1.00 A2 P1.00
1.01 B1 P1.01
1.02 C1 P1.02
1.03 C3 P1.03
1.04 G1 P1.04
1.05 E10 P1.05
1.06 E5 P1.06
1.07 E6 P1.07
1.08 B8 P1.08
1.09 E7 P1.09
1.10 D6 P1.10
1.11 F7 P1.11
1.12 F6 P1.12
1.13 F5 P1.13
1.14 F4 P1.14
1.15 F3 P1.15
GND

1 The maximum output current using 3.3 V is 500 mA.

2 The maximum output current depends on the USB supply.

Arduino Interface🔗

You can use the Arduino interface on the arduino pin headers P9, P10, P11 and P13 9 to stack the evaluation board with other boards and shields that have an Arduino connector.

You can check the details of the pin mappings between the arduino pin headers P9, P10, P11 and P13 9, the module, and the nRF5340 in the following sections.

Upper Arduino Connector🔗

Arduino Pin Function Module Footprint nRF5340 Pin
SCL I²C Clock C3 P1.03
SDA I²C Data C1 P1.02
AREF Analog Reference Input A6 P0.27
GND Ground
D13 GPIO F3 P1.15
D12 GPIO F4 P1.14
D11 GPIO F5 P1.13
D10 GPIO F6 P1.12
D9 GPIO F7 P1.11
D8 GPIO D6 P1.10
D7 GPIO E7 P1.09
D6 GPIO B8 P1.08
D5 GPIO E6 P1.07
D4 GPIO E5 P1.06
D3 GPIO E10 P1.05
D2 GPIO G1 P1.04
D1 GPIO / UART TX1 B1 P1.01
D0 GPIO / UART RX1 A2 P1.00

1 Depending on setup of Arduino UART direction pin header P16 16 described in section Arduino Configuration.

Lower Arduino Connector🔗

Arduino Pin Function Module Footprint nRF5340 Pin
NC Not connected
IOREF 3.3 V Reference Voltage
NRST Module Reset G7 RESET
3V3 3.3 V Power input/output The maximum output current is 500 mA.
5V 5 V Power input/output The maximum output current depends on the USB supply.
GND Ground
GND Ground
VIN Not connected
A0 Analog Input A5 P0.04
A1 Analog Input A4 P0.05
A2 Analog Input B3 P0.06
A3 Analog Input B4 P0.07
A4 Analog Input B5 P0.25
A5 Analog Input A7 P0.26

Arduino Configuration🔗

You can use the evaluation board either as an Arduino board or as an Arduino shield. The main difference between the two is that the UART communication is changed.

Note

In the default configuration the evaluation board is configured as Arduino board.

You can configure the UART communication by using the Arduino UART direction pin header P16 16 which will flip the Rx and Tx direction of the UART communication.

Board Configuration🔗

You can configure the evaluation board to Arduino board configuration as follows:

  1. Set the Arduino UART direction pin header P16 16 as shown

In this configuration the following interfaces are connected like this:

  • mikroBUS™ UART RX and Arduino UART RX are connected to P1.00

  • mikroBUS™ UART TX and Arduino UART TX are connected to P1.01

Shield Configuration🔗

You can configure the evaluation board to Arduino shield configuration as follows:

  1. Set the Arduino UART direction pin header P16 16 as shown

In this configuration the following interfaces are connected like this:

  • mikroBUS™ UART RX and Arduino UART RX are connected to P1.01

  • mikroBUS™ UART TX and Arduino UART TX are connected to P1.00

mikroBUS™ Interface🔗

The evaluation board allows you to easily stack shields onto it using the mikroBUS™ pin headers 12.

You can check the details of the pin mappings between the mikroBUS™ pin headers 12, the module, and the nRF5340 in the following table.

mikroBUS™ Pin Function Module Footprint nRF5340 Pin
AN Analog IO A5 P0.04
RST Reset E5 P1.06
CS SPI Chip Select F6 P1.12
SCK SPI Clock F3 P1.15
MISO SPI Data In F4 P1.14
MOSI SPI Data Out F5 P1.13
+3.3V 3.3V Power in/out
GND Ground
PWM Pulse Width Modulation E6 P1.07
INT Interrupt G1 P1.04
RX UART RX1 A2 P1.00
TX UART TX1 B1 P1.01
SCL I²C Clock C3 P1.03
SDA I²C Data C1 P1.02
+5V 5V Power in/out
GND Ground

1 The configuration of the RX and TX pins depends on the setting of the Arduino UART direction pin header P16 16 as described in section Arduino Configuration.

Peripheral Configuration🔗

The following peripherals on the evaluation board are always enabled:

  • The module itself
  • Reset button
  • User buttons
  • User LEDs
  • Current measurement interface
  • Module native USB interface
  • Arduino interface
  • Breakout pin interface
  • mikroBUS™ interface

But you can enable or disable some of the peripherals on the evaluation board by using the peripheral disable pin header P6 18.

Enable Peripherals🔗

You can enable the power to all peripherals by setting the jumper on the peripheral disable pin header P6 18 to the ON position.

Disable Peripherals🔗

You can disable the power to some peripherals by setting the jumper on the peripheral disable pin header P6 18 to the OFF position.

The following peripherals are disabled:

  • Segger J-Link on-board debugger

This helps you to save energy when the evaluation board is powered from a battery or power-bank or if you want to do a Current Consumption Measurement.

Current Consumption Measurement🔗

You can measure the current consumption of the module independently of the peripheral components.

Tip

If you do not have any equipment for current consumption measurement, check out the Power Profiler Kit II from Nordic Semiconductor, which can be used both as an ammeter and source meter.

Using an Ammeter🔗

For a current consumption measurement using an ammeter you have to execute the following steps:

  1. Connect the ammeter to current measurement pin header P4 4 as follows:

  2. Put a jumper to the peripheral disable pin header P6 18 to deactivate the peripheral components.

Now you have two choices to power the board.

  1. Power the board regularly using the USB connector X1 2.

  2. Power the board using a variable voltage power supply by feeding directly into GND and 3.3 V on the breakout pin headers P21 and P22 8 to be able to simulate different battery voltage levels.

Using a Source Meter🔗

For a current consumption measurement using a source meter you have to execute the following steps:

  1. Connect the source meter to current measurement pin header P4 4 as follows:

  2. Put a jumper to the peripheral disable pin header P6 18 to deactivate the peripheral components.

  3. Power the board using the USB connector X1 2.

Warning

You have to power the board additionally using the USB connector X1 2.

The jumper put on the peripheral disable pin header P6 18 disconnects certain peripheral components from the module by switching multiple analog switches. But for this to work, the analog switches themselves must be powered using the USB connector X1 2.

Otherwise, signal lines that are connected to the analog switches may float which may result in unexpected behavior and incorrect current consumption measurements in the end.

Deactivate External Flash Memory🔗

By default the external flash memory is connected directly to the module using P0.13, P0.14, P0.15, P0.16, P0.17 and P0.18.

You have the option to deactivate the flash memory and make the GPIOs usable for your application by doing a hardware modification to the evaluation board.

This involves moving 6 resistors and removing 1 resistor by soldering, as shown in the following image:

Software Development🔗

Warning

This module is radio certified. There are conditions on hardware and software which must be met for a valid usage of the certification.

For further information please refer to the module-specific product specification at

Nordic Semiconductor provides the nRF Connect SDK with building tools and sample projects.

The nRF Connect SDK contains the pan1783_evb board definition which you can use when adding a build configuration to a project.

For further information also refer to the Software Documentation from Nordic Semiconductor and check out the Getting Started guide.

Bluetooth Device Address Safeguard🔗

Each module is pre-programmed and comes with a public Bluetooth Device Address and a random Bluetooth Device Address. Both can be easily used in applications, depending on the anticipated use case.

All applications from the nRF Connect SDK automatically use the built in random Bluetooth Device Address, but can easily be modified when the public Bluetooth Device Address shall be used.

Before starting development, it is necessary to read out the module specific information, so that it can be restored whenever needed.

During development, it is sometimes necessary to reset the module to the factory default state (“erase all”). This will also reset all the pre-programmed information in the module.

So special care must be taken that the public Bluetooth Device Address is not accidentally erased and lost, even if the public Bluetooth Device Address is not explicitly used during evaluation of the evaluation board.

Background Information🔗

During production of the module, some module specific information is stored in the user information configuration registers (UICRs) of the module.

UICRs are non-volatile memory (NVM) registers for configuring user specific settings and can be modified by the user.

The module specific information in the UICRs include:

  • Public Bluetooth Device Address
  • Hardware Revision

Panasonic Bluetooth Device Address Ranges

The Bluetooth Device Address of the module always starts with one of this prefix:

  • 34:32:e6 - Panasonic Industrial Devices Europe GmbH

This module specific information is also encoded in the 2D barcode on the metal shield box on the module. The 2D barcode can only be read with a suitable barcode reader.

All module specific information is stored in the registers OTP[0] and OTP[1] of the UICR during production.

The UICRs behave like a single block of flash memory, i.e. they can only be written at once, and they can only be erased as a whole.

Whenever the module is reset to the factory default state (“erase all”), this will also reset the UICRs. Thus all module specific information is deleted that was stored during the production of the module.

Saving Production Information🔗

Warning

Please note that every module has a unique Bluetooth Device Address, so this step must be done for every module individually.

To save all module specific information that is programmed during the production of the module, it is sufficient to read out the UICR registers OTP[0] and OTP[1] .

The following requirement must be met:

  1. Use the nrfjprog tool from a command line prompt to read the first half of the module specific information. 

    nrfjprog.exe --coprocessor CP_APPLICATION --memrd 0x00FF8100

    The output should look something like this: 

    0x00FF8100: E6 AA BB CC  |....|

  2. Use the nrfjprog tool again to read the second half of the module specific information. 

    nrfjprog.exe --coprocessor CP_APPLICATION --memrd 0x00FF8104

    The output should look something like this: 

    0x00FF8104: 01 02 34 32  |....|

These two values are unique and must be stored safely.

Restoring Production Information🔗

Warning

To modify already written portions of the UICR, the complete UICR area must be erased before.

To restore the previously saved module specific information, it is sufficient to write back the stored information into the UICR registers OTP[0] and OTP[1].

The following requirement must be met:

  1. Use the nrfjprog tool from a command line prompt and restore the first half of the module specific information that was previously saved. 

    nrfjprog.exe --coprocessor CP_APPLICATION --verify fast --memwr 0x00FF8100 --val 0xe6aabbcc

    The output should look something like this: 

    Parsing parameters.
Writing.

  2. Use the nrfjprog tool again and restore the second half of the module information that was previously saved. 

    nrfjprog.exe --coprocessor CP_APPLICATION --verify fast --memwr 0x00FF8104 --val 0x01023432

    The output should look something like this: 

    Parsing parameters.
Writing.