STM32 MCUs Embedded software

I am Using STM32L412CBT6 controller in that the application working with a regular power supply 2.8 volts but with a battery the remianing modules(i2c/RTC) but in SPI F-open is not working

I've built an STM32F767 board on which I used the LAN8742 Phy chip as per the Nucleo board. The firmware is CubeMX derived with lwip and FreeRTOS used, and all IP addresses are static. If I connect my board to a 100 Mbit hub and a PC then I can sometimes connect and then get reliable comms between the PC and my board. The trouble is that after connecting a PC or a Raspberry Pi to my board directly it doesn't connect. LED2 is lit solidly and LED1 flashes rapidly.Does anyone have any suggestions? Why does my Phy say the link is up but the Pi says it's down?Is it worth trying to force the Pi to work at 100 Mbit?

My setup:SPI(Tx only) + DMA (not circular) and no FIFONow HAL_SPI_TxCpltCallback() is executed only if the transfer-complete-flag is also set before HAL_DMA_IRQHandler() is handled for "half transfer complete interrupt"Problem is: in HAL_DMA_IRQHandler():hdma->ErrorCode |= HAL_DMA_ERROR_FE;triggers because the FIFO is off and should be ignored because FIFO is not used.But it triggers the error routine at the end of HAL_DMA_IRQHandler() and causes the problems.Workaround:Always activate the FIFO.

I can't write word data to specific Page flash use LL driver.This is my test function for testing.void flash_word_test(uint32_t addr,uint32_t val) { uint32_t page; ErrorStatus status; DEBUG_PRINT("\nWrite value: 0x%x to address: 0x%x\n",val,addr); status = FLASH_Unlock(); if(status == ERROR) { DEBUG_PRINT("Flash Can't Unlock!\n"); return; } page = FLASH_GetPage(addr);   FLASH_PageErase(page); /* If operation is completed or interrupted, disable the Page Erase Bit */ CLEAR_BIT(FLASH->CR, FLASH_CR_PER); status = FLASH_WaitForLastOperation(1000); if(status == ERROR) { DEBUG_PRINT("Page erase err!\n"); return; } FLASH_Program_Fast(addr, val); /* If the program operation is completed, disable the PG or FSTPG Bit */ CLEAR_BIT(FLASH->CR, FLASH_TYPEPROGRAM_FAST); FLASH_Lock(); DEBUG_PRINT("Read value: 0x%x to address: 0x%x\n",read_word(addr),addr); }This code run to: *(uint32_t *)dest = *(uint32_t *)src; inFLASH_Program_Fast(addr, val) function and go to

I'm looking to control the CDC_Receive_FS interrupt in a manner that I'm hoping is supported by the lower level hardware, but I'm having difficulty locating registers and functionality to support this behavior.To give a hint to the architecture I'm working with. When the CDC_Receive_FS callback is triggered by interrupt, I take the data and put it into a FIFO queue. I'd like to:Be able to "disable" the interrupt when the FIFO is full such that all messages that are attempted to be sent by the host are NAK'd until I've handled the FIFO and am ready to accept new messages.For handling large file transfer, I'd like to be able to make sure the UserRxBufferFS is completely filled with data BEFORE I receive the interrupt/callback. The idea here is that I can receive a full buffer, transfer it via MEM_TO_MEM DMA_IT, and then receive a new completely filled buffer afterwards. I don't want to receive a bunch of partially filled buffers of a few bytes at a time.I'm trying to get a grasp of how t

CubeIDE makes a completely different file structure, some includes cannot be found "VOID" is written capital and causes an error, etc. I am completely new to RTOS, I did some bare metal HAL with CubeIDE and that worked quite well, but just started recently with STM32 (LabVIEW programmer...).If there is a good tutorial that really starts from scratch with azure and CubeIDE and not just opens and example, that would be very helpful.Any help is much appreciated! Nice greetings, Guenter.

The symbol FLASH_OPTR_DBANK is used to determine the dual bank configuration in stm32g4xx_hal_flash.h, but it is also used for a register bit for the dual bank configuration (CMSIS). If this arrangement is correct, the G4 HAL library can not handle single bank configuration. Is this intentional?EDITOther flash organization constants defined a bit strange, too.For example, FLASH_PAGE_NB for number of pages is 128 for dual bank and 64 for single bank. FLASH_PAGE_SIZE is 0x800U for single bank (this is okay) while this symbol is not available for dual bank with what seems to be corresponding symbol is FLASH_PAGE_SIZE_128_BITS defined as 0x1000U which doesn't make sense in all sense.

Hello,I'm working on an a project that uses an ST32G474, and it needs to run two different/independent applications. The project requires that from a reset, the device boots from Bank2 every time. The application in Bank2 will then decide if it is ok to then jump to, and start running the application that is stored in Bank1.The dual-boot example from ST isn't exactly what is needed, because it flips the BFB2 option bit during each boot, to toggle between banks. My application requires to always boot from Bank2, and then jump to Bank1, without going through a reset operation.From reset, I'm able to get App1 to run from Bank1 when BFB2 is cleared, and also from reset, I'm able to get App2 to start and run from Bank2 when BFB2 is set. However, when I try to jump from App2 to App1, I'm not succeeding. Through various different tests, it looks as though App2 somehow either jumps to itself, or I jump somewhere and just crash.I've tried to figure this out reading various different posts about

Hello everyone,For a project i would like to flash firmware from 1 chip via another chip. So now my question is whether this is possible because in the application note AN2606 they say that this is possible via RS232 for certain chips. Is this also possible for RS485 and does anyone have an example of this or a good way to deal with this?Ex:USB -> STMF412RGT6 -> STMF030C8T6Thanks in advance!

I downloaded the en.x-cube-cellular.zip and unziped the folder STM32CubeExpansion_CELLULAR_V5.2.0.I imported the STM32CubeExpansion_CELLULAR_V5.2.0\Projects\STM32L496G_Discovery\Demonstrations\Cellular\IDE\STM32CubeIDE\DiscoL496_RD_BG96v2_STMOD project into the cube IDE and tried to follow the mqtt readme.txt where i have to "Remove 'Exclude from build' option for the following components of the IART project". But i dont finde the "Exclude from build" option. 

I downloaded the en.x-cube-cellular.zip and unziped the folder STM32CubeExpansion_CELLULAR_V5.2.0. I then installed the changes to upgrade to V5.2.1.I imported the project into CubeIDE and found the MQTT sample was not imported. I then tried to follow the mqtt readme.txt where i have to "Remove 'Exclude from build' option for the following components of the IART project". That note is not too helpful because, as far as I can tell, there are no excluded files that I can include. Anyone know how to get MQTT working for this DISCO board?

I've created a new project using HAL for the NUCLEO-F207ZG with CubeMX that ships within CubeIDE (1.5.0). After implementing a minimal network stack from scratch that supported the bare minimum of ARP, IP and ICMP to ping my board, I was wondering why I was only ever receiving broadcast Ethernet frames, but never frames designated at my board.Turns out the generated code in eth.c by CubeMX has an obvious bug when it comes to initializing pointers with array values: heth.Init.MACAddr[0] = 0x00; heth.Init.MACAddr[1] = 0x80; heth.Init.MACAddr[2] = 0xE1; heth.Init.MACAddr[3] = 0x00; heth.Init.MACAddr[4] = 0x00; heth.Init.MACAddr[5] = 0x00;MACAddr of ETH_InitTypeDef is not defined as uint8_t[6] but simply as a pointer to uint8_t.typedef struct { // ... uint8_t *MACAddr; /*!< MAC Address of used Hardware: must be pointer on an array of 6 bytes */ // ... } ETH_InitTypeDef;Nowhere in the code this pointer gets allocated, so the values end up pretty much nowhere.My quick workaround n

There are many threads about using internal flash as MAss Storage in the USB Mass Storage Class, but non of them ever lead to anything.Has anyone actually managed to get it working and is willing to share their code? I have scraped the internet for any info, but cant't find anything that actually works

I have a custom board with an STM32H743ZIT6 on it. Configuring the OTG_HS2 controller with STM32CubeMx and STM32Cube_FW_H7_V1.9.0 as a USB Host and MSC, I can read a USB memory stick.The question is: my oscilloscope shows the DM and DP lines being clocked at 6MHz. Is there a way to configure the OTG_HS2 to clock them at 12MHz?

Hi, We are designing a USB 2.0 interface between STM32H750IB and PC.PC will be acting as Host and STM32H750IB will be acting as Device.But for some reasons like future upgradability, we are using USB Type-C Connector.Note that we are going to use USB 2.0 pins for Data transfer alone.Our concern here is, what all pins/signals we need to use in Type-C connector, may be for configuration process for determining port’s role or for any other reasons also.Also we are not using power delivery option (neither source nor sink). Can I leave VBUS pin of MCU floating? If not, can we feed from 5V Regulator, instead of Bus power ? Because if we have to feed Bus power in Type-C, then, you might be knowing, that one has to use different chipsets like PD (power delivery) Manager etc.Appreciate your quick response. Best Regards,Preetham

Hello everybody,I am using the NUCLEO-L476RG to send simple ACII text over UART (RS232 adapter) or USB CDC as a virtual COM port. UART communication is working seamlessly but when I use the USB CDC library functions from STM there is hapenning something strange I cannot explain:I am sending in regular intervalls ASCII-tesxt in the follwoing format: ABP;***;***;***\nThe * stands for different numbers. normally I would see this kind of text flow on a terminal like hterm:ABP;***;***;***\nABP;***;***;***\nABP;***;***;***\n... and so onbut with the USB CDC usage I see occasionally this:ABP;***;***;***\nABP;ABP;***;***;***\nABP;***;***;***\nABP;***;***;***\nABP;ABP;***;***;***\nwhen I halt the debugger to check if my character array is corrupted, it isn't. So my assumption is that there is something not working correctly with the USB CDC device library from STM. This is the code, that gets invoked when I transmit the ASCII-text:sprintf(Communication.measure,"ABP;%ld;%ld;%ld\n",Patient.Systol

I've started a new project, using STM32CubeIDE which I downloaded yesterday, and the check for updates says I am on the latest. Nice and simple LED flash and a Hello world over UART.I am using USART2, setup as asynchronous. I have tried with and without DMA. Bar my blink code, everything is auto generated by the CubeIDE.In all cases the programme gets stuck in an infinite loop in the HAL_UART_Init(&huart2) call, inside MX_USART2_UART_Init().Digging deeper I find where it is getting stuck in HAL_UART_Init(&huart2) is:return (UART_CheckIdleState(huart));Inside here is it in the call:/* Wait until TEACK flag is set */ if (UART_WaitOnFlagUntilTimeout(huart, USART_ISR_TEACK, RESET, tickstart, HAL_UART_TIMEOUT_VALUE) != HAL_OK) { /* Timeout occurred */ return HAL_TIMEOUT; }Where it seems that the TEACK flag never gets RESET. Confusingly the comment says SET, but the function call says RESET. I am not sure if this is the issue or not.Grateful if anyone can point me in the directi

file - stm32f7xx_hal_adc.c function - HAL_ADC_ConfigChannel issue - The ADC_CHANNEL_VBAT and ADC_CHANNEL_TEMPSENSOR channels are shared so only one can be used at a time. If you want to use both, you will need to swap between the two. When swapping from VBAT to TS, the VBAT flag remains enabled in ADC->CCR causing ADC_CHANNEL_VREFINT to read unexpected values.work around - when changing channels from vbat to the temp sensor, also clear:CLEAR_BIT(ADC->CCR,ADC_CCR_VBATE);suggested driver update - if(sConfig->Channel == ADC_CHANNEL_TEMPSENSOR) { /* Ensure the vBat channel is disabled */ CLEAR_BIT(ADC->CCR,ADC_CCR_VBATE);   /* Delay for temperature sensor stabilization time */ /* Compute number of CPU cycles to wait for */ counter = (ADC_TEMPSENSOR_DELAY_US * (SystemCoreClock / 1000000)); while(counter != 0) { counter--; } }

I have next trouble:stm32f407vgt6 mcu on my diy board with realized OTG_FS USB host and Android accessory application, that have connecting succesfull to it;After connect cable to board all working perfectly: connection and enumerates succesfully;If cable is stay in place and to turn mcu power off, then when i turn mcu power is on, connect is not reastablished as the bit PCSTS in registry of OTG_FS_HPTR not initialize;Note: that if ST-LINK V2 is connected to the SWD pins and 3.3V goes from it with the same manipulations, the connection occurs normally.The board was not made by me and there is a suspicion that the series resistors in the D + and D- circuit do not correspond to the datasheet: they cost 10 ohms instead of 22.Any help please.

..

Hi everybody,in my current project I use G474RE MCU and I wanted to use internal bootloader with the same tools which I've used with some previous projects and F401 MCU.I jump to internal bootloader with following code (ported from some official reference example):#define dSystemMemoryAddress 0x1FFF0000UL #define dSystemMemoryResetVector 0x1FFF0004UL   void jump(void) { LL_APB2_GRP1_EnableClock(LL_APB2_GRP1_PERIPH_SYSCFG);   /* set stack pointer to the bootloader start address */ __set_MSP(*((uint32_t*)(dSystemMemoryAddress)));   /* system memory mapped at 0x00000000 */ __HAL_SYSCFG_REMAPMEMORY_SYSTEMFLASH();   /* jump to @bootloader + 4 */ ((void (*)(void))(*((uint32_t*)(dSystemMemoryResetVector))))(); }Then I wanted to use exe app "Flash loader demo" but it's doesn't support G4 family yet. By the way version on the site is 0.2.8 from 2015 which is kinda outdated ;)I've checked AN3155 (Bootloader USART protocol) and I tested some commands."Get" command is fi

The product is a temperature logger for use in the shipping industry. The controller will wake up in definite intervals and record the temperature reading and saves it in the memory. We need to store the data in PDF format for the end-user to download the same after use.

Hi, I'm using STM32L452, and i need to get the time and date from RTC. The RTC works fine, but when i enter in standby and check the time after wake up (via RTC), the RTC only incrment durring the waked time, and doesn't count the time durring standby. It seems that during standby mode, the RTC stops increment the time/date.So my question is: can i use the RTC to wake up from standby and to keep track the time at the same time, or it isn't possible to do that?    Anyone have this same issue?

What I do now:Initialize all peripheral in Default mode (this is the dialogue option)USB_OTG_FS MODE: Device Only | Activate VBUS : VBUS sensing | Activate SOFUSB_DEVICE (as middleware) Class For FS IP: Communication Device Class (Virtual Port Com)Default clock configuration (no changes from as it proposed by Cube)I generate it as MakefileAnd just build it and flash it. The only COM port I saw it's ST-Link (com3)As sanity check: usb cabel connected to both usb_connectors on board (not only to ST-Link micro usb) after connecting usb to main part of the board LD8 (green) lights up.The blinking blue led just for debugging purposes, to make sure that board was flashed.But I don't see another COM port into device manager, only the ST-link one:

In function HAL_DMA_IRQHandler() the lines 872, 914, 949 modify the hdma->State variable after __HAL_UNLOCK(hdma) has been called.STM32 HAL is full of bugs, especially race condition related ones, but this one seems to be more urgent, because multiple instances of the DMA are used together with many other peripherals in different combinations. I'm reporting this for F7, but drivers for other series also should be checked for the same.