Solved

Hi I'm using STM32H743ZG.I am currently using all three ADCs. Each ADC initialization code: #ifdef CHANNEL1 /** * @brief ADC1 Initialization Function * None * @retval None */ static void MX_ADC1_Init(void) { /* USER CODE BEGIN ADC1_Init 0 */ /* USER CODE END ADC1_Init 0 */ ADC_MultiModeTypeDef multimode = {0}; ADC_ChannelConfTypeDef sConfig = {0}; /* USER CODE BEGIN ADC1_Init 1 */ /* USER CODE END ADC1_Init 1 */ /** Common config */ hadc1.Instance = ADC1; hadc1.Init.ClockPrescaler = ADC_CLOCK_ASYNC_DIV1; hadc1.Init.Resolution = ADC_RESOLUTION_12B; hadc1.Init.ScanConvMode = ADC_SCAN_DISABLE; hadc1.Init.EOCSelection = ADC_EOC_SEQ_CONV; hadc1.Init.LowPowerAutoWait = DISABLE; hadc1.Init.ContinuousConvMode = DISABLE; hadc1.Init.NbrOfConversion = 1; hadc1.Init.DiscontinuousConvMode = DISABLE; hadc1.Init.ExternalTrigConv = ADC_SOFTWARE_START; hadc1.Init.ExternalTrigConvEdge = ADC_EXTERNALTRIGCONVEDGE_NONE; hadc1.Init.ConversionDataManagement = ADC_CONVERSION

I'm fairly new in NFC technology and was trying to implement a simple project that uses the ST25R3916 to write a message in a specific memory location of the ST25DV04K and then locks write access to that specific memory location. I'm using an adapted version of the library "en.x-cube-nfc6". I can read/write messages without any problem, but when I can't seem to find any function in the library to block the write access that works. I'm using  "ndefPollerWriteBytes(ndefContext *ctx, uint32_t offset, const uint8_t *buf, uint32_t len)" to write, which works fine, butif I try to use "ndefPollerSetReadOnly(ndefContext *ctx)", it returns error 33 "Wrong State". Am I doing something wrong? Should I use different functions? I'll append a picture of my code, which stems from the demo usage of the library. The purpuse of the code was to write 4 bytes, lock access then try to write again (which sould fail, I guess).

Hi, We are attempting to use the ST25R3916 and the RFAL middleware (NFC08A1 demo board) to read Picopass cards using the ISO14443B standards - however the cards we have (that we know work with older Picopass readers) are not detected. I understand the pico cards operate in a non standard way however I could do with some pointers as to where to look to be able to support reading these cards as well as more standard ISO11443 A/B cards.Using the demo software NFC08A1 Polling Tag Detect - the software simply doesnt recognise these cards at all.

Hi,I am currently working with the documentation of TCPP01-M12. I have find some small mistake in the table of recommended capacitor C3. The part codes are switched. Also it seems that the GRM188... 0603 package capacitor is obsolete nowadays. Could you recommend some alternative?With kind regards,Marosh

NUCLEO-WB09KE's ST-Link V3 generate FAIL.TXT and DETAILS.TXT how to fix it I have confirmed that the ST-LINK SWD connection is normal. When I pull up BOOT, I can download the code normally

I am looking at revision 64 of the the AN2606 application note.https://www.st.com/resource/en/application_note/an2606-stm32-microcontroller-system-memory-boot-mode-stmicroelectronics.pdfSection 89 of this document gives some tables for some timings for a number of different processors. I am using the STM32U073 processor but I cannot find entries in tables 200, 201 and 202 for this part.

Hello everyone,I have an X-NUCLEO-IKS4A1 expansion board connected to the STM32F401RE Nucleo board. The LIS2DUXS12 sensor on the expansion board incorporates a Qvar sensor capable of detecting changes in electrical charge near the external electrodes connected to the device. I have a detachable STEVAL-MKE001A board connected to the 2 x Header 3pin SMD for QVAR electrode.To activate the Qvar channel I set the AH_QVAR_EN bit to 1 in the AH_QVAR_CFG register (31h) and I set the INT1_ON_RES bit to 1 in the CTRL1 register (10h) so that the INT1 and INT2 pins are used to connect the electrodes to detect the Qvar signal.The problem is that the signal I read does not vary when I touch the electrodes as it happens when the LSM6DSV16X sensor as Qvar controller.Did I skip any steps by chance? It looks like the INT1 and INT2 pins of the sensor are not connected to QVAR1 and QVAR2

Hello,I would like to use software timers with FreeRTOS but the Add button is disable. The others button (add semaphore, mutexes, Events, ..) are all available...The target is STM32L431.Do you have any suggestion?Best regardsMich 

Hi,I have an issue with low power operation when using the USBPD library. We have successfully implemented a low power feature for our new product. After that we have started the development of a USBPD feature. The problem is, that after the function "USBPD_PreInitOs()" is called in main.c the power is much higher as it was before. As this function calls a static linked library, I have no idea what has been turned on and how to disable it again. Therefore I need your help as only you have the source code.Here my simple steps to reproduce the problem:Hardware (Nucleo144 STM32H563, STLINK-V3PWR):1) In CubeMX I select the example USBPD_SNK, then I generate the code.2) In main I add this two lines after USBPD_PreInitOs(): USBPD_PreInitOs(); /* USER CODE BEGIN 2 */ HAL_SuspendTick(); HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFE);The current is 3600µA (3,6mA).When commented out USBPD_PreInitOs() like here: //USBPD_PreInitOs(); /* USER CODE BEGIN 2 */ H

EDITED:Resolved, but leaving here for the next person who stumbles into this issue.I'm using the STM32G030K6 and encountered two issues:Errata 2.2.3 - which correctly describes a serious issue when using readout protection level 1: if nBOOT_SEL is not set in the option bits, the uC will often fail to boot and even a hard reset will not recover, only a power cycle.  The errata correctly describes a workaround: set nBOOT_SEL in the option bits (removes the option to force entry to the bootloader by tying the BOOT0 pin high).Access to OTP memory is not protected by readout protection level 1.This is expected behavior since SystemMemory is not protected by RDP level 1, but it is unfortunate given that OTP is the perfect place to store device-specific persistent data like serial numbers, encryption keys, etc. This is particularly true on devices with limited flash where allocating a separate sector may be painful. Perhaps in a future version of the component, ST will consider protectin

hello,st friends.   My board use TIM2_CH1 pwm to drive a led.dts configure as:but the led can not light on.use these command byw: I use gpio test led hardware is ok 

Hello ST community,I am working with an ST microcontroller and a W25Q128JV flash memory, interfacing via QSPI. While using the HAL library, I’ve encountered an issue with the HAL_QSPI_Command_IT function.When I use the blocking HAL_QSPI_Command method to read the status register and execute other flash operations, everything works correctly. However, when I switch to the interrupt-based HAL_QSPI_Command_IT function (specifically, when I call it before HAL_QSPI_Receive and HAL_QSPI_Transmit functions), the sequence fails to execute properly, and I do not receive the correct results.Context:Flash Memory: W25Q128JVOperations: Reading the status register, as well as writing to and reading from memory.Working Approach: Using HAL_QSPI_Command (blocking) works perfectly for these operations.Problematic Approach: Using HAL_QSPI_Command_IT (interrupt) fails for certain sequences.My Question:Are there any known limitations or special considerations when using HAL_QSPI_Command_IT with the W25Q128

Hello everyone,I'm experiencing issues with the "Write Multiple Blocks" command on the RF side using the ST25DV64KC.I’ve tried using this command through the ST25 Android app, specifically using the "Send Custom Command" feature. Here’s how I configured the command:Option Flag: EnabledAddressed Mode: EnabledSelect Mode: DisabledHigh Data Rate: EnabledFormat Extension: Disabled"CMD" Code: 0x24Data: 00 01 11 11 11 11 22 22 22 2200 indicates the First Block Number field in the request (Block 00).01 indicates the Number of Blocks (01 = 2 blocks).11 11 11 11 22 22 22 22 is the data to be written into the memory blocks.However, when I send this command, the Android app returns an "ERROR CMD" message.I’ve also tried different configurations (e.g., disabling High Data Rate, using different data values, etc.), but I get the same result each time.I want to note that the single block write command works perfectly and allows me to write one block at a time without any issues.Does anyone know what

what is A/D register for? when i bring the st25r tag(sticker one) near the st25 nfc its value changes. And how is interrupt generated? what are the values of registers to be set in order to read a NfC tag?pseudo code for it. 

Hi,       Can I utilize this IC in a buck converter configuration to step down from +400Vdc to +15Vdc? If so, could you please provide the application guide for buck converter design? Thank you!

Hello, ı want to run a function in ITCMRAM area. But as long as i call the function i enter HardFaultI added code snippet below(just the ITCMSection part) to the linker script.SECTIONS { /* The startup code goes first into FLASH */ .isr_vector : { . = ALIGN(4); KEEP(*(.isr_vector)) /* Startup code */ . = ALIGN(4); } >FLASH _siITCM = LOADADDR(.ITCMSection); .ITCMSection : { . = ALIGN(4); _sITCM = .; /* create a global symbol at ITCM start */ *(.ITCMSection) . = ALIGN(4); _eITCM = .; /* create a global symbol at ITCM end */ } >ITCMRAM AT> FLASH /* The program code and other data goes into FLASH */ .text : I have a simple function below that is causing hardfault that i declare in my main.c file.  __attribute__((section(".ITCMSection"))) uint8_t my_function(uint8_t a) { return 2*a; } I can also see that i put 26Bytes in the ITCMRAM area from build analyzer. What might be the reason for HardFault?

Hi All,I am a newbie in motor control. I am having a X-NUCLEO-IHM08M1 board with me I came to know that it supports both sensored as well as sensorless motors, but could'nt find a sensord motor that is compatible with the board but found one sensor less motor named BR-2804. Can anyone suggest a motor that comes with hall effect sensor which is compatible with the board. If motor does not come with any sensor in it, can we add external sensors to it, If yes can anyone suggest a sensor too.With regards,Tashi George

hi,Using STM32G0B0CET6USB_DRD_FS---Host_Only_FS,USB_HOST---Mass Storage Host Class,FATFS---USB DiskUSB Interrupt---Enable. My requirement: i just want to create  and write the file to usb_host.c and whenever i pluged the usb, the file automatically copied from microcontroller to pendrive. i did, its working fine but i have a doubt, Everything seems clear, but why should i configure to  Drive_VBUS_FS option.On my board, I decided to provide 5V to VBUS directly . This makes me wonder if VBUS sensing is possible at all?And for the Drive_VBUS_FS, I don't want to drive VBUS, but there is no such option available except for keeping the selection at Undefined, which seems to be an invalid state. we don't have a additional pin of Drive_VBUS_FS, what should i do? 

 I am currently ordering the STM32C0116-DK to start developing some FW before getting the shipment. I've also sent the pinout to the EE team so they can start the schematic and laying out the PCB  I started the project using the Board Selector. I've set up the UART and I2C which the pinout is shown below. The I2C peripheral is using PA9 and PA10 However, when I set up a new project using the MCU selector, the I2C peripheral are on other pins. I am selecting the same MCU where it shows the STM32C0116-DK as the development board to use. But when I set up the I2C peripheral, it uses PB7 and PC14I thought I could maybe remap the pins but there is no option for I2C on PA12 pin as shown below.  So which pinout is correct? Or are they actually 2 different MCU's?              

Hello,I am acquiring samples from 50Hz Sine Wave through a CT and want to get 100 samples of this signal (T=20ms). For this, I need each sample at 200us apart so I get an array of 100 bytes. I have following clock setup:APB1 = 36Mhz; ADC = 12MhzTIM3 Event: 36,000,000/ 7,200 = 5,000Hz = 200usADC Sample Time: Sampling Time + 12.5 cycles = 239.5 + 12.5 = 252 cycles => 1/12Mhz X 252 = 21us TIM3:ADC:Using above settings & calculations, SOC is supposed to complete said ADC in 21us and sample time is 200us which is fine. Here is the code:/* USER CODE BEGIN PV */ uint16_t adc_value[500] = {0}; /* USER CODE END PV */ /* USER CODE BEGIN 2 */ HAL_TIM_Base_Start(&htim3); HAL_ADCEx_Calibration_Start(&hadc1); HAL_ADC_Start_DMA(&hadc1, (uint32_t *)adc_value, sizeof(adc_value)); /* USER CODE END 2 */ /* ADC Config */ hadc1.Instance = ADC1; hadc1.Init.ScanConvMode = ADC_SCAN_DISABLE; hadc1.Init.ContinuousConvMode = DISABLE; hadc1.Init.DiscontinuousConvMode = DISABLE;

Dear all,A newbie here. Any help is much appreciated. I appreciate this is an STM forum and while I am using ESP-IDF to interface with STM's lsm303, I believe the problem is caused by my incorrect configuration of the STM lsm303 sensor. Hence any guidance is much appreciated.I am using an LSM303 sensor, connected via I2C to an ESP32 and programmed via ESP-IDF to retrieve the magnetometer and accelerometer data. I was previously using an Ardunio and the the Pololu LSM303 library and everything worked with the same wiring.However, when using bare i2c in ESP-IDF, it seems like I have messed something up as the magnetometer data freezes unless I power cycle the LSM303 (rebooting the ESP32 doesn't seem to change the readings, while unplugging the VCC of the lsm303 and plugging it back in again results in new readings).Here is the code, which reads the data at 50 Hz via I2C. I have checked various sources including the stack exchange electrical engineering forum and others but I am

Hello,I am using STM32F303RBT on a custom board and am trying to communicate through SPI with LTC6811-1 with code generated through CUBEMX.I am able to send and receive the data fine when the data is not required to be sent in one burst (LTC6811 can handle pauses between bytes except when it is trying to write I2C data over SPI and then requires tight clocking).Can the pauses be eliminated by using bare metal for HAL_SPI_TransmitReceive()?Does someone have a simpler (faster) version of this function?Below are clock and MOSI signals aforementioned with 15 us pauses between.The code which calls HAL_SPI_TransmitReceive(...) is also attached.Pauses between bytes___________________________________________________________________________________________ #include "BMSDriver.h" /*******************************************************************************/// MICROCONTROLLER SPECIFIC FUNCTIONS FOR CONTROLLING : void cs_low(){HAL_GPIO_WritePin(BMS_CHIP_SELECT_GPIO_PORT, BMS_CHIP

I am using an STM32H747I-Discovery board for prototyping.I was wondering if I can set:HAL_PWREx_ConfigSupply(PWR_SMPS_1V8_SUPPLIES_LDO); or HAL_PWREx_ConfigSupply(PWR_SMPS_2V5_SUPPLIES_LDO);Then set:__HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE0);And still set up my clocks and PLL for 480 MHz operation?I read in the H747 datasheet section 3.5.3 that to use voltage scale 0 (for boosted performance and get the 480 MHz) you have to use the internal LDO. I am just wondering if I can power the internal LDO from the internal SMPS.Thanks for the help

Hi,For our project we are trying to read out the first 100 bytes of a ST25DV tag. This tag is inside our products which are tested in production line. The test results of these test are written inside the tag by I2C. We are building an end of line test to make sure every piece is tested and collect test results.We are using MB1054B demonstration board as our reader. We program directly in the STM32F103 MCU which is on board and we altered the board so we can talk UART to the CR95HF board.For our first try we use a ST25DV_Discovery_ANT_C5 board to make sure we have working hardware and proper reading distance. We can properly reset the the CR95HF by toggling the IRQ pin.After that we send the 0x55 command to see if the CR95HF is responding.uint8_t commandECHO[] = {0x55};After that we send the IDN command to check if everything is functional as expected.uint8_t commandIDN[] = {0x01, 0x00};Then we set the command protocol to ISO/IEC 15693 because our tag (ST25DV) is ISO/IEC

Hi,I have evaluated various controllers and found that the STM32H725ZGT3 is the best fit for our product due to its memory (both NAND & RAM) size, operating temperature range, secure boot hash features, and ECC capabilities. However, I am unable to locate an evaluation board for this controller on your website. Could you please guide me on where I can find one to initiate our software development work? Your assistance is greatly appreciated.Thank you.