Solved

HelloI'm using 'STM32CubeIDE 1.7.0'.I've copied a project using: The new project failed the first time I built it as the User Code in main.c had not been copied over. Once I added this missing code the project compiled and ran correctly on the Nucleo.However, I'm still getting the warning symbol on the project name:Is there a panel in STM32CubeIDE that I can open to see what this warning is about? Regardsron_w

Hello, I am using a custom board with stm32f411ce and I want to communicate with an SD card over SPI. I have written my own SPI library and I'm trying to write most of the code using registers. I have searched an SD example with registers and found out that I should use a library. I'm developing in Keil IDE and don't want to use Cube MX. can someone help?Thanks

..

Hi!I'm trying to output the LSE clock on the PA8 pin on my Nucleo64 STM32L476 board.The code I have written is the following:#include<stdint.h>   #define RCC_BASE_ADDR 0x40021000UL   #define RCC_CFGR_REG_OFFSET 0x08UL   #define RCC_CFGR_REG_ADDR (RCC_BASE_ADDR + RCC_CFGR_REG_OFFSET )   #define GPIOA_BASE_ADDR 0x48000000UL   int main(void) { uint32_t *pRccCfgrReg = (uint32_t*) RCC_CFGR_REG_ADDR;     //1. Configure the RCC_CFGR MCOSEL bit fields to select LSE as clock source: 0111: LSE clock selected *pRccCfgrReg &=~(0U << 27); *pRccCfgrReg |= (1U << 26); *pRccCfgrReg |= (1U << 25); *pRccCfgrReg |= (1U << 24);   //2. Configure PA8 to AF0 mode to behave as MCO signal   //a ) Enable the peripheral clock for GPIOA peripheral // RCC_AHB2ENR uint32_t *pRCCAhb2Enr = (uint32_t*)(RCC_BASE_ADDR + 0x4C); *pRCCAhb2Enr |= (1U << 0); //Enable GPIOA peripheral clock   //b ) Configure the mode of GPIO

I am trying to generate hex file for my boot loader. I need a fix length hex file for my boot loader. I tried arm-none-eabi-objcopy -O srec --srec-len 0x10 ${ProjName}.elf ${ProjName}.srec;arm-none-eabi-objcopy -I srec -O ihex ${ProjName}.srec ${ProjName}.hex command for generate fixed length hex file it's not working.:10FB70002B6803B1236038BDA40F0124F8B500BF82:10FB8000F8BC08BC9E467047F8B500BFF8BC08BC7E:04FB90009E467047D6:10FB9800626C655F68616E646C65725F7461736BDB:10FBA80000000000256C6C75000000002573000043:10FFC8006F00000025660000437573746F6D6572DD:10FFD8005F4E616D650000004F70656E5F536C6F1A:10FFE80074000000436C6F73655F536C6F7400009E:08FFF8004F726465725F446101:02000004900367:100000007465000041646472657373004C617469C7:1000100074756465000000004C6F6E6769747564E8So any other command to generate fixed length hex file or how to solve this issue?Thanks in advance

I need to use a gyroscope with my Nucleo-64 board, but the gyroscope needs to stand apart (i.e. at the end of a cable). Is the STEVAL-MKI197V1 a good match? Can I connect it directly to my Nucleao-64 with a SPI cable, *without* using an expansion board? (such as X-NUCLEO-IKS01A1, X-NUCLEO-IKS01A2, X-NUCLEO-IKS01A3, X-NUCLEO-IKS02A1).

What is the default USB settings e.g baud rate, parity, stopbit, databit etc for STM32 when using USB_FS?In this case I can only choose FULL SPEED 12 mb/s. Is that 115200 bps?I'm using STM32F373VBTx processor

#GPRS #SIM800 #OTA #STM32f4

The goal is to have the microcontroller which is in sleep mode, wake up when the voltage on a certain ADC channel drop below a set voltage.The plan was to put the core to sleep via HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON, PWR_SLEEPENTRY_WFI);and have it wakeup via the analog watchdog interrupt. DMA is also enabled in circular mode. The idea is that the ADC peripheral handles the task of monitoring the voltage without the need of the Cortex-M4 core running.The issue I am running into is that the DMA interrupts after every conversion forcing the core to wakeup. I tried disabling the DMA interrupt and that causes the analog watchdog to not work. Is it even possible to have the Analog watchdog functional with the core stopped or do I just have to wakeup every so often and check the ADC channel before going back to sleep.Below is the ADC initialization code. uint16_t AnalogBuffer[1]; ADC_ChannelConfTypeDef sConfig = {0}; ADC_AnalogWDGConfTypeDef AnalogWDGConfig = {0}; hadc1.I

Hi,I'd like to be able to read/write for debug purposes peripheral registers of the MPU and MCU from Linux user space. Of course all under root permissions. The most straightforward way should be doing it using /dev/mem but I'm not sure if it is a best way to go. Any thought would be highly appreciated.Thanks.

See:https://community.st.com/s/question/0D53W00000kvhhCSAQ/xnucleolpm01a-powershield-dynamic-current-range-too-limitedAt the time of starting that thread, the STM32-LPM01-XN firmware for the X-NUCLEO-LPM01A board was at v1.0.1.I see that the STM32-LPM01-XN firmware for the X-NUCLEO-LPM01A board is now at v1.0.6.But I can't see any Release Notes - they aren't in the downloaded Zip, and I see nothing on the Product Page:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-utilities/stm32-lpm01-xn.htmlSo the question is: where are the release notes?

I am using the STM32411CC MCU for reading a signal from a GPIO IDR, process it, and write it to a GPIO ODR. An interrupt routine is a suitable method for signal processing on demand. Question: how can the host computer create an interrupt during runtime if no GPIO pins are available? Is it possible to create a software interrupt with the ST-Link V2 during runtime? Thank you for your feedback.

I've recently put together a new design and ST-Link doesn't seem to detect the STM32L486 on the board using the STM32CubeProgrammerThe part used is the 144 LQFP version, but I've double checked the pins and connections for the SWD port. I'm supplying the microcontroller with 3.3V, but powered up is sitting at 3.2V strangely. Strangely I'm noticing some shorts from other pins to the 3v3 rail from some GPIO pins (PA2, PF2, PF11) and I'm not sure if this is normal when the device is unpowered.Does anyone have any idea what might be the problem here? Schematic below

/*UPDATE*/ It turned out that im my case the problem was in the start up routine:There was a "Start up" project (written not by me) that was downloaded at 0 flash address and it was jumping to another address where my project was located.I did not know that in this "Start up" project there was an RTC initialization (which prevented my RTC from running continuously).Everything below this sentence is what I wrote before I knew where the problem is.Good day!I'm using RTC in a STM32F407VG controller.I configured RTC_ALARM_A to generate an interrupt every second (this indicates when a second changes in RTC). By this interrupt, an oscilloscope and a reference 1Hz clock from another device (that is not being reset) I watch whether my RTC is ticking consistently.With this setting it can be seen if MCU's RTC is shifting during power reset. And that's exactly what I'm observing (don't know the absolute value of the time shift, but I see that the phase of MCU's 1Hz clock output is changing random

Hardware:MCU: STM32L4R9ZGJ6 (Custom board)OSPI mapped to address 0x90000000ST-Link V2PH3-BOOT0 pin pulled to ground with 10k Ohm resistor.Software:IDE: STM32CubeIDE 1.6.0 (Build: 9614_20210223_1703 (UTC)SDK: STM32Cube_FW_L4_V1.14.0TouchGFX assets are loaded in OSPI at address 0x90000000 (Probably not relevant to my issue)STM MCU Option Bytes Configuration in STM32CubeProgrammer:nBOOT1: CheckednSWBOOT0: CheckednBOOT0: CheckedIssue:Hello,My issue is that when attempting to debug the MCU in STM32CubeIDE, it often attempts to start at address 0x1fff51F4 with the message "Break at address "0x1fff51f4" with no debug information available, or outside program code". main() is never called because my breakpoint at the top of main() is never hit. To mitigate the issue, I simply press the red "Terminate" button to stop the debug session, then press the "Debug" button to restart, and the program then loads at the correct address and breaks in main(). This happens randomly without any changes to th

After reading most of the topics concerning my question and not finding an answer, which solves our problem, here my describtion:We are currently integrating OpenAMP in our Application. For now, we are using the configuration from the OpenAMP_TTY_echo example project with enabled trace logs, and a single virtual UART between the M4 and the A7.When starting the Application by using 'rproc start' in a booted linux system, it works as expected. The trace logs are available, and the /dev/ttyRPMSG0 virtual UART is loaded:cat /sys/class/remoteproc/remoteproc0/state outputs 'running'cat /sys/kernel/debug/remoteproc/remoteproc0/trace0 shows our debug outputs from the M4We can send dummy data to /dev/ttyRPMSG0 and get the echoed responseIn our use case we need the M4 Application to start as early as possible, so we have configured u-boot SSBL to load the ELF file and start the M4 execution. We are then facing the problem that the software is started, but the linux kernel does not load the /dev/

Cant compile code from CubeMX generated project. I get:undefined reference to `touchgfx_init'I have generated code from cubeMX and then TouchGFX and then clicked build all in the CubeIDE, but get errors I cant seem to fix. Any help appreciated...

We get three 16-bit value from the register of ISM330DLC, how to use the three values to calculate the acceleration? Please help.

-

Hi i have a custom board with SPC560B50L3 that is in the  SPC560BC Family.There is no SPC560BC xx Firmware Updater Component.If i try to add it (with shw incompatible components) of course i have problem generation files.There is some alternative?Thanks

I was able to program my SPC584B70E3 via UDESTK 5.0 and SPC5-UDESTK tool. After using it for a while I tried to build a Bootloader application. Now I cannot access the device and program it or erase it.When I try to flash something I get the pop-up error message "Can't activate FLASH/OTP Device !" and the error messages below appear in the Messages List:Fr 06.08.2021 10:46:30.430, Error, Core2::PpcJtagTargIntf, Operation has failed partly ! Fr 06.08.2021 10:46:30.433, Error, Core2::PFLASH, Failed to download driver section 0x400A8000-0x400A900B Fr 06.08.2021 10:46:30.433, Error, Core2::PFLASH, Initializing FLASH driver on target failed Fr 06.08.2021 10:46:30.433, Warning, Core2::PFLASH, FLASH programming for device '2 MByte OnChip program FLASH (Starterkit)' not available !Is my device broken? Is there a way to fix it?Thanks for all the answers,Talha Uyar

static void PingPong_Process(void) { Radio.Sleep(); APP_LOG(TS_ON, VLEVEL_L, "PP Task Start\n\r");   if (isMaster == true) { //Master switch (State) { case TX_TIMEOUT: APP_LOG(TS_ON, VLEVEL_L, "Master Tx timeout\n\r"); case TX: HAL_Delay(1000); HAL_Delay(Radio.GetWakeupTime() + RX_TIME_MARGIN + random_delay); APP_LOG(TS_ON, VLEVEL_L, "Master Tx start\n\r"); // master sends PING memcpy(BufferTx, PING, sizeof(PING) - 1); Radio.Send(BufferTx, PAYLOAD_LEN); break; default: break; } } else { //Slave switch (State) { case RX: if (RxBufferSize > 0) { if (strncmp((const char*) BufferRx, PING, sizeof(PING) - 1) == 0) { UTIL_TIMER_Stop(&timerLed); // switch off red led BSP_LED_Off(LED_RED); // slave toggles green led BSP_LED_Toggle(LED_GREEN); // Add delay between RX and TX HAL_Delay(Radio.GetWakeupTime() + RX_TIME_MARGIN); APP_LOG(TS_ON, VLEVEL_L, "Slave Rx Received - Wait for New D

..

Hi all,I have a setup with Pi and STM board. The Pi acts like an SPI master, the STM is setup as SPI full duplex slave.The SPI input and outputbuffer are the same size, what i want is that when i receive x bytes from the pi, i send back the first x bytes of the SPI output buffer back .I can receive data from the Pi with no issue's, but when i put data into the DMA SPI outputbuffer , this data is not send by the slave(STM) the next time the Pi initiate an SPI communication.I use HAL library and setup the STM like this : in main(void) -> uint8_t cnt=0; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++; spi_buf_out[cnt]=cnt++;   HAL_SPI_TransmitReceive_DMA(&hspi2,spi_buf_out,spi_buf_in,SPI_SIZE);At the logic analyser i see correct data at MOSI and MISO lines when the pi sends the first SPI package.But at

STM32F4xx standard peripherals library version 1.0.0 is required.Please tell me how i can get that version.Only the latest version 1.8.0 can be downloaded from ST site.​Thank you.​