InPlay NanoBeacon™
IN100 Command Tool
Application Notes
Specifications and information are subject to change without notice.
IN100C0 Application Notes
About Documentation
Document Name IN100C0 Application Notes
Part number
Control Number IN1IDOC-HC-IN100-EN-V0_9 External User
Revision V0.9
Product Status Document Content Data Status
In Development Target specification / MRD Initial release
Main functions and features
Engineering Document Preliminary version
description
Description of all functional Subject to revision and
Official Release Document
features updates
This document applies to the following products:
Document number Applicable Products Document Status
IN100-D1-R-RC1I Engineering Document
IN100-Q1-R-RC1I Engineering Document
IN100-D1-R-RC1F Engineering Document
IN100-Q1-R-RC1F Engineering Document
1/9 www.inplay-tech.com
IN100C0 Application Notes
Contents
ABOUT DOCUMENTATION .............................................................................. 1
1. INTRODUCTION...................................................................................... 3
2. COMMANDS ........................................................................................... 5
2.1 burn .......................................................................................................................... 5
2.2 RAM test ................................................................................................................... 6
2.3 DTM test start ........................................................................................................... 7
2.4 DTM test stop ........................................................................................................... 8
2.5 Carrier test start ........................................................................................................ 8
2.6 Carrier test stop ........................................................................................................ 8
3. REVISION HISTORY ................................................................................ 9
4. DISCLAIMER .......................................................................................... 9
2/9 www.inplay-tech.com
IN100C0 Application Notes
1. Introduction
The NanoBeacon IN100 MP Command tool is used to burn and test the IN100 using the command
line mode. The IN100 device supports a host controller interface, as shown in Figure 1, and this
document will describe how to burn the device with a host controller through this interface.
Figure 1: NanoBeacon device in host controller mode
The MP Command Tool is used with NanoBeacon Config Tool to facilitate the user to do the device
programming and test during mass production.
The process is as follows.
1. First debug the prototype with NanoBeaconConfigTool according to the application
requirements. Then save the configuration to a file.
2. Use the config file saved in step 1 as input and start the executable file
beacon_mp_cmd.exe of MP Command Tool via command line to burn it into the device.
3. The operation flow of the MP Command Tool is as follows
3/9 www.inplay-tech.com
IN100C0 Application Notes
load config file
modify bluetooth address
[option]
modify customer product ID
[option]
on-chip ADC's calibration data processing
generate raw data
burn
4/9 www.inplay-tech.com
IN100C0 Application Notes
2. Commands
2.1 burn
Arguments Example Description
-c beacon_mp_cmd.exe -c burn burn eFuse command Mandator
-p beacon_mp_cmd.exe -c burn -p COM4 Which UART port to use Mandator
-i beacon_mp_cmd.exe -c burn -p COM4 -i Which config file to use as Mandator
x.cfg input file. The config file
comes from NanoBeacon
config tool.
-a beacon_mp_cmd.exe -c burn -p COM4 -i Using the argument to Option
x.cfg -a 0605AE030201 update Bluetooth device
address. Six bytes of
hexadecimal data, MSB first.
Addresses of multiple
advertising sets are separated
by semicolons (;).
-d beacon_mp_cmd.exe -c burn -p COM4 -i Using the argument to Option
x.cfg -d 0000000000F1 update customer product ID.
Six bytes of hexadecimal
data, MSB first.
-r beacon_mp_cmd.exe -c burn -p COM4 -r 1 : reset chip after brun; Option
1 -i x.cfg
0 : not reset chip after burn
burn example 1，Configuration from nano_beacon_config.cfg file：
beacon_mp_cmd.exe -c burn -p COM4 -i nano_beacon_config.cfg
burn example 2，modify Bluetooth device address based config file (nano_beacon_config.cfg)：
beacon_mp_cmd.exe -c burn -p COM4 -i nano_beacon_config.cfg -a 0605AE030201
example 3，modify multiple addresses:
beacon_mp_cmd.exe -c burn -p COM4 -i nano_beacon_config.cfg -a 0605AE030201; 0605AE030202
example 4，modify Bluetooth device address and customer product id：
beacon_mp_cmd.exe -c burn -p COM4 -i nano_beacon_config.cfg -a 0605AE030201 -d 0000000000F1
5/9 www.inplay-tech.com
IN100C0 Application Notes
2.2 RAM test
Arguments Example Description
-c beacon_mp_cmd.exe -c ram RAM test command Mandator
-p beacon_mp_cmd.exe -c ram -p COM4 Which UART port to use Mandator
-i beacon_mp_cmd.exe -c ram -p COM4 -i Which config file to use as Mandator
x.cfg input file. The config file
comes from NanoBeacon
config tool.
-a beacon_mp_cmd.exe -c ram -p COM4 -i Using the argument to Option
x.cfg -a 0605AE030201 update Bluetooth device
address. Six bytes of
hexadecimal data, MSB first.
Addresses of multiple
advertising sets are separated
by semicolons (;).
-d beacon_mp_cmd.exe -c ram -p COM4 -i Using the argument to Option
x.cfg -d 0000000000F1 update customer product ID.
Six bytes of hexadecimal
data, MSB first.
RAM test example 1, Configuration from nano_beacon_config.cfg file:
beacon_mp_cmd.exe -c ram -p COM4 -i nano_beacon_config.cfg
RAM Test example 2, modify Bluetooth device address:
beacon_mp_cmd.exe -c ram -p COM4 -i nano_beacon_config.cfg -a 0605AE030201
example 3, modify multiple addresses:
beacon_mp_cmd.exe -c ram -p COM4 -i nano_beacon_config.cfg -a 0605AE030201; 0605AE030202
example 4, modify Bluetooth device address and customer product id:
beacon_mp_cmd.exe -c ram -p COM4 -i nano_beacon_config.cfg -a 0605AE030201 -d 0000000000F1
6/9 www.inplay-tech.com
IN100C0 Application Notes
2.3 DTM test start
Arguments Example Description
-c beacon_mp_cmd.exe -c DTM test start command Mandator
dtm_start
-p beacon_mp_cmd.exe -c Which UART port to use Mandator
dtm_start -p COM4
-x beacon_mp_cmd.exe -c <ch,tx_len,tx_payload,phy,cap,tx_power> Mandator
dtm_start -p COM4 -x
37,25,0,1M,11,3 Parameters to be set for DTM test. There
are six parameters in total, separated by
commas (,).
ch: physical channel 0~39;
tx_len: length for transmitting 0 ~ 255;
tx_payload: index of payload pattern 0~7
0 - prbs 9
1 - 0x0f
2 - 0x55
3 - prbs 15
4 - 0xff
5 - 0x0
6 - 0xf0
7 - 0xaa
phy: ‘1M’ for 1M PHY，’125K’ for
125K coded PHY
cap: on-chip capacitor code 0~15
tx_power: tx power, dBm
7/9 www.inplay-tech.com
IN100C0 Application Notes
2.4 DTM test stop
Arguments Example Description
-c beacon_mp_cmd.exe -c dtm_stop DTM test stop command Mandator
-p beacon_mp_cmd.exe -c dtm_stop - Which UART port to use Mandator
p COM4
2.5 Carrier test start
Arguments Example Description
-c beacon_mp_cmd.exe -c Start carrier test command Mandator
carrier_start
-p beacon_mp_cmd.exe -c Which UART port to use Mandator
carrier_start -p COM4
-x beacon_mp_cmd.exe -c <ch,cap,tx_power> Mandator
carrier_start -p COM4 -x 37,11,3
Parameters to be set for carrier test.
There are three parameters in total,
separated by commas (,).
ch: physical channel 0~39;
cap: on-chip capacitor code 0~15
tx_power: tx power, dBm
2.6 Carrier test stop
Arguments Example Description
-c beacon_mp_cmd.exe -c Stop carrier test Mandator
carrier_stop command
-p beacon_mp_cmd.exe -c Which UART port to Mandator
carrier_stop -p COM4 use
8/9 www.inplay-tech.com
IN100C0 Application Notes
3. Revision History
Revision Description Prepared By Date
Ver 0.9 Preliminary version WZ, Liu 2022-05-12
4. Disclaimer
InPlay has made every attempt to ensure the accuracy and reliability of the information provided on
this document. However, the information is provided “as is” without warranty of any kind. The
content of the document will subject to change without prior notice. InPlay does not accept any
responsibility or liability for the accuracy, content, completeness, legally, or reliability of the
information contained on this document. We shall not be liable for any loss or damage of whatever
nature (direct, indirect, consequential or other) whether arising in contract or otherwise, which may
arise as a result of your use of (or inability to use) this document, or from your use of (or failure to
use) the information on this document. InPlay Inc and its company logo are registered trademarks
of InPlay Inc with its registered office at 1 Technology Drive, STE J728, Irvine, CA, USA 92618.
9/9 www.inplay-tech.com
