TEXT   6

zephyr.txt

Guest on 23rd May 2021 07:51:46 AM

  1. Zephyr Notes
  2.  
  3. Entry: Supported boards
  4. Date: Wed Apr  1 18:40:03 EDT 2020
  5.  
  6. https://docs.zephyrproject.org/latest/boards/arm/stm32_min_dev/doc/index.html
  7. https://docs.zephyrproject.org/latest/boards/arm/stm32f0_disco/doc/index.html
  8. https://docs.zephyrproject.org/latest/boards/arm/stm32f030_demo/doc/index.html
  9. https://docs.zephyrproject.org/latest/boards/arm/stm32f4_disco/doc/index.html
  10. https://docs.zephyrproject.org/latest/boards/arm/nrf52840_mdk/doc/index.html
  11.  
  12.  
  13. Entry: setting up
  14. Date: Wed Apr  1 19:08:17 EDT 2020
  15.  
  16. $ cd /nix/exo
  17. $ west init zephyr-project
  18. $ cd zephyr-project/
  19. $ west update
  20. $ west zephyr-export
  21.  
  22. The latter one crashes on a Python f string, introduced in 3.6 and I have 3.5
  23. Installed 3.7.2 from nix.
  24.  
  25. Another issue: requirements-run-test.txt contains: pyocd>=0.24.0 which
  26. fails install due to rust error on cmsis_pack_manager
  27.  
  28. pip install --user cmsis_pack_manager
  29.  
  30. Why the hell is there a rust package in there?
  31.  
  32. https://github.com/ARMmbed/cmsis-pack-manager
  33.  
  34. The needs:
  35. rustup update stable
  36. rustup default stable
  37.  
  38.  
  39. So pip isn't too smart.  It installs everything that it is asked to
  40. install even if it is already installed.  Smart skipping is done only
  41. for things that are not directly mentioned.
  42.  
  43.  
  44. Wow this shit really is complex and hard to get going.
  45.  
  46. OK this is a problem with nix.
  47.  
  48. Nix is a fucking pain in the ass.
  49.  
  50.  
  51. cd /nix/exo/zephyr-project/zephyr
  52. export PYTHONPATH=/home/tom/.local/lib/python3.7/site-packages
  53. west build -p auto -b stm32_min_dev_blue samples/basic/blinky
  54.  
  55.  
  56.  
  57. Entry: STLink-V2
  58. Date: Thu Apr  2 11:38:33 EDT 2020
  59.  
  60. https://www.youtube.com/watch?v=dB4xIs0-Kb4
  61. https://devzone.nordicsemi.com/f/nordic-q-a/38670/nrf52840-and-st-link-v2
  62.  
  63. So it should work.
  64.  
  65. I have just one left?  Maybe order some more then.
  66.  
  67. After installing OpenOCD 0.10.0 (Debian had 0.9.x) it works with nrf52.cnf:
  68.  
  69. root@zoe:/etc/net/udev/openocd# ./openocd_nRF52_STLink.sh
  70. Open On-Chip Debugger 0.10.0
  71. Licensed under GNU GPL v2
  72. For bug reports, read
  73.         http://openocd.org/doc/doxygen/bugs.html
  74. Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
  75. Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
  76. adapter speed: 10000 kHz
  77. Info : Unable to match requested speed 10000 kHz, using 4000 kHz
  78. Info : Unable to match requested speed 10000 kHz, using 4000 kHz
  79. Info : clock speed 4000 kHz
  80. Info : STLINK v2 JTAG v17 API v2 SWIM v4 VID 0x0483 PID 0x3748
  81. Info : using stlink api v2
  82. Info : Target voltage: 3.251098
  83. Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
  84.  
  85.  
  86.  
  87.  
  88. Entry: blinky on nRF52 board
  89. Date: Fri Apr  3 09:32:21 EDT 2020
  90.  
  91. First find out which board this should be.
  92.  
  93.  
  94.  
  95. Entry: nRF52 board
  96. Date: Fri Apr  3 09:36:47 EDT 2020
  97.  
  98. This one is supported:
  99. https://wiki.makerdiary.com/nrf52840-mdk/
  100. https://docs.zephyrproject.org/latest/boards/arm/nrf52840_mdk/doc/index.html
  101.  
  102.  
  103. I have this one:
  104. https://wiki.makerdiary.com/nrf52840-mdk-usb-dongle/
  105.  
  106. LEDs are the same on both
  107.  
  108. P0.22 green
  109. P0.23 red
  110. P0.24 blue
  111.  
  112. So that should be fine.
  113.  
  114. Trying it out:
  115.  
  116. cd /nix/exo/zephyr-project/zephyr
  117. . ~/.zephyrrc
  118. export PYTHONPATH=/home/tom/.local/lib/python3.7/site-packages
  119. west build -p auto -b nrf52840_mdk samples/basic/blinky
  120.  
  121.  
  122. [117/122] Linking C executable zephyr/zephyr_prebuilt.elf
  123. Memory region         Used Size  Region Size  %age Used
  124.            FLASH:       12188 B         1 MB      1.16%
  125.             SRAM:        3956 B       256 KB      1.51%
  126.         IDT_LIST:          56 B         2 KB      2.73%
  127.  
  128. The dts for this board is here:
  129. tom@panda:/nix/exo/zephyr-project/zephyr$ cat ./boards/arm/nrf52840_mdk/nrf52840_mdk.dts
  130.  
  131.  
  132.  
  133.  
  134. Entry: load failed
  135. Date: Fri Apr  3 09:47:36 EDT 2020
  136.  
  137. (gdb) file /i/panda/nix/exo/zephyr-project/zephyr/build/zephyr/zephyr.elf
  138. A program is being debugged already.
  139. Are you sure you want to change the file? (y or n) y
  140. Reading symbols from /net/10.1.3.2/vol/2/panda/nix/exo/zephyr-project/zephyr/build/zephyr/zephyr.elf...done.
  141. (gdb) load
  142. Loading section rom_start, size 0x100 lma 0x0
  143. Loading section text, size 0x2ac2 lma 0x100
  144. Loading section .ARM.exidx, size 0x8 lma 0x2bc4
  145. Load failed
  146.  
  147.  
  148. I don't have the energy to debug that now.
  149. Possible solution:
  150. https://github.com/marcelobarrosalmeida/openocd_nrf52
  151.  
  152.  
  153.  
  154. Entry: 802.15.4 is not BLE link layer
  155. Date: Fri Apr  3 18:09:14 EDT 2020
  156.  
  157. http://www.diva-portal.org/smash/get/diva2:872772/FULLTEXT01.pdf
  158.  
  159.  
  160. Entry: Setting up the BLE example
  161. Date: Fri Apr 24 14:00:02 EDT 2020
  162.  
  163. https://www.zephyrproject.org/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/
  164.  
  165. 1. ninja menuconfig + 'D' to save defconfig (rename to prj.conf?)
  166. 2. where to save dts?
  167.  
  168.  
  169. Entry: UART output
  170. Date: Mon Apr 27 11:35:48 EDT 2020
  171.  
  172. So I want to see what is coming out of the uart.
  173. How do I know which pin is the uart?
  174.  
  175. ./build/zephyr/zephyr.dts
  176.  
  177.             uart0: uart@40002000 {
  178.                   reg = < 0x40002000 0x1000 >;
  179.                   interrupts = < 0x2 0x1 >;
  180.                   status = "okay";
  181.                   label = "UART_0";
  182.                   compatible = "nordic,nrf-uart";
  183.                   current-speed = < 0x1c200 >;
  184.                   tx-pin = < 0x14 >;
  185.                   rx-pin = < 0x13 >;
  186.                   rts-pin = < 0x5 >;
  187.                   cts-pin = < 0x7 >;
  188.             };
  189.  
  190.  
  191.             uart1: uart@40028000 {
  192.                   compatible = "nordic,nrf-uarte";
  193.                   reg = < 0x40028000 0x1000 >;
  194.                   interrupts = < 0x28 0x1 >;
  195.                   status = "disabled";
  196.                   label = "UART_1";
  197.             };
  198.  
  199. What are the pin numbers?
  200.  
  201.       model = "nRF52840-MDK Dev Kit";
  202.  
  203. As usual, pin naming isn't universal.
  204.  
  205. Start with what's on the board's doc site:
  206.  
  207. This is the config I'm using for zephyr and is the board used for the
  208. client, but not the board I have myself.
  209.  
  210. https://github.com/makerdiary/nrf52840-mdk
  211. TXD P0.20
  212. RXD P0.19
  213.  
  214. I have this board:
  215.  
  216. https://github.com/makerdiary/nrf52840-mdk-usb-dongle
  217.  
  218. The pins are marked.
  219.  
  220. With USB connector on top
  221.  
  222. LEFT:
  223.  
  224.  1 VIN
  225.  2 +5V
  226.  3 GDN
  227.  4 P0.04
  228.  5 P0.05
  229.  6 P0.06
  230.  7 P0.07
  231.  8 P0.08
  232.  9 P0.09
  233. 10 P0.10
  234.  
  235. RIGHT:
  236.  
  237.  1 +3v3V
  238.  2 GND
  239.  3 RST
  240.  4 SWDCLK
  241.  5 SWDIO
  242.  6 P0.19  RXD
  243.  7 P0.20  TXD
  244.  8 P0.21
  245.  9 P0.02
  246. 10 P0.03
  247.  
  248.  
  249.  
  250. Entry: BT840 pinout
  251. Date: Mon Apr 27 15:14:09 EDT 2020
  252.  
  253. Can up, antenna top
  254.  
  255. LEFT
  256.  
  257. 1 P26 SDA
  258. 2 P27 SCL
  259. 3 P00 XL1
  260. 4 P01 XL2
  261. 5 P02 AIN0
  262. 6 P03 AIN1
  263. 7 P09 NFC1
  264. 8 P10 NFC2
  265.  
  266.  
  267. RIGHT
  268.  
  269. 16      SWDIO
  270. 15      SWCLK
  271. 14 P18  RST
  272. 13 P13  LED
  273. 12 P100 SWO
  274. 11 P11  BUTTON
  275. 10      GND
  276.  9      VDD
  277.  
  278.  
  279.  
  280. Entry: uart config
  281. Date: Tue Apr 28 23:36:14 EDT 2020
  282.  
  283.             uart0: uart@40002000 {
  284.                   reg = < 0x40002000 0x1000 >;
  285.                   interrupts = < 0x2 0x1 >;
  286.                   status = "okay";
  287.                   label = "UART_0";
  288.                   compatible = "nordic,nrf-uart";
  289.                   current-speed = < 0x1c200 >;
  290.                   tx-pin = < 0x14 >;
  291.                   rx-pin = < 0x13 >;
  292.                   rts-pin = < 0x5 >;
  293.                   cts-pin = < 0x7 >;
  294.             };
  295.             uart1: uart@40028000 {
  296.                   compatible = "nordic,nrf-uarte";
  297.                   reg = < 0x40028000 0x1000 >;
  298.                   interrupts = < 0x28 0x1 >;
  299.                   status = "disabled";
  300.                   label = "UART_1";
  301.             };
  302.  
  303. 0x14 is P0.20
  304. 0x13 is P0.19
  305.  
  306. #x1c200 115200
  307.  
  308.  
  309. Entry: dts
  310. Date: Tue Apr 28 23:40:43 EDT 2020
  311.  
  312. So I have dts modifications I want to make.  What is the proper way to
  313. include those in the git archive and build?
  314.  
  315. Maybe first look at what a board directory looks like in the zephyr
  316. tree.
  317.  
  318. /nix/exo/zephyr-project/zephyr/boards/arm/nrf52840_mdk
  319.  
  320. This has some explanation:
  321.  
  322. https://www.zephyrproject.org/getting-started-with-zephyr-rtos-on-nordic-nrf52832-hackable/
  323.  
  324. It seems to suggest to add a board file to the zephyr-project
  325.  
  326. Can I just put that in the main source tree?
  327.  
  328. EDIT: I don't see a way to put that in the application source tree, so
  329. it is simplest to add a zephyr fork and use that.
  330.  
  331.  
  332. Entry: Compiling BLE example
  333. Date: Fri May  8 14:07:51 EDT 2020
  334.  
  335. Example has bitrotted, so track down some errors.
  336.  
  337. [  9%] Building C object CMakeFiles/app.dir/src/main.c.obj
  338. In file included from /home/tom/exo/zephyr/ble/src/main.c:18:
  339. /home/tom/exo/zephyr/ble/src/main.c:67:17: warning: initialization of 'void (*)(const struct bt_gatt_attr *, u16_t)' {aka 'void (*)(const struct bt_gatt_attr *, short unsigned int)'} from incompatible pointer type 'struct bt_gatt_ccc_cfg *' [-Wincompatible-pointer-types]
  340.    67 |     BT_GATT_CCC(T_ccc_cfg, T_ccc_cfg_changed),
  341.       |
  342.  
  343.  
  344. void (*)(const struct bt_gatt_attr *, u16_t)
  345. aka
  346. void (*)(const struct bt_gatt_attr *, short unsigned int)
  347. !=
  348. struct bt_gatt_ccc_cfg *
  349.  
  350. That's odd.
  351.  
  352. Ok I'm going to have to index this.
  353.  
  354. Indexed.
  355.  
  356. So what is going on here?
  357.  
  358.     BT_GATT_CCC(T_ccc_cfg, T_ccc_cfg_changed),
  359.  
  360. gatt.h says:
  361.  
  362. /** @def BT_GATT_CCC
  363.  *  @brief Client Characteristic Configuration Declaration Macro.
  364.  *
  365.  *  Helper macro to declare a CCC attribute.
  366.  *
  367.  *  @param _changed Configuration changed callback.
  368.  *  @param _perm CCC access permissions.
  369.  */
  370. #define BT_GATT_CCC(_changed, _perm)                        \
  371.       BT_GATT_CCC_MANAGED(((struct _bt_gatt_ccc[])                \
  372.             {BT_GATT_CCC_INITIALIZER(_changed, NULL, NULL)}), _perm)
  373.  
  374. So this is just another macro.
  375.  
  376. API docs from
  377. https://docs.zephyrproject.org/1.9.0/api/bluetooth.html
  378.  
  379. say:
  380.  
  381. BT_GATT_CCC(_cfg, _cfg_changed)
  382.  
  383.     Client Characteristic Configuration Declaration Macro.
  384.  
  385.     Helper macro to declare a CCC attribute.
  386.  
  387.     Parameters
  388.  
  389.             _cfg: Initial configuration.
  390.             _cfg_changed: Configuration changed callback.
  391.  
  392.  
  393.  
  394. So what am I running?
  395.  
  396. tom@panda:/nix/exo/zephyr-project/zephyr$ cat VERSION
  397. VERSION_MAJOR = 2
  398. VERSION_MINOR = 2
  399. PATCHLEVEL = 99
  400. VERSION_TWEAK = 0
  401. EXTRAVERSION =
  402.  
  403.  
  404. This is the old definition from:
  405.  
  406. https://github.com/zephyrproject-rtos/zephyr/blob/v1.9-branch/include/bluetooth/gatt.h
  407.  
  408.  
  409. /** @def BT_GATT_CCC
  410.  *  @brief Client Characteristic Configuration Declaration Macro.
  411.  *
  412.  *  Helper macro to declare a CCC attribute.
  413.  *
  414.  *  @param _cfg Initial configuration.
  415.  *  @param _cfg_changed Configuration changed callback.
  416.  */
  417. #define BT_GATT_CCC(_cfg, _cfg_changed)                           \
  418. {                                                     \
  419.       .uuid = BT_UUID_GATT_CCC,                             \
  420.       .perm = BT_GATT_PERM_READ | BT_GATT_PERM_WRITE,             \
  421.       .read = bt_gatt_attr_read_ccc,                              \
  422.       .write = bt_gatt_attr_write_ccc,                      \
  423.       .user_data = (&(struct _bt_gatt_ccc) { .cfg = _cfg,         \
  424.                                      .cfg_len = ARRAY_SIZE(_cfg), \
  425.                                      .cfg_changed = _cfg_changed, }),\
  426. }
  427.  
  428.  
  429. It's probably going to be easier to start from another example.
  430.  
  431.  
  432.  
  433.  
  434.  
  435.  
  436. Entry: BLE testing with Bluez
  437. Date: Sat May  9 12:55:00 EDT 2020
  438.  
  439. https://bcdevices.github.io/zephyr/ble/2019/10/30/zephyr-ble-testing.html
  440.  
  441.  
  442. Entry: Looking for some other examples
  443. Date: Sat May  9 12:56:24 EDT 2020
  444.  
  445. https://www.novelbits.io/zephyr-getting-started-bluetooth-low-energy-development/
  446.  
  447. But this is just advertising for their course on bluetooth which is not public.
  448.  
  449.  
  450. Entry: Compare Bluetooth docs between 1.9 and 2.2.99
  451. Date: Sat May  9 13:21:08 EDT 2020
  452.  
  453. https://docs.zephyrproject.org/1.9.0/api/bluetooth.html
  454.  
  455. https://docs.zephyrproject.org/latest/reference/bluetooth/index.html
  456.  
  457.  
  458. Entry: BLE example
  459. Date: Mon May 11 11:20:26 EDT 2020
  460.  
  461. 1.9 and 2.2.99 seem significantly different.  I am confused.  Let's
  462. look for a different example.
  463.  
  464. There are a couple in the source tree.  I'm not bootstrapped far
  465. enough yet to pick a good one, so let's just pick this one:
  466.  
  467. zephyr-project/zephyr/samples/bluetooth/peripheral/src/main.c
  468.  
  469. EDIT: This uses the heart rate service that is already part of zephyr:
  470.  
  471. zephyr/subsys/bluetooth/services/hrs.c
  472.  
  473. So it probably needs to be enabled in the config.
  474.  
  475. Bluetooth -> GATT Services -> GATT Heart Rate service
  476.  
  477.  
  478.  
  479. Entry: Found a new example
  480. Date: Tue May 26 20:12:40 EDT 2020
  481.  
  482. This is sufficiently complex and not too complex:
  483. zephyr-project/zephyr/samples/bluetooth/peripheral/src/main.c
  484.  
  485. Some questions:
  486.  
  487. - What is Client Configuration Change?
  488.  
  489.  
  490.  
  491. Entry: Weird error
  492. Date: Tue May 26 20:37:06 EDT 2020
  493.  
  494. +*** Booting Zephyr OS build zephyr-v2.2.0-1076-g9162e7d81298  ***
  495. Bluetooth initialized
  496. Advertising failed to start (err -11)
  497.  
  498. The error is returned by:
  499. bt_le_adv_start
  500.  
  501.  *  @return -ENOMEM No free connection objects available for connectable
  502.  *                  advertiser.
  503.  *  @return -ECONNREFUSED When connectable advertising is requested and there
  504.  *                        is already maximum number of connections established
  505.  *                        in the controller.
  506.  *                        This error code is only guaranteed when using Zephyr
  507.  *                        controller, for other controllers code returned in
  508.  *                        this case may be -EIO.
  509.  
  510.  
  511. I had removed:
  512.  
  513.     if (IS_ENABLED(CONFIG_SETTINGS)) { settings_load(); }
  514.  
  515. So don't!
  516.  
  517.  
  518. Entry: BLE GATT indicate
  519. Date: Tue May 26 22:07:33 EDT 2020
  520.  
  521. Like notification, but with confirmation.
  522.  
  523.  
  524.  
  525. Entry: Single reader?
  526. Date: Tue May 26 23:07:34 EDT 2020
  527.  
  528. It does seem to be possible, because the pointer to the attribute is
  529. passed into the read/write function, and it is possible to pass a
  530. type-tagged thing in there such that the read/write function can do
  531. some dispatch.
  532.  
  533.  
  534. Entry: Multiple notifications?
  535. Date: Wed May 27 00:30:00 EDT 2020
  536.  
  537. It seems that Nordic app does caching and I don't find a reliable way
  538. to clear the cache..
  539.  
  540. Also I seem to have an issue with multiple notifications.  Here's a
  541. service that has multiple sensors, from
  542. samples/bluetooth/peripheral_esp/src/main.c
  543.  
  544.  
  545. BT_GATT_SERVICE_DEFINE(ess_svc,
  546.       BT_GATT_PRIMARY_SERVICE(BT_UUID_ESS),
  547.  
  548.       /* Temperature Sensor 1 */
  549.       BT_GATT_CHARACTERISTIC(BT_UUID_TEMPERATURE,
  550.                          BT_GATT_CHRC_READ | BT_GATT_CHRC_NOTIFY,
  551.                          BT_GATT_PERM_READ,
  552.                          read_u16, NULL, &sensor_1.temp_value),
  553.       BT_GATT_DESCRIPTOR(BT_UUID_ES_MEASUREMENT, BT_GATT_PERM_READ,
  554.                      read_es_measurement, NULL, &sensor_1.meas),
  555.       BT_GATT_CUD(SENSOR_1_NAME, BT_GATT_PERM_READ),
  556.       BT_GATT_DESCRIPTOR(BT_UUID_VALID_RANGE, BT_GATT_PERM_READ,
  557.                      read_temp_valid_range, NULL, &sensor_1),
  558.       BT_GATT_DESCRIPTOR(BT_UUID_ES_TRIGGER_SETTING,
  559.                      BT_GATT_PERM_READ, read_temp_trigger_setting,
  560.                      NULL, &sensor_1),
  561.       BT_GATT_CCC(temp_ccc_cfg_changed,
  562.                 BT_GATT_PERM_READ | BT_GATT_PERM_WRITE),
  563.  
  564.       /* Temperature Sensor 2 */
  565.       BT_GATT_CHARACTERISTIC(BT_UUID_TEMPERATURE,
  566.                          BT_GATT_CHRC_READ | BT_GATT_CHRC_NOTIFY,
  567.                          BT_GATT_PERM_READ,
  568.                          read_u16, NULL, &sensor_2.temp_value),
  569.       BT_GATT_DESCRIPTOR(BT_UUID_ES_MEASUREMENT, BT_GATT_PERM_READ,
  570.                      read_es_measurement, NULL, &sensor_2.meas),
  571.       BT_GATT_CUD(SENSOR_2_NAME, BT_GATT_PERM_READ),
  572.       BT_GATT_DESCRIPTOR(BT_UUID_VALID_RANGE, BT_GATT_PERM_READ,
  573.                      read_temp_valid_range, NULL, &sensor_2),
  574.       BT_GATT_DESCRIPTOR(BT_UUID_ES_TRIGGER_SETTING,
  575.                      BT_GATT_PERM_READ, read_temp_trigger_setting,
  576.                      NULL, &sensor_2),
  577.       BT_GATT_CCC(temp_ccc_cfg_changed,
  578.                 BT_GATT_PERM_READ | BT_GATT_PERM_WRITE),
  579.  
  580.       /* Humidity Sensor */
  581.       BT_GATT_CHARACTERISTIC(BT_UUID_HUMIDITY, BT_GATT_CHRC_READ,
  582.                          BT_GATT_PERM_READ,
  583.                          read_u16, NULL, &sensor_3.humid_value),
  584.       BT_GATT_CUD(SENSOR_3_NAME, BT_GATT_PERM_READ),
  585.       BT_GATT_DESCRIPTOR(BT_UUID_ES_MEASUREMENT, BT_GATT_PERM_READ,
  586.                      read_es_measurement, NULL, &sensor_3.meas),
  587. );
  588.  
  589.  
  590.  
  591.  
  592. Entry: BLE on linux
  593. Date: Sun May 31 19:37:13 EDT 2020
  594.  
  595. don't use bluetoothctl for querying characteristics.
  596. use gatttool.  "-t random" is required.
  597.  
  598.  
  599.  gatttool -b 7D:EE:B0:80:2E:F8 -I -t random
  600.  
  601. https://stackoverflow.com/questions/15657007/bluetooth-low-energy-listening-for-notifications-indications-in-linux
  602.  
  603. [7D:EE:B0:80:2E:F8][LE]> char-desc 0x27 0x28
  604.  
  605. handle: 0x0027, uuid: 0000ffa3-0000-1000-8000-00805f9b34fb
  606. handle: 0x0028, uuid: 00002902-0000-1000-8000-00805f9b34fb
  607.  
  608. To turn on notifications, write 0100 to the ccc
  609.  
  610. char-write-req 0x0031 0100
  611.  
  612.  
  613.  
  614. Entry: serial radio
  615. Date: Mon Jun  1 00:39:35 EDT 2020
  616.  
  617. https://lists.zephyrproject.org/g/users/topic/zephyr_compatible_motes_for/31617871?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,31617871
  618. https://www.zephyrproject.org/introducing-the-zephyr-reel-board/
  619. https://github.com/zephyrproject-rtos/zephyr/tree/master/samples/net/wpan_serial
  620.  
  621.  
  622. Entry: ipv6 over ble
  623. Date: Mon Jun  1 13:36:23 EDT 2020
  624.  
  625. https://blog.nordicsemi.com/getconnected/why-run-ipv6-over-bluetooth-low-energy
  626.  
  627.  
  628. Entry: BLE midi
  629. Date: Mon Jun  1 13:38:27 EDT 2020
  630.  
  631. From 2016. Probably by now it is part of bluez?
  632.  
  633. https://www.youtube.com/watch?v=eKnC9_Buxus
  634. https://bugs.archlinux.org/task/56776
  635.  
  636. Since 5.44
  637.  
  638. Debian has 5.43
  639.  
  640. But it's not enabled by default.

Raw Paste


Login or Register to edit or fork this paste. It's free.