Solved

Hello Everyone, I'm yugentharI want Nucleo-f767zi schematic diagram -link so i search online for schematic but proper schematic is not available. So any body give the link

I seen several loader project at this git hub locations but non are for the W25Q64 NORFlash with the STM32H743.https://github.com/STMicroelectronics/stm32-external-loaderI have driver file already for the W25Q64 that I'm debugging a few issues now. Once I have those resolved can I create an external loader using these and the Dev_Inf and Loader_Src .c and .h file from another STM32H743 project to build an external loader or do they need to be modified for the specific NORFlash device as well?If not does anyone have the loader source file need for this device?

Hi,I had been using ST/Link 2.1 nucleo header so far to program and debug custom STM32 H723 ZG boards and wanted to switch to ST/Link v3 in order to debug with compact probes. Thus I ordered two genuine ST-Link/V3 MINIE from Mouser. My custom board and debug connector is confirmed to be working since I can connect and program with STLink V2 and V2.1 .I've tried to connect through CN2 B2B connector as well a CN4 STDC14 Connector but I can not connect to the target via either method on both MINIE board I purchased.I've updated firmware to V3J10M3, tried versions with and without Mass Storage. I've tried all Modes and Reset Modes.Still I can not get target informations. Interestingly, CubeProgrammer states that the (target ?) voltage is 0.24V.Wondering if there is an issue with my custom STD14 to JST-SH6 cable, i've tried to use a V3-SET with the very same cable and I can successfully connect to the MCU. Displayed voltage is 0.0V which is surprising because I get 3.25V with ST-Link V2.My

Hello Support Team,Good day,We have chosen the STM32U585ZIT6Q (-40C to 85C, LQFP -144 pins, with trust zone core) controller for our product.As per our requirement, We have activated TrustZone security is activated(Option bit TZEN=1) and Tread-X middleware in M33NS cause as well as trust zone securityWe have enabled trust zone security and also enabled the middleware of TreadX in M33NS reason.The non-secure reason is directly accessible from the secure reason, according to the paper below.https://www.st.com/resource/en/application_note/dm00625692-stm32l5-series-trustzone-features-stmicroelectronics.pdfI have some questions regarding the secure reason project which is mentioned below1. I noticed that the secure project has a while loop and int main(). What is the purpose of this while loop?2. Can I create threads or tasks in the secure reason project? As per our application, we have 4 tasks(Task-1:Display, Task-2:Metering, Task-3:Monitoring Metering data and Task4:Relay operation).

..

On a custom board, the RED_LED is connected to PA15, which is pulled-up by default (JTDI).The pin has been set to Push-Pull Output GPIO in CubeMX and is initialized to 0.The STM32WB55CGUx was experiencing random resets, until this particular IO was set to 1, line 34 in the code below.Now the code runs fine and is stable.int main(void) { /* USER CODE BEGIN 1 */   /* USER CODE END 1 */   /* MCU Configuration--------------------------------------------------------*/   /* Reset of all peripherals, Initializes the Flash interface and the Systick. */ HAL_Init();   /* USER CODE BEGIN Init */   /* USER CODE END Init */   /* Configure the system clock */ SystemClock_Config();   /* USER CODE BEGIN SysInit */ //SysTick_Config(32000/0);   /* USER CODE END SysInit */   /* Initialize all configured peripherals */ MX_GPIO_Init(); MX_ADC1_Init(); MX_SPI1_Init(); MX_TIM1_Init(); MX_TIM2_Init(); MX_USART1_UART_Init(); MX_RF_Init(); MX_RTC

..

..

Attached is the IOC setup for simple continuous PWM Mode from LPTIM1 from STM32BW55 (all Cube IDE/MX updated with the library, etc).. RB2 showing the waveform as per Peroid and Pulse width (from 64MHz clock input) but I get no interrupt (enabled by IOC setting). I have looked thro the documents and could not find something useful. Have I missed something?

I created a Keil project for STM32G070 without using Cube. It compiles but the link fails with error L6236E which seems to indicate there is no startup file. Can anyone send me a file that will work? In case it matters, the board that I am using is a cheapie Aliexpress that basically has the CPU and a 8 MHz xtal oscillator.

I'm having a significant problem debugging my board with CAN traffic. Whenever the debugger is paused, and a CAN message is received via interrupt, the independent watchdog is being reset. As far as I can tell, I'm disabling that peripheral on debug correctly, but anytime I set a breakpoint, the IWDG is resetting the MCU. If my board does NOT receive any CAN messages, everything works as expected.Relevant InformationMCU: STM32F091VBDevelopment Environment: IAR Embedded Workbench 9.30Debug Probe: STLink/V2Below is my code for disabling peripherals for debugging://Halt Interrupts on Debug stop __HAL_RCC_DBGMCU_CLK_ENABLE(); __HAL_FREEZE_IWDG_DBGMCU(); __HAL_FREEZE_WWDG_DBGMCU(); __HAL_FREEZE_TIM1_DBGMCU(); __HAL_FREEZE_TIM2_DBGMCU(); __HAL_FREEZE_TIM3_DBGMCU(); __HAL_FREEZE_TIM16_DBGMCU(); __HAL_FREEZE_CAN_DBGMCU();Disabling the watchdog entirely appeared to work, but pausing in the debugger only allows me to debug the CAN interrupt, so it seems when the debugger is paused, the MCU gets

Hi! I'm using STM32 F301C8T for my LLC converter project. I have two MOSFETs switching at variable frequencies ranging from 80kHz to 400 kHz. Due to significant noise caused by switching, I need to time the output voltage measurement between the switches of MOSFETs.I use TIM2 for PWM to switch the MOSFETs and TIM1 to count output events of TIM2 (TIM2's arr = 4, meaning that every 5TIM2 overflows, TIM1 overflows as well). Using the debugger, I checked that TIM1 counts appropriately. I set ADC conversion to be triggered by "Timer 1 Trigger Out Event," and it seems like the AD conversion is not triggered. (+using DMA in circular mode). Can you guys please advise what I am doing wrong? I start the TIMs and ADC by:HAL_TIM_Base_Start_IT(&htim1); HAL_ADC_Start_DMA(&hadc1,(uint32_t*) adcResultsDMA,4);HAL_TIM_PWM_Start(&htim2, TIM_CHANNEL_2);HAL_TIM_PWM_Start(&htim2, TIM_CHANNEL_3);Thank you! Pj

Hello,I am about to improve the execution speed of an existing code base on a NUCLEO-H743ZI2 board.So far, I have the following memory setup:Instruction Memory:ITCM for time-critical functionsFLASH (+ I-Cache) for remaining instructionsData Memory:AXI_SRAM for two DMA-buffers (Peripheral to Memory)SRAM1 for another DMA buffer (Memory to Peripheral)DTCM for everything else (including ISR table)My program with the above setup works fine.Now I want to check whether enabling the D-Cache can actually further improve execution speed. My intention is, to use this Cache solely for a faster reading/processing of the DMA-Buffers in AXI_SRAM. Their reading happens upon a DMA half- or full-complete interrupt and the D-Cache is always invalidated before accessing any DMA-Buffer data. SRAM1 stays non-cacheable.This is my new setup:Instruction Memory:ITCM for time-critical functionsFLASH (+ I-Cache) for remaining instructionsData Memory:AXI_SRAM (+ D-Cache) for two DMA-buffers (Peripheral to Memory)S

Hi,i had a programm running on the stm32f407 and PWM output via Tim2 The timer is configured with clock 84MHz and PWM Counter Period 5040 which gives me a period time of 60us. The timer is clocked via APB1. this works finenow i use an h753 with the same settings(at least this is what i think) and my output period is halved with the same counter period of 5040ok, i could double my counter period and get the result i want but i do not understand what setting i'm missing which halves my period. can anybody give me a hint where to look?

Hi,I start STM32CubeMx with this command /mydir/STM32CubeMX/STM32CubeMX -q /mydir/myscriptInside the file myscript there are this lines:swmgr refreshswmgr install STM32Cube_FW_G0_V1.6.0 askexitWhen run this line "swmgr install STM32Cube_FW_G0_V1.6.0 ask" the output in the terminal is 2023-05-05 09:27:39,236 [INFO] MainUpdater:1566 - Unknown pack: STM32Cube_FW_G0_V1.6.0KOwhere can i find the correct pack name?Best regards

..

Hey,I'm trying to add '%' as a wildcard character for a value that will passed through as, for example, 50%, for a battery level in a status bar container.I have the value set up as a single use resource that uses a topology where the wildcard range/characters are set as 0-9/% respectively, and is written via a buffer with sprintf, as follows:Unicode::snprintf(txtBatteryBuffer, TXTBATTERY_SIZE, "%d%%", chargeLevel);txtBattery.invalidate();I believe the % should be appended to my chargeLevel int in the formatting of the string here. Unfortunately I only see the numbers in GUI and no '%' still.Any advice would be much appreciated, perhaps my appending of % is wrong?Thanks,

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.