About MSuva.1

MSuva.1 · 2023-01-23

I am currently trying to read the value from a characteristic after detecting that the user has written to it. I am calling aci_gatt_read_char_value() which is returning 0 (BLE success). From here I am expecting an event which triggers the aci_att_r...

MSuva.1 · 2022-12-08

HI,I'm currently struggling to add new characteristics and characteristic descriptors to my BLE profile. Unfortunately it seems that CubeMX does not support adding more than five characteristics and has no support for adding descriptors.This is the m...

MSuva.1 · 2022-09-27

Hi,Every time I attempt to flash the BLE wireless stack to the chip or I try to perform a mass erase I receive the same error and the USB dongle disconnects.FYI - I have successfully been able to upgrade the FUS version with no issue:I attach the log...

MSuva.1 · 2022-09-09

Here is the output of STM32CubeIDE on flashing the custom board:On STM32CubeProgrammer I am not able to consistently get a connection (by hitting the connect button).There are some instances if the configuration is set to "Shared" mode that the devic...

MSuva.1 · 2023-02-02

This explanation and example have fixed my issue. Thanks very much Remy, much appreciated 

MSuva.1 · 2023-02-01

Hi,I've removed these from the GATT attributes now:I want the client to write without me having to give any sort of response and I want to be able to read what they wrote immediately. I've removed the "wait for response" GATT attributes. I assume thi...

MSuva.1 · 2023-01-31

Hi Remy,The ACI_GATT_ERROR_RESP_EVENT seems to have cleared up by itself. I'm not sure i'm going about this the write way at all. Is there a correct way to access the value that has just been written by the client? When the client writes to the varia...

MSuva.1 · 2022-09-28

Apologies, it seems I was reading the V1.14 notes but trying to flash the V1.13 binaries. Thanks very much for your help I think this is closed now 

MSuva.1 · 2022-09-28

Thank you very much! This seems to have fixed my issue.Does this solution mean that the address given in the documentation (release notes) is just wrong? This is what I was working off of: Device info:

User statistics

User Activity

Correct procedure for reading BLE characteristic values.

Adding characteristic descriptor and characteristics manually to BLE profile ERROR

Cannot flash STM32WB55 dongle with wireless stack or perform mass erase.

No issues flashing STM32WB55 M4 via STM32CubeIDE but cannot flash coprocessor with BLE stack with STM32CubeProgrammer.

Re: Correct procedure for reading BLE characteristic values.

Re: Correct procedure for reading BLE characteristic values.

Re: Correct procedure for reading BLE characteristic values.

Re: Cannot flash STM32WB55 dongle with wireless stack or perform mass erase.

Re: Cannot flash STM32WB55 dongle with wireless stack or perform mass erase.