Pyocd errors when debugging on NUCLEO-F746ZG (pyocd.core.exceptions.DebugError: No cores were discovered!)

mukp · January 27, 2021, 9:30am

I’m using Mbed Studio: 1.3.1 with NUCLEO-F746ZG (STM32F746). The program is able to run on the board without errors, but the debug function gives this error log below. Any idea on how to fix this issue?

0000671:INFO:rom_table: [1]
0000673:INFO:rom_table: [2]
0000676:INFO:rom_table: [3]
0000677:INFO:rom_table: [1]
0000679:INFO:rom_table:[1]
0000681:INFO:dwt:4 hardware watchpoints
0000687:INFO:fpb:8 hardware breakpoints, 1 literal comparators
0000709:CRITICAL:main:No cores were discovered!
Traceback (most recent call last):
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd_main_.py”, line 362, in run
self.COMMANDSself._args.cmd
File "c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd_main.py", line 680, in do_gdbserver
with session:
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\core\session.py”, line 302, in enter
self.open()
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\core\session.py”, line 420, in open
self._board.init()
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\board\board.py”, line 85, in init
self.target.init()
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\core\coresight_target.py”, line 160, in init
seq.invoke()
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\utility\sequencer.py”, line 208, in invoke
resultSequence = call()
File “c:\Users\MikoNore\AppData\Local\Mbed Studio\mbed-studio-tools\python\lib\site-packages\pyocd\core\coresight_target.py”, line 299, in check_for_cores
raise exceptions.DebugError(“No cores were discovered!”)
pyocd.core.exceptions.DebugError: No cores were discovered!
“GDB server stopped unexpectedly with exit code 1”

Thanks

JohnnyK · January 27, 2021, 10:22am

Hello,

I not sure but I think the situation is still same

BR, Jan

mukp · January 27, 2021, 10:28am

Thanks for your reply.
Do you mean that the board is not supported for debug in Mbed Studio?
//Miko

jeromecoutant · January 27, 2021, 12:52pm

Hi
Are you working with mbed-os-6.6.0 version ?
There is an issue corrected with STM32: RESET GPIO during init is configurable by jeromecoutant · Pull Request #14032 · ARMmbed/mbed-os · GitHub

Regards,

JohnnyK · January 27, 2021, 5:11pm

Ye, I mean it is not supported because it is probably still in development.

DISCO-F746NG - “No cores were discovered!” · Issue #863 · pyocd/pyOCD (github.com)
CMSIS Pack for STM32F7/H7 broken? · Issue #727 · pyocd/pyOCD (github.com)

I also tried some steps according to this page pyOCD/target_support.md at master · pyocd/pyOCD (github.com) but without succesful.

BR, Jan

JojoS · February 6, 2021, 1:19pm

I have the same problem, no cores were discovered.
The pyocd that comes with MbedStudio is not the most recent, but also with an external pyocd it reports the same when started with ‘pyocd gdbserver’. I have installed also the packs for the STM32F7, the pyocd version is 0.29.1.dev16.

Debugging in VSCode with Cortex-Debug works, but with some other old problem: a step over runs always into the interrupt handler
I will try some workaround that is posted here:

But again, this is next problem when you got the debugger running. I guess pyocd has a problem with the complex ROM table scanning in the ARM coresight.

Edit:
another link for this problem:

I have performed a mass erase with the STM32CubeProgrammer tool and now pyocd can connect correctly. But debugging in MBedStudio still quits without an error message.
ok, that problem was the CubeProgrammer was still connected. After disconnecting, the old behaviour, no cores were discovered.

rotu · May 14, 2021, 11:40pm

Did you ever figure this out? I’m having a similar-looking issue (No cores were discovered) on a STM32H743ZI2

danielpe · May 17, 2021, 6:39am

More or less randomly means that it used to run ok, then started to stop after some time

jeromecoutant · May 17, 2021, 7:56am

Hi
Maybe you could have a look on

github.com/pyocd/pyOCD

Memory Transfer Fault connecting to STM32H743ZI2

opened 11:24PM - 05 May 21 UTC

rotu

target

I'm using Mbed studio to try and debug on a STM32H743ZI2, and it fails with a re…ad error like: ``` 0000860:WARNING:rom_table:Invalid coresight component, cidr=0x0 0000861:WARNING:rom_table:Invalid coresight component, cidr=0x0 0000862:ERROR:rom_table:Error attempting to probe CoreSight component referenced by ROM table entry #5: Memory transfer fault (read) @ 0xe00f0fbc-0xe00f1043 Traceback (most recent call last): File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/coresight/rom_table.py", line 358, in _read_table self._handle_table_entry(entry, entryNumber) File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/coresight/rom_table.py", line 408, in _handle_table_entry cmpid.read_id_registers() File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/coresight/rom_table.py", line 113, in read_id_registers regs = self.ap.read_memory_block32(self.top_address + self.IDR_READ_START, self.IDR_READ_COUNT) File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/probe/stlink_probe.py", line 271, in read_memory_block32 return conversion.byte_list_to_u32le_list(self._link.read_mem32(addr, size * 4, self._apsel)) File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/probe/stlink/stlink.py", line 385, in read_mem32 return self._read_mem(addr, size, Commands.JTAG_READMEM_32BIT, self.MAXIMUM_TRANSFER_SIZE, apsel) File "/home/dan/.config/Mbed Studio/mbed-studio-tools/python/lib/python3.7/site-packages/pyocd/probe/stlink/stlink.py", line 343, in _read_mem raise exc pyocd.core.exceptions.TransferFaultError: Memory transfer fault (read) @ 0xe00f0fbc-0xe00f1043 Resetting target ``` A minimal command that causes this is: `pyocd cmd -c reset` Repeatedly trying to reproduce this shows the fault happens at particular addresses: `0xe00f0fbc-0xe00f1043` or `0xe000efbc-0xe000f043` See logs: [mbed-studio.log](https://github.com/pyocd/pyOCD/files/6430775/mbed-studio.log) [minimal.log](https://github.com/pyocd/pyOCD/files/6430784/minimal.log)

Regards,
Jerome