Solved

The most important spec I'm looking for is INL error. I'v searched the datasheet, reference manual, and google search but to no avail. In particular, I'm looking for the STM32F072 series.

..

Is it ok to connect boot0 from STM32 (with a 10k pulldown to GND) to one of pin 1 or 2 on STDC14 from STLINK-V3SET?The pins are 'reserved' regarding to the STLINK-V3SET manual p. 23 with the comment 'Do not connect on target' ;)The boot0 should be ignored in this case, but we need boot0 for an alternative device.Thanks!

Hi,some thing is strange with the cube ide in the display controller LTDC initialization . i choose 1 layer only but the cube ide generate code for 2 layers!!First time to see such thing

 I was implementing 2-way switch project on my Nucleo-F303RE. For that, I put the 13th and 14th pins of port-c as input and the 15th pin of the same port as output. I am using pull-down resistor for 13th and 14th pin but even after enabling pull-down resistor of these pins. SFR window in debug mode shows 13th bit of IDR still high.  I have made sure that no pin should be connected to any external sourceHere is my code and screenshots: /** Pin 13, 14, 15 of port-c will be used:-  -> 13 and 14 pins will be used for input  -> 15 pin will be used for output* RCC address - 0x40021000 :-  -> RCC_AHBENR - 0x40021014  -> 19th bit for GPIOC* GPIOC address - 0x48000800 :-  -> GPIOC_MODER - 0x48000800   => 15 (31[0] and 30[1]), 14(29[0] and 28[0]), 13(27[0] and 26[0])  -> GPIOC_PUPDR - 0x48000808 :-   => 14(29[1] and 28[0]), 13(27[1] and 26[0])  -&g

..

Dear ST Team,I'm doing a project about: display LCD (DSI Video mode) with TouchGFX. I have example TouchGFX DSI Adapted CMD mode, but can't find out example for DSI video mode.Please give me some idea!!!Thanks

HAL_SPI_TransmitReceive(&hspi1,tx_sensor_data,rx_sensor_data,8,0);​I want sent 8bytes, but only 2bytes sent, why?​

I am working with STM32F&508-DISCO, which is said to have external Flash of size 16MB connected through QSPI. I am trying to read from it, but it is not working.I tried running this: https://github.com/STMicroelectronics/STM32CubeF7/blob/master/Projects/STM32F7508-DISCO/Examples/QSPI/QSPI_ReadWrite_IT/Src/main.cWith the code as it is, it works fine. However, it is reading from address = 0, which is not the external Flash connected through QSPI (I wonder why is the example like that? Isn't address 0 internal Flash and not through QSPI?).Anyway, I wanted to access external Flash which I think is located at 0x9000_0000 (I couldn't find the memory address in the user guide, so I just googled it).However, when I simply change the above code from address = 0 to address = 0x9000_0000, it simply does not work.I also tried with BSP libraries, but the result is the same.Is there an external Flash at 0x9000_0000 for my board? If so, what additional steps do I have to take to make it work?Also

Hi all.I want to prevent the contents of "RETRAM" from being erased when I run the firmware with m4 rproc on "OpenSTLinux"."RETRAM" is powered by the battery through the VBAT pin to maintain data.To this end, TF-A was also modified to set and maintain the value of "PWR_CR2_RREN" in the "PWR_CR2" registry.In the "Engineering Mode" where M4 Firmware can be run on its own, "RETRAM" data is well maintained. However, when you boot into "OpenSTLinux" and load the firmware into M4 rproc and debug it, the contents of "RETRAM" are initialized.The following is the contents of the "RETRAM" related ld file.MEMORY{ m_interrupts (RX) : ORIGIN = 0x00000000, LENGTH = 0x00000298 m_retram   (RWX) : ORIGIN = 0x00000400, LENGTH = 0x0000FC00 m_text    (RX) : ORIGIN = 0x10000000, LENGTH = 0x00030000 m_data    (RW) : ORIGIN = 0x10030000, LENGTH = 0x00010000 m_ipc_shm  (RW) : ORIGIN = 0x10040000, LENGTH = 0x00008000}SECTIONS{

I followed the UART example (https://wiki.st.com/stm32mcu/wiki/STM32StepByStep:Step3_Introduction_to_the_UART) and implemented it on a STM32F051 Discovery kit and on a STM32F446 Nucleo board with pretty much identical settings from CubeMX.If I scope the STM32F051 I get a TX2 signal out of pin PA2 as expected. If I do the same on the STM32F446 I get nothing. Interestingly I get normal output out of the STM32F446 using Tera Term over USB but if I do the same with STM32F051 I get nothing on terminal.Any ideas please?

I believe I have found a bug in `HAL_I2C_Master_Transmit`.The timeout parameter begins counting from the instant the transaction begins, and it doesn't appear that the watchdog is being reset with each incoming byte. Therefore, when you have a long I2C transaction, it will timeout, even if it is working perfectly.Here is an example with a 250ms timeout: I would expect the timeout to related to the amount of time the slave device holds the line low, or time between incoming bytes.I'm using the STM32L4P5G-DK. I would be happy to log the bug, but I don't know where to put it.Thanks,Zak

AN2957 is specifically for RC5 IR transmitter. I need implementation support for Reciver/Detector using STM8 series of MCUs.There is AN3174 which has the basics of RC5 but the implementation is focussed on STM32 series.

..

For the gyro at least, LPF1 is not an anti-aliasing filter (https://community.st.com/s/question/0D53W00000Ac1obSAB/is-it-true-that-the-gyro-of-the-lsm9ds1-has-the-lpf1-low-pass-filter-after-the-adcthis-design-will-suffer-from-aliasing-not)Perhps for the acceleromter it is an AAF?In general, I'm unclear about why there are two LPF.

I'm converting the CubeMX usb audio device example to be audio class 2.0 compliant, with high-speed external phy.I have to implement a feedback endpoint to report the current number of samples per microframe. For this, I have tim2 set up as external timer connected to the audio codec's I2C_SCK bitclock. This gives me a 26.6 fixed point frame count (64 clock pulses per audio frame). The problem lies when I try to calculate the delta time between SOF 's in my USBD_AUDIO_SOF callback (coming from HAL_PCD_IRQHandler -> HAL_PCD_SOFCallback -> USBD_LL_SOF). The callback happens every 125 uS (I can verify this by toggling a gpio), so with a samplerate of 96khz, i'd expect the delta to be about (96000 / 8000 = ) 12 samples, or 768 SCK pulses.The actual delta is nowhere near that.There seems to be a problem reading the timer during the USB interrupt. When reading the timer every second during the main program loop, the delta is as expected (around 96000 samples, or 6144000 pulses).I have

Hi -I had been working on getting FUS support for upgrading images integrated into our firmware, and I discovered that my initialization of the CRC peripheral was causing the FUS subsystem to reject all upgrade attempts. I couldn't find any documentation inside AN5185 that indicated that the CRC peripheral was used for the FUS services, but could I get confirmation that it is indeed being used by FUS?I can get FUS to succeed by resetting the CRC peripheral in my code before invoking (thus deinitializing the CRC peripheral) a FUS upgrade attempt.If this is indeed the case that it requires the CRC peripheral, please update AN5185's table 3 "FUS resources usage".Thanks,Tim

Hello,​I have some question about use STSPIN840.Page 19 in datasheet, R_EN and C_EN's value are 39KΩ and 10nF.In the graph that is the basis of the recommended value, the value of V is 3.3V.​Also in page 18, FAULT and EN pins in MUC are tied Driver's EN/FAULT pin.​And this typical schematic, each EN/FAULT pin's resistor is tied V_DD.Do they have to be tied to 3.3V or is it okay to configure as shown in Figure 9?(In this case, VDD means the MCU's EN pin is 3.3V?)​A lot is difficult because it is the first time to design.​Best regards,Minkyu Kim.​

Hi All,How do I generate a generic Makefile from STM32Cube ide? Preferably for L56 series. Currently when I create a project the Makefile option under toolchains inside the cubemx is grayed out. The CubeMX is installed as part of IDE. thanks,

 I'd like to start with that using the STM32CubeIDE and modify from there to get my own code to work. I looked in the example space and there are no code examples for the F3 series. Thank you for all pointers.

On STLink-V3MINI (https://www.st.com/resource/en/data_brief/stlink-v3mini.pdf) there is a neat connector used for the STDC14 connection, which has the top and bottom sides of a box header but no ends. This means it takes up a smaller footprint space than if it was a normal box header, but is still keyed (unlike just using a pin header with no plastic sides).Can anyone tell me where to find a connector like this, for my own boards?

Hello,I have a STM32CubeMX installed on an offline cumputer (that cannot be changed!)I would like to install the last firmware for L0 familly, so I download:stm32cube_fw_l0_v1110.zipstm32cube_fw_l0_v1113.zip (patch only file)From local, there is no problem to install the version 1.11.0. But when selecting the 1.11.3 file, there is an error "corrupted or not recognized package)How can I install the 1.11.3 FW version? I tried to extract the 1.11.3 zip in the repository directory. But after that, the version 1.11.3 do not appear in the Packages Manager, and version 1.11.0 is no more there!Thank you for your helpAntoine

..

i want to have my CNC system moments feedback, which involves displacements of 0.01mm sensitivity

Hello, The stack size is defined by a macro definition, INTERFACE_THREAD_STACK_SIZE inside the "ethernetif.c" file located under: LWIP/Target.I had to manually increase the size due to stack overflow and any new code generation via CubeMX overwrites those changes. Since code generation always defaults the size of INTERFACE_THREAD_STACK_SIZE to 350, I would hope that there would be a way to adjust it via CubeMX?