RAU6 Dokuwiki

User Tools

Site Tools

Trace: • Programming in Assembler Laboratory • Fan and Servo controlling • STM32 Control of built-in LEDs with PWM • IoT Networks: Laboratory 3 - CoAP • nRF52840 Zephyr BLE client • Bluetooth Low Energy for STM32 - peripheral write • ESP32 BLE in Arduino. Part2: Setting-up BLE Server • Zephyr BLE peripheral • Laboratory on GPIO use in Zephyr OS • Laboratory on the Internet of Things - Advanced IoT Hardware - on-site edition
No ACL setup yet! Denying access to everyone.
en:edu:zmitac:s2:aih:lab:nrf52zephyrblebeacon

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
en:edu:zmitac:s2:aih:lab:nrf52zephyrblebeacon [2023/12/09 18:37] – ktokarzen:edu:zmitac:s2:aih:lab:nrf52zephyrblebeacon [2023/12/09 18:42] (current) – ktokarz
Line 1: Line 1:
 ====== Zephyr Beacon example ====== ====== Zephyr Beacon example ======
 It's time to deal with some wireless transmission using nRF52840 SoC. At the beginning, we will use the example of the Bluetooth Low Energy Beacon which is included in the Zephyr installation in PlatformIO. It's time to deal with some wireless transmission using nRF52840 SoC. At the beginning, we will use the example of the Bluetooth Low Energy Beacon which is included in the Zephyr installation in PlatformIO.
-This example advertises the device as the "Test beacon" with details provided in Eddystone (([[https://en.wikipedia.org/wiki/Eddystone_(Google)]])) format. Notice that to use BLE it must be enabled in the prj.conf file.+This example advertises the device as the "Test beacon" with details provided in Eddystone (([[https://en.wikipedia.org/wiki/Eddystone_(Google)]])) format.  
 + 
 +After importing it to the Visual Studio Code we should make some configuration: remove the unwanted build target from platformio.ini, and if we want to receive messages via serial port enable it within prj.conf. Notice that to use BLE it is enabled by default in the example's prj.conf file.
 <code> <code>
 CONFIG_BT=y CONFIG_BT=y
Line 7: Line 9:
 CONFIG_BT_DEVICE_NAME="Test beacon" CONFIG_BT_DEVICE_NAME="Test beacon"
 </code> </code>
- 
-After importing it to the Visual Studio Code we should make some configuration: remove the unwanted build target from platformio.ini, and if we want to receive messages via serial port enable it within prj.conf.  
 This example starts the Bluetooth interface with the function bt_enable() that passes the pointer to the bt_ready() which is the callback function to notify that initialization has finished.  This example starts the Bluetooth interface with the function bt_enable() that passes the pointer to the bt_ready() which is the callback function to notify that initialization has finished. 
 <code> <code>
Line 54: Line 54:
 You can observe the details in the nRF Connect application on your mobile phone. You can observe the details in the nRF Connect application on your mobile phone.
  
-The beacon example is very simple because the beacon device is intended to advertise only so, there is no further functionality implemented. This example shows the so-called Eddystone format (([[https://en.wikipedia.org/wiki/Eddystone_(Google)]])) of Bluetooth Beacons that send simple information to nearby devices. To reduce the number of bytes sent in the advertisement frame the Eddystone format defines the list of prefixes and suffixes that can be used in the URL encoded as values of non-printable characters((https://github.com/google/eddystone/tree/master/eddystone-url)).+The beacon example is very simple because the beacon device is intended to advertise only, so there is no further functionality implemented. This example shows the so-called Eddystone format (([[https://en.wikipedia.org/wiki/Eddystone_(Google)]])) of Bluetooth Beacons that send simple information to nearby devices. To reduce the number of bytes sent in the advertisement frame the Eddystone format defines the list of prefixes and suffixes that can be used in the URL encoded as values of non-printable characters((https://github.com/google/eddystone/tree/master/eddystone-url)).
 For example, web prefixes can be encoded as in the table {{ref>eddyprefix}}. For example, web prefixes can be encoded as in the table {{ref>eddyprefix}}.
 <table eddyprefix> <table eddyprefix>
en/edu/zmitac/s2/aih/lab/nrf52zephyrblebeacon.1702143454.txt.gz · Last modified: by ktokarz