2020-06-16 07:30 AM
Hello All,
I am using custom board using stm32f446ret7 controller. I am creating a sample project using CUBEMX for this stm32f446re controller and trying to flash using st-link/v2. But has got one warning as below. Can anyone help in understanding whether this warning affect any reset issue on board? is this can be neglected (complete logs are attached below for reference)?
Warn : STM32 flash size failed, probe inaccurate - assuming 512k flash
We are facing flashing issue on this custom board as below,
Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
none separate
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 8000 kHz
adapter_nsrst_delay: 100
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 8000 kHz
Info : STLINK v2 JTAG v31 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.215124
Info : Unable to match requested speed 8000 kHz, using 4000 kHz
Info : Stlink adapter speed set to 4000 kHz
Info : STM32F446RETx.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : device id = 0x10006421
Warn : STM32 flash size failed, probe inaccurate - assuming 512k flash
Info : flash size = 512kbytes
undefined debug reason 7 - target needs reset
Error: timed out while waiting for target halted
TARGET: STM32F446RETx.cpu - Not halted
in procedure 'reset'
in procedure 'ocd_bouncer'
Error: Target not halted
Error: failed erasing sectors 0 to 0
Error: flash_erase returned -304
Can anyone suggest the solution for this above issue?