Interface and connectivity ICs

I'm using the BlueNRG-M2 as my processor on an enclosed system with UART communication. My goal is to add the ability to update the firmware via this connection using the built-in bootloader.Using this answer, I am able to activate the bootloader within the application code, but I am not getting full capability out of it using the BlueNRG Flasher utility. The autobaud and Read Memory functions work, but the Write Flash command does not. All of these work when launching the Bootloader on start via DIO7.Initially, I was getting even less ability, but I realized if I reset the High Frequency clock to 16MHz (from the Application's 32MHz), it worked more reliably. My assumption is that there are more parameters my application code changes from their default which the Bootloader relies upon. Is there any list of these requirements, or even better a function within the Keil DFP that will reset the processor to the required state for the Bootloader?

Hello,In different project with S2-LP we want to read raw the for understand and anlyze any data of the communicate between 2 devices.Are we take tke raw data?Is the S2-LP support E527 standart?Thanks Melih

HiAs i can see your eSIMs come with Truphone preinstalled, so i wonder if its possible to use differrent provider.And if it is, how can you do so on examle of B-L462CELL1

Error observed: From dmesg: tpm tpm0: tpm_try_transmit: send(): error -62OS Version:5.15.71TPM Chip: ST33KTPM2XI2CConnectivity: CPU->I2C-> TPM2.0Driver: https://github.com/STMicroelectronics/TCG-TPM-I2C-DRV/tree/5.10.yStep to reproduce the issueExercise tpm_pcrextend and tpm_pcrread and then issue tpm reset using GPIO pin of our platform.and tried to access the tpm after tpm_startup. However observed below erroError observed: From dmesg: tpm tpm0: tpm_try_transmit: send(): error -62unloading and loading the tpm_tis_i2c driver have access to tpm and issue disappeared and tpm is accessible.However I have investigated tpm_tis_spi driver, even after resetting tpm through GPIO, No issues found.Explored driver probe between i2c and spi, init sequence looks different as controller is different.Pls help resolving the issue.Incase this is not the correct forum, help me to reach out to correct community.ThanksSelvan    

I did not see this question answered. I did see a related discussion which motivated me to ask: https://community.st.com/s/question/0D53W00001JVdk5SAD/bluenrg-advertise-while-having-a-connectionI was using the BlueNRGLP DK sample application: BLE_RC_LongRange with two separate BlueNRG NP boards (Server and Client) and a Cell Phone to view BLE advertisements. I am connecting and disconnecting the Client BlueNRG LP board to connect and disconnect from the BlueNRG Server board.I noticed the Server seems to stop advertising once a connection is made with the client but the Server does not explicitly call the Stop_Advertising function in the Server code (verified by breakpoints in the Server code). Question: Does the disabling of Advertising when a connection terminates happen automatically by the BLE stack?

Hi,I am using the Bluenrg-332ac and the eval board BlueNRG-LPS STEVAL-IDB012V1.  I used the 'hci_le_connectionless_iq_report_event' function to extract IQ signals and RSSI. However, the magnitude, which is derived from the IQ samples, fluctuates dramatically even if I put two antennas close (but not stick to each other). (It sometimes can be stable but very sensitive to the position). What is the problem for solving this issue when trying to access the IQ signals?  

This is a question about a TPM IC, if this is the wrong channel please advise as to correct channel. The question relates to the Linux driver for the ST33TPHF2XI2C.Setup:Driver Verion - unlnown - downloaded from GITHUB 06-JUN-2022.IC as ordered: ST33HTPH2X32AHE1Hardware: On a HAT for a Raspberry PI 4, connected to i2c channel 1 (SLC1, SDA1 GPIO pins)OS Linux 5.4.72-v7l Error observed: From dmesg: tpm tpm0: tpm_try_transmit: send(): error -62Generated by: Issuing the tpm2_getrandom 10 command after having reset the ST33TPHF2XI2C via its physical reset pin, which is tied to GPIO 17 on the RPI HAT.Questions:Is this a known issue or has this issue been reported in another bug (my search did not find this issue).Is there a known patch/workaround?Is STMicro supporting this driver - it doesn't appear to have been accepted into the Linux kernel and there doesn't appear to be a lot of activity with it.

Hello!I have been trying to run the example codes from BLE_examples. It works well on BlueNRG_Navigator GUI. Unfortunately, It throws this error to every projects I try to run and deug on WISE-Studio. What must be the problem that causes this error?  

Hello,I configured the s2-lp csma as follow: xCsmaPersistentMode = S_DISABLE xMultiplierTbit = CSMA_PERIOD_128TBIT xCcaLength = 1 cMaxNb = 2 nBuCounterSeed = 0xFA21 cBuPrescaler = 2 I set the rssi threshold at -82 dBm, If the channel is free, it listens for 5.2ms (from the datasheet the Tcca time should be 2.56ms as the datarate = 50kbps : (1/50000)*128*xCcaLength ) and send the packet :If the channel is busy, it listens continuously like in persistent mode until the channel becomes free :It should go to sleep and to Rx mode again twice as I set the max. number of back-off cycles to 2 and I should get the MAX_BO_CCA_REACH Irq from s2-lp. (I did the RCO calibration in init and I use the SLEEP_B mode).Why it does not go to sleep for BOtime after the 5.2ms of Rx ?Thanks,Andy Rochette,Electronic engineer,Inocess [ST Partner]

Hello,I am integrating the BlueNRG-2 module (BlueNRG-M2SA) in a development with an STM32L496VGT6 processor.Currently I cannot communicate with the BLueNRG module.I have done all the tests of my code with the STEVAL-STWINKT1 module, and the minimum configuration to initialize the module and make it operational works correctly, however in the new development the module cannot be made available.I have searched a lot of information on the web, and I think I understand that the default module comes without any firmware, I don't know if this is correct. My native language is not English and I don't know if I interpret the documentation correctly.Considering this, I have tried to connect the BlueNRG-2 module to the STLink-v3 mini, but without success.I don't know if the connections are correct.I would need if someone can guide me.1- Does the module have any preloaded firmware?2 - How should I connect the module to the stlink to load the firmware through one of the BlueNRG GUI or BlueNRG-1_2

Hello,I am using the STEVAL-IDB012V1 module, can you please tell me how I can test it? program it?

Hi.Currently we use SIM7000G and SIM7070G (GSM, NB-IoT, LTE-M, GNSS) modules from Simcom in our projects, using for authentication only a SIM holder with plastic chip, in the old way. We are starting to integrate the eSIM ICs on the boards, to use holder for plastic SIM + eSIM IC + dual SIM card analog MUX, I already did a layout including these 3 things, but still have doubts about the the eSIM. I have sent this email do Simcom support:"Hi, we would like to know if, for SIM7000G and SIM7070G modules, if they are compatible and can work with eSIM chip/IC like the ST4SI2M0020TPIFW of ST Microelectronics, we plan to use this one. Do I just need to connect the electronic signals of the SIM interface of the modules to the same named signals of the eSIM chip/IC? I saw that in Brazil, for the newer smartphones integrating an eSIM, the network operator would generate a QR code to the user, who would scan it with the camera and then the smartphone would write informations in the eSIM chip

Hi team, kindly assist us with below mentioned queries..For the some ST Microcontroller components Datasheet did not specify Thermal characteristics such as junction-case or junction-board thermal resistance. we need these values for the thermal simulation. so can you please provide these data as soon as possible.ST Microcontroller part series mention below: 1] SMAJ15A-TR2] STL13N60DM23] TS924AIPT4] STTH4R02U

We transitioned from BLUENRG-M0L to BLUENRG-M2SP. We did some basic application testing with the X-NUCLEO-BNRG2A1 platform, and we had the example application up and running seamlessly.However, we’ve encountered an issue when integrating the BLUENRG-M2SP with our existing boards. I’m having trouble running the example application. The module and the main controller talk via SPI. While going through the data sheet, I discovered that the BLUENRG-M2SP module must be in Mode “100” pin configuration to be able to talk via SPI with our main controller. Question:Does the module come in “MODE 100” out of the package or is this something we must do at our end. Any clarity on the topic would help us a lot.  

I connected:SIM7000E ->  ST4SIM-200MPIN 30 SIM_VDD -> VCCPIN 31 SIM_DATA -> I/OPIN 32 SIM_CLK -> CLKPIN 33 SIM_RST -> RSTWhen I send the AT+CCID command it returns: "+CME ERROR: SIM not inserted"The same command with a standard plastic SIM card works and returns the right card's ICCID.Did I make the wrong connections? Do I have to do something about RESET denied?Thank you

Dear All, my name is  Mario and I am working the the STEVAL-IDB008V1M board with WiseStudio IDE, version: 1.3.1_R.I want to debug my application with ST-LINK V2 but I have no experience with Wise Studio.Could kindly anybody give me some piece of advice for debug configuration? I configured a debug configuration according to the Wise-Studio instructions but the following error occurs:  Open On-Chip Debugger 0.10.0+dev-01002-g983a95ff-dirty (2020-01-08-15:00)Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmladapteradapter assert |deassert [srst|trst [assert|deassert srst|trst]]adapter deassert |assert [srst|trst [deassert|assert srst|trst]]adapter usbadapter usb location [<bus>-port[.port]...]adapter_khz [khz]adapter_nameadapter_nsrst_assert_width [milliseconds]adapter_nsrst_delay [milliseconds]interface driver_nameinterface_listreset_config [none|trst_only|srst_only|trst_and_srst][srst_pulls_trst|trst_pulls_srst|com

We work on BLUENRG2 SDK 3.2.1 as a peripheral device, and we face a lot of 0x22 disconnection reasons; we don't know why it happens.We find that sometimes on sniffer session at the beginning of the connection, the chip doesn't reply to the LL_version_ind, and after the 40s, the disconnection happens. We checked and didn't do any flash operations during that time.And sometimes during a running connection.Currently, we are handling this by reconnecting from the central side, but in some cases, we face the same disconnection over and over, and the only way to recover from this state is to do a software reset. My questions are.1- Why sometimes the disconnection occurs repeatedly?2- How can we avoid this disconnection reason (The RSSI is good)?3- What's the proper solution if this disconnection reason appears? Should I ignore it? Or should we do specific handling?4- Is there another way to handle it without performing a software reset?

Which esim chip I can use in smartwatch . ? I see two type of SIM M2M and Consumer . But consumer SIM is not available but I see M2M sim available . can we use M2M sim ST4SIM-200M in smartwatch for consumer . ? Please help in selection of right ST SIM . RegardsRohit 

Hi STMicrocontroller developer community,I am currently working on a project that involves interfacing of infineon IM69D130 digital MEMS microphone with STM32WB55G microcontroller. However, I am facing challenges in setting up the communication between the microphone and the micro controller and could use some assistance with a Library or Code Sample that allows interface. Any help, advice or resource that can assist me would be greatly appreciated.Thanks and regardsManik Banagar

Hello everyone, I'm using a STEVAL-MKBOXPRO connected to an RPi3B+ to receive data via Bluetooth.The BLESensors code is integrated into Sensortile.I've tried two approaches and for now I'm stuck:Using the BlueSTSDK library, I've run example_ble_1.py with sudo (Python version is 3.7).pi@raspberrypi:~/BlueSTSDK_Python/blue_st_examples $ sudo python3 example_ble_1.py ################## # BlueST Example # ################## Scanning Bluetooth devices... Discovery started. Discovery stopped. Discovery started. Discovery stopped. No Bluetooth devices found. Exiting...Trying both synchronously and asynchronously to find the device, but it's not being detected (very strange because I can find it from the RPi3 and also from the Android app).On the other hand, trying a different approach using the bleak library, writing this code manages to connect to the device. #import asyncio from bleak import BleakScanner #async def main(): # devices = await BleakScanner.discover() # for d in dev

Hi, MURALI SELVAM from India. I using "STM32H743VIT6" I want know heart beat signal hardware configuration, in the project I using three MCU for safety purpose, in case 1st MCU will get failure, 2nd one is take control, 2nd one will get  failure, 3rd one will take control for this I have taking "heart beat signal processing" but I don't know how to do hardware configuration and what kind of communication interface between three processor suitable for this like SPI, I2C. Anyone who know about it kindly let me know.

Hi everybody, I'm a newby of ST development boards and I'm trying to use the BlueST-SDK for Python to get the data sent by the STEVAL-MKBOXPRO on the BLE interface. The python library is running on a Raspberry Pi 4 Model B, hosting on it a Python installation with version 3.9 or 3.10 (depending on the Operating System I tried to install on the Raspberry - Raspbian or Ubuntu). The problem is that the BlueST SDK which on its turn uses the bluepy library is declared to work with Python 3.5. Indeed using Python 3.9 or 3.10 and running one of the examples provided with the SDK, no BLE node is discovered, even if the STEVAL-MKBOXPRO is active. The MKBOXPRO is correctly detected by the command:sudo hcitool lescan but it is not detected by the BlueST-SDK.I have then read a post on github where a user indicates that this problem was solved downgrading Python from 3.10 to 3.5. I have then configured another alternative Python installation on the Raspberry, namely version 3.5.4.I started the

i have 2 STEVAL-BCN002V1B boardsthe first one i tried using the app and using bluetooth and the daughterboard (sensor board) showed solid green and i can't bluetooth connect to it and using firmware updater with USB doesnt erase to load new firmwarethe second device, used USB connection to load a firmware version that has worked on other bluetile, and gets green light. tried to erase the flash, says it did it, but then solid green need help as both boards are solid green and i can't new firmware loaded. I read in an article that there is possibility of permanent brickingI have gone through this doc:https://www.tme.com/Document/b19a4c2ae115b1ffbff8b10955022a24/SPBTLE-1SINS.pdf The utility shows successful flashing of our FW update, and also when doing erase but getting solid green light 

These answers say that the BlueNRG-M2SP module comes blank and must be programmed with a firmware binary.https://community.st.com/t5/interface-and-connectivity-ics/preloaded-firmware-of-bluenrg-m2sp/m-p/134698#M1534https://community.st.com/t5/interface-and-connectivity-ics/what-mode-is-the-bluenrg-m2sp-module-in-when-its-comes-from-the/td-p/657978How do you recommend the BlueNRG-M2SP module be programmed in a production environment?  For example, are there tools available for pre-programming the module before it's soldered to the custom board?  Or does the module need to be programmed in circuit through the module's SWD connection with tools such as ST-Link V2 and the programmer application?  Programming in-circuit with ST-Link might be OK for low volume production but is there a better solution for high-volume products?