Posted on January 03, 2013 at 09:55Hello, I am not sure about what's the problem but :
If you use FULL_ASSERT, you need this code : For me it is present on every example and it works.
#ifdef USE_FULL_ASSERT
/**
* @brief Reports the name of the source file and the source line number
* where the assert_param error has occurred.
* @param file: pointer to the source file name
* @param line: assert_param error line source number
* @retval None
*/
void assert_failed(uint8_t* file, uint32_t line)
{
/* User can add his own implementation to report the file name and line number,
ex: printf(''Wrong parameters value: file %s on line %d\r\n'', file, line) */
/* Infinite loop */
while (1)
{
}
}
#endif
Good Luck.
We have an STM32373C-EVAL board and we've been trying out the firmware demo samples. One thing I've noticed is that if I enable the USE_FULL_ASSERT, most samples will crash. (Well, not crash but get caught in the assert trap.)
Eg. in the ''STM32F3xx_AN4045_V1.0.0'' (STM32F3xx_IAP), the following will crash:
...
if (STM_EVAL_PBGetState(BUTTON_KEY) == 0x00)
...
(Only if you push the button though.)
and
...
FLASH_If_Init();
...
Is this normal? Should I just disable the USE_FULL_ASSERT and forget about it or is there somewhere where I should submit a bug report?
