Interface and connectivity ICs

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

Hello,I'm using a STPM32 to measure the ac line voltage and current. It is connected via a galvanic isolator ISO7341CDW to a STM32F072 with SPI. Most of the time, this works just fine. I can read the correct RMS values for I1 and V1 (Register DSP_REG14 at 0x48) as well as the period (Register DSP_REG1 at 0x2E) to convert it to the line frequency. I can change the ac voltage with a adjustable transformer and see the correct values. I'm polling the values every 1 second, but the STPM32 is set to autolatching.So sometimes something seem to go wrong:Sometimes I get the correct voltage value but a strange value for the current. Starting from a value of ~3000 mA it decreases to zero and then again starts at ~3000 mA etc. When I change the ac input voltage, still the correct voltage value is read by the STPM32, but the current value stays wrong. When the ac voltage is decreased to ~85 VAC, the current decreases to 0 and stays there, even when the ac input voltage is increased again.Sometimes

Protocol Used : SPISPI Master : ESP32SPI Slave : STPM32 I am trying to interface with STPM32 using SPI interface.Whenever I make any read request I am getting the value of 0x00 register again and again which is 0x040000A0.As per the datasheet the internal read pointer updates on a read request and points to the register address received in the request and it gives the value of that register on the end of the next request.But that is not happening in my caseExample Code Used : https://www.blog.neudeep.com/embedded/how-guide-on-stpm33-32-spi-interface-with-esp32-using-esp-idf/689/I have used this code and interfaced with the Evaluation board for STPM32 and it works fine. However while interfacing with the custom STPM32 board I am facing the above mentioned issue

Hello,we purchased two ST4SIM-200M eSIMs for testing but we have trouble activating them. In the truphone portal when I enter their ICCIDs, I always receive "This ICCID has already been activated". They should not be activated, they are brand new not yet soldered parts.I have found same issue here at ST forumshttps://community.st.com/s/question/0D53W000015YQwkSAG/brand-new-bl462ecell1-esim-iccid-is-already-in-useThank you for any ideas.

Dear ST Community,I have the following test setup:- 1x SPIRIT-1 transmitter (reads a pin from a STM32 MCU and modulates it over the radio)- 2x SPIRIT-1 receivers (receive the pin state and pass it to the MCU)Expectation: Both receivers should receive the same bit-stream data, sent by the transmitter.Now.. whenever I use a single receiver (either #1 or #2 only), everything works fine every time after restart. However, as soon as I start the second receiver, it somehow does not receive the data. After numerous restarts I have observe the following sporadic behavior:- Receiver #1 works, Receiver #2 does not- Receiver #2 works, Receiver #1 does not- Occasionally and rarely, both Receiver #1 and #2 workI expect that since I am using a single pin for data transmission, I have properly bypassed the framing subsystem. So... is it related to some "negotiation" procedure, like on-boot CRC polynomial generation or anything similar? May someone suggest what I may be missing?Thanks and regards!

..

Title shortened in accordance with community guidelines.Original title: "How does UART work without the HAL layer? Does the shift register clear itself once it has transmitted its data? And what's the timing I need to have?"Some context, I'm using a RS485 data line in half-duplex mode to communicate between an STM32F107 (the master card here) and an STM32F072 (the slave card). My end goal is to be able to use the bootloader on the slave card and reprogram it from the master crad (the binary file I'll use is stored on an SD card, I already have a library ready to use but I want to make sure I can make the two boards talk properly). So, here's what I gather is the problem : I'm touching the registers for communication directly, to avoid HAL (that's just how the project I'm working on is, I never used HAL and neither has anyone in the team). The F107 uses only a DR register for reading and writing, so when I send a data on the DR register this byte is transferred to a shift register

Hi,I was looking at the display interface overview and saw that the max resolution for an SPI connection seems to be 480*272. https://support.touchgfx.com/4.19/docs/development/hardware-selection/hardware-components/hardware-selection-displayI'm currently looking at some displays that are SPI 456x456 resolution, so I was wondering if that resolution limitation was in the TouchGFX infrastructure itself or if not, where the bottleneck was.Thanks!Daniel

Background:I have two STEVAL-IDB011V2 BlueNRG-LP boards. One of these evaluation boards is no longer recognized by MS Windows10 host machine at the serial port (i.e. Device Manager shows a problem with that USB device). As a result, the ST RF-Flash Utility (in fact, all of the ST Micro development software) cannot communicate with this board. Thus I have no easy way to reflash the firmware on this board.The last firmware I loaded on the malfunctioning board still communicates with my cell phone over BLE, so the Cortex M0 and BLE stack seem to be intact. However, it appears the circuitry associated with the UART is unhappy.The second evaluation board I have (identical hardware to the one that is malfunctioning) is recognized fine by the Windows10 host machine.Questions:Is there a way to recover the board, or am I going to have to purchase a new one?Has anyone seen this type of behavior in the past and how do I avoid this in the future? Thanks for any help or recommendations you can give

Hi there!May I know how to determine the best number of TTL(time to live) in BLE MESH application?What criteria should I consider before setting TTL? Thank you!Cheers,Mo

The STUSB47 GUI (STSW-STUSB001) is an easy tool to configure quickly the STUSB47 evaluation board.But if you don't use the ST Evaluation board, and you want instead to configure the STUSB47 on a custom board, the tool will not work because it is using the micro-USB connector located on the STUSB47 eval board ( and not the USB connector located on the Nucleo board).You can still use the STM32-Nucleo-Board and the GUI to configure easily any STUSB47 device, as long as you have access to the I2C interface of the chip (see picture below).For this purpose, you'll need a specific version of STM32 firmware and the GUI (the uart version), to be able to connect using the default USB connector (CN1) of the Nucleo board, and the Virtual COM port (VCP) interface.The software is in attachment. - STUSB47 GUI with VCP (uart)Best Regards.

Hello,I have a custom board based on STM32L073 MCU with S2LP radio device to provide SIGFOX functionality. I am looking to provision my on chip S2LP device (i.e get ID/PAC/KEY) information from ST. I have referred "Getting started with the Sigfox S2-LP kit" and also this video https://www.youtube.com/watch?v=JD6UE7ekRxE but all the information is related to NUCLEO boards and not regarding any custom S2-LP board. Tested: When i flash SIGFOX_CLI_DEMO_NUCLEO_L0.bin to my custom board and try to open the COM Port (ST-DK) in SIGFOX GUI App i get the error of "Wrong FW in the selected board". So can anyone please tell me how can i get ID/PAC/KEY for S2LP custom board based on STM32L073 MCU as i am unable to perform the same.

Hi friend,I want to implement watchdog function at Ble_beacon project of the BlueNRG-1_2 DK-2.5.0 platform. Where I need to call the function of WDG_SetReload to reset the watchdog timer? My project has I2C slave and HAL_VTimerTimeoutCallback. Thank you in advance.Ted Wu

Hi,I am using the BlueNRG-2 alone as an MCU.I want to import X-Cube-AI into the BlueNRG-2.However, there isn't the 'BlueNRG-2' name list in the MCU selection in the STM32CubeMX.Is it possible to import the X-Cube-AI into the BlueNRG-2?Thanks

I am trying to know the status of MCP3424, either it is connected or not to the master STM32 with defined address 0x68. The ADC module gets connected with the Arduino in same address but using STM32, I am not able to get connected with the following code: if((HAL_I2C_IsDeviceReady(&hi2c1, 0x68 << 1, 100, 1000))==HAL_OK){ HAL_UART_Transmit(&huart2, "device connected\r\n", 10, 10); } else{ HAL_UART_Transmit(&huart2, "no device\r\n", 100, 10); }

..

I've been looking for some data sheets related to the IC with the MAX5969ETB series IC. is it the same type of ic? because I can't find the pin of the IC

In below attached screen shot, at last point it is advised to download ​s2-lp_project_stm32l053 from Google Drive. How you get that? Please suggest.

Hello everyone,I'm working on a project with BLE technology,I have a ST-BlueNRG-LP device which is controlled by a host STM32 through HCI/ACI commands.I was wondering if it is possible to set my Host STM32 in a sleep mode while the ST-BlueNRG-LP is scanning surroundings, and then at the end of the scanning, by RTC or any event IT, the MCU wakes up and reads the advertising reports.I've not seen it yet.Maël

Hello,I am using a BlueNRG-2 acting as a central to connect with multiple BLE devices, these devices can connect and disconnect multiple times.I am using up to 6 simultaneous connections to different devices, after some successful attempts I keep getting errors from the ST API during the connection stage, usually at the pair/bonding stage.The errors are either:BLE_STATUS_NOT_ALLOWED (0x46): no further information is available and I cannot understand why is this operation not allowed when calling 'aci_gap_send_pairing_req()'?BLE_STATUS_DEV_IN_BLACKLIST (0x59): how can I access and handle this blacklist, information on this is nonexistent, can I remove devices from the blacklist or prevent them from being stuck there?When a connection fails the system seems to enter a loop and cannot recover.Most commonly, what happens is that when there is an error, the initial connection is successful, but the process fails when negotiating at the encryption step (I am using default encryption with fix

Hello ST,I am working on BLE_MeshLightingProvisioner sample project and trying to set heartbeat messages mention below:MOBLE_RESULT BLEMesh_SetHeartbeatCallback(MOBLE_HEARTBEAT_CB cb);Could you please help me to figure out how to use this function from Provisioner side or share the example code to test this function.Best RegardsDeepak Aagri

..

We are using the LIV3F in our project. We need an effective output data rate of at least 2 updates per second. I set the update rate at 4 updates/second ($PSTMSETPAR,1303,0.25,0*1F\n\r"). I selected only GPRMC and GPGGA messages. me($PSTMCFGMSGL,0,1,00000042,00000000*4A\r\n",39). Without GPS lock it does output at 4 updates/second. However as soon as GPS is locked, the data rate becomes very variable and has an average of 1.5 updates/second.Itried switching off the low power mode ($PSTMCFGLPA,0,1,10,2,8,60,180,0,0,15,9,100,0*20\r\n",49) without difference.Of course I save the parameters ($PSTMSAVEPAR*58\r\n",17)All other parameters are default. Software version 4.6.8.2 What do I do wrong?