Solved

I developed a multi-port charger with multiple STUSB4710A and companion ST1S14PHR with the recommended bill of materials. The evaluation kit worked fine however my board does not work consistently. I read back the status register and detecting undervoltage.      uint8_t vbusStatus = readRegister(STUSB4710_I2C_ADDR, 0x10); // MONITORING_STATUS    Serial.println(":magnifying_glass_tilted_left: Checking VBUS Voltage Faults...");    if (vbusStatus & (1 << 0)) Serial.println(":warning:  VBUS Overvoltage Detected!");    if (vbusStatus & (1 << 1)) Serial.println(":warning:  VBUS Undervoltage Detected!");    if (vbusStatus & (1 << 2)) Serial.println(":warning:  Power Good Fault!");

Can anyone help identify this chip, please!Thanks in advance!!

I'm trying to achieve a simple characteristic read from a client device on a STM32WB55 to a server device on a STM32WB35on client side - after connecting I get a HCI_LE_CONNECTION_COMPLETE_SUBEVT_CODE and I keep track of connection_handle in a grobal struct and immediatly calling aci_gatt_disc_all_primary_services()- when receiving ACI_ATT_READ_BY_GROUP_TYPE_RESP_VSEVT_CODE I'm keeping track of my services handles(start and end)  in my global struct and out of event handle I'm requesting aci_gatt_disc_all_char_of_service() of the service I'm intrested in- when receiving ACI_ATT_READ_BY_TYPE_RESP_VSEVT_CODE I'm recording the attribute carac handle in mùy global struct and out of event handler I'm calling aci_gatt_read_char_value(ClientContext.connHandle, ClientContext.CaracHandle); the return value is OK and I was hopping for a ACI_ATT_READ_RESP_VSEVT_CODE to pop in my event handler but I get none I'm just receiving a ACI_GATT_ERROR_RESP_VSEVT_CODE with parametersCon

I tried to generate code using stm32cube ide to run lwip and tried to ping the board. But it is not working. Is it possible to generate code that runs without any modifications in the generated code?

My organization is currently planning to develop a monitoring unit that will connect with a mobile app via NFC. For this, we have chosen the ST25R3916 NFC module, with the STM32WLE5 series controller as our main MCU. Recently, we started working on the NFC-A configuration for active peer-to-peer communication using the ISO14443A standard.We are currently encountering issues with lagging during testing and have been unable to find reference sources online for implementation and testing. We have come across a video that demonstrates some testing methods through a GUI, which I will share below. Additionally, we found some source files for the ST25R3916 module, which I will also provide links to. However, the problem is that the complete implementation is in C, while we are looking for a C++ implementation since we are using Mbed OS for development.We also have a key question: is it possible to implement FOTA (Firmware Over-The-Air) using NFC in passive mode? If so, we would appreciate gui

We are developing a product using the STM32WB55 chip and using the S.T W.P.A.N stack. We intend to release our product with a Bluetooth certification / logo, so we need to register our company to get a company I.D right ? Do we need to use the company ID, or do we need to register a 16bit unique U.U.I.D (and pay for it ?). I don't think it's allowed to use the company ID of St Microelectronics, I don't want a lawsuit from either the Bluetooth S.I.G or St Microelectronics, but I also don't want to explain to my boss we have to spend more money if it's not necessary because we are a startup. I also didn't found a way to set / get the company ID from memory or flash. Is it possible to use the S.T W.P.A.N stack to do this or do we need to modify the source code generated by STM32CubeMX directly ?

Dear I hope you are doing well.I would like to confirm if the default antenna power of the STM32WB05KZ board is set to 0 dBm ?  Additionally, could you please guide me on how to modify this power setting?Thank you in advance for your support. I look forward to your response.Best regards,

I followed 'STEVAL-MKI109D Professional MEMS Tool motherboard for MEMS adapter boards' and installed MEMS Studio.I then placed STEVAL-MKI250KA on STEVAL-MKI109D by following UM3420 and AN6173.  When I boot MEMS Studio, it just does not recognise the board either via bluetooth or serial.  I also installed https://www.st.com/en/development-tools/stsw-stm32102.htmlAny ideas what I am doing wrong?

Dear Gfx Team1. Could you consider adding a 'Refresh' button to the Typography ?With GfxDesigner open, when I copy a font to ./assets/fonts, the font is not recognized in Typography. Close/Open of GfxDesigner is necessary.2. Could you make slider bigger and more visible please ?3. Could you add a text field showing an example of the font?4. Could you make the dropdown list searchable so that typing filters the items containing the typed text?Thank you  

I am working with the LSM6DSO16IS in MODE2 configuration with ISPU enabled. I have some questions regarding the MDRDY (Master Data Ready) signal:1. How is the MDRDY signal handled in MODE2 when using the master I2C interface with external sensors?2. Is there any specific configuration needed in DRDY_PULSED_REG (0x0B) for proper MDRDY operation in MODE2?3. Can you provide information about the timing relationship between MDRDY and the external sensor's data ready signal in MODE2?4. Are there any application notes or reference designs specifically addressing MDRDY usage in MODE2?Current configuration:- Like JP4 from X-NUCLEO-IKS4A1 SCH, the INT2 of LSM6DSO16IS is connected to the interrupt output of an external sensor- LSM6DSO16IS in MODE2- ISPU enabled- External sensor connected via master I2C- Using X-CUBE-ISPU framework

hello. I was using PA9 pin as an interrupt in a project made with Stm32F072CBT6. I am working as Stm32F072CBTx in cubeide. The card I am working on accidentally installed Stm32F072C8T6. only difference is that it is visible in flash but PA9 pin can be defined as interrupt in the same way but the function does not work. Is the fact that the processors are different a reason why the interrupt cannot work?. I do not get any overflow error caused by flash.

Some errors occurred during the model conversion process. I have provided my model file below. Cube-AI report ：NOT IMPLEMENTED: Gemm with channel first A input is not supportedIt seems to be caused by an inability to handle the transposed data, but how do I resolve this issue? Or is the transpose operator unusable?

Hello,Do you have a FDA accession number for the VL53L4CX ToF chip? I can find only the document "VL53L4 IEC 60825-1 CB test certificate (eye safety)" at the attachments and there it isn't noted. Furthermore I guess it is not the same as for the VL53L5CX.Regards Tobias

This is a long and weird one.My boss gave me a board with an STM32L433 that wouldn't communicate or do anything after power-on. After a lot of debugging and code tracing, I discovered that the function HAL_RTC_WaitForSynchro returns a HAL_TIMEOUT error code. The auto-generated code then jumps to the error handler with the infinite loop.I have checked the RTC registers, and found an anomaly that may back this up. On a functioning board, the RTC_ISR register reads 0x00000037. On the bad board, the same register reads 0x00001017. Bit 5 (RSF) being 0 on the defective board indicates that shadow registers are not synchronized.So, what can keep the RTC from synchronizing its shadow registers?I found this line in the reference manual:"The RSF bit must be cleared after wakeup and not before entering low-power mode."Now, this board distributes 24 V to some other boards. In this particular case, the supply wires to one of these other boards were swapped, nearly shorting the supply voltage. I don

Hii, I am using hrtim in stm32G474RET6 mcu, so i want to know how we generate a counter of 500ns in which i call adc in it.If somebody know about it please help me.

Posted on June 07, 2017 at 18:46I need to have a PC algorithm that produces the same result as the hardware CRC (using an F0 chip).I can produce identical results between hardware and software when doing a byte by byte crc calculation.I would like to use the word based calculation since it is much faster.However, the result produced using the word by word in the hardware CRC is different than the one produced using the byte by byte option. I've tried all combinations of bit and byte ordering on the word value in the software based calculation (taking 4 bytes at a time and re-ordering bits and bytes) but I haven't come up with a combination that works.It isn't necessary for me to have the hardware word vs byte calculation produce the same result (would be good if it did though).  However the software and hardware calculations must obviously match.Does anyone have any tips to share on this?

HiI Reported this for Improvement in STSW-ST25RFAL 3.0 source before.Now STSW-ST25RFAL 4.0 is available but the following problems are not changed.1) Add to rfal_analogConfig.h, rfal_crc.h, rfal_iso15693_2.h header files.#if defined( __cplusplus )extern "C" {#endifotherwise this file makes it difficult with C++ 2) Add to rfal_analogConfig.h header files.#if !defined( __cplusplus )typedef struct {  uint8_t id[sizeof(rfalAnalogConfigId)];   rfalAnalogConfigNum num;   rfalAnalogConfigRegAddrMaskVal regSet[];} rfalAnalogConfig;#elsestruct rfalAnalogConfig;#endifC++ can't handle an empty array regSet[] in a struct 

Hi, I set the button on the board to WAKE_UP2 to wake up from standby mode, but it doesn't work. Also, waking up through the RTC interrupt doesn't work either. The LSE source is an external crystal. This is my code: int main(void) { /* USER CODE BEGIN 1 */ /* USER CODE END 1 */ /* MCU Configuration--------------------------------------------------------*/ /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the System Power */ SystemPower_Config(); /* Configure the system clock */ SystemClock_Config(); /* USER CODE BEGIN SysInit */ /* USER CODE END SysInit */ /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ICACHE_Init(); MX_USART1_UART_Init(); MX_RTC_Init(); /* USER CODE BEGIN 2 */ if(__HAL_PWR_GET_FLAG(PWR_FLAG_SBF) !=RESET) { __HAL_PWR_CLEAR_FLAG(PWR_FLAG_SBF); char *str ="Wakeup form the STANDBY MODE\r\n\n"; HAL_UART_Transmit(&huart1, (uint8_t*)str,

Hi,I am evaluating/learning the SBSFU application example on STM32WBA55CG. I have disabled the MCUBOOT_HW_ROLLBACK_PROT and generated the signed confirmed image sbsfu_app_init.bin using the imgtool.exe  without the security counter TLV using the below command. imgtool.exe sign -k root-rsa-2048.pem -S 229376 -e little -H 0x400 --pad-header --align 8 --overwrite-only -v 1.0.0 --confirm --pad sbsfu_app_init.bin The only change I made to the above command is to remove the "-s auto" and +0 from the version to ensure TLV for the security counter isn't added. However, when I run the application, the image validation fails within the bootutil_tlv_iter_begin as shown below i.e if (info.it_magic == IMAGE_TLV_PROT_INFO_MAGIC) {// fails with info.it_magic = 0x6907 if (hdr->ih_protect_tlv_size != info.it_tlv_tot) { return -1; } if (LOAD_IMAGE_DATA(hdr, fap, off_ + info.it_tlv_tot, &info, sizeof(info))) { return -1; } } else if (hdr->ih_pr

Hi!I am trying to reproduce some examples and got stuck at simple sensor.The example code is working fine on my P-Nucleo-wb55, but if I am trying to reproduce i with CubeMX i've got failedCode is simply stuck at void shci_cmd_resp_wait(uint32_t timeout){ UNUSED(timeout); UTIL_SEQ_WaitEvt(1U << CFG_EVT_SYSTEM_HCI_CMD_EVT_RESP); return;}I’ve tried to compare example ioc file and mine and can't find something Could, someone, please help me find what I've missed?

I'm using an ST-Link V2 to stream (over ITM) code coverage data from an STM32G4 via GDB Server on a PC.This works fine most of the time (for many days), but the data stream sometimes drops some of the data. Adding a delay between calls to ITM_SendChar() on the target stops the data loss, so it appears as if the ST-Link and/or its driver are sometimes unable to keep up.I'm not exactly sure how long the delay needs to be as I am not able to use timers to generate it (as this would invalidate the testing), so I've been using a simple volatile access loop:for ( volatile unsigned delay=0; delay<500; ++delay ); Based on timings and data length, that is introducing delays of about 20uS between the calls.It seems strange to me that it works without the delay most of the time, especially as the target and PC are both running the same software at the time.Is this a known limitation of the ST-Link that would be fixed with a "professional" trace probe? 

Hello,Has anyone used the USBX host code in AzRtos (not standalone)?  The system seems very flaky, and when I looked into it, it seems the Variable: _ux_system_host in file ux_host_stack_initialize.c is never initialized./* Defined USBX host variables. */ UX_SYSTEM_HOST *_ux_system_host;So the pointer to this structure = 0, which happens to be pointing at the memory location for the ITCMRAMITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64KWas the intent to run USBX with no cache, and leave the _ux_system_host structure in the ITCM RAM, or am i missing some initialization routine?Obviously, with this data structure in the ITCMRAM, it would explain why the system is flaky when the ICACHE is turned on.  However, I'm still not able to get the USB_host up and running properly even with the icache off.  (a lot of bus faults due to incorrect callback pointers in this structure)The ST examples don't seem to run either. Any help would be greatly appreciated

Hello,I'm working with a graphics output on an STM32H750-based board.My bitmap resources are stored in SQPI, and the frame buffers (double buffering) are in external SDRAM.The external SDRAM settings are as follows: TEX=1, Bufferable=1, Cacheable=1, Shareable=0SCB_CleanDCache() is being properly executed during frame buffer switching. In TouchGFX 4.24.0, I'm experiencing the following issue: Screen flickering occurs under specific conditions (image is a sample):When displaying a rounded corner window overlaid on top of a background with texAfter updating to TouchGFX 4.25.0, the screen flickering improves but still slightly exists (visible in the top right of the sample image).I believe this was improved by modifications to the TouchGFX core, but there still seems to be a bug in handling the contention between CPU and DMA2D/LTDC when accessing the frame buffer.What do you think?For reference, in both 4.24.0 and 4.25.0, the flickering disappears when the MPU setting for external SDR

Hallo,Im trying to flash an image (st-example-image-qt-openstlinux-eglfs-stm32mp1), bu it fails on partition 0x23this is the output on Terminal:giomate@giolaptop:~/Development/STM32/MP15/Distribution/openstlinux/build-openstlinuxeglfs-stm32mp1/tmp-glibc/deploy/images/stm32mp2/stm32mp1$ STM32_Programmer_CLI -c port=usb1 -w flashlayout_st-example-image-qt/FlashLayout_sdcard_stm32mp157c-dk2-trusted.tsv -log   -------------------------------------------------------------------            STM32CubeProgrammer v2.1.0             -------------------------------------------------------------------Log output file:  /home/giomate/.STM32CubeProgrammer/trace.logUSB speed  : High Speed (480MBit/s)Manuf. ID  : STMicroelectronicsProduct ID : USB download gadget@Device ID /0x500, @Revision ID /0x0000SN    &nbsp

I am configuring to support Stop mode 2 in the stm32_wpan configuration section in the STM32CubeMX.The following lines are generated in stm32_lpm_if.cSYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ENTER); SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_ACTIVE); SYSTEM_DEBUG_SIGNAL_SET(LOW_POWER_STOP2_MODE_EXIT);However, the definitions of LOW_POWER_STOP2_MODE_ENTER, LOW_POWER_STOP2_MODE_ACTIVE and LOW_POWER_STOP2_MODE_EXIT don't get generated, which are causing undefined compilation errors.I checked the expected types for these definitions, and see that these should be defined as part of the system_debug_signal_t enum inside debug_signals.h. I have tried looking for additional configurations that might generate the missing definitions but I haven't had any success so far.What should I look into or how can I generate these missing definitions? I could try to manually add these definitions to system_debug_signal_t. but then any time I re-generate with new configurations it