You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2018/05/22 16:45:41 UTC
[GitHub] aditihilbert closed pull request #428: Remove bletiny from
documentation
aditihilbert closed pull request #428: Remove bletiny from documentation
URL: https://github.com/apache/mynewt-site/pull/428
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/network/ble/ble_intro.md b/docs/network/ble/ble_intro.md
index 31484a3030..63d35aebf6 100644
--- a/docs/network/ble/ble_intro.md
+++ b/docs/network/ble/ble_intro.md
@@ -59,7 +59,7 @@ Subsequent chapters in this manual will go into the details of the implementatio
Mynewt comes with two built-in projects that allow users to play with NimBLE, try the tutorials out with, and see how to use available services.
-1. **btshell** : A simple shell application which provides a basic interface to the host-side of the BLE stack (replaces **bletiny**).
+1. **btshell** : A simple shell application which provides a basic interface to the host-side of the BLE stack (replaces deprecated **bletiny**).
2. **bleprph**: A basic peripheral device with no user interface. It advertises automatically on startup, and resumes advertising whenever a connection is terminated. It supports a maximum of one connection.
3. **blemesh**: A sample application for Bluetooth Mesh Node using on/off model.
diff --git a/docs/network/ble/bletiny/bletiny_GAP.md b/docs/network/ble/bletiny/bletiny_GAP.md
deleted file mode 100644
index 6c3d63ce5d..0000000000
--- a/docs/network/ble/bletiny/bletiny_GAP.md
+++ /dev/null
@@ -1,209 +0,0 @@
-
-## GAP API for bletiny
-
-<br>
-
-Generic Access Profile (GAP) defines the generic procedures related to discovery of Bluetooth devices (idle mode procedures) and link management aspects of connecting to Bluetooth devices (connecting mode procedures). It also defines procedures related to use of different security levels.
-
-Several different modes and procedures may be performed simultaneously over an LE physical transport. The following modes and procedures are defined for use over an LE physical transport:
-
-1. **Broadcast mode and observation procedure**
- - These allow two devices to communicate in a unidirectional connectionless manner using the advertising events.
-2. **Discovery modes and procedures**
- - All devices shall be in either non-discoverable mode or one of the discoverable modes.
- - A device in the discoverable mode shall be in either the general discoverable mode or the limited discoverable mode.
- - A device in non-discoverable mode will not be discovered by any device that is performing either the general discovery procedure or the limited discovery procedure.
-3. **Connection modes and procedures**
- - allow a device to establish a connection to another device.
- - allow updating of parameters of the connection
- - allow termination of the connection
-4. **Bonding modes and procedures**
- - Bonding allows two connected devices to exchange and store security and identity information to create a trusted relationship.
- - Bonding can occur only between two devices in bondable mode.
-
-
-<br>
-
-
-### Usage API
-
-
-|**Item No.** | **Modes and Procedures** | **nimBLE command** |
-|----|---------|---------------|
-| 1 | Broadcast Mode | `b adv conn=non disc=x` |
-| | Observation Procedure | `b scan dur=x disc=x type=x filt=x` |
-| 2 | Non-Discoverable mode | `b adv conn=x disc=non` |
-| | Limited Discoverable mode | `b adv conn=x disc=ltd` |
-| | General Discoverable mode | `b adv conn=x disc=gen` |
-| | Limited Discovery procedure | `b scan dur=x disc=ltd type=active filt=no_wl` |
-| | General Discovery procedure | `b scan dur=x disc=gen type=active filt=no_wl` |
-| | Name Discovery procedure | `b scan dur=x` <br> `b scan cancel` <br> `b conn peer_addr_type=x peer_addr=x` <br> `b read conn=x uuid=0x2a00` |
-| 3 | Non-connectable mode | `b adv conn=non disc=x` |
-| | Directed connectable mode | `b adv conn=dir [own_addr_type=x] [disc=x] [dur=x]` |
-| | Undirected connectable mode | `b adv conn=und [own_addr_type=x] [disc=x] [dur=x]` |
-| | Auto connection establishment procedure | `b wl addr_type=x addr=x [addr_type=y addr=y] [...]` <br> `b conn addr_type=wl` |
-| | General connection establishment procedure | `b scan dur=x` <br> `b scan cancel` <br> `b conn peer_addr_type=x peer_addr=x` |
-| | Selective connection establishment procedure | `b wl addr_type=x addr=x [addr_type=y addr=y] [...]` <br> `b scan filt=use_wl dur=x` <br> `b scan cancel` <br> `b conn peer_addr_type=x peer_addr=x [own_addr_type=x]` |
-| | Direct connection establishment procedure | `b conn addr_type=x addr=x [params]` |
-| | Connection parameter update procedure | `b update conn=x <params>` |
-| | Terminate connection procedure | `b term conn=x` |
-| 4 | Non-Bondable mode | `b set sm_data bonding=0` [\*] |
-| | Bondable mode | `b set sm_data bonding=1` [\*] |
-| | Bonding procedure | `b sec start conn=x` [\*] |
-
-**[\*]** Security is disabled by default in bletiny. To use the bonding modes and procedures, add `BLE_SM_LEGACY: 1` or `BLE_SM_SC: 1` to your syscfg.yml file depending on your needs.
-
-<br>
-
-### Address Types
-
-| *bletiny string* | *Description* | *Notes* |
-|------------------|---------------|
-| public | Public address. | |
-| random | Random static address. | |
-| rpa_pub | Resolvable private address, public identity. | Not available for all commands. |
-| rpa_rnd | Resolvable private address, random static identity. | Not available for all commands. |
-| wl | Use white list; ignore peer_addr parameter. | Only availble for "conn" command. |
-
-### Connection Types
-
-Bluetooth Specification Version 5.0 allows for different types of connections:
-
-| *Description* | *bletiny ext parameter value* |
-|------------------------------------------------|-------------------------------|
-| Legacy connection | none |
-| Extended connection with 1M PHY | 1M |
-| Extended connection with coded PHY | coded |
-| Extended connection with both 1M and coded PHY | both |
-| Extended connection with 1M, 2M and coded PHYs | all |
-
-### Connection Parameters
-
-Connection parameter definitions can be found in Section 7.8.12 of the BLUETOOTH SPECIFICATION Version 5.0 [Vol 2, Part E].
-
-Connection parameters for all types of connections:
-
-| *Name* | *Description* | *bletiny string* |
-|-------------------|-------------------------------------------------------------------------------------|------------------|
-| Connection Type | Parameter indicating the type of connection | ext |
-| Peer_Address_Type | Whether the peer is using a public or random address (see Address types table). | peer_addr_type |
-| Peer_Address | The 6-byte device address of the peer; ignored if white list is used | peer_addr |
-| Own_Address_Type | The type of address to use when initiating the connection (see Address types table) | own_addr_type |
-| Duration | Number of milliseconds before aborting the connect attempt | dur |
-
-Connection parameters for legacy and 1M PHY extended connection:
-
-| *Name* | *Description* | *bletiny string* |
-|---------------------|---------------------------------------------------------------------------------------------------------|------------------|
-| LE_Scan_Interval | Recommendation from the Host on how long the Controller should scan | scan_itvl |
-| LE_Scan_Window | Recommendation from the Host on how frequently the Controller should scan | scan_window |
-| Conn_Interval_Min | Defines minimum allowed connection interval | itvl_min |
-| Conn_Interval_Max | Defines maximum allowed connection interval | itvl_max |
-| Conn_Latency | Defines the maximum allowed connection latency | latency |
-| Supervision_Timeout | Link supervision timeout for the connection. | timeout |
-| Minimum_CE_Length | Informative parameter providing the Controller with the expected minimum length of the connection event | min_ce_len |
-| Maximum_CE_Length | Informative parameter providing the Controller with the expected maximum length of the connection event | max_ce_len |
-
-Extended Connection parameters for coded PHY connection:
-
-| *Name* | *Description* | *bletiny string* |
-|---------------------|---------------------------------------------------------------------------------------------------------|-------------------|
-| LE_Scan_Interval | Recommendation from the Host on how long the Controller should scan | coded_scan_itvl |
-| LE_Scan_Window | Recommendation from the Host on how frequently the Controller should scan | coded_scan_window |
-| Conn_Interval_Min | Defines minimum allowed connection interval | coded_itvl_min |
-| Conn_Interval_Max | Defines maximum allowed connection interval | coded_itvl_max |
-| Conn_Latency | Defines the maximum allowed connection latency | coded_latency |
-| Supervision_Timeout | Link supervision timeout for the connection. | coded_timeout |
-| Minimum_CE_Length | Informative parameter providing the Controller with the expected minimum length of the connection event | coded_min_ce_len |
-| Maximum_CE_Length | Informative parameter providing the Controller with the expected maximum length of the connection event | coded_max_ce_len |
-
-Extended Connection parameters for 2M PHY connection:
-
-| *Name* | *Description* | *bletiny string* |
-|---------------------|---------------------------------------------------------------------------------------------------------|------------------|
-| Conn_Interval_Min | Defines minimum allowed connection interval | 2M_itvl_min |
-| Conn_Interval_Max | Defines maximum allowed connection interval | 2M_itvl_max |
-| Conn_Latency | Defines the maximum allowed connection latency | 2M_latency |
-| Supervision_Timeout | Link supervision timeout for the connection. | 2M_timeout |
-| Minimum_CE_Length | Informative parameter providing the Controller with the expected minimum length of the connection event | 2M_min_ce_len |
-| Maximum_CE_Length | Informative parameter providing the Controller with the expected maximum length of the connection event | 2M_max_ce_len |
-
-### Scan Types
-
-Bluetooth Specification Version 5.0 allows for different types of scan:
-
-| *Description* | *bletiny ext parameter value* |
-|------------------------------------------|-------------------------------|
-| Legacy scan | 0 |
-| Extended scan with 1M PHY | 1M |
-| Extended scan with coded PHY | coded |
-| Extended scan with both 1M and coded PHY | both |
-
-### Scan Parameters
-
-Scan parameter definitions can be found in Section 7.8.10 of the BLUETOOTH SPECIFICATION Version 5.0 [Vol 2, Part E].
-
-| *Name* | *Description* | *bletiny string* |
-|------------------------|---------------------------------------------------------------------------|------------------|
-| Scan Type | Parameter indicating the type of scan | ext |
-| LE_Scan_Type | Controls the type of scan to perform (passive or active) | passive |
-| LE_Scan_Interval | Recommendation from the Host on how long the Controller should scan | itvl |
-| LE_Scan_Window | Recommendation from the Host on how frequently the Controller should scan | window |
-| Scanning_Filter_Policy | Policy about which advertising packets to accept | filter |
-| Duration | Number of milliseconds before canceling scan procedure | dur |
-| Limited | Limited scan procedure | ltd |
-| No duplicates | Filter out duplicates in shell output | nodups |
-| Own_Address_Type | The type of address to use when scanning (see Address types table) | own_addr_type |
-
-Extended Scan parameters:
-
-| *Name* | *Description* | *bletiny string* |
-|------------------|---------------------------------------------------------------------------|------------------|
-| Duration | Number of milliseconds before canceling scan procedure | duration |
-| Period | Period in which scan should be enabled for specified duration | period |
-| LE_Scan_Type | Controls the type of scan to perform (passive or active) | lr_passive |
-| LE_Scan_Interval | Recommendation from the Host on how long the Controller should scan | lr_itvl |
-| LE_Scan_Window | Recommendation from the Host on how frequently the Controller should scan | lr_window |
-
-### Advertisment Parameters
-
-| *bletiny string* | *Description* | *Notes* | *Default* |
-|------------------|---------------------------------------|--------------------------------------------------------------|---------------------------|
-| conn | Connectable mode | See Connectable Modes table. | und |
-| disc | Discoverable mode | See Discoverable Modes table. | gen |
-| own_addr_type | The type of address to advertise with | See Address Types table. | public |
-| peer_addr_type | The peer's address type | Only used for directed advertising; see Address Types table. | public |
-| peer_addr | The peer's address | Only used for directed advertising | N/A |
-| chan_map | | | 0 |
-| filt | The filter policy | See Advertisement Filter Policies table. | none |
-| itvl_min | | units=0.625ms | non: 100ms; und/dir: 30ms |
-| itvl_max | | units=0.625ms | non: 150ms; und/dir: 60ms |
-| hd | Whether to use high-duty-cycle | 0/1 | 0 |
-| dur | | Milliseconds | Forever |
-
-Extended Advertising parameters:
-
-| *bletiny string* | *Description* | *Notes* | *Default* |
-|------------------|-------------------------------------------------------------------------------------------|----------------|------------------------------|
-| tx_power | Maximum power level at which the advertising packets are to be transmitted | -127 - 127 dBm | 127 (Host has no preference) |
-| primary_phy | PHY on which the advertising packets are transmitted on the primary advertising channel | | none |
-| secondary_phy | PHY on which the advertising packets are transmitted on the secondary advertising channel | | primary_phy |
-
-
-### Advertising PHY Types
-
-| *Description* | *bletiny parameter value* |
-|-------------------------------------|---------------------------|
-| Legacy advertising | none |
-| Extended advertising with 1M PHY | 1M |
-| Extended advertising with 2M PHY | 2M |
-| Extended advertising with coded PHY | coded |
-
-### Advertisement Filter Policies
-
-| *btshell string* | *Description* | *Notes* |
-| ----------------- | --------------- | --------- |
-| none | No filtering. No whitelist used. | Default |
-| scan | Process all connection requests but only scans from white list. | |
-| conn | Process all scan request but only connection requests from white list. | |
-| both | Ignore all scan and connection requests unless in white list. | |
diff --git a/docs/network/ble/bletiny/bletiny_GATT.md b/docs/network/ble/bletiny/bletiny_GATT.md
deleted file mode 100644
index 9242cbc0ac..0000000000
--- a/docs/network/ble/bletiny/bletiny_GATT.md
+++ /dev/null
@@ -1,53 +0,0 @@
-## GATT feature API for bletiny
-
-<br>
-
-GATT(GENERIC ATTRIBUTE PROFILE) describes a service framework using the Attribute Protocol for discovering services, and for reading and writing characteristic values on a peer device. There are 11 features defined in the GATT Profile, and each of the features is mapped to procedures and sub-procedures:
-
-|**Item No.** | **Feature** | **Sub-Procedure** | **nimBLE command** |
-|----|---------|---------------|------|
-| 1 | Server Configuration | Exchange MTU | `b mtu` |
-| 2 | Primary Service Discovery | Discover All Primary Services | `b disc svc conn=x` |
-| | | Discover Primary Services By Service UUID | `b disc svc conn=x uuid=x` |
-| 3 | Relationship Discovery | Find Included Services | `b find inc_svcs conn=x start=x end=x` |
-| 4 | Characteristic Discovery | Discover All Characteristic of a Service | `b disc chr conn=x start=x end=x` |
-| | | Discover Characteristic by UUID | `b disc chr conn=x start=x end=x uuid=x` |
-| 5 | Characteristic Descriptor Discovery | Discover All Characteristic Descriptors | `b disc dsc conn=x start=x end=x` |
-| 6 | Reading a Characteristic Value | Read Characteristic Value | `b read conn=x attr=x` |
-| | | Read Using Characteristic UUID | `b read conn=x start=x end=x uuid=x` |
-| | | Read Long Characteristic Values | `b read conn=x attr=x long=1` |
-| | | Read Multiple Characteristic Values | `b read conn=x attr=x attr=y attr=z` |
-| 7 | Writing a Characteristic Value | Write Without Response | `b write conn=x value=0xXX:0xXX no_rsp=1` |
-| | | Signed Write Without Response | NOT SUPPORTED |
-| | | Write Characteristic Value | `b write conn=x attr=x value=0xXX:0xXX` |
-| | | Write Long Characteristic Values | `b write conn=x attr=x value=0xXX:0xXX long=1` |
-| | | Characteristic Value Reliable Writes | `b write conn=x attr=x value=0xXX:0xXX attr=y value=0xYY:0xYY` |
-| 8 | Notification of a Characteristic Value | Notifications | Write CLIENT CONFIGURATION characteristic |
-| 9 | Indication of a Characteristic Value | Indications | Write CLIENT CONFIGURATION characteristic |
-| 10| Reading a Characteristic Descriptor | Read Characteristic Descriptors | `b read conn=x attr=x` |
-| | | Read Long Characteristic Descriptors | `b read conn=x attr=x long=1` |
-| 11 | Writing a Characteristic Descriptor | Write Characteristic Descriptors | `b write conn=x value=0xXX:0xXX` |
-| | | Write Long Characteristic Descriptors | `b write conn=x value=0xXX:0xXX long=1` |
-
-
-<br>
-### Using nimBLE commands
-Assuming you have discovered and established a BLE connection with at least one peer device (as explained earlier in [API for bletiny app](bletiny_api.md), you can find out what characteristics and services are available over these connections. Here is a recap.
-
-```
-b show conn
-```
-To show discovered services
-```
-b show svc
-```
-
-To show discovered characteristics
-```
-b show chr
-```
-
-To show connection RSSI
-```
-b show rssi conn=x
-```
\ No newline at end of file
diff --git a/docs/network/ble/bletiny/bletiny_advdata.md b/docs/network/ble/bletiny/bletiny_advdata.md
deleted file mode 100644
index 215232e8e7..0000000000
--- a/docs/network/ble/bletiny/bletiny_advdata.md
+++ /dev/null
@@ -1,26 +0,0 @@
-
-## Advertisement Data Fields
-
-<br>
-
-This part defines the advertisement data fields used in the `bletiny` app. For a complete list of all data types and formats used for Extended Inquiry Response (EIR), Advertising Data (AD), and OOB data blocks, refer to the Supplement to the Bluetooth Core Specification, CSSv6, available for download [here](https://www.bluetooth.org/DocMan/handlers/DownloadDoc.ashx?doc_id=302735&_ga=1.133090766.1368218946.1444779486).
-
-
<br>
-
|**Name** | **Definition** | **Details** |
|----|---------|---------------|
-| uuids16 |16-bit Bluetooth Service UUIDs | Indicates the Service UUID list is incomplete i.e. more 16-bit Service UUIDs available. 16 bit UUIDs shall only be used if they are assigned by the Bluetooth SIG. |
| uuids16_is_complete | 16-bit Bluetooth Service UUIDs | Indicates the Service UUID list is complete. 16 bit UUIDs shall only be used if they are assigned by the Bluetooth SIG. |
-| uuids32 | 32-bit Bluetooth Service UUIDs | Indicates the Service UUID list is incomplete i.e. more 32-bit Service UUIDs available. 32 bit UUIDs shall only be used if they are assigned by the Bluetooth SIG. |
| uuids32_is_complete | 32-bit Bluetooth Service UUIDs | Indicates the Service UUID list is complete. 32 bit UUIDs shall only be used if they are assigned by the Bluetooth SIG. |
-| uuids128 | Global 128-bit Service UUIDs | More 128-bit Service UUIDs available. |
| uuids128_is_complete | Global 128-bit Service UUIDs | Complete list of 128-bit Service UUIDs |
-| tx_pwr_lvl | TX Power Level | Indicates the transmitted power level of the packet containing the data type. The TX Power Level data type may be used to calculate path loss on a received packet using the following equation: <br> <br> pathloss = Tx Power Level – RSSI <br> <br> where “RSSI” is the received signal strength, in dBm, of the packet received. |
-| device_class | Class of device | Size: 3 octets |
-| slave_itvl_range | Slave Connection Interval Range | Contains the Peripheral’s preferred connection interval range, for all logical connections. Size: 4 Octets . The first 2 octets defines the minimum value for the connection interval in the following manner: <br> <br> connIntervalmin = Conn_Interval_Min * 1.25 ms <br> <br> Conn_Interval_Min range: 0x0006 to 0x0C80 <br> Value of 0xFFFF indicates no specific minimum. <br> <br> The other 2 octets defines the maximum value for the connection interval in the following manner: <br> <br> connIntervalmax = Conn_Interval_Max * 1.25 ms <br> Conn_Interval_Max range: 0x0006 to 0x0C80 <br> Conn_Interval_Max shall be equal to or greater than the Conn_Interval_Min. <br> Value of 0xFFFF indicates no specific maximum.|
-| svc_data_uuid16 | Service Data - 16 bit UUID | Size: 2 or more octets <br> The first 2 octets contain the 16 bit Service UUID followed by additional service data |
-| public_tgt_addr | Public Target Address | Defines the address of one or more intended recipients of an advertisement when one or more devices were bonded using a public address. This data type shall exist only once. It may be sent in either the Advertising or Scan Response data, but not both. |
-| appearance | Appearance | Defines the external appearance of the device. The Appearance data type shall exist only once. It may be sent in either the Advertising or Scan Response data, but not both. |
-| adv_itvl | Advertising Interval | Contains the advInterval value as defined in the Core specification, Volume 6, Part B, Section 4.4.2.2. |
-| le_addr | LE Bluetooth Device Address | Defines the device address of the local device and the address type on the LE transport. |
-| le_role | LE Role | Defines the LE role capabilities of the device. <br> 0x00 Only Peripheral Role supported <br> 0x01 Only Central Role supported <br> 0x02 Peripheral and Central Role supported, Peripheral Role preferred for connection establishment <br> 0x03 Peripheral and Central Role supported, Central Role preferred for connection establishment <br> 0x04 – 0xFF Reserved for future use |
-| svc_data_uuid32 | Service Data - 32 bit UUID | Size: 4 or more octets <br> The first 4 octets contain the 32 bit Service UUID followed by additional service data |
-| svc_data_uuid128 | Service Data - 128 bit UUID | Size: 16 or more octets <br> The first 16 octets contain the 128 bit Service UUID followed by additional service data |
-| uri | Uniform Resource Identifier (URI) | Scheme name string and URI as a UTF-8 string |
-| mfg_data | Manufacturer Specific data | Size: 2 or more octets <br> The first 2 octets contain the Company Identifier Code followed by additional manufacturer specific data |
<br>
-
\ No newline at end of file
diff --git a/docs/network/ble/bletiny/bletiny_api.md b/docs/network/ble/bletiny/bletiny_api.md
deleted file mode 100644
index 59cb5967f5..0000000000
--- a/docs/network/ble/bletiny/bletiny_api.md
+++ /dev/null
@@ -1,124 +0,0 @@
-## API for bletiny app
-
-`NOTE bletiny is deprecated and will be removed in next version of Apache Mynewt. Please use btshell application instead.`
-
-"bletiny" is one of the sample applications that come with Mynewt. It is a shell application which provides a basic interface to the host-side of the BLE stack. "bletiny" includes all the possible roles (Central/Peripheral) and they may be run simultaneously. You can run bletiny on a board and issue commands that make it behave as a central or a peripheral with different peers.
-
-"bletiny" is a BLE application which uses the 1.0 shell. If you want to use the 1.1 shell in BLE application please go to [btshell app](../btshell/btshell_api.md).
-
-Highlighted below are some of the ways you can use the API to establish connections and discover services and characteristics from peer devices. For descriptions of the full API, go to the next sections on [GAP in bletiny](bletiny_GAP.md) and [GATT in bletiny](bletiny_GATT.md).
-
-All bletiny commands are prefixed with `b`. This prefix distinguished bletiny commands from other shell commands that are implemented by other Mynewt packages.
-
-<br>
-
-### Set device address.
-
-On startup, bletiny has the following identity address configuration:
-
-* Public address: None
-* Random address: None
-
-The below `set` commands can be used to change the address configuration:
-
-```
-b set addr_type=public addr=<device-address>
-b set addr_type=random addr=<device-address>
-```
-
-For example:
-
-```
-b set addr_type=public addr=01:02:03:04:05:06
-b set addr_type=random addr=c1:aa:bb:cc:dd:ee
-```
-
-The address configuration can be viewed with the `b show addr` command, as follows:
-
-```
-b show addr
-public_id_addr=01:02:03:04:05:06 random_id_addr=c1:aa:bb:cc:dd:ee
-```
-
-<br>
-
-### Initiate a direct connection to a device
-
-In this case, your board is acting as a central and initiating a connection with another BLE device. The example assumes you know the address of the peer, either by scanning for available peers or because you have set up the peer yourself.
-
-```hl_lines="1"
-b conn own_addr_type=public peer_addr_type=public peer_addr=d4:f5:13:53:d2:43
-connection established; handle=1 our_ota_addr_type=0 our_ota_addr=0a:0b:0c:0d:0e:0f out_id_addr_type=0 our_id_addr=0a:0b:0c:0d:0e:0f peer_addr_type=0 peer_addr=43:d2:53:13:f5:d4 conn_itvl=40 conn_latency=0 supervision_timeout=256 encrypted=0 authenticated=0 bonded=0
-```
-
-The `handle=1` in the output indicates that it is connection-1.
-
-<br>
-
-### Configure advertisements to include device name
-
-In this case, your board is acting as a peripheral.
-
-```
-b set adv_data name=<your-device-name>
-```
-
-<br>
-
-### Begin sending undirected general advertisements
-
-In this case, your board is acting as a peripheral.
-
-```
-b adv conn=und disc=gen
-```
-
-<br>
-
-### Show established connections.
-
-```
-b show conn
-```
-
-<br>
-
-### Discover and display peer's services, characteristics, and descriptors.
-
-This is how you discover and then display the services of the peer you established earlier across connection-1.
-
-```hl_lines="1 2"
-b disc full conn=1
-b show chr
-[ts=132425ssb, mod=64 level=2] CONNECTION: handle=1 addr=d4:f5:13:53:d2:43
-[ts=132428ssb, mod=64 level=2] start=1 end=5 uuid=0x1800
-[ts=132433ssb, mod=64 level=2] start=6 end=16 uuid=0x1808
-[ts=132437ssb, mod=64 level=2] start=17 end=31 uuid=0x180a
-[ts=132441ssb, mod=64 level=2] start=32 end=65535 uuid=00000000-0000-1000-1000000000000000
-```
-
-<br>
-
-### Read an attribute belonging to the peer
-
-```
-b read conn=1 attr=21
-```
-
-<br>
-
-### Write to an attribute belonging to the peer
-
-```
-b write conn=1 attr=3 value=0x01:0x02:0x03
-```
-
-<br>
-
-### Perform a passive scan
-
-This is how you tell your board to listen to all advertisements around it. The duration is specified in ms.
-
-```
-b scan dur=1000 type=passive filt=no_wl
-```
diff --git a/docs/newt/command_list/newt_create_image.md b/docs/newt/command_list/newt_create_image.md
index 0ed9e35c92..d929a9a697 100644
--- a/docs/newt/command_list/newt_create_image.md
+++ b/docs/newt/command_list/newt_create_image.md
@@ -28,5 +28,5 @@ To sign an image, provide a .pem file for the `signing-key` and an optional `ke
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
- | newt create-image myble2 1.0.1.0 | Creates an image for target `myble2` and assigns it version `1.0.1.0`. <br> <br> For the following target definition: <br> targets/myble2 <br> app=@apache-mynewt-core/apps/bletiny <br> bsp=@apache-mynewt-core/hw/bsp/nrf52dk <br> build_profile=optimized <br> syscfg=STATS_NAMES=1 <br><br> the 'bin/targets/myble2/app/apps/bletiny/bletiny.img' and 'bin/targets/myble2/app/apps/bletiny/bletiny.hex' files are created, and the manifest in 'bin/targets/myble2/app/apps/bletiny/manifest.json' is updated with the image information.
+ | newt create-image myble2 1.0.1.0 | Creates an image for target `myble2` and assigns it version `1.0.1.0`. <br> <br> For the following target definition: <br> targets/myble2 <br> app=@apache-mynewt-core/apps/btshell <br> bsp=@apache-mynewt-core/hw/bsp/nrf52dk <br> build_profile=optimized <br> syscfg=STATS_NAMES=1 <br><br> the 'bin/targets/myble2/app/apps/btshell/btshell.img' and 'bin/targets/myble2/app/apps/btshell/btshell.hex' files are created, and the manifest in 'bin/targets/myble2/app/apps/btshell/manifest.json' is updated with the image information.
| newt create-image myble2 1.0.1.0 private.pem | Creates an image for target `myble2` and assigns it the version `1.0.1.0`. Signs the image using private key specified by the private.pem file.
diff --git a/docs/newt/command_list/newt_debug.md b/docs/newt/command_list/newt_debug.md
index d68fd7f5a6..d493752bad 100644
--- a/docs/newt/command_list/newt_debug.md
+++ b/docs/newt/command_list/newt_debug.md
@@ -32,5 +32,5 @@ Opens a debugger session to the image built for the <target-name> target.
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
- | newt debug myble2 | Opens a J-Link connection and starts a GNU gdb session to debug bin/targets/myble2/app/apps/bletiny/bletiny.elf when the target is as follows: <br> <br> targets/myble2 <br> app=@apache-mynewt-core/apps/bletiny <br> bsp=@apache-mynewt-core/hw/bsp/nrf52dk <br> build_profile=optimized <br> syscfg=STATS_NAMES=1
- | newt debug myble2 -n | Opens a J-Link connection bin/targets/myble2/app/apps/bletiny/bletiny.elf but do not start GDB on the command line.
+ | newt debug myble2 | Opens a J-Link connection and starts a GNU gdb session to debug bin/targets/myble2/app/apps/btshell/btshell.elf when the target is as follows: <br> <br> targets/myble2 <br> app=@apache-mynewt-core/apps/btshell <br> bsp=@apache-mynewt-core/hw/bsp/nrf52dk <br> build_profile=optimized <br> syscfg=STATS_NAMES=1
+ | newt debug myble2 -n | Opens a J-Link connection bin/targets/myble2/app/apps/btshell/btshell.elf but do not start GDB on the command line.
diff --git a/docs/newt/command_list/newt_pkg.md b/docs/newt/command_list/newt_pkg.md
index 97264eb68f..0c89f1b35b 100644
--- a/docs/newt/command_list/newt_pkg.md
+++ b/docs/newt/command_list/newt_pkg.md
@@ -36,7 +36,7 @@ remove | The remove <my-pkg> command deletes the `my-pkg` package.
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
-copy | newt pkg copy <br>apps/bletiny apps/new_bletiny | Copies the `apps/bletiny` package to the `apps/new_bletiny`.
+copy | newt pkg copy <br>apps/btshell apps/new_btshell | Copies the `apps/btshell` package to the `apps/new_btshell`.
move | newt pkg move <br>apps/slinky apps/new_slinky | Moves the `apps/slinky` package to the `apps/new_slinky` package.
new | newt pkg new apps/new_slinky | Creates a package named `apps/new_slinky` of type `pkg` in the current directory.
new | newt pkg new hw/bsp/myboard -t bsp| Creates a package named `hw/bsp/myboard` of type `bsp` in the current directory.
diff --git a/docs/newt/command_list/newt_resign_image.md b/docs/newt/command_list/newt_resign_image.md
index d35dc1241d..b28c5cd2ac 100644
--- a/docs/newt/command_list/newt_resign_image.md
+++ b/docs/newt/command_list/newt_resign_image.md
@@ -30,5 +30,5 @@ Warning: The image hash will change if you change the key-id or the type of key
Sub-command | Usage | Explanation
-------------| -----------------------|-----------------
- | newt resign-image bin/targets/myble/app/apps/bletiny/bletiny.img private.pem | Signs the `bin/targets/myble/app/apps/bletiny/bletiny.img` file with the private.pem key.
- | newt resign-image bin/targets/myble/app/apps/bletiny/bletiny.img | Strips the current signature from `bin/targets/myble/app/apps/bletiny/bletiny.img` file.|
+ | newt resign-image bin/targets/myble/app/apps/btshell/btshell.img private.pem | Signs the `bin/targets/myble/app/apps/btshell/btshell.img` file with the private.pem key.
+ | newt resign-image bin/targets/myble/app/apps/btshell/btshell.img | Strips the current signature from `bin/targets/myble/app/apps/btshell/btshell.img` file.|
diff --git a/docs/newt/command_list/newt_target.md b/docs/newt/command_list/newt_target.md
index d1b8e136d3..680617e08c 100644
--- a/docs/newt/command_list/newt_target.md
+++ b/docs/newt/command_list/newt_target.md
@@ -54,12 +54,12 @@ amend | newt target amend myble syscfg=CONFIG_NEWTMGR=0 cflags="-DTEST"|
amend | newt target amend myble -d syscfg=LOG_LEVEL:CONFIG_NEWTMGR cflags="-DTEST"|Deletes the `LOG_LEVEL` and `CONFIG_NEWTMGR` settings from the `syscfg.yml` file and the -DTEST flag from `pkg.cflags` for the `myble` target. Other syscfg setting values and cflags values are not changed.
config show | newt target config show rb_blinky | Shows the system configuration settings for all the packages that the `rb_blinky` target includes.
config init | newt target config init my_blinky | Creates and populates the `my_blinky` target's `syscfg.yml` file with the system configuration setting values from all the packages that the `my_blinky` target includes.
-copy | newt target copy <br>rb_blinky rb_bletiny | Creates the `rb_bletiny` target by cloning the `rb_blinky` target.
+copy | newt target copy <br>rb_blinky rb_btshell | Creates the `rb_btshell` target by cloning the `rb_blinky` target.
create | newt target create <br>my_new_target | Creates the `my_newt_target` target. It creates the `targets/my_new_target` directory and creates the skeleton `pkg.yml` and `target.yml` files in the directory.
-delete | newt target delete rb_bletiny | Deletes the `rb_bletiny` target. It deletes the `targets/rb_bletiny` directory.
+delete | newt target delete rb_btshell | Deletes the `rb_btshell` target. It deletes the `targets/rb_btshell` directory.
dep | newt target dep myble | Displays the dependency tree of all the package dependencies for the `myble` target. It lists each package followed by a list of packages it depends on.
revdep | newt target revdep myble | Displays the reverse dependency tree of all the package dependencies for the `myble` target. It lists each package followed by a list of packages that depend on it.
-set | newt target set myble <br>app=@apache-mynewt-core/apps/bletiny | Use `bletiny` as the application to build for the `myble` target.
+set | newt target set myble <br>app=@apache-mynewt-core/apps/btshell | Use `btshell` as the application to build for the `myble` target.
set | newt target set myble <br>cflags="-DNDEBUG -Werror" | Set `pkg.cflags` variable with `-DNDEBUG -Werror` in the `myble` target's `pkg.yml` file..
set | newt target set myble syscfg=LOG_NEWTMGR=0:CONFIG_NEWTMGR | Sets the `syscfg.vals` variable in the `myble` target's `syscfg.yml` file with the setting values: LOG_NEWTMGR: 0 and CONFIG_NEWTMGR: 1. CONFIG_NEWTMGR is set to 1 because a value is not specified.
set | newt target set myble cflags= | Unsets the `pkg.cflags` variable in the `myble` target's `pkg.yml` file.
diff --git a/docs/newt/newt_operation.md b/docs/newt/newt_operation.md
index fec01e60c5..c45c8296a1 100644
--- a/docs/newt/newt_operation.md
+++ b/docs/newt/newt_operation.md
@@ -41,10 +41,13 @@ When newt sees a directory tree that contains a "project.yml" file it knows that
```
@~/dev/myproj$ ls repos/apache-mynewt-core/apps/
-blecent blesplit boot sensors_test splitty
-blehci bletest fat2native slinky test
-bleprph bletiny ffs2native slinky_oic testbench
-bleprph_oic bleuart ocf_sample spitest timtest
+blecent bleprph bsnprph ocf_sample testbench
+blecsc bleprph_oic btshell pwm_test timtest
+blehci blesplit ffs2native sensors_test trng_test
+blehr bletest iptest slinky
+blemesh bleuart lora_app_shell slinky_oic
+blemesh_light boot loraping spitest
+blemesh_shell bsncent lorashell splitty
```
Along with the `targets` directory, `apps` represents the top-level of the build tree for the particular project, and define the dependencies for the rest of the system. Mynewt users and developers can add their own apps to the project's `apps` directory.
diff --git a/docs/newtmgr/command_list/newtmgr_image.md b/docs/newtmgr/command_list/newtmgr_image.md
index e070ccfe2b..82409528cc 100644
--- a/docs/newtmgr/command_list/newtmgr_image.md
+++ b/docs/newtmgr/command_list/newtmgr_image.md
@@ -58,4 +58,4 @@ corelist | newtmgr image corelist<br>-c profile01 | Lists the core files on
erase | newtmgr image erase<br>-c profile01 | Erases the image, if unused, from the secondary image slot on a device. Newtmgr connects to the device over a connection specified in the `profile01` connection profile.
list | newtmgr image list<br>-c profile01 | Lists the images on a device. Newtmgr connects to the device over a connection specified in the `profile01` connection profile.
test | newtmgr image test <br>be9699809a049...73d77f | Tests the image, identified by the `be9699809a049...73d77f` hash value, during the next reboot on a device. Newtmgr connects to the device over a connection specified in the `profile01` connection profile.
-upload | newtmgr image <br>upload bletiny.img<br>-c profile01 | Uploads the `bletiny.img` image to a device. Newtmgr connects to the device over a connection specified in the `profile01` connection profile.
+upload | newtmgr image <br>upload btshell.img<br>-c profile01 | Uploads the `btshell.img` image to a device. Newtmgr connects to the device over a connection specified in the `profile01` connection profile.
diff --git a/docs/newtmgr/command_list/newtmgr_mpstats.md b/docs/newtmgr/command_list/newtmgr_mpstats.md
index 928b3e43cb..6feaa6830c 100644
--- a/docs/newtmgr/command_list/newtmgr_mpstats.md
+++ b/docs/newtmgr/command_list/newtmgr_mpstats.md
@@ -50,8 +50,8 @@ $ newtmgr mpstat -c myserial
ble_hs_hci_ev_pool 16 10 10 9
ble_l2cap_chan_pool 28 3 3 3
ble_l2cap_sig_proc_pool 20 1 1 1
- bletiny_chr_pool 36 64 64 64
- bletiny_dsc_pool 28 64 64 64
- bletiny_svc_pool 36 32 32 32
+ btshell_chr_pool 36 64 64 64
+ btshell_dsc_pool 28 64 64 64
+ btshell_svc_pool 36 32 32 32
msys_1 292 12 9 6
```
diff --git a/docs/os/get_started/project_create.md b/docs/os/get_started/project_create.md
index 2df233d292..7db8bc6f5d 100644
--- a/docs/os/get_started/project_create.md
+++ b/docs/os/get_started/project_create.md
@@ -153,9 +153,9 @@ repos/apache-mynewt-core/
│ ├── bleprph_oic
│ ├── blesplit
│ ├── bletest
-│ ├── bletiny
│ ├── bleuart
│ ├── boot
+│ ├── btshell
│ ├── fat2native
│ ├── ffs2native
│ ├── ocf_sample
diff --git a/docs/os/tutorials/add_newtmgr.md b/docs/os/tutorials/add_newtmgr.md
index a8201841f1..33a3deac40 100644
--- a/docs/os/tutorials/add_newtmgr.md
+++ b/docs/os/tutorials/add_newtmgr.md
@@ -33,7 +33,7 @@ Ensure that you have met the following prerequisites before continuing with this
### Use an Existing Project
We assume that you have worked through at least some of the other tutorials and have an existing project.
-In this example, we modify the `bletiny` app to enable Newt Manager support.
+In this example, we modify the `btshell` app to enable Newt Manager support.
We call our target `myble`. You can create the target using any name you choose.
### Modify Package Dependencies and Configurations
@@ -141,8 +141,8 @@ Generate an application image for the `myble` target. You can use any version nu
```
$ newt create-image myble 1.0.0
-App image successfully generated: ./bin/makerbeacon/apps/bletiny/bletiny.img
-Build manifest: ./bin/makerbeacon/apps/bletiny/manifest.json
+App image successfully generated: ./bin/makerbeacon/apps/btshell/btshell.img
+Build manifest: ./bin/makerbeacon/apps/btshell/manifest.json
```
<br>
diff --git a/docs/os/tutorials/blehci_project.md b/docs/os/tutorials/blehci_project.md
index 387b95db26..fd956911fd 100644
--- a/docs/os/tutorials/blehci_project.md
+++ b/docs/os/tutorials/blehci_project.md
@@ -104,7 +104,7 @@ Generate a signed application image for the `myble2` target. The version number
```no-highlight
$ newt create-image myble2 1.0.0
-App image succesfully generated: ~/dev/blehciproj/bin/targets/myble2/app/apps/bletiny/bletiny.img
+App image succesfully generated: ~/dev/blehciproj/bin/targets/myble2/app/apps/blehci/blehci.img
```
<br>
diff --git a/docs/os/tutorials/bleprph/bleprph-app.md b/docs/os/tutorials/bleprph/bleprph-app.md
index 79b9953f76..0cc3be5dad 100644
--- a/docs/os/tutorials/bleprph/bleprph-app.md
+++ b/docs/os/tutorials/bleprph/bleprph-app.md
@@ -20,7 +20,7 @@ which is a free app to browse and connect to BLE Peripheral devices.
### Create a New Target
-You can create a new project instead, but this tutorial will simply use the previously created bletiny project and add a new target for the BLE Peripheral
+You can create a new project instead, but this tutorial will simply use the previously created btshell project and add a new target for the BLE Peripheral
```no-highlight
$ newt target create myperiph
diff --git a/mkdocs.yml b/mkdocs.yml
index 12e45d74dd..33a0b6ea5c 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -538,11 +538,6 @@ pages:
- 'ble_uuid_to_str': 'network/ble/ble_hs/other/functions/ble_uuid_to_str.md'
- 'ble_uuid_u16': 'network/ble/ble_hs/other/functions/ble_uuid_u16.md'
- - bletiny Usage API [deprecated]:
- - toc: 'network/ble/bletiny/bletiny_api.md'
- - 'GAP in bletiny': 'network/ble/bletiny/bletiny_GAP.md'
- - 'GATT in bletiny': 'network/ble/bletiny/bletiny_GATT.md'
- - 'Advertisement Data Fields': 'network/ble/bletiny/bletiny_advdata.md'
- btshell Usage API:
- toc: 'network/ble/btshell/btshell_api.md'
- 'GAP in btshell': 'network/ble/btshell/btshell_GAP.md'
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services