Unable to read device id from ROM table

[Prathiksha]

Hi,

I am currently facing an issue while connecting to the STM32 board using STM32CubeProgrammer. The tool consistently shows the error: "Unable to read device ID from ROM table."

I have already tried the following troubleshooting steps:

• Performed a hardware/software/core reset using the RESET button

• Verified that all required supply voltages are correct

• Checked the hardware connections

Despite this, the programmer is still unable to establish communication with the M7 core via ST-Link. It appears that the device is not being detected properly, and at the moment the board has become unusable.

Could you please guide me on possible causes or additional steps I can take to resolve this issue? I would be happy to provide any further information if required.

Thank you for your support.

Best regards,
Prathiksha

[mfgkw]

Hi Prathiksha,

which board and which ST-Link do you talk about?

[Prathiksha]

Board: STM H755Ziq
and I'm talking about when I try to connect ST link debugger in STM IDE it won't connect and hence I tried in STM cube programmer and there I'm getting that mentioned error.

I have attached the error window.

Thankyou

[mfgkw]

So it is a NUCLEO board NUCLEO-H755ZI-Q and you use the integrated ST-Link?
Do you work on Windows or Linux?

[Prathiksha]

Yes.
I use Linux currently.
But if you say Windows might help, I can try in that too!

[mfgkw]

(From my side you will never hear a recommendation to use Windows. Never.

For Windows I could not contribute anything useful, that's why I asked.)

Maybe you have the wrong USB cable?

Is the ST-Link detected properly when you connect it to the PC? I would have a look on the messages from dmesg while connecting (maybe you have to change to root and then run "dmesg -w" in a console, then connect the ST-Link and see which messages appear now in the console windows, you can stop it with Ctrl-C).

[Prathiksha]

Reference: [104563.147223] usb 3-7: New USB device found, idVendor=0483, idProduct=3754, bcdDevice= 1.00
[104563.147232] usb 3-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[104563.147235] usb 3-7: Product: STLINK-V3
[104563.147238] usb 3-7: Manufacturer: STMicroelectronics
[104563.147241] usb 3-7: SerialNumber: 004300493234511233353533
[104563.150690] cdc_acm 3-7:1.1: ttyACM0: USB ACM device

I checked using dmesg -w as suggested.
The ST-Link V3 is correctly detected by the kernel (VID:PID 0483:3754), and the virtual COM port appears as /dev/ttyACM0.

[mfgkw · Accepted solution]

That looks ok so far.

Do you have "connect under reset" enabled?

The described problem seems to arise for all STM32 when the core is not genuine STM but some fake. Obviously this is not the case here.

Regarding STM32H75... there seems to be an issue when boot order of the two cores is changed in some way.

Did you change any jumpers/solder bridges/option bytes or something like that?

What did you flash before?

I have not really any experience with this. But maybe it helps when you look in this direction, so "STM32H755 unable device ID from ROM table...".

There are already some similiar problems like https://community.st.com/t5/stm32cubeprogrammer-mcus/can-t-connect-to-stm32h755-after-changing-boot-option-byte/td-p/783892 or https://community.st.com/t5/stm32-mcus-embedded-software/nucleo-h755zi-q-deadlock/td-p/66695

If this does not help you might want to hope for somebody more familiar with STM32H755 ...

[Prathiksha]

Hey, the Problem links you shared were helpful, fortunately I had the same case.
And I could solve it.

Thanks a lot!