Solved

I am in the process of transferring from Mbed to VSCode with the STM332 extension. I have set up a project using CubeMX set to the default settings for a NUCLEO-L073 and have no issues. I believe this setup uses the MSI clock. I am trying to implement the HSE with an external 8MHz crystal but cannot get it to work. The program does not run (basic LED blinky) and there is no clock signal on the crystal when monitored with an oscilloscope.The changes I have made from the default NUCLEO-L073 CubeMX settings are:Pinout & Configuration tab: RCC High Speed Clock (HSE) set to Crystal/Ceramic ResonatorClock Configuration tab: System Clock Mux set to HSEI have verified that there is no issue with the hardware - when running from mbed the crystal has a good 8Mhz signal. Are there any other settings I am missing?Is there any other code i need to add on top of the CubeMX generated output?Thanks  

I have a structure that starts from my own bootloader, and I want to jump to the application. My question is similar to the one in this thread: Is it possible to keep dual bank active and executing the whole FLASH?  I am using the STM32G0B1RE microcontroller. If I put my program starting at an address in Bank 1 and continue through Bank 2, will it work without any issues?

Hi All,I'm sure this has been discussed before - and there's probably a solution out there, but for the life of me, I can't find it.So here's the situation.I have a large (~256K) block of graphics data, that sits within its own designated sectors at the top of the CPU flash. This data very rarely changes.Is there any method that I can use, that will stop this data being re-programmed by CubeIDE everytime I change some software? Is there an IDE setting that will ignore reprogramming data/sectors that haven't  changed since the last reprogram?Obviously, this would speed up development - which would be nice...Cheers,Toneski

Hello,I would like to know where I could find the ST25FTM library for Android.Thank you in advance,Best Regards,Selvaraj

This may be such a basic question, that I may be embarrassing myself here. Not even sure if I've selected the best fitting location...I like to keep a "clean slate" when compiling, that is, no warnings should be present. It makes it easier to see if a problem has occurred, if I don't need to remember how many warnings are to be expected in a certain piece of firmware. Also, if I get too comfortable with a number of warnings being present, something may slip.Now, in microcontrollers, we sometimes need to read something from a register, without actually needing the value for anything, such as emptying an SPI receive buffer after transmitting. In some cases, I use a variable that already exists, and is in use elsewhere, but this is not always practical. And then I get the "variable set but not used" warning.I don't want to suppress the warning type altogether, because it does come in handy now and then.There is the possibility to declare a global variable for this purpose, as the compiler

Hello,We are in the process of migrating our current BMS from an old MCU to a new one. and we want to check if ST has a suitable MCU for our use case:1) The MCU will manage up to 100 battery monitoring chips connected in daisy chain (isolated SPI)2) Enough RAM and speed to run moderately complex SoX algorithms while being able to keep very low latencies2) The MCU can be rated SIL 33) The MCU most obviously have multiple SPI, I2C channels as well as at least two CAN channels and an Ethernet channel4) The MCU must enable encryption/decryption operations and other cyber security mechanisms5) Able to Implement internal fault checks and auto diagnostics and redundancy mechanisms6) Have extensive dev material: example projects, application notes and be well supported by the community7) Having examples of up and running RTOS instances and also secure bootloader examples is a very nice to have8) While being cost efficientI understand an MCU fitting all these requirements is a very hard th

Hello,I have been trying to make a driver for the Winbond W25Q512JV, It's works normally ( I can read/write data, erase sector/chip, can write image as external flash loader with Touchgfx) until one day I could no longer erase sectors or full chips ( My chip has been erased no more than 100 times). When erasing, it doesn't report any errors, it just responds to a successful erase very quickly (~ 0.5s) , almost immediately (previously it took ~ 140 seconds to erase a full chip). When I read back these memory areas, they are not equal to 0xFF. I understand that erase has not been performed yet.I checked by reading the registers status: reg1 = 0xFE, reg2 = 0x02, reg3 = 0x03 and compare with datasheet, it mean bit SRL = 0, SRP = 1, WEL = 1, TB = 1, BP[3-0] = 1 => My chip into protection stateI use STM32H723 on OSPI2 running with QSPI mode, how can i resolve this problem? please give me solution. Thank you for your help

I used STM32CubeMX to set up a Nucleo board (STM32F411RE) to communicate via I2C with a ADXL345 accelerometer.- RCC & clock settings at default- SDA on PB9 and SCL on PB8- I2C Fast Mode- targeted MDK-ARM toolchain- generated code In `main.c` added the following code, #define adxl_address 0x53<<1 // was told that this left shift was necessary for the HAL to fucntion properly?? uint8_t data_rec[6]; // data recieved in bytes uint16_t x, y, z; // acc data void adxl_write(uint8_t reg, uint8_t value) { uint8_t data[2]; data[0] = reg; data[1] = value; HAL_I2C_Master_Transmit(&hi2c1, adxl_address, data, 2, 10); } void adxl_read(uint8_t reg, uint8_t numberofbytes) { HAL_I2C_Mem_Read(&hi2c1, adxl_address, reg, 1, data_rec, numberofbytes, 100); } void adxl_init(void) { /* registers are all listed in adxl345 datasheet */ adxl_read(0x00, 1); // check if adxl is on line adxl_write(0x2d, 0); // reset all bits adxl_write(0x2d, 0x08); // measure bit-1, wakeup 0, 0 at 8hz

Hi,We have a custom design based on STM32L053C8U8 with the pinout mapping  as image attached. The GPIOs setting and initialization code is generated by STM32CubeIDE version 1.17.0 and companion CubeMX . however, the GPIO level the output pins are not in line with the firmware control using HAL_GPIO_WritePin(). for example, HAL_GPIO_WritePin(GPIOA, GPIO_PIN_11, GPIO_PIN_RESET) won't sew the PA11 to LOW. The initialization code is attached. What's wrong? thanks in advance and appreciate your responses!   

Hello, everyone,I have a problem with setting the GPO of M24SR64-Y as an INTERRUPT. The micro needs to come out of Sleep condition through an Interrupt sent from smartphone via RF, I saw that you have to set the GPO with 0x4X, but I don't know how to send this packet to set the GPO as INTERRUPT.The bytes I send and receive are:SYSTEM Select and UpdateBin with the GPO Field at 0x4X (can be seen in the attached figure).(BLUE-SCL / RED-SDA / GREEN-GPO)I receive as a response (R-APDU) from the module bytes 6A 82.Could you please help me out? Do I also need to implement the Capability Container to set GPO as INT? Also, the packet I send as SendInterrupt is as follows:0x56, 0x02, 0xA2, 0xD6, 0x00, 0x1E, 0x00 + CRC (0xCA,0x7F)wanted to know if this is correct as a structure or if something is missing Thank you very much

Hi,Can anybody tell me whether the X-NUCLEO-NFC07A1 works with an Arduno Uno ?In other words, can I just plug an Arduno Uno onto this unit, or do I need to buy a STM32 development board ?When plugging it onto a normal Arduno Uno I am unable to read an NFC tag (13.56 Mhz).Please help.Thanks

Hello ST Community!I am using the M24SR64-Y NFC front-end in my system where the microcontroller is always in a SLEEP state and it is woken up by a SendInterrupt from the Smartphone.The microcontroller is used to perform weight measurements.I would like to know if there is a specific RF command that not only allows me to wake up the micro, but also to make it perform an action.The GPO is set as INT (0x40)Could you give me some advice?Thank you

Hello ST Community,    I have a project using the H563. I recently upgraded STM32CubeMX from 6.12.0 to 6.13.0.  After upgrading, and attempting to open the .ioc file, the following message is displayed: Regardless if I choose Continue or Migrate, I get the following error message in STM32CubeMX: If I downgrade STM32CubeMX to 6.12.0, I do not get the migration notification pop-up, and the .ioc file opens as expected.   I was hoping to find out why this is occuring and a resolution to it.  I have attached the STM32CubeMX log (which contains both the attempt at Continue and attempt at Migrate, both of which returns the 'not valid ioc file' error), and the .ioc file used.   Please let me know if additional details or documents are needed. Best regards,-Aaron Wheeler

Hi, Can't find the source code for the STM32H7S78-DK preloaded TouchGFX Demo, Where could I find this?  Thank you,

Is there any STM32 in TSSOP-20 package with OSC_OUT pin for use with a crystal oscillator?Mark Jordan 

Congratulations. I have such a problem. I've made 1000 PCB prototypes and 30% don't want to enter DFU mode. If you try to turn the PCB back on multiple times, the part will go into DFU.I'm using a USB Type-C connector, could that be the problem? Also tried changing the USB cable, but that didn't fix the problem.I use a microcontroller STM32F405RGT6TR.What can this be related to?

I am working with the X-NUCLEO-IKS4A1 expansion board and NUCLEO-F401RE.I’ve successfully programmed and run the examples provided by MEMS Studio and those in the STMems_Finite_State_Machine/application_examples/lsm6dsv16x repository. Additionally, I’ve used .ucf files and AlgoBuilder to generate C programs.But I have no idea how to program my own FSM from scratch. I have read some of AN5882 but I am not sure if that is the right way to learn about FSMs. Are there any tutorials I am missing?How do I implement my own FSM from scratch based on my own requirements and application? I would like pointers to some good tutorials with examples which explain how to program the FSM.

I'm testing whether HAL_I2S_TxCpltCallback or HAL_I2S_TxHalfCpltCallback is called properly by setting i2s to normal and periodically calling HAL_I2S_Transmit_DMA. However, HAL_I2S_TxCpltCallback or HAL_I2S_TxHalfCpltCallback is called only once and not again. I want to use i2s in normal mode, not circular mode, so I'm testing like below. Is there something wrong?When I check the return value with status = HAL_I2S_Transmit_DMA(&hi2s2, audioBuffer, AUDIO_BUFFER_SIZE);, HAL_BUSY(2) is returned. while (1) { HAL_I2S_Transmit_DMA(&hi2s2, audioBuffer, AUDIO_BUFFER_SIZE); HAL_Delay(1000); } void HAL_I2S_TxCpltCallback(I2S_HandleTypeDef *hi2s) { dma_count++; } void HAL_I2S_TxHalfCpltCallback(I2S_HandleTypeDef *hi2s) { dma_count++; } 

Hi,   typedef struct { uint8_t Status; /*!< ResultStatus */ uint16_t Distance; /*!< ResultDistance */ uint16_t Ambient; /*!< ResultAmbient */ uint16_t SigPerSPAD;/*!< ResultSignalPerSPAD */ uint16_t NumSPADs; /*!< ResultNumSPADs */ } VL53L1X_Result_t; We have cases when the Sensor Status result is non zero.  When it is it is usually a 3 or 255: #define RANGE_ERROR_DISTANCE_BELOW_DETECTION_THRESHOLD 0x03#define RANGE_ERROR_OTHER 0xFF I asked about these in a different post but now I have a somewhat different perhaps more general question.  If the Status returns a non zero in any case should the Distance be disregarded -- in all cases? Or,  are there certain non zero Status conditions where we should "trust" the Distance versus not "trust" the Distance (reading) returned? As usual thank you, Will    

I'm adding Power-Down mode to my Listen Mode implementation, and have come across some unexpected behavior.I keep the chip in Power-Down, with the field detector set to automatic, and then see EON when a field is detected, as expected. The first time this happens, it behaves as expected (see first screenshot): the osc_ok bit was set automatically upon EON, then I set en and rx_en, and ~1ms millisecond later, the IRQ comes in. But the next time, 100-300ms after the previous emulation, it doesn't behave the same way. The osc_ok bit is set after EON, then I set en and rx_en, but the IRQ never comes in. This all the same logic as the previous cycle - so EON is definitely not masked, and should be coming in after ~1ms. Is there some logic/behavior here I'm missing?

Hi everyone,I am implementing the communication between MCU SPC582B and High side driver VN9D5D20F. SPI signals seem fine to me, see next image:Spi Clk frequency = 625kHz  (range is 0Mhz to 8Mhz)CS transaction time = 71usTime between bytes = 7usTransaction 1 = read CTRL (en = 1, parity = 1, GSBN = 1)Transaction 2 = read SOCR (all zeroes, GSBN = 1)Transaction 3 = GSB = 20h (SPIE = 1) On the third transaction, I can't understand why reading SOCR register cause the driver to throw the SPI error (clk count is adequate and SDI is not stuck.I can't figure out what I am doing wrong. Any help would be very much appreciated. Thanks,FP 

What is the Hex code to enable extended mode for the VL53L4CX please ??

MCSDK 6.3.1, FOC with STOPLL, EVSPIN32G4, this motor.We're using a custom board based on EVSPIN32G4 as a drone ESC in a traditional sensorless configuration. Naturally, in our application the motor starts up to a low RPM under idle load and then after FOC takes over it spins up and down within the whole range as commanded by the autopilot. The MCSDK is in the speed control mode.We have found an interesting fault condition (also recreatable with the original EVSPIN32G4): if the motor is held in place somewhat elastically, e. g. by hand, during startup, the following things might happen:Speed feedback fault flag is set ~45% of the time -- expectedStartup fault flag is set ~45% of the time -- expectedNo fault flag is set, the motor is not spinning (sometimes making noises), the indicated RPM jumps to very high negative numbers, followed by speed feedback fault after a few seconds -- unexpected, but easy to catch and handle, RPM flips are easy to see.No fault flag is set, the motor is

I want to generate 6 PWMs using channel 1 of timers 1,8,2,3,4,5. All of them are set the same way except ARR, PSC and CCR1 registers. However, it turned out that timers 2 and 3 don't have PWM signal on their pins. The content of registers for those timers are the same (checked during debugging). I also tried to initialize timers by writing directly to registers, with no luck. MCU: STM32F103RCT6. Here is the the initialization for timer 3, for example: // ------------------------- PA6 settings ------------------------- // RCC->APB2ENR |= RCC_APB2ENR_IOPAEN; // Port A clock (PA6 - TIM3_CH1) GPIOA->CRL |= GPIO_CRL_MODE6; // PA6 speed MAX GPIOA->CRL &= ~GPIO_CRL_CNF6_0; // Alternate function Push-Pull GPIOA->CRL |= GPIO_CRL_CNF6_1; // ------------------------- TIM3 settings ------------------------- // RCC->APB1ENR |= RCC_APB1ENR_TIM3EN; // TIM3 clock TIM3->CCMR1 &= ~TIM_CCMR1_OC1M_0; // PWM mode 1 TIM3->CCMR1 |= TIM_CCMR1_OC1M_1; TIM3->

Hi,By mistake in our PCBA, ST 556D4 K148/B IC is used instead of M95256 EEPROM.now I am searching for ST 556D4 K148/B datasheet.Can you share the datasheet of this IC ?