I am trying to use a STM32H743VIT6 mini board from Boring_tech (configured as Nucleo-H743ZI2) with Mbed studio and MbedOS 6.3.0. The board runs at 480 MHz. The download of the software is OK via the TX/RX (PA9/PA10) ports at the 0x8000000 default address. When I reset nothing occurs. Nothing from the serial port or even a simple blinking example does not run. Something wrong/missing?
External clock? You mean RTC ? There is a RTC inside but no connected battery. The internal clock seems correct: announced 480 MHz. I only see a stable blue led (another was blinking before the first load).
The simple code: #include “mbed.h”
Hmm it does seem like the clock config would be a likely culprit. From what I can find about the board it seems like it has an 8MHz crystal. This matches the Nucleo V1 board, but the Nucleo V2 board uses a 25MHz crystal. Aha! So try setting the target as Nucleo-H743ZI instead of Nucleo-H743ZI2.
Hi Jamie,
The board is found here https://fr.aliexpress.com/item/4000117622966.html with the 3 buttons.
Running at 480 MHz I have already tested at 400 MHz (Nucleo-H743ZI files)… no luck.
The load of the board works perfectly but no boot at all.
It seems the board is for the garbage can.
Regards,
Alain
The problem is the clock as I mentionend already.
I have a similar board: https://github.com/JojoS62/custom_targets/blob/master/TARGET_STM/TARGET_STM32H743xI/TARGET_DEVEBOX_H743VI/docs/STM32H7XX_M.jpg
you can try my custom_target with your board, the clock is set for 25 MHz xtal.
The Nucleos use external clock, this will fail and fallback to HSI clock. But HSI clock was buggy, it has been fixed a few days ago. But using my clock setting is better.
I still have a problem with getting the USB running, this issue is still not answered.
You are using another board: DevEBox. I am using a Boring_tech.
Just tested… nothing happens. A nightmare.
Last but not least I have ordered a DevEBox. I hope it will work with your modifications.
strange… How do you program the board? You said TX/RX, using the bootloader in ROM? Do you have some other probe for debugging?
And do have the schematics for the board?
I am using the USART TX/RX port (PA9/PA10) with the bootloader in ROM and STM32CubeProgrammer software (as other boards).
I dont have the schematic.
Maybe I can try with a ST-LINK V2 I have ? Never used.
with STLink, you need also only 3 wires, GND, SWCLK and SWDIO. Reset is optional, but when the program is hanging in a WFI instruction, you need to hold the reset button while trying to connect or connect also the reset wire.
The STLink tool is also easy to use, maybe its the same in Cube Programmer? I haven’t used the ROM bootloader.
More info: I have received the schematic… but I see some differences with my board (e.g. LED). I got the 2 buttons board version I have a 3 buttons version. Still unlucky.
could you add the two lines for LSEDRIVE_CONFIG and enabling LSE in system_clock.c
/** Configure LSE Drive Capability
*/
HAL_PWR_EnableBkUpAccess();
__HAL_RCC_LSEDRIVE_CONFIG(RCC_LSEDRIVE_HIGH);
/** Macro to configure the PLL clock source
*/
__HAL_RCC_PLL_PLLSOURCE_CONFIG(RCC_PLLSOURCE_HSE);
/** Initializes the RCC Oscillators according to the specified parameters
* in the RCC_OscInitTypeDef structure.
*/
RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE|RCC_OSCILLATORTYPE_LSE;
RCC_OscInitStruct.HSEState = RCC_HSE_ON;
RCC_OscInitStruct.LSEState = RCC_LSE_ON;
after flashing this modification, the target needs to be powered down for a few seconds because the LSE is running in seperate power domain and keeps alive for some time.