WATCH ON-DEMAND | STM32 Summit 2026
Ask questions and find answers on connectivity ICs, focusing on protocols and I2C challenges on STM32 Nucleo boards and BlueNRG products.
Most recent activity
..
How can i assign addresses in EEPROM code of BlueNRG 232 for different vaiables location.As in the sample code bluenrg232 only device address is used not the register address where we will save varaible values memory.function taken from sample i2c code of bluenrg232./** * @brief I2C Master communication. * @param uint8_t dev_address: I2C device address * @param uint8_t send_val: value to send * @param uint8_t get_val: value to get * @retval I2C_OpStatus: I2C operation sattus */I2C_AppOpStatus I2C_Read_Reg(uint8_t dev_address, uint8_t send_val, uint8_t* get_val){ I2C_TransactionType t; /* Write I2C device address address */ t.Operation = I2C_Operation_Write; t.Address = dev_address; t.StartByte = I2C_StartByte_Disable; t.AddressType = I2C_AddressType_7Bit; t.StopCondition = I2C_StopCondition_Disable; t.Length = 1; I2C_FlushTx((I2C_Type*)SDK_EVAL_I2C); &
Is there anybody, how has this file for sharing with me? Thanks Joachim
I'm using the snaphat M4T32-BR12SH6 (battery + crystal) with RTC M41T94.The battery life is short, after less than 1 year, the battery voltage is lower than 2.5 V and the RTC does not work well.And according to the datasheet, the minimum expected life is 10 years!I suspect that the manufacturing date is old, probably manufactured in 2013, but could it still operate for another 3 years or not?
Hi,I would like to know is there any way to port the STEVAL-IDP005V1 code to other STM32F469 controller. I know it is not possible directly inside STM32CubeIDE? any suggestions?The existing micro is not cheap and BGA is very complicate.Thanks.Naveen
In one of my project I have to connect my bluenrg2 with custom android app.In order to make this which example code I have to refer?I use BLE-chat example but it couldn't pair from the default bluetooth settings.Then I tried with BLE_SENSOR_DEMO_CENTRAL but it showing the 'Device Discovery procedure timeout' .Anybody can help me?
i am working with bluenrg2 chat example.After uploading the bluetooth is not discoverable in our custom made app .It is asking pairing key while trying to connect from the default bluetooth list of phone.Could you please update why I can't connect or pair blueNRG2 from the default bluetooth list of my phone?
Dear ST, Do you know amount of is the maximum allowable capacitance on the ~RST output for SR1 reset controller? By tradition we put 0.1 uF on the NRST pin, but is it OK with SR1?We use SR1PBBU with OD output.Thanks in advance!
Hi everyone,I'm currently using the BlueNRG-M2SP Bluetooth 5.0 module for the design of a body-worn wearable medical device (patch which should be used for up to 7 days). I'd like to know if there's any specification regarding the minimum distance of the module to the body following the CE marking directives?In the product's datasheet it is specified that for FCC and IC, additional tests are required for body-worn devices (distance < 20cm), but no indication is given for CE. Can you please give me further information?I believe there is, and I think it is dependent on the SAR (Specific Absorption Rate), but couldn't find any information about it. Furthermore, I don't know if there's something more to take into account in order to know the minimum acceptable distance.Can anyone help me, please?Best regards,Bern
Hi,We have assembled 10 Boards with LIS2DH12TR out of which only 6 Boards are working Rest 4 aren't at all working.we tried resoldering the sensor again and checked still the same issue.What would you suggest to do?
For battery management I using BQ25713Power profiles, which I tried is: 20V 1A (PDO3 default) and 20V 3.25 (also PDO3 manually configured on STUSB4500, this profile appropriate to maximum power of my USB PD adapter 65W 20V 3.25A)This problem exists for USB PD adapters from differences vendorsPeak current, which I detected when BQ25713 trying to start charging is less than 3AWhen I supplied battery manager from DC power supplier (bypass STUSB4500), battery normal chargingWhat I see on VBUS, when plug USB Type-C connectorWhen STUSB4500 block disconnect from load (all other terms not change) on it output I can see stable 20V
Hello, I'm working with BlueNRG-M0.All is fine when I work with 1 little service. Today I need to implement lot of services and I'm stuck with the error 0x1F from aci_gatt_add_serv() function.My init is this:/*----- CODE -----*/ uint8_t SERVER_BDADDR[] = {0x12, 0x34, 0x00, 0xE1, 0x80, 0x02}; uint8_t bdaddr[6]; uint8_t role = 0x02; int ret; hci_init(Srv_BLE_Core_user_notify, NULL); hci_reset(); HAL_Delay(100); BLUENRG_memcpy(bdaddr, SERVER_BDADDR, sizeof(SERVER_BDADDR)); ret = aci_hal_write_config_data(CONFIG_DATA_PUBADDR_OFFSET,CONFIG_DATA_PUBADDR_LEN,bdaddr); ret = aci_hal_write_config_data(CONFIG_DATA_MODE_OFFSET, CONFIG_DATA_MODE_LEN, &role); ret = aci_gatt_init(); ret = aci_gap_init_IDB05A1(GAP_PERIPHERAL_ROLE_IDB05A1, 0,NAME_SIZE_MAX, &service_handle, &dev_name_char_handle, &appearance_char_handle);ret = aci_gatt_add_serv(UUID_TYPE_128,(uint8_t *)UUID_SRV_PWR,PRIMA
Hi,I would like to use the STUSB4500L to power a battery powered application as well as talk to it over I2C, however since I'm running low on I2C buses I want to share the I2C bus with it and my other battery management ICs. From reading the datasheet, it would appear that the recommended configuration in my case would be to only power the STUSB4500L from the USB-C port and not the battery, which means that when on battery power the STUSB4500L would be unpowered. Will the I2C pins be in a hi-Z state in this case, allowing me to still talk to the other battery management ICs (which are always powered) or should I put some sort of isolator in?Thanks
I'm starting a new SW project for a BlueNRG2 module and it's not clear what the currently preferred development toolchain is. I want to make sure I'm not using deprecated tools.The BlueNRG2 will be used as an application processor (i.e. not connected to a host processor) that will monitor the state of IO pins and expose them over BLE. The software needs to implement that application logic as well as BLE functionallity.It looks like STM32CubeIDE does not support programming of the BlueNRG2 module. There's an X-CUBE-BLE2 module, but I think that's for code running on an STM32 that's interfaced to an BlueNRG2 configured as a network processor. Is that correct? I'm currently using Atollic TrueStudio.I don't see an SWO pin, so debug console output through RTT is not supported, correct?BlueNRG DK 3.2.1 is the source of example projects, which I'm running on both a dev board (STEVAL-IDB008V2) and on a BlueNRG-2 module located on a custom board. Is this the best p
Hi, I am making a USB power hub which support USB C Power delivery. There is a upstream USB C which support Sink and Source role:if there is a DC input, this is a Source, STUSB4700 is enabledif there is no DC input, this is a Sink, STUSB4500 is enabledI have already made the prototype for this. The SNK is working fine. If there is no DC power plug as input, the hub is in SNK mode. It is able to ask for 20V (MAX) from the PD power source. However, if there is a DC input power which is 20V (MAX), the Source mode does not work. I checked the STUSB4700 power pin. It has 5V in VDD and the internal 2.7V LDO and 1.2V LDO is working fine which I can measure it (while there is no power on the STUSB4500). If I check the CC pins voltage, I can see they are 1.5V and 0.8V. One of the CC pin, with the 0.8V, I also see the square wave on it in about 200kHzThis seems to be preamble but there is no response to it. I am wondering if the problem might be the CC pin is connecting to the Rd and Rp at
Also, will the VBUS_EN_SNK pin get asserted (pulled low) in this case, allowing the power path to enable 5V from the USB 2.0 cable to power the device?
Hello,I have build a custom pcb and I am using the BlueNRG-M0 module and the STM32L162VET microcontoller. My main goal is to be able to transfer data via bluetooth to a computer.To get starter, I tried to generate the VirtualCOMPort example that is available with the STM32CubeIDE using the BLE stack and sample application for Blue-NRG-MS module version 6.0.0.I have followed the instructions on the following video:https://www.youtube.com/watch?v=jGSdMAFVI_U&t=646sThe code is generated successfully but when I build the project I get the following error: 'COM1' undeclared (first use in this function); did you mean 'COMP1'?Is this a common error and how can i overcome this?Could you please give me some information on how to get started using a simple bluetooth application to transfer data between my device and a computer?Thank you
HiRegarding the P-NUCLEO-USB002, the schematic available in the resource section of this product does not seem to match at all the product advertised. The file is named MB1303 in the resource list.The file downloaded is namned MB1136.The P-NUCLEO-USB002 has two USB-C connectors, the schematic shows none, just as one example.Where can I find the correct full schematic of the P-NUCLEO-USB002 board, so I can check out what it is and how it works?Thanks!
Hi together,I'm using the NUCLEO-F401RE and NUCLEO-IDW04A1 trying to connect and publish to a MQTT Broker. Therefore i've edited the example HTTP_Request. Connecting to my WiFi-AP is working fine, but connecting to the Broker does not work. This is what my console output looks like after connecting to the WiFi-AP:wifi connected... >>connected...AT+S.STS=ip_ipaddrAT-S.Var:ip_ipaddr=192.168.178.122AT-S.OK>>IP address is 192.168.178.122AT+S.GCFG=nv_modelAT-S.Var:nv_model=SPWF04SAAT-S.OK>>model no is SPWF04SAAT+S.MQTTCONN=mqtt.eclipse.org,1883,,,,,,,,,,AT-S.ERROR:111:Request failed+WIND:87:MQTT Closed:0:0This is how I'm trying to connect the Broker:char console_host[20];char * hostname = "mqtt.eclipse.org";uint32_t port_num = 1883;memcpy(console_host, (const char*)hostname, strlen((char*)hostname));wifi_mqtt_connect((uint8_t *)console_host, port_num);Does anyone of you have an idea what I'm doing wrong?Thanks for your help!Fabian
In the case where USB power is first applied and a 20V contract established, the STUSB4500 would enable the power path to Vsnk as per usual. Then assume a 20.9V (for example) secondary power source is applied to the Vsnk output (say from a wall adapter/secondary charging port). 20.9V is within the default +5% VMONUSBH threshold, so it looks like the STUSB4500 would keep the VBUS_EN_SNK path enabled and current would flow back out of the USB port. Is this correct or is there another mechanism that would prevent this from happening? Another way to frame the question - assume the following sequence takes place:1) A 20V contract is established after a USB 3 PD-capable charger is attached, as per usual. 2) A 20V wall adapter is plugged in which also drives Vsnk to 20V. 3) The USB3 charger is unplugged. Will the STUSB4500 detect this removal even though Vbus will still be driven to 20V through the previously enabled MOSFETs? If not, what then happens if the USB cable is plugged into a 5V out
Hello,I'm working on extrem low power radio with S2-LP transceiver. To obtain a very low consumption in rx mode i puted it in sniff mode. My design has external TCXO reference and when i left it always on all work fine, but if i set gpio to switch off/on TCXO, gpio doesn't work and TCXO stay off. Please, somebody has some idea? Thanks
In Spirit1:SpiritRadioGetChannel() is flawed:uint32_t SpiritRadioGetChannelSpace(void) { uint8_t channelSpaceFactor; /* Reads the CHSPACE register, calculate the channel space and return it */ g_xStatus = SpiritSpiReadRegisters(CHSPACE_BASE, 1, &channelSpaceFactor); /* Compute the Hertz value and return it */ //BUG: return (((uint64_t)channelSpaceFactor*s_lXtalFrequency)/CHSPACE_DIVIDER); return ((((uint64_t)channelSpaceFactor)*s_lXtalFrequency)/CHSPACE_DIVIDER); }And in S2-LP S2LPRadioComputeChannelSpacingRegValue() is flawed:uint8_t S2LPRadioComputeChannelSpacingRegValue(uint32_t lChannelSpace) { //BUG: return (uint32_t)(((uint64_t)lChannelSpace)<<15)/s_lXtalFrequency; return (uint32_t)((((uint64_t)lChannelSpace)<<15)/s_lXtalFrequency); } There might be other places as well, but these are the two I encountered for now... It's clear this code is not tested, also examples on how to use channels are lacking.&n
I'm a bit confused regarding some nuances of the BlueNRG-2's BLE characteristic value write procedures' functions & events. Below is my understanding with a few questions.Bluetooth Core Specification v5.2 | Vol 3, Part G; 4 GATT Feature Requirements 4.9 Characteristic Value Write4.9.3 Write Characteristic ValueClient calls aci_gatt_write_char_valueServer event aci_gatt_write_permit_req_eventaci_gatt_prepare_write_permit_req_event will not be generated based on Figure 4.15 correct?Server calls aci_gatt_write_respIf the server allows the write…Client event aci_att_exec_write_resp_eventAPI documentation says aci_att_prepare_write_resp_event would occur from a call to aci_gatt_write_char_value; assuming this is inaccurate, otherwise ignore event…?Client event aci_gatt_proc_complete_eventServer event aci_gatt_attribute_modified_eventIf the server rejects the write with an error code…Client event aci_gatt_error_resp_eventaci_att_exec_write_resp_event & aci_att_prepare_write_resp_even
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.