cancel
Showing results for 
Search instead for 
Did you mean: 

STM32 h747 Dual CoreDebugging Issues - 2nd core doesn't connect

meme002
Associate II

Hello All,

I was trying the basic Led pin example that is on you tube  and tried to replicate the same thing in STM32 747 board. I was able to successfully start the debug for CM7 core. I get Download verified successfully. But when I start the CM4 core, I get his from the console

Starting server with the following options:
 Persistent Mode : Disabled
COM frequency = 24000 kHz
Target connection mode: Attach
Reading ROM table for AP 3 @0xe00fffd0
Hardware watchpoint supported by the target 
ST-LINK Firmware version : V3J12M3
Device ID: 0x450
PC: 0x8100488
ST-LINK device status: HALT_MODE
ST-LINK detects target voltage = 3.27 V
ST-LINK device status: HALT_MODE
ST-LINK device initialization OK
Failed to bind to port 61235, error code -1: No error
Stm32Device, pollAndNotify running...
Failure starting SWV server on TCP port: 61235
Failed to bind to port 61234, error code -1: No error
Failure starting GDB server: TCP port 61234 not available.
GdbSrv, deInit entry.
Shutting down...
GdbSessionManager, deInit entry.
GdbSessionManager, deInit exit
SwvSrv deInit entry
SwvSrv deInit exit
Stm32Device, closeDevice() entry
Stm32Device, pollAndNotify stopped
Stm32Device, closeDevice() exit
Stm32Device, deInit success
GdbSrv, deInit exit.
Exit.

I tried all this options.

1. Restarted the PC, didn't work

2. Shutdown and waited some time, still didn't work.

3. changed the port number. No luck.

4. Tried on Mac laptop still no success. This tells me it has somethings to with the hardware.

5. I re flashed the chip using STcubemx, still no luck.

6. I triple checked the STM32 Debugger settings from the youtube still I cant seem to find what it can be.

Do you think there is a possibility that CM4 chip is not working? or let me know if you guys have any other solutions.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
meme002
Associate II

Got it I mistyped the port number wrong for 2nd core and hence it did not work. I followed the AN 5361 document.

View solution in original post

1 REPLY 1
meme002
Associate II

Got it I mistyped the port number wrong for 2nd core and hence it did not work. I followed the AN 5361 document.