STM32L412 hardfault while using minimal CubeIDE example.

I had recently a similar issue. In my case the debug messages where activated and tried to printf() the messages in to the void.

Have you tried to deactivate the debug messages or redirect printf() to a serial port?

 #ifdef __GNUC__
 /* With GCC, small printf (option LD Linker->Libraries->Small printf
 set to 'Yes') calls __io_putchar() */
 #define PUTCHAR_PROTOTYPE int __io_putchar(int ch)
 #else
 #define PUTCHAR_PROTOTYPE int fputc(int ch, FILE *f)
 #endif /* __GNUC__ */
 
 /**
 * @brief Retargets the C library printf function to the USART.
 * @param None
 * @retval None
 */
 PUTCHAR_PROTOTYPE
 {
 /* Place your implementation of fputc here */
 /* e.g. write a character to the EVAL_COM1 and Loop until the end of transmission */
 HAL_UART_Transmit(&huart6, (uint8_t *)&ch, 1, 0xFFFF);
 
 return ch;
 }

Thank you very much for your answer! I would never expected something like this - but unfortunately, this doesn't seems to be the answer.

I set up __io_putchar and verified that it is usable by printing in the main loop (and disabling MX_USB_DEVICE_Init()), but if I enable this function the program still ends in the hardfault handler :(

Have you tried to set the linkers min. heap size to at least 0x1000?

According to ST support "the default heap size is usually not big enough".

I tried it with even 0x2000 for stack and heap (which would have be a tremendous waste of RAM) - and it didn't work.

But this time I noticed the solution when single-stepping through the USB initialization:

USB_EnableGlobalInt() has been called by HAL_PCD_Init() and it results in the hardfault handler if it is called again in HAL_PCD_Start. If I comment out the second call, the initialization runs through and at least I get reenumeration attempts. Is there a way to notice ST of this problem and possible fix?

Hi.

Did you ever find the solution to this problem ?

I have the exact same problem on the STM32L412CB (Rev A) chip.

Your error explanation is spot on the same problem that I have.

I have tested 10 diffrent setups, and all have the same problem.

When I do the same setup on a STM32L452RE there is no problem what so ever.

Hope you have any new info

The Cube FW is STM32Cube FW_L4 V1.14.0

Best // Mike

Hi.

I do not have any way to print the printf output right now.

So I checked with TrueStudio (Stm32CubeIDE)

I have tested this with both Truestudio 9.3 and Stm32CubeIDE with the same result.

I set the breakpoint at the position before the error accrue, and each picture is an step in assembly.

next

next

next

next

Hard fault

and assembly code at the error

I do not know ow to follow this, becuas from my perspective it looks well and fine before the error hits.

Hope there is a way to solve this.

btw, Thanks Clive for all your help, indirect (others post) and direct :)

> each picture is an step in assembly.

I'd say, you used "step over" rather than "step into" (I don't use eclipsoids so I don't know exactly which key does what). In other words, IMO you run the USB_DevConnect routine, and failed somewhere there.

Learn how to "step into" and step until the fault occurs.

JW

Hi JW.

I am not a eclips guy my self, so I am no expert.

But I used "run to line" for each "step"

I culd not find another way to do it (Assembly step).

(picture courtesy of @SToma​ )

hi all.

thanks for the hint Jan, but when I do singel step, it works fine until I push resume.

So I can single step trough the whole thing and it is fine, but when I let the processor run freely again it ends up in HardFault.

So I am not any wiser from that unfortunately.

I have really been trying to figure this out, and solve how to implement clive's HardFault data.

What I can not figure out is how to make the compiler/MCU the added HardFualt addition in startup.s

Because I use Truestudio the code sample for the assembly code did not work,

So I found a example on https://nathan.vertile.com/blog/2016/05/04/stm32-hardfault-debugging/

/**
 * My code in startup_stm32l412xx.s
 *
*/
	.section .text.Reset_Handler
	.weak HardFault_Handler
	.type HardFault_Handler, %function
HardFault_Handler:
 movs r0,#4
 movs r1, lr
 tst r0, r1
 beq _MSP
 mrs r0, psp
 b _HALT
_MSP:
 mrs r0, msp
_HALT:
 ldr r1,[r0,#20]
 b hard_fault_handler_c
 bkpt #0
 
.size HardFault_Handler, .-HardFault_Handler

// My code in stm32l4xx_it.c
 
void hard_fault_handler_c(unsigned long *hardfault_args)
{
 volatile unsigned long stacked_r0 ;
 volatile unsigned long stacked_r1 ;
 volatile unsigned long stacked_r2 ;
 volatile unsigned long stacked_r3 ;
 volatile unsigned long stacked_r12 ;
 volatile unsigned long stacked_lr ;
 volatile unsigned long stacked_pc ;
 volatile unsigned long stacked_psr ;
 volatile unsigned long _CFSR ;
 volatile unsigned long _HFSR ;
 volatile unsigned long _DFSR ;
 volatile unsigned long _AFSR ;
 volatile unsigned long _BFAR ;
 volatile unsigned long _MMAR ;
 
 stacked_r0 = ((unsigned long)hardfault_args[0]) ;
 stacked_r1 = ((unsigned long)hardfault_args[1]) ;
 stacked_r2 = ((unsigned long)hardfault_args[2]) ;
 stacked_r3 = ((unsigned long)hardfault_args[3]) ;
 stacked_r12 = ((unsigned long)hardfault_args[4]) ;
 stacked_lr = ((unsigned long)hardfault_args[5]) ;
 stacked_pc = ((unsigned long)hardfault_args[6]) ;
 stacked_psr = ((unsigned long)hardfault_args[7]) ;
 
 // Configurable Fault Status Register
 // Consists of MMSR, BFSR and UFSR
 _CFSR = (*((volatile unsigned long *)(0xE000ED28))) ;
 
 // Hard Fault Status Register
 _HFSR = (*((volatile unsigned long *)(0xE000ED2C))) ;
 
 // Debug Fault Status Register
 _DFSR = (*((volatile unsigned long *)(0xE000ED30))) ;
 
 // Auxiliary Fault Status Register
 _AFSR = (*((volatile unsigned long *)(0xE000ED3C))) ;
 
 // Read the Fault Address Registers. These may not contain valid values.
 // Check BFARVALID/MMARVALID to see if they are valid values
 // MemManage Fault Address Register
 _MMAR = (*((volatile unsigned long *)(0xE000ED34))) ;
 // Bus Fault Address Register
 _BFAR = (*((volatile unsigned long *)(0xE000ED38))) ;
 
 __asm("BKPT #0\n") ; // Break into the debugger
}

but this do not work, ??

what I found in Truestudio was the problem window.

It reports an hard fault and gives some info, unfortunately I do not understand what it means.

The wired thing is, I downloaded the tryout of Crossworks and it works with the board if I create an MDK-ARM V5 project in CubeMX and import it into crossworks and just run. It works. So there is no problem with the MCU or the board.

:see_no_evil_monkey: