Interface and connectivity ICs

Hello,I am trying to build my Bluetooth application by configuring the services and characteristics I need. I saw ST recommends using BlueNRG-X Radio Initialization Parameters Wizard.I am using BlueNRG-M0 (X-Nucleo-IDB05A2) and I read the FW version and HW version from the board.HW Version - 49(dec)FW Version - 1840(dec), 0x730 (FW 7.30)I want to know what FW stack version do I use in the Radio Init Wizard program (see attached picture). I assume the BlueNRG-M0 is a BlueNRG-1 device. Is that correct?Eventually I am looking to support 8 GATT custom services on the device. I think the device can support up to 8 services as I read that in the release notes from ST (can't remember where).Thanks,

I am trying to edit the BLE Sensor Demo app for STM32 micro and BLUENRG-M0 module (using Nucleo boards). I want to advertise one service in the advertising packet. When I make the call to aci_gap_set_discoverable() I get a response of BLE_STATUS_INVALID_PARAMS( 66 dec ) . The only change I made to the example source code is to add in the HW service UUID as used in the sample code. void Set_DeviceConnectable(void) { uint8_t ret; const char local_name[] = {AD_TYPE_COMPLETE_LOCAL_NAME,SENSOR_DEMO_NAME}; uint8_t svc_uuid[] = { 0x07,0x00,0x00,0x00,0x00,0x00,0x01,0x11,0xe1,0x9a,0xb4,0x00,0x02,0xa5,0xd5,0xc5,0x1b};   uint8_t manuf_data[] = { 2,0x0A,0x00, /* 0 dBm */ // Trasmission Power 8,0x09,SENSOR_DEMO_NAME, // Complete Name 11,0xFF,0xFF, /* SKD version */ 0x52, 0x41, 0x4c, bdaddr[5], /* BLE MAC start -MSB first- */ bdaddr[4], bdaddr[3], bdaddr[2], bdaddr[1], bdaddr[0] /* BLE MAC stop */ };   //manuf_data[18] |= 0x01; /* Sensor Fusion */ //COPY_HW_SENS_W2ST_SER

With DMA or interrupts I can only receive the first byte of a message. What do I need to change in the preipherals/SPI_slave_dma example to receive more than one byte?Any help appreciated. Thanks

Hello everyone,I recently successfully used a BlueNRG-2 chip for a BLE project (connected to an external microcontroller and integrating the BlueNRG-2 API by means of .ioc project manager). However, it needed a very small baloon which has been a real mess to solder by hand. I then saw that the BlueNRG-LP comes with the baloon integrated, which could help me hand-soldering the PCBs. However, the BlueNRG-LP doesn't come with a preflashed image. Is there any available image by ST that I can flash on the BlueNRG-LP that will let me keep using the same (or at least similar) APIs used on the BlueNRG-2? I think that including the libraries via STM32CubeIDE Project Manager really speeds up the programming time.Thank you for reading,Mariano

i use stm32f030 with bluenrg-1 on a card i made i want to test and communicate with it using the BlueNRG GUI --------------------------------------------------------------------------------------------------------------------------But I have problems to connect with the GUI. I choose the right COM Port, open it and then it always says: "No device detected!" and "No firmware detected. Update firmware on the motherboard (Under tools menu)." I tried to use that tool called "Flash Motherboard FW" and followed the steps and there it always says "No DFU Bootloader found"Anyone has some advice to solve that problem?Thanks in advance!

Hello every onewe are using BlueNRG-1 for Our BLEFor the Information,We have connected 32MHz external crystal oscillator in HS Pins..We haven't connected any external crystal oscillator at LS Pins..And we haven't connected any inductor at SMPS pins of BlueNRG2. we are not able to start the BlueNRG2 application and the MCU is stuck at the while(CKGEN_BLE->CLK32K_IT == 0); point in DeviceConfiguration() function.

I am hoping this has a simple answer. If I develop a solution based on the BLUENRG-355MC and attribute that design is based STMicroelectronics SOC solution, are there additional fees I need to be aware of? I checked the following link:https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/ and saw that this https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/ SOC was qualified with Bluetooth SIG. Would I be subjected to additional fees from Bluetooth SIG?

Hello! I'm using module Bluenrg-355MT in my project. There is the antenna ACAG0801-2450-T on my board. This antenna transmits enough over a long distance (D>250m). But reception of this antenna is not more than 15m. Is it possible to achieve long range reception with such type of antennas? Have you tested this module with small size chip antennas? Thanks in advance!

I am trying to evaluate the BlueNRG-332AC using the IDB012V1A eval board.I have setup the BlueNRG GUI software. However, when trying to connect to the COM port, provided by the eval board, it says "No device detected!" followed by "No firmware detected on the motherboard. Update motherboard Firmware (under Tools menu)."After performing the firmware upgrade (Tools -> Flash Motherboard FW) with "BlueNRG GUI 4.3.0\Firmware\STEVAL-IDB012V1\USB_CMSISDAP\USB_CMSISDAP_LPS.hex", which processes successfully, nothing changes. (Also repowering, etc.)In the BlueNRG GUI manual (UM2058) I have read, that the target MCU firmware has to be programmed, before being usably together with BlueNRG GUI. This is referred to in chapter 2.1.3.Here, programming the "DTM_UART_WITH_UPDATER.hex" (or _SPI_) firmware is suggested to be flashed, by putting it on the virtual SD card. However, the flashing operation fails. The virtual SD card disappears, then reappears without .hex file but with "FAIL.TXT" stating

I'm working on a new IOT device. I'm using your BLUENRG-232N device with STM32L496AGI6 microcontroller, and I'm using your STMicroelectronics.X-CUBE-BLE2 version 3.2.2 stack for the firmware and the application. but unfortunately the mcu goes into the Infinite_Loop: during the call of the MX_BlueNRG_2_Init function. Find attached the demo_project and schematic.

Hi All,I want to ask "is it possible to run BLUENRG-355 on internal oscillator (64Mhz) "As per data sheet it supports internal HSI but device firmware says HSE only. /* High speed crystal configuration: BlueNRG-LP supports only HSE 32 MHz */ SystemTimer_TimeoutConfig(32000000, 100, TRUE);

Hi I am looking to used X-Nucleo-IDB05A2 board for BLE development.After reading about the information provided on the board page the only example project folder I got, i.e en.x-cube-ble2After going through all the project given in the folder I didn't got any firmware code for X-nucleo-IDB05A2, only I can see the reference code for X-nucleo-IDB05A1 and X-nucleo-IDB04A1.So can I use same library as for X-nucleo-IDB05A1 or any changes required?

There is a bug in S2LP_Library which is part of the STSW-S2LP-DK package. In the following function you need to shift xCcaLength to the upper nibble, but there is no shift in currently available version. The bug won't allow you to set CCA length.Please fix that in next STSW-S2LP-DK release./** * @brief Set the CCA length. * @param xCcaLength the CCA length (a value between 1 and 15 that multiplies the CCA period). * This parameter can be any value of @ref CsmaLength. * @retval None. */ void S2LPCsmaSetCcaLength(uint8_t xCcaLength) { uint8_t tmp; s_assert_param(IS_CSMA_LENGTH(xCcaLength));   S2LPSpiReadRegisters(CSMA_CONF0_ADDR, 1, &tmp);   tmp &= ~CCA_LEN_REGMASK; tmp |= (xCcaLength << 4);   *(uint8_t*)&g_xStatus = S2LPSpiWriteRegisters(CSMA_CONF0_ADDR, 1, &tmp);   }

We know that ST4SIM supports embedded Secure Element(eSE) applet to store and protect sensitive data and provides security services. We think the access to eSE via SPI by STM32 MCU is possible. How can we use this feature?

Hi,I am developing on top of the BlueNRG LP Serial Port example. I have added a few services & characteristics according to requirement. However, while connecting the BlueNRG to a host application (NRF connect), connection & service discovery takes a very long time - around 5 seconds or so.I have reduced the connection interval times to 5 ms and tried, but the results are still the same.Any help would be appreciated.Thanks!

..

Hello, I am developing a platform with BLE Beacon connectivity and I am looking to extend the range of our device. Until now, I have been using BLUENRG-M2SA module, which is BLE v5.2 ceritifed. I know that BLE v5.1 >= versions include "long range" mode ( 125 or 500 kbps datarate ), usually described as Coded PHY, but couldn't find any mention of it on M2SA documents. Does BLUENRG-M2SA module support BLE Coded PHY ? If yes, could you point me to a respective document or source file ?

VNI8200 has been impossible to source even small quantities (100s) . My customer is exasperated and looking for alternatives. Are there changes in availability expected, other similar ST parts in the pipeline, or should I design it out?

I am a bit confused about the number of connections the BlueNRG-LP can handle.The device is advertised with 128 concurrent links.I visited a ST talk where the discussed number was about 50 Connections.I used the BlueNRG-LP 1.0.0 Radio Wizard that limits the 'Links Number' to 24.I used the BlueNRG GUI 4.0.0 that limits the 'Num of Links' for the GUI and Python API to 8.What is meant by concurrent links?Concurrent 1 = Connections can be open simultaneous, but conflicting if the radio has to handle multiple packet at one moment. (retransmission)Concurrent 2 = Fully independed channels, working line #n transceiversConcurrent 3 = The device can store information about this number of connections. But the number of devices with an open connection may be much smaller.Of course the number of supported links will vary depending on the circumstances.But could you help me to get a little clearer about this?My BlueNRG-LP in central role has to bond and connect to 50 peripheral devices. These 5

At the moment with the X-NUCLEO-PLM01A1 + Nucleo-F401RE boards is supplied a firmware stack with only PHY and DATA link.What full stack do you suggest to use with ST7580?An old job of Nunzio Dipaola (Application Note AN4411) build a 802.15.4 stack over ST7580, but this job is not anymore present on ST resources.Thanks in advanceM.S.

Recommendet is 66µm CU with 305µm distance to ground layer. I would like to have 35µm CU with 180µC distance to ground layer.

I am using a BlueNRG-LP MC355 SoC. When connected to my debugger, I can call NVIC_SystemReset() just fine. However, if I disconnect the debugger, the device hard faults on reset.uint8_t ret = BLE_STATUS_SUCCESS; uint16_t service_handle, dev_name_char_handle, appearance_char_handle;   static uint8_t adv_data[] = {0x02, AD_TYPE_FLAGS, FLAG_BIT_LE_GENERAL_DISCOVERABLE_MODE | FLAG_BIT_BR_EDR_NOT_SUPPORTED, 6, AD_TYPE_COMPLETE_LOCAL_NAME, 'H', 'O', 'W', 'D', 'Y'};   /* Set the TX power 0 dBm */ aci_hal_set_tx_power_level(0, 24);   /* GATT Init */ ret = aci_gatt_srv_init(); if (ret != BLE_STATUS_SUCCESS) { PRINTF("aci_gatt_srv_init() failed: 0x%02x\r\n", ret); return ret; }   /* GAP Init */ ret = aci_gap_init(GAP_PERIPHERAL_ROLE, 0, 0x07, STATIC_RANDOM_ADDR, &service_handle, &dev_name_char_handle, &appearance_char_handle); if (ret != BLE_STATUS_SUCCESS) { PRINTF("aci_gap_init() failed: 0x%02x\r\n", ret); return ret; }   /* Update devic

Hi everyone,I try to implement the stack Bluetooth 4.2.0 X-CUBE-BLE1 with the sensorDemo application on a Nucleo-L452RE evaluation kit, coupled with X-NUCLEO-IDB05A1 Bluetooth Board.The code C has been generated thanks to STM32CubeMX 5.0.0 standalone with the help of the manual "UM1873: Getting started with the X-CUBE-BLE1 Bluetooth Low Energy software expansion for STM32Cube".The compilation is realized thanks to the ac6 OpenSTM32 (Eclipse + gcc-arm).When the code is implemented with no others modifications, the bluetooth module doesn't work. After investigation by a step-by-step running, it appears the initialisation is not finalised: the software goes to nowhere land once the SPI reset is realized (hciContext.io.Reset() of the hci_init function). I would have the feeling the software stays somewhere in interrupt. I have found, also, a weirdo thing: the SPI and UART initialisation functions don't appear in the CubeMx generated code. I tested to add manually the SPI and UART init func

..

Please help me with the setup required to flash the latest firmware version for the BlueNRG devices. I would request your help to explain me the setup required for both the usecases exlained below -There are some devices we have in stock and they need to be updated with the new firmware version 7.23There are few devices already in our product and they are soldered. They have FW version 7.15. There are some issues with FW version - 7.15. So need to update to 7.23