2022-02-28 05:45 AM
STMicroelectronics ST-LINK GDB server. Version 5.8.0
Copyright (c) 2020, STMicroelectronics. All rights reserved.
Starting server with the following options:
Persistent Mode : Disabled
LogFile Name : C:\WORK\NEW_PROJECTS_DEV_BOARD\prototype_1\prototype\CM4\Debug\st-link_gdbserver_log.txt
Logging Level : 31
Listen Port Number : 61234
Status Refresh Delay : 15s
Verbose Mode : Enabled
SWD Debug : Enabled
Target connection mode: Attach
Reading ROM table for AP 3 @0xe00fffd0
Hardware watchpoint supported by the target
COM frequency = 4000 kHz
ST-LINK Firmware version : V2J37S7
Device ID: 0x450
PC: 0x1
ST-LINK device status: LOCKUP
Enter STM32_AppReset() function
NVIC_DFSR_REG = 0x00000009
NVIC_CFGFSR_REG = 0x00001100
ST-LINK detects target voltage = 2.94 V
Device in lock up state, possibly "read and debug" protected. Use monitor commands to remove the protection
ST-LINK device initialization OK
Waiting for debugger connection...
Waiting for connection on port 61234...
Accepted connection on port 61234...
Debugger connected
ST-LINK device status: HALT_MODE
Enter STM32_AppReset() function
NVIC_DFSR_REG = 0x00000008
NVIC_CFGFSR_REG = 0x00000000
------ Switching to STM32CubeProgrammer -----
-------------------------------------------------------------------
STM32CubeProgrammer v2.7.0-RC1
-------------------------------------------------------------------
Log output file: C:\Users\FMOHAM~1\AppData\Local\Temp\STM32CubeProgrammer_a20644.log
ST-Link Server is running on port : 7184
ST-LINK SN : 30FF6F065647373734141043
ST-LINK FW : V2J37S7
Board : --
Voltage : 2.93V
SWD freq : 4000 KHz
Connect mode: Under Reset
Reset mode : Hardware reset
Device ID : 0x450
Revision ID : Rev V
Device name : STM32H7xx
Flash size : 2 MBytes (default)
Device type : MCU
Device CPU : Cortex-M7/M4
Memory Programming ...
Opening and parsing file: ST-LINK_GDB_server_a20644.srec
File : ST-LINK_GDB_server_a20644.srec
Size : 39552 Bytes
Address : 0x08100000
Erasing memory corresponding to segment 0:
Erasing internal memory sector 8
Error: failed to erase memory
Error: failed to erase memory
Encountered Error when opening C:\ST\STM32CubeIDE_1.2.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_1.6.0.202101291314\tools\bin\STM32_Programmer_CLI.exe
------ Switching context -----
Error in STM32CubeProgrammer
Debugger connection lost.
Shutting down...
i did try to erase all the memory but it says its read protected and i checked in the options bites too there is no protection
2022-02-28 05:46 AM
its says some flash pages are protected when i try to erase it
2022-02-28 06:05 AM
Check your chip is real BI 2M flash or dual bank config...
Your code addr seems to load code with 1M offset
2022-02-28 06:12 AM
it is a dual core M4 and M7
2022-02-28 06:29 AM
A custom designed board?
Sure that VCAP pins have suitable capacitance, and are at around 1.25V?
Watch also that code uses LDO or SMPS configuration based on design, as these aren't interchangeable and can lead to serious connectivity issues.
2022-02-28 07:07 AM
hi
it is a custom board, the SMPS are power pins.
so you need to connect them high or low depending on design not to be left floated
2022-03-02 01:10 PM
hi
every one
i check every thing, but its not the power or the connection. i solved it by connecting the ST-Link VCC to the board VCC. when i connect the external power then i am having the problem
2022-03-02 01:10 PM
i am having a different problem, i am using dual core but when i program it and start the debugger the it says "Target is not responding, retrying...". i thing it has to do with the TRACK and DEBUG in .ioc file. can you help me with that?
i never used dual core so i am not familiar with it.
2022-03-02 01:45 PM
>>TRACK and DEBUG
??
Trace?
Sorry I'm using Keil
Perhaps look for some videos or tutorials for CubeIDE
https://www.youtube.com/watch?v=k3mXhPZSasw
2022-03-02 01:47 PM
yes sorry ,
trace