Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Sync to ArduinoBLE master#74

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fpistm merged 155 commits intomainfromrebase_1.3.7
Mar 28, 2025
Merged

Sync to ArduinoBLE master#74

fpistm merged 155 commits intomainfromrebase_1.3.7
Mar 28, 2025

Conversation

@fpistm
Copy link
Member

@fpistmfpistm commentedMar 21, 2025•
edited
Loading

This PR syncs the STM32duinoBLE library to ArduinoBLE master:
arduino-libraries@9e523b5

To ease future update, this update does not simply do a merge.
First the STM32duinoBLE main was merged to be the same than ArduinoBLE master:

  • Steps:
    • git checkout master
    • git merge -s ours main
    • git checkout main
    • git merge master

Then all changes made in STM32duinoBLE were grouped in several commits per topics.
Some fixes/improvements has been added.

Including PR not merged yet from ArduinoBLE:

Finally, the way a HCITransport was selected has not been preserved to be aligned with ArduinoBLE, moreover it ease support of new board and avoid to modify all sketches to add the new support.

See below:

The user can include the fileble_spi_conf.h to define which shield and configuration to use from the following list:

  • X-NUCLEO-IDB05A2
    • IDB05A2_SPI_CLOCK_D3: SPI clock on D3
    • IDB05A2_SPI_CLOCK_D13 SPI clock on D13
  • X-NUCLEO-IDB05A1
    • IDB05A1_SPI_CLOCK_D3: SPI clock on D3
    • IDB05A1_SPI_CLOCK_D13: SPI clock on D13
  • X-NUCLEO-BNRG2A1
    • BNRG2A1_CLOCK_D3: SPI clock on D3
    • BNRG2A1_CLOCK_D13: SPI clock on D13
  • CUSTOM_BLE_SPI: define a custom configuration, it requires below definition:
    • BLE_SPI_MISO: SPI MISO pin
    • BLE_SPI_MOSI: SPI MOSI pin
    • BLE_SPI_CLK: SPI CLocK pin
    • BLE_SPI_CS: SPI Chip Select pin
    • BLE_SPI_IRQ: SPI IRQ pin
    • BLE_SPI_FREQ: SPI bus frequency
    • BLE_SPI_MODE: can be one of the belowSPIMode:
      • SPI_MODE0
      • SPI_MODE1
      • SPI_MODE2
      • SPI_MODE0
    • BLE_CHIP_TYPE: can be one of the belowBLEChip_t:
      • SPBTLE_RF
      • SPBTLE_1S
      • BLUENRG_M2SP
      • BLUENRG_M0
      • BLUENRG_LP
    • BLE_RESET: BLE reset pin

Examples

To use theX-NUCLEO-IDB05A2 with SPI clock on D3, define inble_spi_conf.h:

#defineIDB05A2_SPI_CLOCK_D3

This is equivalent to the below configuration using theCUSTOM_BLE_SPI:

#defineCUSTOM_BLE_SPI#defineBLE_SPI_MISO    D12#defineBLE_SPI_MOSI    D11#defineBLE_SPI_CLK     D3#defineBLE_SPI_CS      A1#defineBLE_SPI_IRQ     A0#defineBLE_SPI_FREQ    8000000#defineBLE_SPI_MODE    SPI_MODE0#defineBLE_CHIP_TYPE   BLUENRG_M0#defineBLE_RESET       D7

Using a SPI BLE module on STM32WB

If required, user can use a compatible BLE module over SPI.

In theble_spi_conf.h, defineUSE_BLE_SPI.

Tests

Peripheral:

HardwareBLEEnhancedAdvertisingRawDatadAdvertisingBatteryMonitorButtonLEDCallbackLEDLED
B-L475E-IOT01ASPBTLE_RF✅✅✅✅✅✅
B-L4S5I-IOT01ASPBTLE_RF✅✅✅✅✅✅
NUCLEO-WB15CCSTM32WB✅✅✅✅✅✅
P-NUCLEO-WB55RGSTM32WB✅✅✅✅✅✅
STEVAL-MKSBOX1V1SPBTLE_1S✅✅✅✅✅✅
STEVAL-MKBOXPROBLUENRG_LP✅✅✅✅✅✅
STM32L562E-DKBLUENRG_M0✅✅✅✅✅✅
STM32WB5MM-DKSTM32WB✅✅✅✅✅✅
X-NUCLEO-BNRG2A1] on [NUCLEO-L476RGBLUENRG_M2SP✅✅✅1✅✅✅
X-NUCLEO-IDB05A1 on NUCLEO-L476RGSPBTLE_RF✅✅✅1✅✅✅
X-NUCLEO-IDB05A2 on NUCLEO-L476RGBLUENRG_M0✅✅✅1✅✅✅

1: using A2 as AO used for IRQ pin.

Central

Note

SensorTagButton not tested as no TI sensor tag

HardwareBLELedControlPeripheralExplorerScanScanCallback
B-L475E-IOT01ASPBTLE_RF✅✅✅✅
B-L4S5I-IOT01ASPBTLE_RF✅✅✅✅
NUCLEO-WB15CCSTM32WB✅✅✅✅
P-NUCLEO-WB55RGSTM32WB✅✅✅✅
STEVAL-MKSBOX1V1SPBTLE_1S✅✅✅✅
STM32L562E-DKBLUENRG_M0✅✅✅✅
STM32WB5MM-DKSTM32WB✅✅✅✅
X-NUCLEO-BNRG2A1] on [NUCLEO-L476RG]BLUENRG_M2SP✅✅✅✅
X-NUCLEO-IDB05A1 on NUCLEO-L476RGSPBTLE_RF✅✅✅✅
X-NUCLEO-IDB05A2 on NUCLEO-L476RGBLUENRG_M0✅✅✅✅

polldoand others added30 commitsNovember 2, 2020 15:30
While the old way of preparing advertising data is still supported, an alternative enhanced method to build advertising packets is now available.It consists in defining and configuring an object of type 'BLEAdvertisingData' to build the desired packet.When it has been configured, by setting the appropriate parameters, it can be used to populate the advertising data packet or the scan response data packet.Following this way, the user can decide in which packet each parameter should be put.Also, it is now possible to configure an advertising packet (advertising or scan response) by passing a raw data packet.If an advertising packet has a raw data parameter set, all its other parameters will be ignored.Also, advertising parameters such as manufacturer data, service data or raw data should have a GLOBAL scope, because they are passed as pointers and are not copied internally.
With write encryptionn requirement
Write encryption & visible LTK / IRK
Fix timing issue during pairing, add pairing control/status methods
Pairing code & IOCaps set via implementation of callbacks
Add Nano RP2040 Connect to "smoke test" examples compilation CI workflow
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
@github-project-automationgithub-project-automationbot moved this fromIn progress toReviewer approved inSTM32duino librariesMar 28, 2025
fpistmand others added22 commitsMarch 28, 2025 11:30
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
to support the shared memory transport layer for theSTM32WB built-in chip.It also Allows HCI SPI Transport with STM32WBxxSigned-off-by: Francois Ramu <francois.ramu@st.com>Co-Authored-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Carlo Parata <carlo.parata@st.com>
On STM32WB, Cube FW version 1.14.1,messages ACI_GATT_INIT and ACI_GAP_INITare not available on HCI only BLE firmware(stm32wb5x_BLE_HCILayer_fw.bin)This imply to move Random Address to host instead of relying on controllerSigned-off-by: Alexandre Bourdiol <alexandre.bourdiol@st.com>
Signed-off-by: Lorenzo Bini <lorenzo.bini@studenti.unimi.it>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Carlo Parata <carlo.parata@st.com>Co-Auhthored-by: Frederic Pillon <frederic.pillon@st.com>
Signed-off-by: Arkadiusz Ambroziak <arekambroziak@op.pl>Co-Auhthored-by: Frederic Pillon <frederic.pillon@st.com>
Linked to:arduino-libraries#310Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
See LE_META_EVENT supported.Note:Value should be 0x3B3 but set to 0x1B3 to explicitlyignore ENHANCED_CONN_COMPLETE eventSigned-off-by: Frederic Pillon <frederic.pillon@st.com>
… processing during ATTClass::discoverDescriptors causes crashingI've highlighted this issue on 9th July ... this is an issue of causing __CRASHES__ if using ArduinoBLE to connect as central and the response to ATT_OP_FIND_INFO_RESP includes 128-bit UUIDs.
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
Now correctly acceses the existing variables and uses an unsigned int for size comparisonfpistm: changed the uint type to uint32_t to avoid build issue with below target:- arduino:megaavr:uno2018- arduino:renesas_uno:unor4wif
Signed-off-by: Frederic Pillon <frederic.pillon@st.com>
@fpistmfpistm merged commit8fdf958 intomainMar 28, 2025
12 checks passed
@github-project-automationgithub-project-automationbot moved this fromReviewer approved toDone inSTM32duino librariesMar 28, 2025
@fpistmfpistm deleted the rebase_1.3.7 branchMarch 28, 2025 10:48
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@cparatacparatacparata approved these changes

Assignees

No one assigned

Labels

enhancementNew feature or requestfix 🩹Bug fix

Projects

Milestone

1.3.7

Development

Successfully merging this pull request may close these issues.

34 participants

@fpistm@cparata@polldo@eltos@tlossen@per1234@LiamAljundi@karlsoderby@akash73@Lukas-kV@facchinm@aentinger@bigbearishappy@bboyho@giulcioffi@jacobhylen@mklemarczyk@alranel@laviator98@dominsch@grobwrk@sallasia@roleroz@manchoz@leonardocavagnis@fabik111@andreagilardoni@FRASTM@ABOSTM@AresMaster@andrewchilds@carterd@FidelSch
[8]ページ先頭
©2009-2025 Movatter.jp