You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ad...@apache.org on 2016/11/15 19:34:42 UTC
[34/40] incubator-mynewt-site git commit: This closes #118.
This closes #118.
Project: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/commit/4a883474
Tree: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/tree/4a883474
Diff: http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/diff/4a883474
Branch: refs/heads/master
Commit: 4a88347482353f9ea446e5081adb6942017c5d6f
Parents: 62808ed 54755cb
Author: aditihilbert <ad...@runtime.io>
Authored: Tue Nov 15 10:49:10 2016 -0800
Committer: aditihilbert <ad...@runtime.io>
Committed: Tue Nov 15 10:49:10 2016 -0800
----------------------------------------------------------------------
docs/about.md | 11 +-
docs/faq/how_to_edit_docs.md | 7 +-
docs/network/ble/ble_intro.md | 43 ++--
docs/newt/install/newt_linux.md | 4 +-
docs/os/core_os/callout/callout.md | 20 +-
docs/os/core_os/callout/os_callout_func_init.md | 20 +-
docs/os/core_os/callout/os_callout_init.md | 16 +-
docs/os/core_os/callout/os_callout_queued.md | 7 +-
docs/os/core_os/callout/os_callout_reset.md | 12 +-
docs/os/core_os/callout/os_callout_stop.md | 10 +-
.../os/core_os/context_switch/context_switch.md | 20 +-
.../os/core_os/context_switch/os_arch_ctx_sw.md | 10 +-
docs/os/core_os/context_switch/os_sched.md | 6 +-
.../context_switch/os_sched_ctx_sw_hook.md | 2 +-
.../core_os/context_switch/os_sched_insert.md | 7 +-
.../context_switch/os_sched_os_timer_exp.md | 4 +-
.../core_os/context_switch/os_sched_resort.md | 6 +-
.../context_switch/os_sched_set_current_task.md | 6 +-
.../os/core_os/context_switch/os_sched_sleep.md | 10 +-
.../core_os/context_switch/os_sched_wakeup.md | 2 +-
docs/os/core_os/event_queue/event_queue.md | 16 +-
docs/os/core_os/event_queue/os_eventq_get.md | 4 +-
docs/os/core_os/event_queue/os_eventq_init.md | 4 +-
docs/os/core_os/event_queue/os_eventq_put.md | 6 +-
docs/os/core_os/event_queue/os_eventq_remove.md | 6 +-
docs/os/core_os/heap/heap.md | 2 +-
docs/os/core_os/heap/os_free.md | 4 +-
docs/os/core_os/heap/os_malloc.md | 12 +-
docs/os/core_os/heap/os_realloc.md | 10 +-
docs/os/core_os/mbuf/OS_MBUF_DATA.md | 4 +-
docs/os/core_os/mbuf/OS_MBUF_LEADINGSPACE.md | 4 +-
docs/os/core_os/mbuf/OS_MBUF_PKTHDR.md | 2 +-
docs/os/core_os/mbuf/OS_MBUF_PKTHDR_TO_MBUF.md | 2 +-
docs/os/core_os/mbuf/OS_MBUF_PKTLEN.md | 2 +-
docs/os/core_os/mbuf/OS_MBUF_TRAILINGSPACE.md | 4 +-
docs/os/core_os/mbuf/OS_MBUF_USRHDR.md | 2 +-
docs/os/core_os/mbuf/OS_MBUF_USRHDR_LEN.md | 2 +-
docs/os/core_os/mbuf/mbuf.md | 26 +--
docs/os/core_os/mbuf/os_mbuf_adj.md | 6 +-
docs/os/core_os/mbuf/os_mbuf_append.md | 14 +-
docs/os/core_os/mbuf/os_mbuf_concat.md | 4 +-
docs/os/core_os/mbuf/os_mbuf_copydata.md | 10 +-
docs/os/core_os/mbuf/os_mbuf_copyinto.md | 8 +-
docs/os/core_os/mbuf/os_mbuf_dup.md | 4 +-
docs/os/core_os/mbuf/os_mbuf_extend.md | 8 +-
docs/os/core_os/mbuf/os_mbuf_free_chain.md | 2 +-
docs/os/core_os/mbuf/os_mbuf_get.md | 8 +-
docs/os/core_os/mbuf/os_mbuf_get_pkthdr.md | 10 +-
docs/os/core_os/mbuf/os_mbuf_memcmp.md | 10 +-
docs/os/core_os/mbuf/os_mbuf_off.md | 12 +-
docs/os/core_os/mbuf/os_mbuf_pool_init.md | 10 +-
docs/os/core_os/mbuf/os_mbuf_prepend.md | 8 +-
docs/os/core_os/mbuf/os_mbuf_pullup.md | 8 +-
docs/os/core_os/memory_pool/OS_MEMPOOL_BYTES.md | 8 +-
docs/os/core_os/memory_pool/OS_MEMPOOL_SIZE.md | 16 +-
docs/os/core_os/memory_pool/memory_pool.md | 2 +-
docs/os/core_os/memory_pool/os_memblock_get.md | 6 +-
docs/os/core_os/memory_pool/os_memblock_put.md | 8 +-
docs/os/core_os/memory_pool/os_mempool_init.md | 26 +--
docs/os/core_os/mqueue/mqueue.md | 6 +-
docs/os/core_os/mqueue/os_mqueue_get.md | 6 +-
docs/os/core_os/mqueue/os_mqueue_init.md | 6 +-
docs/os/core_os/mqueue/os_mqueue_put.md | 10 +-
docs/os/core_os/msys/msys.md | 4 +-
docs/os/core_os/msys/os_msys_get.md | 10 +-
docs/os/core_os/msys/os_msys_get_pkthdr.md | 8 +-
docs/os/core_os/msys/os_msys_register.md | 2 +-
docs/os/core_os/mutex/mutex.md | 2 +-
docs/os/core_os/mutex/os_mutex_init.md | 6 +-
docs/os/core_os/mutex/os_mutex_pend.md | 14 +-
docs/os/core_os/mutex/os_mutex_release.md | 10 +-
docs/os/core_os/mynewt_os.md | 8 +-
docs/os/core_os/os_init.md | 6 +-
docs/os/core_os/os_start.md | 4 +-
docs/os/core_os/os_started.md | 6 +-
docs/os/core_os/porting/port_bsp.md | 112 ++++++----
docs/os/core_os/porting/port_cpu.md | 20 +-
docs/os/core_os/porting/port_mcu.md | 9 +-
docs/os/core_os/porting/port_os.md | 24 +-
docs/os/core_os/sanity/sanity.md | 2 +-
docs/os/core_os/semaphore/os_sem_init.md | 8 +-
docs/os/core_os/semaphore/os_sem_pend.md | 14 +-
docs/os/core_os/semaphore/os_sem_release.md | 8 +-
docs/os/core_os/semaphore/semaphore.md | 8 +-
docs/os/core_os/task/os_task_info_get_next.md | 18 +-
docs/os/core_os/task/os_task_init.md | 20 +-
docs/os/core_os/task/task.md | 15 +-
docs/os/core_os/time/os_gettimeofday.md | 4 +-
docs/os/core_os/time/os_settimeofday.md | 4 +-
docs/os/core_os/time/os_time.md | 12 +-
docs/os/core_os/time/os_time_delay.md | 2 +-
docs/os/get_started/cross_tools.md | 4 +-
docs/os/get_started/project_create.md | 108 ++++++---
docs/os/get_started/vocabulary.md | 67 ++++--
docs/os/modules/baselibc.md | 21 +-
docs/os/modules/bootloader/bootloader.md | 218 ++++++++++++++++---
docs/os/modules/console/console.md | 37 +++-
.../os/modules/console/console_blocking_mode.md | 12 +-
docs/os/modules/console/console_echo.md | 13 +-
docs/os/modules/console/console_init.md | 18 +-
docs/os/modules/console/console_is_init.md | 8 +-
docs/os/modules/console/console_printf.md | 22 +-
docs/os/modules/console/console_read.md | 18 +-
docs/os/modules/console/console_write.md | 11 +-
docs/os/modules/shell/shell.md | 30 ++-
docs/os/modules/shell/shell_cmd_register.md | 13 +-
.../modules/shell/shell_nlip_input_register.md | 15 +-
docs/os/modules/shell/shell_nlip_output.md | 6 +-
docs/os/modules/shell/shell_task_init.md | 18 +-
docs/os/tutorials/STM32F303.md | 6 +-
docs/os/tutorials/arduino_zero.md | 117 ++++++++--
docs/os/tutorials/bletiny_project.md | 135 +++++++-----
docs/os/tutorials/nRF52.md | 16 +-
docs/os/tutorials/repo/add_repos.md | 14 +-
docs/os/tutorials/repo/create_repo.md | 40 +++-
docs/os/tutorials/repo/upgrade_repo.md | 4 +
mkdocs.yml | 4 +
117 files changed, 1180 insertions(+), 706 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/docs/about.md
----------------------------------------------------------------------
diff --cc docs/about.md
index a842db4,5ba9e00..6f0606b
--- a/docs/about.md
+++ b/docs/about.md
@@@ -2,12 -2,13 +2,11 @@@
Some upcoming features:
--* Host-only BLE stack
--* Serial upgrade of image in bootloader
--* HAL redesign to abstract across a diverse set of chip peripherals ([View discussion thread](http://mail-archives.apache.org/mod_mbox/incubator-mynewt-dev/201606.mbox/%3C06CB0682-8F67-4C3F-93E4-6A20444487A1%40apache.org%3E))
--* HAL for SPI access (master and slave)
--* Ability for drivers to turn on/off low power settings automatically
-* Support for Wi-Fi controllers via a socket interface
--
++* Full IP support
++* Low power support with ability for drivers to turn on/off low power settings automatically
++* Sensor API, see [discussion thread](https://lists.apache.org/list.html?dev@mynewt.apache.org:dfr=June%201|dto=2016-11-14:%22Sensor%20Drivers%22)
++* Support for MIPS architecture
++* Support for additional boards
<font color="#F2853F"> The detailed roadmap is tracked on [JIRA for Mynewt](https://issues.apache.org/jira/browse/MYNEWT/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel). </font>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/docs/newt/install/newt_linux.md
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/docs/os/core_os/porting/port_bsp.md
----------------------------------------------------------------------
diff --cc docs/os/core_os/porting/port_bsp.md
index 4747589,4265c58..602a517
--- a/docs/os/core_os/porting/port_bsp.md
+++ b/docs/os/core_os/porting/port_bsp.md
@@@ -34,16 -34,22 +38,20 @@@ name that describes the board/system yo
###Create a Target using Mynewt
-Create a newt target for your test project for the BSP. To learn how to create a target,
-see this **howto** [Tutorial](../../get_started/project_create). Once you are familiar
-with creating targets, move on below to create a target to use to test your BSP.
+Create a newt target for your test project for the BSP. To learn how to create a target, see this **howto** [Tutorial](../../get_started/project1). Once you are familiar with creating targets, move on below to create a target to use to test your BSP.
- It is recommended that you use a simple `project` like `blinky` to minimize time to get a working Mynewt system. For this document, we will assume the `target` is called `myboard_blinky` and uses project `blinky`.
+ It is recommended that you use a simple project like [blinky](../../tutorials/blinky_primo.md) to minimize the time
+ to get a working Mynewt system. For this document, we will assume the *target* is called *myboard_blinky*
+ and uses project *blinky*.
- Set the `bsp` of the project to `/hw/bsp/myboard`. While creating your target, you will need to specify your `arch`and `compiler`. If your platform requires an architecture or compiler that are not defined in Mynewt, you will need to add them first. To add a CPU architecture see [CPU Porting](port_cpu.md).
+ Set the `bsp` of the project to `/hw/bsp/myboard`. While creating your target, you will need to
+ specify your `arch`and `compiler`. If your platform requires an architecture or compiler
+ that are not defined in Mynewt, you will need to add them first. To add a CPU architecture see [CPU Porting](port_cpu.md).
- When you are complete, your `target` may look similar to this.
+ When this is complete, your *target* may look similar to this.
```c
- $ newt target show
+ $newt target show
myboard_blinky
arch=cortex_m0
bsp=hw/bsp/myboard
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/docs/os/core_os/porting/port_os.md
----------------------------------------------------------------------
diff --cc docs/os/core_os/porting/port_os.md
index 1a3b779,2d3895a..2390bf4
--- a/docs/os/core_os/porting/port_os.md
+++ b/docs/os/core_os/porting/port_os.md
@@@ -15,16 -15,17 +15,17 @@@ support from the underlying platform
The platform dependency of these components can fall into several categories:
-* **CPU Core Dependencies** -- Specific code or
+* **CPU Core Dependencies** -- Specific code or
configuration to operate the CPU core within your target platform
-* **MCU Dependencies** -- Specific code or configuration to operate the MCU or
+* **MCU Dependencies** -- Specific code or configuration to operate the MCU or
SoC within your target platform
-* **BSP Dependencies** -- Specific code or configuration to accommodate the
-specific layout and functionality of your target platform
+* **BSP Dependencies** -- Specific code or configuration to accommodate the
+specific layout and functionality of your target platform
- ###BSP Dependency
+ ###Board Support Package (BSP) Dependency
- With all of the functionality provided by the core, MCU, and MCU HAL (Hardware Abstraction Layer), there are still some things that must be specified for your particular system. This
+ With all of the functionality provided by the core, MCU, and MCU HAL (Hardware Abstraction Layer),
+ there are still some things that must be specified for your particular system. This
is provided in Mynewt to allow you the flexibility to design for the exact
functionality, peripherals and features that you require in your product.
@@@ -56,21 -58,32 +58,27 @@@ You need only set the `bsp` attribute i
###MCU Dependency
- Some OS code depends on the MCU or SoC that the system contains. For example, the MCU may specify the potential memory map of the system - where code and data can reside.
+ Some OS code depends on the MCU or SoC that the system contains. For example, the MCU may specify
+ the potential memory map of the system - where code and data can reside.
-* If your MCU is already supported by Mynewt, there is no additional MCU work involved in
-porting to your platform. You need only set the `arch` attribute in your Mynewt target
-using the [newt command tool](../../../newt/newt_intro).
-* If your MCU is not yet supported by Mynewt, you can add support by following the
-instructions on [how to add MCU support to Mynewt](port_mcu.md)
+* If your MCU is already supported my Mynewt, there is no additional MCU work involved in porting to your platform. You need only to set the `arch` attribute in your Mynewt target using the [newt command tool](../../../../newt/newt_intro).
+* If your MCU is not yet supported by Mynewt, you can add support following the instructions on[how to add MCU support to Mynewt](port_mcu.md)
- ### MCU HAL
+ ### MCU Hardware Abstraction Layer (HAL)
- Mynewt's architecture supports a hardware abstraction layer (HAL) for common on or off-chip MCU peripherals such as GPIO, UARTs, flash memory etc. Even if your MCU is supported for the core OS, you may find that you need to implement the HAL functionality for a new peripheral. For a description of the HAL abstraction and implementation information,
+ Mynewt's architecture supports a hardware abstraction layer (HAL) for common on or off-chip MCU peripherals
+ such as GPIO, UARTs, flash memory etc. Even if your MCU is supported for the core OS,
+ you may find that you need to implement the HAL functionality for a new peripheral.
+ For a description of the HAL abstraction and implementation information,
see the [HAL API](../../modules/hal/hal.md)
-###CPU Core Dependency
+###CPU Core Dependency
- Some OS code depends on the CPU core that your system is using. For example, a given CPU core has a specific assembly language instruction set, and may require special cross compiler or compiler settings to use the appropriate instruction set.
+ Some OS code depends on the CPU core that your system is using. For example, a given CPU core
+ has a specific assembly language instruction set, and may require special cross compiler or
+ compiler settings to use the appropriate instruction set.
-* If your CPU architecture is already supported by Mynewt, there is no CPU core work involved
-in porting to your platform. You need only set the `arch` and `compiler` attributes in your
-Mynewt target using the [newt command tool](../../../newt/newt_intro).
-* If your CPU architecture is not supported by Mynewt, you can add support by following the
-instructions on [how to add CPU architecture support to Mynewt](port_cpu.md)
+* If your CPU architecture is already supported my Mynewt, there is no CPU core work involved in porting to your platform. You need only to set the `arch` and `compiler` attributes in your Mynewt target using the [newt command tool](../../../../newt/newt_intro).
+* If your CPU architecture is not supported by Mynewt, you can add support following the instructions on [how to add CPU architecture support to Mynewt](port_cpu.md)
+
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/docs/os/tutorials/arduino_zero.md
----------------------------------------------------------------------
diff --cc docs/os/tutorials/arduino_zero.md
index 9926656,d37b280..cbf9484
--- a/docs/os/tutorials/arduino_zero.md
+++ b/docs/os/tutorials/arduino_zero.md
@@@ -89,30 -89,21 +89,21 @@@
### Create your bootloader target
-Next, you need to tell Newt what to build. For the Arduino Zero, we are going to
+Next, you need to tell Newt what to build. For the Arduino Zero, we are going to
generate both a bootloader, and an image target.
-To generate the bootloader target, you need to specify the following options. The output of the commands (indicating success) have been suppressed for easier readability.
+To generate the bootloader target, you need to specify the following options. The output of the commands (indicating success) have been suppressed for easier readability.
```no-highlight
- $ newt target create arduino_boot
- $ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
- $ newt target set arduino_boot app=@apache-mynewt-core/apps/boot
+ $ newt target create arduino_boot
+ $ newt target set arduino_boot bsp=@mynewt_arduino_zero/hw/bsp/arduino_zero
+ Target targets/arduino_boot successfully created
+ $ newt target set arduino_boot app=@apache-mynewt-core/apps/boot
+ Target targets/arduino_boot successfully set target.app to @apache-mynewt-core/apps/boot
$ newt target set arduino_boot build_profile=optimized
- ```
-
- <br>
-
- If you have an Arduino Zero Pro or M0 Pro, you have to set the following next:
-
- ```
- $ newt target set arduino_boot features=arduino_zero_pro
- ```
-
- If you have an Arduino Zero, you have to set the following instead:
-
- ```
- $ newt target set arduino_boot features=arduino_zero
+ Target targets/arduino_boot successfully set target.build_profile to optimized
+ $ newt target set arduino_boot syscfg=BSP_ARDUINO_ZERO_PRO=1
+ Target targets/arduino_boot successfully set target.syscfg to BSP_ARDUINO_ZERO_PRO=1
```
<br>
@@@ -157,9 -171,10 +171,10 @@@ board
<br>
-### Build your blinky app
+### Build your blinky app
- To create and download your application, you create another target, this one pointing to the application you want to download to the Arduino board. In this tutorial, we will use the default application that comes with your project, ```apps/blinky```:
+ To create and download your application, you create another target, this one pointing to the application you want to download to the Arduino board.
+ In this tutorial, we will use the default application that comes with your project, ```apps/blinky```:
**Note**: Remember to set features to `arduino_zero` if your board is Arduino Zero and not a Pro!
@@@ -224,9 -239,58 +239,58 @@@ Execute the command to download the boo
$ newt load arduino_boot
```
-If the newt tool finishes without error, that means the bootloader has been
+If the newt tool finishes without error, that means the bootloader has been
successfully loaded onto the target.
+ If, on the other hand, you get errors like the following:
+
+ ```
+ $ newt load arduino_boot -v
+ Loading bootloader
+ Error: Downloading ~/dev/arduino_zero/bin/targets/arduino_boot/app/apps/boot/boot.elf.bin to 0x0
+ Open On-Chip Debugger 0.9.0 (2015-11-15-05:39)
+ Licensed under GNU GPL v2
+ For bug reports, read
+ http://openocd.org/doc/doxygen/bugs.html
+ Info : only one transport option; autoselect 'swd'
+ adapter speed: 500 kHz
+ adapter_nsrst_delay: 100
+ cortex_m reset_config sysresetreq
+ Info : CMSIS-DAP: SWD Supported
+ Info : CMSIS-DAP: JTAG Supported
+ Info : CMSIS-DAP: Interface Initialised (SWD)
+ Info : CMSIS-DAP: FW Version = 01.1F.0118
+ Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 1 TDO = 1 nTRST = 0 nRESET = 1
+ Info : CMSIS-DAP: Interface ready
+ Info : clock speed 500 kHz
+ Info : SWD IDCODE 0x0bc11477
+ Info : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints
+ Error: Target not halted
+ ```
+
+ Then you'll need to erase your board first before downloading the `arduino_boot` application. Here's how you do that using gdb,
+ the GNU Debugger.
+
+ ```gdb
+ $ newt debug arduino_blinky
+
+ (gdb) mon at91samd chip-erase
+ chip erased
+ chip erased
+ (gdb) x/32wx 0
+ 0x0: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x10: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x20: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x30: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x40: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x50: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x60: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ 0x70: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
+ (gdb) q
+ ```
+
+ Once the chip is erased, go back and download the `arduino_boot` image to the board as above.
+
<br>
<font color="#FF0000"> Reminder if you are using Docker: </font> When working with actual hardware, remember that each board has an ID. If you swap boards and do not refresh the USB Device Filter on the VirtualBox UI, the ID might be stale and the Docker instance may not be able to see the board correctly. For example, you may see an error message like `Error: unable to find CMSIS-DAP device` when you try to load or run an image on the board. In that case, you need to click on the USB link in VirtualBox UI, remove the existing USB Device Filter (e.g. "Atmel Corp. EDBG CMSIS-DAP[0101]") by clicking on the "Removes selected USB filter" button, and add a new filter by clicking on the "Adds new USB filter" button.
@@@ -292,12 -356,13 +356,13 @@@ Continuing
<br>
-**NOTE:** The 0.0.0 specified after the target name to `newt run` is the version
-of the image to load. If you are not providing remote upgrade, and are just
+**NOTE:** The 0.0.0 specified after the target name to `newt run` is the version
+of the image to load. If you are not providing remote upgrade, and are just
developing locally, you can provide 0.0.0 for every image version.
- If you want the image to run without the debugger connected, simply quit the
- debugger and restart the board. The image you programmed will come and run on the Arduino on next boot!
+ If you want the image to run without the debugger connected, simply quit the
+ debugger and restart the board. The image you programmed will come up and run on
+ the Arduino on the next boot!
<br>
http://git-wip-us.apache.org/repos/asf/incubator-mynewt-site/blob/4a883474/mkdocs.yml
----------------------------------------------------------------------
diff --cc mkdocs.yml
index 8370943,a775619..5a8f702
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@@ -52,7 -56,8 +54,9 @@@ pages
- 'Service Registration': 'os/tutorials/bleprph/bleprph-svc-reg.md'
- 'Characteristic Access': 'os/tutorials/bleprph/bleprph-chr-access.md'
- 'Advertising': 'os/tutorials/bleprph/bleprph-adv.md'
+ - 'Connection Callbacks': 'os/tutorials/bleprph/bleprph-conn.md'
+ - 'GAP Event Callbacks': 'os/tutorials/bleprph/bleprph-gap-event.md'
+ - 'BLE Peripheral App' : 'os/tutorials/bleprph/bleprph-app.md'
- 'BLE iBeacon': 'os/tutorials/ibeacon.md'
- 'BLE HCI interface': 'os/tutorials/blehci_project.md'
- OS User Guide: