Solved

..

..

This STM software allows to monitor and modify the value of some variables in real-time using the SWD or JTAG connection in a non-intrusive way.In the documentation for the use of this software (https://www.st.com/resource/en/user_manual/cd00291015.pdf) we talk about the "Snapshoot" mode (Par.2.5.2): using the code to be integrated into your firmware you can perform sampling of the variables at a given time. This is very useful, because in "Direct acquisition mode" (the standard one) there are some cases in which the variables assume non-coherent values.Following the instructions for the operation in "Snapshot mode", I have integrated in my firmware the necessary code ("softTrace" subdirectory), but by compiling the program I always get an error: '_FAR_DATA_' undeclared (first use in this function) This error is in the source "acqTrigger.c" line 310, one of the files to be included in the project, made by STM.Now my question is: has any of you already used STM Studio in this mode?

UPDATE: The issue has been solved. The nBFB2 option bit had to be enabled.Hello, I am currently programming and STM32L152RE on a Nucleo development board. I am using SysTick as a .5s timer that ran a status LED. Everything was working up until recently when I noticed the LED stopped working, and the processor seemed to be restarting. Stepping through with a debugger showed it was able to run all the setup code correctly, but when I let it run to get to the SysTick_Handler(), it would instead go to the reset handler. I also verified it is caused by SysTick as the code does not crash when I do not use it. I also checked the RCC_CR register after the reset to determine the cause, and only the PORRSTF and PINRSTF bits are set, which didn't help me. Here is the code:int main(void) { clk_init(); statusLedInit(); // Turn status LED on GPIOA->ODR |= GPIO_ODR_ODR_5; usartInit(); SysTick_Config(SYS_TCK_RELOAD_VAL); int val = 0; printStr("Hello World!\n"); while (1) { val += 1; }

Hello, i have a problem to build in PIL mode PMSM_FOC example. The problem is in the use of CRL: "ARM CMSIS SIN CON". After has manually add of the arm_math.h directory (C:\MATLAB\STM32-MAT\STM32\CRL\CMSIS_SIN_COS_CRL\FastMathFunctions) in the include paths (-l) the building process returns the following error code for 100 elements. Building file: C:/MATLAB/STM32-MAT/STM32/STM32demos/MotorControl/FOC/PMSM_FOC_Compute_PIL/PMSM_FOC_Compute/Src/arm_cos_f32.c Invoking: MCU GCC Compiler C:\MATLAB\STM32-MAT\STM32\STM32demos\MotorControl\FOC\PMSM_FOC_Compute_PIL\SW4STM32\PMSM_FOC_Compute\Debug arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -DUSE_HAL_DRIVER -DARM_MATH_CM4 '-DMemUnit_T=uint8_T' '-DMEM_UNIT_BYTES=1' '-DRTIOSTREAM_TX_BUFFER_BYTE_SIZE=128' '-DRTIOSTREAM_RX_BUFFER_BYTE_SIZE=128' '-DCODER_ASSUMPTIONS_ENABLED=1' -DCODE_INSTRUMENTATION_ENABLED -DCA_CHECK_FLOATING_POINT_ENABLED -DCA_CHECK_LONG_LONG_ENABLED -DCA_CHECK_DAZ_ENABLED -DSTM32F429xx -I"C:/MATLAB/

Hello, I have configured a BlueNRG-M2SA as a network coprocessor using the provided DTM_SPI.hex file. I have connected it to an external uC and am able to read data from it. The problem is that as soon as the BlueNRG boots up and the interrupt is enabled on the uC for the IRQ pin, the BlueNRG repeatedly sends requests. The header it sends is always the same: { 0xFF, 0x90, 0x80, 0x60, 0x00 } and I'm assuming the data is too. I am not able to reach anywhere in my main application like initializing gatt or gap layers as it goes from handling one IRQ request to the next, back to back. One potential problem that I am uncertain about is using the same pin, GPIO7, as both the Boot pin and IRQ pin. The BlueNRG is programmed to use the same pin for both of these. The external uC needs to drive this pin low on device reset, but then have it configured as an input by the time the BlueNRG firmware is ready. In order to avoid having two outputs connected to each other at one time, I configured the

Hi,I'm using serial communication with DMA and sometimes the transmission complete interrupt is not triggered (HAL_UART_TxCpltCallback) the issue happens every few minutes, or every several hundred transmissions. I saw https://community.st.com/s/question/0D50X00009XkfArSAJ/dmausart-on-stm32f407vg-tc-interrupt-sometimes-not-triggered and I think it may be related: I am putting variable length messages into the DMA and I wonder whether there's constraints in the length that can be set. I have tested for some time now triying to find a pattern and in all cases the data packet length was pretty small, whenever the DMA stopped triggering the interrupt, the lengths were 17, 11, 5, 5, 3, 5 (6 different tests).So the questoin is, is there any limitation in the data length to set into the DMA? For sending, I'm using HAL's HAL_UART_Transmit_DMA()Best regards.

Hi, is it possible to connect STM32 instead of display and read its pins (A0, RD, WR, D0, D1, D2, D3, D4, D5, D6, D7) to know what device is sending and maybe replace original display with different display?For example I would need to detect that WR pin went LOW and read all pins values at that moment in time. WR is LOW only for 187 nanoseconds. So is there any way to read this fast with STM32? How does display read that data so fast?I have attached display commands which I have read with logic analyzer.

The article in the following link no longer exists (frustrating) and I'd like to refer to the info previously found there.https://touchgfx.zendesk.com/hc/en-us/articles/203642951-MCUs-without-TFT-controllerI did search support.touchgfx.com and did not find it.Apparently one must copy/paste articles because they will disappear?

I'm trying to use STM32CubeMX to enable TouchGFX on a STM32F427 which doesn't have a LTDC peripheral. Is this possible?Per https://touchgfx.zendesk.com/hc/en-us/articles/203642951-MCUs-without-TFT-controller, TouchGFX is capable.Also, what is required to enable TIM? Any timer with any config?Thanks!

I ran across the documentation which has release notes for a version 4.13.1:https://support.touchgfx.com/api/pages.htmlThere is at least one fix that I am interested in.Where/how does one find this update and HOW does one update it?Great job on the documentation page, by the way!https://support.touchgfx.com/docs/introduction/welcome

I am using STM32F779 and trying to use its RTC sub second functionality. Also, using a network time to synchronize with RTC. The issue I am having is as follows along with what I have already tried:In order to advance SSR register to synchronize with network clock first set RTC_SHIFTR_ADD1S bit and then put advance value into the SUBF (at the moment in order to test code i am just using constant lets say "4"Also tried with Delaying SSR (to test if RTC is faster than network clock) by same value of constant "4" after checking there is not RTC Register->RTC_SHIFTR.Set(Any_value); // tried various values to Code is as follows for synchronization if (precise_offset > prediv_s) { /* We check SS[15] is equal to 0 to avoid overflow */ if ((RTCRegisters_m->RTC_SSR.Get() & 0x1000) == 0) { /* We set an advance */ RTCRegisters_m->RTC_SHIFTR.Set(RTC_SHIFTR_ADD1S_MSK); rtc_shiftr_temp |= (0x00000004& RTC_SHIFTR_SUBFS_MASK)|RTC_SHIFTR_ADD1S_MSK; // rtc_shiftr_temp |= ((((

I am using STEVAL-MKSBOX1V1 and I want to do some changes in the firmware. What in-circuit debugger/programmer should I use? Should I use ST-LINK/V2 or STLINK-V3SET or STLINK-V3MINI?Please help me. Thank you

I am genreating a hex file from .elf in post, and adding crc to it. Is there any way to debug using new hex, in cubeide 1.1.0

I'm controlling the temperature of high power heaters in my project. Because ithe product can damage if the heaters stay on too long, I have added code to disable the heaters in the hard fault handler. This way I can be sure that if something goes wrong the heaters are turned off directly.However, it turns out that if the hard fault handler is entered while debugging a breakpoint is set at the beginning of the handler. All safety code that follows after the breakpoint isn't executed until I continue the program.Since the heaters can overheat in a few seconds there is a good chance I'm not fast enough to respond when this happens. Can anyone tell me how I can make STM32CubeIDE not stop there or not add breakpoints at the hard fault handler?

..

I cannot for the life of me find out where the interface descriptors are defined. Examples I have found on the web indicate ( for a CDC device at least ) a file "usbd_desc.c / h" that contains the definitions. There is no equivalent usbh_desc.c file. I can find the structures ok but not where they are initilised. So, my question is: in which file are the interface descriptors initialised?

As the title suggests, I'm trying to implement on of the example applications that come with the cube expansion NFC5 for the NUCLEO-F303RE. The example application is called "Nucleo_PollingTagDetect".Hardware setup: -NUCLEO-F303RE -X-NUCLEO-NFC505A1 What I've done so far: -Started a new project and set it up using CUBEMX. I made sure to setup the SPI, LED pin and IRQ pins so they were routed to the correct Arduino headers (i can give specific set up if needed). -edited Platform.h for my setup. -included the Middleware packages "ndef" and "rfal". -included the STR3911 drivers.What works: -The project gets to the demo loop of the sample application fine. I can push the blue, user button to toggle between "wake up mode on" and "wake up mode off". What doesn't work: -The RF field never seems to turn on and the reader never detects and tags I place near it. -It seems like the function "rfalRunWakeUpModeWorker()" in "rfal_rfst25r911.c" should eventually set "gFRAL.wum.state" to "RFAL_WUM_ST

 I am using SPI1 to communicate with an IMU, which work perfectly. I used the same initialization code for SPI2 making changes for SPI2 and initialize PB13, PB14 and PB15 as SCLK, MISO and MOSI. It doesn’t work and I have run out of ideas. When SPI1 is initialized its SCLK pin immediately goes high, clock is high at idle, but when SPI2 is initialized its SCLK pin never goes high. I have tried initializing PB13 as an individual port and it works fine, goes high when set high and low when set low. So, it appears the hardware is OK. I have also eliminated all the rest of the code, still doesn’t work. I tried using other pins for SPI2, they don’t work either.  My SPI2 Init is attached.  

Hi.I am currently trying to have USB virtual com port to work on STM32L462CEU6. I made simplest project using IDE, just enabling usb then setting the usb class to be CDC. Nothing fancy, no more things than setting the 48mhz clock and flashing cpu. No usb is detected and the cabling is correct. USB is not detected on macos. I tried same approach on a nucleo64 with a stm32L452, which is basically the same chip. Same procedure works, i get the device detected and configured.Tried flashing the 462 with 452 firmware and while flashing works, usb did not.I checked my board and cables thousand times and i am sure it is ok. I get absolutely no signal on the DP and DM pins... at all...Do you have any idea of what to test or bug reports to share?Thanks.

I'm working on a custom boot loader for a STM32F429, where I want to reserve the second of the first four 16K flash sectors for user data. Because the vector table has to start at 0x08000000, the memory layout would look like this:0x08000000 - isr vector table and padding (16K) 0x08004000 - user flash sector (16K) 0x08008000 - bootloader code (224K) ------------------ 0x0800C000 - application code with footer containing version and CRC (768K)This gives me a size constraint of 256K for the boot loader code. That's why I want to use the second flash sector, because this is one of the 16K ones. Nice and small, leaving enough room for the code.I'm using a modified version of ST's original gnu linker script:/* Custom bootloader linker script, edited from ST's STM32F429IITx_FLASH.ld. */   /* Entry Point */ ENTRY(Reset_Handler)   /* Highest address of the user mode stack */ _estack = 0x20030000; /* end of RAM */ /* Generate a link error if heap and stack don't fit into RAM */ _Min_H

Hi all,I am trying the example of USB CDC in:https://www.youtube.com/watch?v=rLnQ3W8gmjY&list=PLnMKNibPkDnEEvQWrDqVuu1w_iQ214GXi&index=35It uses the above functions.But when I compile, I get :undefined reference to `USBD_CDC_SetTXBuffer' and to  USBD_CDC_Transmit_PacketCan someone help ?ThanksEli

..

I'm using STM32CubeMX to create a project for a NUCLEO-F746ZG with the LwIP middleware.Unfortunately, the IP Address Settings (IP, Netmask, Gateway) don't show up in the code anymore. In MX_LWIP_Init() there's justvoid MX_LWIP_Init(void) { /* IP addresses initialization */ /* Initilialize the LwIP stack without RTOS */ lwip_init(); ...without the actual address settings.Before updating CubeMX the settings where done in between those two comments like this:void MX_LWIP_Init(void) { /* IP addresses initialization */ IP_ADDRESS[0] = 192; IP_ADDRESS[1] = 168; IP_ADDRESS[2] = 0; IP_ADDRESS[3] = 2; NETMASK_ADDRESS[0] = 255; NETMASK_ADDRESS[1] = 255; NETMASK_ADDRESS[2] = 255; NETMASK_ADDRESS[3] = 0; GATEWAY_ADDRESS[0] = 0; GATEWAY_ADDRESS[1] = 0; GATEWAY_ADDRESS[2] = 0; GATEWAY_ADDRESS[3] = 0; /* Initilialize the LwIP stack without RTOS */ lwip_init(); ...I can't seem to find them anywhere else (they only show up in the .ioc file).Am I missing something or is this a bug

Hi!I tried to set peripheral initialization order in Project Manager->Advanced Settings.After I finished sorting the list and saved the project, the function list mixed.The problem is reproducable. When you save the project, the function list gets a random order.It would be good if somebody has a solution to this problem.Thanks!