Solved

I would like to use node-red on STM32MP157C-DK2 to handle datas computed and shared with IPCC by Cortex-M4.Any advice ?Thank you

Hi,We have use STM32L496 controller, can I interface external SRAM or pSRAM on QSPI pins?If not, what is the other option for accessing the external SRAM.

Hi ,Ive started configuring gpio's and ADC with stm32f103 in Assembly ,Can somone tell me the basic procedure to setup ADC interrupts ?? .There's alot to keep in mind while setting up the initialization and i've failed at it.

I am planning to connect a LSE 32kHz crystal and a 25MHz crystal to the HSE input, but I am having a hard time identifying whether the STM will drive my crystal selection within the limits of the 100uW drive level. I have read thru the app note, but it still isn't clear. The crystal I am using for the HSE is the ECS-250-8-33-JGN-TR. It has a 100uW drivel level maximum. Will this be compatible with the STM32H753?

In old AC6 workbench, I could add such python script as external tool to auto-build always before compiler runs. Now with STM32CubeIDE, I've found how to do manually with 'external tools' button. Can I add back to project to auto-run again?

..

Using STM32CubeMonitor-RF I am able to update my device via OTA with one small issue. I send the command to program my device and my application gets deleted and the device reboots into our OTA application but I have to search for my device a second time, select the device and then reinitate the programming process. It works fine as a two step process but would like for it to be a single step process.I have a BLE sniffer and I can see where the problem occurs but I have not been able to figure out what is causing it.Here's a snippet from the Nucleo board that works:Here's the snippet form our device that doesn't:The LL_TERMINATE_IND is missing from our connection but I am not sure what is causing the problem.

I configured a few working projects with FreeRTOS and CubeMX, but today I notified something strange with my .ioc files.I initally configured a project with CubeMX 5 and after having configured the FreeRTOS, the NVIC configuration pages looked like that:(Don't mind the red circle specially, it is an old screenshot). But the point is, there were a column to select if the interrupt will use some freertos functions and if so, it applies the priority level according to the parameter "LIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY" of your FreeRTOS", in my case, level 5.It was great and clear.But now, there isn't anymore this column with this great feature with cubeMx 6 which is sad (see picture below)But more important, in this same project, the priority as been modified without my will to 0 instead of 5.Unless I am wrong, FreeRTOS API can't be called from interrupt with lower number (higher priority) than the parameter mentionned earlier.So my project would't be working because of that. Happily f

Hello,we use STM32H7 in our new development. I was excited about the announcement of the new revision V because it promises an increase of speed from 400MHz to 480 MHz. My distributor told me that except for that, the devices were hard- and software compatible.Now I set a rev V STM32H742 into our prototype and after hours found out that there are a number of differences in ADC alone.So my first general question is, if there is a paper summarizing all the differences?My second question is, if the new ADC will in any case have at least the same performance as the old one (we use it at the edge of the old specs)?The third question is, when will a new package for CubeMX be available that support the new revision? I have STM32H7 package ver 1.2.0 and it complains when I try to set sysclk to 480 MHz.Now some questions in detail:There is a new clk divider by two for adc_ker_clk. With the old settings for rev Y I get only half the samples per second. Can I simply double pll2_p_ck to get back t

..

is there any solution or tool for memory information export to text file as followed window shows.

I think there is a bug in the new CubeMX 6.0 when generating code using freeRTOS. It may just be when migrating from an older CubeMX project to a newer one, I'm not sure.I updated a project that was built using CubeMX 5.3 to CubeMX 6 and rebuilt all the files. While there was an issue with the Call to HAL handlers being unchecked under the NVIC controls so that all the interrupt handlers no longer called the HAL files, that was at least easily fixable. However, I did notice a change to the SysTick interrupt with regards to freeRTOSBelow is the code generated by CubeMX 5.3void SysTick_Handler(void) { /* USER CODE BEGIN SysTick_IRQn 0 */ /* USER CODE END SysTick_IRQn 0 */ HAL_IncTick(); #if (INCLUDE_xTaskGetSchedulerState == 1 ) if (xTaskGetSchedulerState() != taskSCHEDULER_NOT_STARTED) { #endif /* INCLUDE_xTaskGetSchedulerState */ xPortSysTickHandler(); #if (INCLUDE_xTaskGetSchedulerState == 1 ) } #endif /* INCLUDE_xTaskGetSchedulerState */ /* USER CODE BEGIN SysTick_IRQn 1 */

I have an interrupt which I'm trying to streamline (for an STM32F031K6). I am using some commands like GPIOA->BSRR |= (1<<4);and i was surprised to see how much there is in this command in the disassembly. Is there any faster way of implementing this?

Hello.I was developing a GUI with STM32F767 & RGB TFT LCD.However, the specification has changed and I should consider changing to the STM32H743.Are there any issues to watch out for when changing the cpu?Does CubeIDE & TouchGFX Deginer support H7 development environment?If yes, which version can I use?​Thanks for your help.

I'm looking for a simple, low cost tag (passive ~1-2 cm square nominally transmitting a unique ID one-way) & reader (antenna & analog front-end) solution. Although read range data is ferociously difficult to find, it must be readable at a distance >= 1 ft under ideal (low noise, no collision) conditions. That would appear to lead me to ST25TV Type 5 'vicinity' tags, the ISO15693 standard with its greater range (as opposed to ISO14443) and the ST25R3911B chips. Can anyone suggest tag and reader (ST-LINK V2 programmable) with demo board products to get me started or otherwise advise?

HelloI am using stm32Cube IDE.Where should I edit the makefile?Thank you.

I've been trying to use TIM1CH2N to generate PWM to control ws2812b RGB LED. I have got one working library for TIM1CH2, but I'm unable to generate the same signals in the CH2N pin (STM32H750VB)​. Can anyone help me out to resolve this issue?

..

SPC5Studio cannot use the malloc() and free() functions in the stdlib.h standard library.​For Example:char * str = (char *) malloc(1024); free(str);​​I've added the GCC standard header path to SPC5Studio, and other library functions are used normally, and I can't compile through when using the malloc function, reporting the following error:​c:/spc5studio/eclipse/plugins/com.st.tools.spc5.tools.gnu.gcc.ppcvle.win32_4.9.4.20190604105544/toolchain/bin/../lib/gcc/powerpc-eabivle/4.9.4/../../../../powerpc-eabivle/lib\libc.a(lib_a-sbrkr.o): In function `_sbrk_r': sbrkr.c:(.text._sbrk_r+0x1a): undefined reference to `sbrk' collect2.exe: error: ld returned 1 exit status make: *** [build/out.elf] Error 1​​How do I solve the problem that malloc and free are not available, or how do I dynamically allocate memory in SPC5Studio?​Thank you.​

I was looking at the STM32L476 datasheet (https://www.st.com/resource/en/datasheet/stm32l476vg.pdf) and noticed there's no LQFP100_SMPS pin definitions (see Table 16 or chapter 7). All other packages seem to have an _SMPS section. Is this an oversight or is an external SMPS not supported on the LQFP100 package?I noticed that the STM32L496, which seems to be pin compatible, does have an LQFP100_SMPS option, which is why I ask.

Hello everyone,I'm using STM32F429 MCU (STM32F429I-DISC1 board). I was generating PWM signals on PA1, PA2,PA3 and PA5 using TIM2 ... The important part is that the PWM signals on PA3 & PA5 are fine where the high digital state is at 3.3V. For PA1 & PA2 , the PWM signals have digital high state at 650mV !? ... I attached a picture to show the PWM (on PA3) and the PWM (on PA1)I also tried to make PA1 as an output with an open drain and a pull-up resistor ... when I give it high state ... the output voltage of the pin is 0V .... The pin is acting as if there is some kind of a medium pull-down resistance.Does this mean that these 2 pins are damaged?(Note: this is not a probe or oscilloscope problem ... I measured the digital high state with a voltmeter as well)ThanksNour

HiSo here's the thing: I've been getting familiar with flashing the STM32F407 discovery board using the in-build bootloader via USART3. Boot mode is set to System memory using Boot0 = 1 (5V)Boot1 = 0 (GND)I am using an USB to serial converter. Connection is:USB_serial_TX (Green wire) <=> MCU_RX (PC11)USB_serial_RX (White wire) <=> MCU_TX (PC10)When using the bootloader to upload a program to control an LCD via I2C, I get the expected result. However, when trying to run a simple GP timer to control an LED, the LED does not blink.The code itself works, because when using the on-board STLink programmer, the LED blinks. Just with the bootloader, it does not. Any ideas? Thank you.#include "stm32f4xx.h"   #if !defined(__SOFT_FP__) && defined(__ARM_FP) #warning "FPU is not initialized, but the project is compiling for an FPU. Please initialize the FPU before use." #endif   void funcISRInit(); void funcGPIOInit(); void funcTIM4Init();     int main(void)

Hello,the UART is not working. st-link is stand alone (not connected to Nucleo anymore)i am using a separate stm32f446ret6, tx(PIN16) and rx (PIN17) are connected to CN3 (TX/RX).in addition the SWD CN4 of the st-link is used (all connections are made to the uC).Programming is working fine. COM port is shown once i connect the st-link but tera term is showing nothing.going back to a second board where the st-link is still part of the Nucleo (not break up) everything is working, uart is working. What do you need to know to support me?

I am using Stm32l0 and am receiving data from GPS via uart but I am facing this problem.uart receives the first byte and then repeats the number of bytes it wanted to receiveFor example:AL_UART_Receive (& huart1, buf, 80, 200);It receives the first letter "$" eighty times !!like this $$$$$$$$$$$$$$$$$........80 time

The st25r3916.pdf data sheet includes Table 23 which lists the Initiator operation modes. This list includes ISO14443A/B but excludes ISO15693.