Solved

HelloI would like to configure for z axis acceleration in LIS2DTW12 IC and read the data in FIFO mode. Kindly take a look at the below code for which i have configured as FIFO mode and 5 samples of data in that. let me know any correction!​​int main() {InitialiseHardware();InitialiseModules();             ​whoamI = I2C1_ReadRegister(who_i_am);  /* Check device ID */​if(whoamI != LIS2DTW12_ID)while (1) {   /* manage here device not found */  }​// v1 = I2C1_ReadRegister(0x21);​I2C_WriteRegister(SLAVE_ADDR, 0x20, 0x60); /* set ODR 4000hz in ctrl1*/I2C_WriteRegister(SLAVE_ADDR, 0x25, 0x10); /* set 4g in ctrl6 */I2C_WriteRegister(SLAVE_ADDR, 0x2E, 0x25); /* fifo mode and 5 samples */​// reg.fth = 10;​//lis2dtw12_full_scale_set(&dev_ctx, LIS2DTW12_2g);// lis2dtw12_filter_path_set(&dev_ctx, LIS2DTW12_LPF_ON_OUT);​​/* Infinite loop */while(1){​I2C_WriteRegister(S

..

HiI would like to know, if it is possible to flash my FW via CAN1 on a STM32F103 or only via USART1?AN3154 mentions the F1 series but AN2606 does only mention USART1.ThanxAndy

Hi, I need some help trying to undestand this operation in Lorawan_end_node example projectnvm_size = ( ( sizeof( LoRaMacNvmData_t ) + 7 ) & ~0x07 ); in the code below:Maybe it is so simple, but i thought that it would be something like that nvm_size = sizeof( LoRaMacNvmData_t );Thanks in advanceLmHandlerErrorStatus_t LmHandlerNvmDataStore( void ) { #if (defined( CONTEXT_MANAGEMENT_ENABLED ) && ( CONTEXT_MANAGEMENT_ENABLED == 1 )) LoRaMacNvmData_t *nvm; uint32_t nvm_size; LmHandlerErrorStatus_t lmhStatus = LORAMAC_HANDLER_SUCCESS; int32_t status = NVM_DATA_OK;   lmhStatus = LmHandlerHalt();   if( lmhStatus == LORAMAC_HANDLER_SUCCESS ) { status = NvmDataMgmtStoreBegin();   if( status == NVM_DATA_NO_UPDATED_DATA ) { lmhStatus = LORAMAC_HANDLER_NVM_DATA_UP_TO_DATE; } else if( ( status != NVM_DATA_OK ) || ( LmHandlerCallbacks->OnStoreContextRequest == NULL ) ) { lmhStatus = LORAMAC_HANDLER_ERROR; } else { MibRequestConfirm_t mibReq; mibReq.

..

Hi,I'm using latest STMCubeProgrammer/ST-Link-Utility releases. My goal is to provide the option bytes directly in the .elf/.hex file, so our manufacturing department only needs to download this file.I already managed to get the settings into the .elf/.hex file automatically. But when I try to program the device, I got verification error. It seems(!) that the device is programmed correctly, but I want to be sure.The device is a L011F4. There are two configurations for the option byte corresponding to the debug and release builds. For the debug build, the option bytes are the same as for a blank device delivered from factory. For the release build, the RDP level is 1, and the bootloader pin is disabled. No write protection fro both configurations.Even for the debug build with no RDP, the verification fails and I don't know why. Here's my call to STM32_Programmer_CLI.exe:-c port=swd freq=4000 ap=0 index=0 mode=normal -vb 1 -rdu -e all -d %1 -v%1 is replaced with the name of the .elf/.hex

We are bringing up a custom board with LPDDR2 and no STPMIC. I have been following the bring up guide and have gotten past disabling I2C4 and fixing the HSE clock issue in the device tree. I have merged in quite a few things from dev kit 'working' devicetrees as well.I am stuck at the following TF-A error though.Data Abort at: 0x2fff3e20 DFSR = 0x00000206 DFAR = 0x3664647fAbort at: 0x2ffe93a0I have used devtool to modify the tf-a recipe and increase the DEBUG level but nothing I do makes any difference. I just get this error.Attached is the flattened ftd from the TF-A build dir along with the cubemx generated set of devicetrees for tf-a.

..

Hello,I have configured a CUBE IDE project to match a Nucleo-F401RE board to measure the system clock pulses (at 84MHz) between to consecutive rising edges of an external signal applied to pin PA3 (which is Timer2 Channel4 input).The Input Capture interrupt gets never fired.I have done a similar test on a custom made board with a different STM32 chip (namely STM32L431RCT6) and the interrupts are fired. For this reason I suspect that the auto generated code by the IDE contains some error preventing the system to work properly, but I'm not able to identify what I am missing here.Attached the whole CUBE IDE project.Thanks in advance for your hints,Marco

HiI am trying to make work the internal temperature sensor from a STM32G474RE and it seems to return a low value... 11.14 celsius degrees.This is the code I am using:#define TS_CAL1_ADDR ((uint16_t*) ((uint32_t)0x1FFF75A8)) #define TS_CAL2_ADDR ((uint16_t*) ((uint32_t)0x1FFF75CA)) #define TS_CAL1_TEMP 30.0 #define TS_CAL2_TEMP 130.0   double getTemperatureMCUPCB(void) { uint32_t TS_CAL1 = (int32_t) * TS_CAL1_ADDR; uint32_t TS_CAL2 = (int32_t) * TS_CAL2_ADDR; mcuPCBTempADCValue = global_adc1_val[1]; mcuPCBTemperature = ((TS_CAL2_TEMP - TS_CAL1_TEMP)/((double)TS_CAL2 - (double)TS_CAL1)) * ((double)mcuPCBTempADCValue*(3.3/3.0) - (double)TS_CAL1) + 30.0;   printf("MCU temp: %.2f\n", mcuPCBTemperature);   return mcuPCBTemperature; }And this is how is setup ADC1:​​Thanks in advance.

Hello everyone, I want to design with st25dv only RFID systems. I cannot find any example about this. Do you have any suggestion?

Started learning FREERTOS and ran into a problem.I showed 3 pieces of code of the same tasks.All 3 pieces of code work differently.Code 1void Task1(void *argument) { int j = 0; for(;;) { HAL_GPIO_TogglePin(GPIOB, GPIO_PIN_0); for(j=0; j<10000000; j++); } }       void Task2(void *argument) { int i = 0; for(;;) { HAL_GPIO_TogglePin(GPIOB, GPIO_PIN_14); for(i=0; i<10000000; i++); } }Why does the blinking order of the LEDs start to change over time?For example: first the PB0 LED lights up first, then the PB14. After a few periods, the PB14 LED starts to light up first.Code 2void Task1(void *argument) { for(;;) { HAL_GPIO_TogglePin(GPIOB, GPIO_PIN_0); for(int j=0; j<10000000; j++); } }       void Task2(void *argument) { for(;;) { HAL_GPIO_TogglePin(GPIOB, GPIO_PIN_14); for(int i=0; i<10000000; i++); } }Then the blinking of the LEDs is strange.Example: Sometimes the PB0 LED may turn on first, then turn off first.Code 3. I made t

The RHFLVDS2281 datasheet suggests there is an internal pullup on the EN pin, but doesn't list this value. Does anyone know what this internal pullup resistance is?

Hello,I am using the STM32F756ZGT6 for an upcoming project. I am using a 480x272 resolution display (RGB565) with a single layer. I also have additional features that will be on this board that use more RAM (2 tasks, multiple variables, etc.) that add up in the RAM. In total, I have 310 kBytes of RAM usage, according to the Memory Regions tab. The MCU has 320 kBytes of internal RAM and I have tested it with the display and my code works as intended.My question is, long term, will I experience problems when the RAM usage is that high? My RAM usage percentage is about 96%, which is quite high. I cannot think of any issues (aside from limitations on software additions later), but I wanted to ask in case I'm not thinking of something.

I am trying to set up a dual boot system using a bootloader in stm32F7 without using the dual bank operation. I have the bootloader, which can flash the bin files directly to the flash .My concern is whether .bin files contain any address information, if so are they relative? Also, will the jmp instructions work as intended ?The idea is to use the same linker file to generate the bin files for both memory sections and flash them to different sections using the bootloader. Right now I used different linker scripts for different sections of the memory.

Hello,I'm trying to do a basic spi master transmit, and am having issues with the MOSI pin output. It seems the value is getting written, but the voltage swing is ~200mV rather than full value. I suspect I have the GPIO pin mis-configured, but I'm at a loss as to where my mistake is after reading the datasheet and searching online. Here's my basic code for stm32l476 (using the nucleo board)...void basic_spi() { GPIO_TypeDef* gpio = GPIOA; SPI_TypeDef* spi = SPI1; uint8_t data = 0x12;   // gpio config RCC->AHB2ENR |= (1<<0); GPIOA->MODER &= ~((3<<10)|(3<<12)|(3<<14)|(3<<18)); //af pa5,pa6,pa7,output pa9 GPIOA->MODER |= (2<<10)|(2<<12)|(2<<14)|(1<<18); // high speed GPIOA->OSPEEDR |= (3<<10)|(3<<12)|(3<<14)|(3<<18); // af5 for pa5,pa6,pa7 GPIOA->AFR[0] |= (5<<20)|(5<<24)|(5<<28);   // spi config RCC->APB2ENR |= (1<<12); //clock enable SPI

Hi ,I integrated st25dv64kc nfc tag into stm32 board. I have to store a serial number permanently in NFC EEPROM user area. It should not be erased in RF write and I2c Write. I used NDEF format . Is it possible to store text permanently ?

Datasheet says STM32MP15xx has ADC but here seem no ADC.​I am not sure if I am missing something.​

void USART3_IRQHandler(void) is incorrect, since USARTs 3/4 share the interrupt, it doesn't compile. What replaces 'USART3' in the interrupt handler?NVIC_ClearPendingIRQ(USART3_IRQn); is incorrect since USART3 3/4 share the interrupt. What replaces 'USART3_IRQn' so that the NVIC_ClearPendingIRQ will compile?

I'm using STM32CubeIDE 1.12.0 with a TrustZone enabled project and observed incorrect initialization of GTZC when the option "Generate peripheral initialization as a pair of '.c/.h' files per peripheral" is active: If this option is not active the function HAL_MspInit() in stm32XXXX_hal_msp.c contains some code to enable the clock of GTZC1 and/or GTZC2, depending on the further configuration e.g.:/** * Initializes the Global MSP. */ void HAL_MspInit(void) { /* USER CODE BEGIN MspInit 0 */   /* USER CODE END MspInit 0 */   __HAL_RCC_GTZC1_CLK_ENABLE();   /* System interrupt init*/   /* USER CODE BEGIN MspInit 1 */   /* USER CODE END MspInit 1 */ }If this option is active the GTZC clocks are not enabled in stm32XXXX_hal_msp.c any more. This is as expected. But the generated gtzc_s.c, which then contains the whole initialization of the GTZC, misses the code to enable the clock of GTZC1 and/or GTZC2.Of course GTZC peripheral must be enabled (I enabled

Hi,I want to make custom bootloader on STM32G051. I did something, but it does not work well. After jump to the application it get stucked on some address which correspond HAL_Delay function in my application - it looks like the Systick in my app can not geneate interrupt.A) Bootloader:The code when I want to jump to the application:SysTick->CTRL = 0x0; HAL_DeInit(); __disable_irq(); RCC->CIER = 0x00000000; // Disable all interrupts related to clock __set_MSP(*((volatile uint32_t*) APP_START_ADDRESS));   __DMB(); SCB->VTOR = APP_START_ADDRESS; __DSB(); //ARM says to use a DSB instruction just after relocating VTOR *   /* jump to App */ uint32_t JumpAddress = *((volatile uint32_t*) (APP_START_ADDRESS + 4 )); void (*reset_handler)(void) = (void*)JumpAddress;   reset_handler(); //We start the execution from he Reset_Handler of the main firmware //Never coming here where APP_START_ADDRESS == 0x8005000also I edited STM32G051C8TX_FLASH.ld :MEMORY { R

I'm working with the STM32F446-microcontroller and once in a while after power-up the microcontroller is unable to drive pin PA0 high or low and I also suspect that it can't drive PA8, configured as an I2C-clock, either when this problem occurs. There is no issue with input sensing on PA0, i.e. reading GPIOx->IDR always returns the correct result. Also, I'm able to communicate with a custom-made PC-application via CAN-bus and I can upgrade firmware on the microcontroller using a custom-made bootloader, but it won't get PA0 out of the non-controllable state. A software reset doesn't help either, the only solution is to disconnect power for about 5-6 seconds and then things work fine again. Can anybody think of anything I can do to solve this? Are there any registers I can play with to try get PA0 controllable again?

..

Hi.I'm writing a bootloader for update a firmware of my project by usb pen drive.Whe bootloader start verify that in the pen drive there io a .bin file, erase the flash and copy teh bin in the flash defined address.The flash address is 0x08010000.This process appare running fine , whith debugger I verified the address and the application is present, but when Jump the cpu don't run.I tested various jump routines take from examples of bootloader find OnLine , but none work.I don't. know there is the problem.I use STM32Cube compiler and the test is applied to Nucleo -F413ZH.this is the routines code:/*  Bootloader Test */#include "bootloader.h"#include "stm32f4xx_hal.h"#include "string.h"extern UART_HandleTypeDef huart3;extern char USBHPath[4];  /* USBH logical drive path */extern FATFS USBHFatFS;   /* File system object for USBH logical drive */extern FIL USBHFile;      /* File object for USBH */extern char RD_buffer[100];e

Dear Colleagues,I have tried for more than a week to get the internal D+ pull up resistor to activate on my custom board.I have checked the clocks and they seem to be all running. I created a new project with only USB OTG FS hid class enabled. STMCube v1.12. When I probe the D+ pin I get the following.It took me a while to find the point where the process is started and that is in /** * @brief USB_DevConnect : Connect the USB device by enabling Rpu * @param USBx Selected device * @retval HAL status */ HAL_StatusTypeDef USB_DevConnect(USB_OTG_GlobalTypeDef *USBx) { uint32_t USBx_BASE = (uint32_t)USBx;   /* In case phy is stopped, ensure to ungate and restore the phy CLK */ USBx_PCGCCTL &= ~(USB_OTG_PCGCCTL_STOPCLK | USB_OTG_PCGCCTL_GATECLK);   USBx_DEVICE->DCTL &= ~USB_OTG_DCTL_SDIS;   return HAL_OK; }If I put a break point at line 13 the output on the D+ pin PA12 remains low, but when I step to the next line the output appears is in the image above.Wh