Solved

I connect the PB9-BOOT0 to VDD, then power up the board, but it just run from flash(application program), not the bootloader, what's the matter? I am not firmilar with ISP, I suppose it should enter bootloader, and wait for ISP program to communicate.I want to confirm, besides connect PB9-BOOT0 to VDD, is there any other thing need be done? 

I'm using the board STM32H747I-DISCO with the FP-AI-VISION1_V3.1.0 SDK, and made some experiments with some example projects and all of them are working on my board. But with the FoodReco_MobileNetDerivative project that can use external RAM and Flash I'm not able to make it work. The problem I think is related with the definitions of the #defines: "WEIGHT_QSPI", "WEIGHT_EXEC_EXTRAM", "WEIGHT_QSPI_PROGED".On the instruction manual (UM2611), it is mention to set those flags, but is not mentioned in what file they should be set. (In image attach)I've tried to set it under the file "fp_vision_app.h" and follow all the instructions in manual but with no success. Could any one help me with this?Thank you

Hello everyone, I have a lot (too much) question regarding code optimisation, the safety of a code and some return value of the HAL.Firstly, I am currently using HAL and CMSIS RTOS v2.  I am using a spi bus protected with a mutexe. Assuming that I am correctly using the mutexe, is it possible for HAL_Transmit_IT or HAL_Receive_IT to actually return HAL_Busy?What I want to know is:1) Am I making too much verification? Afterall a if/else bloc is require some ressources from the core, even if it's very little.2) I read on various post that using assert was a good practice in embbeded system but I'm still strugling to know when to use it and when not. I also read that it was recommanded to always check a return value of a function when it has one. Am I using correctly the assert() function? Is there too much usage of it? Not enough? Where is it really required and when is it not?Here is a sample of a basic function for a driver I am currently working on. I'm following the same co

Hi,I am injecting a UART DMA error by using DTCM memory and DMA2. For example:// Induce a DMA error by using DTCM RAM for DMA2 which is inaccessibleif ( HAL_UART_Transmit_DMA( huart, transmit_buffer_dtcm_memory, num_bytes_to_transmit ) != HAL_OK ){// Log error}What happens is the frame error, parity error, and noise error interrupts are disabled after the DMA error on transmit. This I can see by the EIE bit in CR3.  HAL function UART_EndRxTransfer is called and clears EIE.I have a streams connected to the TX and RX lines:TX is connected to DMA2 Stream 5 - High priortyRX is connected to DMA2 Stream 4 - High priority When I try to restart the UART receiving:if ( HAL_UART_Receive_DMA( uart_handle, receive_buffer, RX_BUF_SIZE ) != HAL_OK ){// Log error}There is a check in sub function HAL_DMA_Start_IT that returns an error because the DMA stream is busy. So what is the correct way to recover/restart after a DMA and set the interrupt flags for frame, noise, and parity?\Thanks

 Hello everyone,I'm trying to use IN1, IN2, and IN4 from the ADC1 of the NucleoF303K8. I transmit the ADC values via UART2 to my laptop.Now to my problem: When all three ADC channels are at 1.6V, I receive the correct values. However, if I pull one of the channels to 0V (GND), the values of all ADC channels decrease. I want to measure the exact value of all three ADC1 channels independently. I have tried different codes, but none of them work. Does anyone know what the problem might be or how I need to change my code to fix this issue?My code is attached.I am grateful for any help.

Following the instructions here: https://wiki.st.com/stm32mpu/index.php/How_to_create_your_own_machineAnd then making a trivial devicetree modification (enabling I2C5 output) fails to build on a fresh yocto install (via the "distribution package").  I'm beginning to port code from a DK2 to a custom board, and creating a transitional package.The build slams right into the `flavorlist` mess in the optee make confs (specifically workspace/sources/optee-os-stm32mp/core/arch/arm/plat-stm32mp1/conf.mk) , ignoring the `CUBEMX_BOARD_DDR_SIZE = "512"` variables or anything else..Very frustrating to see all these hardcoded filenames when yocto is very aware of the actual device tree in use at buildtime... looks like maybe the intended `CFG_EXT_DTS` escape hatch is broken?Lots of previous posts have hit this problem, but on custom hardware, and with more significant DT changes.  I didn't touch the RAM or anything else other than have a default DK2 template MX project and then enable/"ok

Hi ST community members! For a long time ago with another nick (but lost the account access), I have wanted to add U-Boot support for this board. Now I have done this but not released a patch series yet (only on my local Git repo) in the U-Boot mailing list. Also must do some tests on real hardware. Short question:Does somebody need support for this board or is it useless? I know the board has less RAM, but some ST maintainers on the U-Boot list where interested in the past. But unfortunately I haven't finally done this, because of an illness. Also when it's useless for other users, it was a fun project for me. :)

I am looking for ST products that will:Receive bluetooth audio (i.e. from a smart phone)Play the bluetooth audio through a single minature speaker (mono)Play stored samples of a voice counting down numbers at intervals based on an external event (if bluetooth audio is being played when the voice sample is triggered, the bluetooth audio will need to be temporarily attenuated)Read Bosch BME280 pressure sensor (I2C or SPI)Other requirements are:Small form factor: As an example 56x41x11mm, although this is not fixed so there is room for some flexibilityLow power consumptionPowered by lithium battery with built in (wired) chargingI prototyped this project many years ago using:Microchip dsPIC33EP256MU806Bluetooth receiver WT32i-A-AI6CODEC (I2S) TLV320AIC32IRHBTAmplifier (for speaker) TPA6120A2DWPBattery charger DS2745UFlash (to store audio samples) S25FL032P0XMFI011Pressure sensor Bosch BMP280The original prototype was too large and drained the battery too quick (partly due to an assembly/de

HI, I am MURALI SELVAM from India, I need reference design for Below given part number. I want DCMI Camera Interface 8-bit D[7:0](BT.601), PCLK, HSYNC, VSYNC. So anyone who has reference design related that kindly give me.*****STM32F407VET6

Does the system memory bootloader for the STM32L4P5xx consider RAM3 as valid SRAM for the stack pointer?After programming bank 2, and then setting BFB2, The device will not boot into bank 2.  The linker has the top of the stack at RAM3.  The value written to both 0x8000000 (bank 1) and 0x8040000 (bank 2) is 0x20050000.  I want to make sure this is correct.  By the way, this is the 512K part STM32L4P5xE.  The other relevant options bytes are set as follows: nBOOT1=1, nSWBOOT0=0, nBOOT0=1 (BOOT0=0).  When I clear BFB2 I can boot.  I have compared the flash memory from 0x08000000-Length with 0x8040000-Length, and they both match.

I am trying to write to the flash memory of the STM32L4S5QIIX microcontroller on the EVAL-ADIN1110EBZ development board. I have also tried similar code on an STM32L4S5VITX microcontroller on a custom circuit board.Short example code:uint32_t flash_memory_address = 0x08100000; uint64_t flash_write_data = 0x12345678; uint8_t flash_read_data[4]= {0}; HAL_FLASH_Unlock(); FLASH_PageErase(0, FLASH_BANK_2); HAL_FLASH_Lock(); HAL_FLASH_Unlock(); __HAL_FLASH_CLEAR_FLAG(FLASH_FLAG_ALL_ERRORS); HAL_StatusTypeDef status = HAL_FLASH_Program(FLASH_TYPEPROGRAM_DOUBLEWORD, flash_memory_address, flash_write_data); HAL_FLASH_Lock(); The full code and project files can be found at: https://github.com/landas/stm32l4s5-flash-memory/blob/e8304c3d17e27ee9f27f8a8243ceb7f73ba077bf/Core/Src/main.c#L135FLASH_PageErase(0, FLASH_BANK_2) operation was completed successfully. This was verified by using STM32CubeProgrammer to write to the flash memory and confirm the changes in the specified memory are

Hi, was wondering if anyone could suggest what the problem could be with trying to build the example USB-C PD Source application per this tutorial :https://wiki.st.com/stm32mcu/wiki/STM32StepByStep:Getting_started_with_USB-Power_Delivery_SourceI've checked that I have worked through all the steps as instructed but build is failing with error :/USBPD/Target/usbpd_devices_conf.h:83:58: error: 'valueNotSetted' undeclared (first use in this function)83 | NVIC_SetPriority(valueNotSetted,2); \Looks like I have a missing or incomplete header file. Can anyone help?

I am using NUCLEO_H723ZG in which I am using 12-bit resolution ADC. Below is the clock used for ADC:Moreover, I have used DIV2 clock prescaler. So my BOOST bits in ADC_CR register should be 11 as it is mentioned in the reference manual.I checked those BOOST bits while debugging and they are set 10 instead of 11.So I assumed the clock frequency to be 50 MHz and checked all the condition. With that all condition the BOOST bits changes accordingly.Although 64 MHz is shown there but the clock frequency used is 50 MHz?

Hello,I am creating a CMake project using STM32CubeMX 6.13.0 for the STM32U575QGI6Q, but am having trouble with the following error: [1/10] Building ASM object CMakeFiles/rtm.dir/Middlewares/...x/ports/cortex_m33/gnu/src/tx_thread_context_restore.S.objFAILED: CMakeFiles/rtm.dir/Middlewares/ST/threadx/ports/cortex_m33/gnu/src/tx_thread_context_restore.S.objC:\ARM-NO~1\14EFD8~1.2RE\bin\AR19DD~1.EXE -DDEBUG -DSTM32U575xx -DTX_INCLUDE_USER_DEFINE_FILE -DTX_SINGLE_MODE_NON_SECURE=1 -DUSE_HAL_DRIVER -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../Core/Inc -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../AZURE_RTOS/App -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../Drivers/STM32U5xx_HAL_Driver/Inc -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../Drivers/STM32U5xx_HAL_Driver/Inc/Legacy -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../Middlewares/ST/threadx/common/inc -ID:/code/firmware/rtm/stm32/cmake/stm32cubemx/../../Drivers/CMSIS/Device/ST/STM32U5xx/Include

I have an STM32L011 on a board I am developing.I can enter the bootloader no problem, as per AN2606/AN3155.  I am using USART2, 57600 baud.I can program FLASH/erase FLASH/read FLASH - all works as expected.I note that the bootloader reserves 2048bytes of SRAM, I assume it's the addresses 0x2000_0000 .. 0x2000_07FF.When I try to use the memory read command to read from anywhere in SRAM (whether the bootloader reserved area or any other address) I get a NACK just after the address+xor-check-byte.I believe the protocol is correctly implemented because the same thing works reading from FLASH addresses (e.g. 0x0800_0000).Is there a known issue here (I have seen other posts on this forum with similar problems on other STM32 parts - but these are either unresolved or they are trying to read from the reserved SRAM which is expected to be NACK'd). 

NUCLEO-WB55RG communicating via SPI1 to an ADXL362 eval boardI set up the project (attched below) using CubeIDE, generated the code & placed my own callbacks for the SPI in main.When I look at the value for the Z direction I should be getting a value that indicates roughly 1g but all I get is 0. The same for all the other axis, no change in any value no matter how I orient the sensor.To check that the acceleromter was working I hooked it up to an Arduino using a 3rd party library especially for the ADXL362. That all worked as expected, so I know the accelerometer is working.When I go through the code with the debugger it doesn't hang anywhere so I'm guessing my callbacks are working, its just I dont get any data back, all values remain at 0Anyone see anything obvious that I'm doing wrong?

 I'm using an STM32H7 microcontroller to interface with an OV2640 camera. I'm utilizing the 8-bit DCMI interface to capture data from the camera and transfer it to a DMA FIFO buffer. My camera configuration includes generating an 8MHz MCO signal for the MCLK input on the OV2640. I'm processing the data with a Digital Signal Processor to obtain RGB565 format at a resolution of 120x160 pixels. Currently, my HSYNC is set to HIGH, VSYNC to LOW, and I'm using a pixel clock with a rising edge. The problem I am having is I get no valid bytes from the DMA FIFO buffer. I get the value of 0x00. Below is my main.c with the functions running the program, the values I write to the register also work. Please help.

Hi,i am using NUCLEO-WBA55 with the BLE_p2pServer example from firmware package.Here for example in file app_ble.c is a define statement#define ADV_TIMEOUT_MS (60 * 1000)and this ends the advertising after 60 seconds.However, I would like to start and stop the advertising individually with a command, for example.Can someone explain to me how I can do this?

I am working with a dual core STM32H755 and attempting to create a shared memory location for the two cores to access. I am attempting to do this by modifying the linker script.  I have added the following lines to the M7 core linker script, in the SECTIONS block:/* Shared Memory section for inter core comms */ .sharedRAMsection 0x30040000 : { .= ALIGN(4); KEEP(*(.sharedRAMsection)) . = ALIGN(4); } > RAM_D2 Then in one of my .c files, I have declared the following global variable:RegisterMap_t __attribute__((section(".sharedRAMsection"))) g_RegisterMap; However, when I debug I can see the address of this variable has been assigned to memory location 0x24000064, as seen in the watch window: I am using visual studio and visual GDB, and I am debugging with 2 separate VS instances for the two cores. Is there something else that I need to do in order to get this variable into the correct memory location? Thanks 

I am currently making an artificial horizon for a project in TouchGFX, but I just noticed that when I tried to use the svg of the Pitch_Angle_Indicator that has numbers I get a compile error. Are there any plans to implement the usage of numbers in svg images? BSNeyus 

Hello, I am asking for help from the community. My application is completely written, but I can't set read protection. I tried to do all the steps in this guide, but it led to bricking one of my boards. The second board is still in product state = 17? but I can't install the obk file or remove protection, returning it to the ED state. Cube programmer did not give me the choice "Change the PRODUCT_STATE option to 17, then press [Apply]. A window appears asking if the default DA-Config should be applied, press [NO]." it just set the state to 17 without asking.I did not find any sensible information on the network on how to set or remove protection. Maybe it is possible to do this directly from the application? in state 17 I can flash h503, but I can't switch to debugging.I really ask for help, my project is completely ready, but it needs to be protected.

Hi. I am programming a board with STM32G0, which is battery powered. All processor pins are used. Overall, the device works without any problems. In normal operation mode, only STM draws about 3.5mA. However, I wanted to put the device to sleep and:1. In Shutdown mode, STM draws 40nA (according to the documentation), and the entire device 720uA, which is satisfactory for me, but I want to be able to wake it up from a dozen or so GPIO pins, so I tried to start Stop mode and:2. In Stop mode, STM draws 600nA (more than the documentation indicates, but still quite good). I have the ENABLE pins of the additional LDO and charge pump connected to the PB9 pin through 100R resistors, which are on the PCB and power other systems. There is also a 4k7 pull-down on the ENA pins. During normal operation, PB9 is in a high state, and before sleep it is set to a low state to turn these systems off. And here comes the problem: when I leave PB9 in the high state before switching to Stop mode, the cu

Please kindly support to provide PFAS Declaration of MPN : M24C02-FMN6TP? Please kindly help to reply into my mail at RWIMINTO@OSIELECTRONICS.COMThank you.

I have connected the STEVAL-25R200SA via micro-USB to the computer however the device is not identified.  Is there any virtual com port driver needed for this and if so can someone provide what it is that I am missing.  

I am trying to debug some functions to write to the memory mapped QSPI. When I go to debug it, I notice that before any functions even run the QPSI is in HAL_QSPI_STATE_ERROR, therefore I cannot test my code to see if is running because it is dependent on the State of the QSPI. My QSPI is a WinBond25Q128JVSQ. Is there a way to trouble shoot this?