ST-LINK on STM32N6570-DK board warning 0x486 when connecting on STM32CubeProgrammer

[Avgerinos]

Hello

As I am trying to connect the STM32N6570-DK board on the STM32CubeProgrammer, initially the STM32CubeProgrammer recognises my device as in the following picture:

 

When I press Connect on the STM32CubeProgrammer I get a
warning: Connection to device 0x486 is lost
as in the following picture:

 

and then an error that says Data read fail
as in the following picture:

 

I am using a MacBook Air M3, 2024, but even on windows (running on a virtual machine) I get the same error on the STM32CubeProgrammer windows version.

Is there a way to overcome this issue? What could be the cause?

 

Thank you

 

[STTwo-32]

Hello @Avgerinos 

I think this FAQ may help you.

Best Regards.

STTwo-32

[RomainR.]

Hello @Avgerinos 

I managed to get all STM32Cube tools working on Mac OS M1 and M2 without any issues. I don't have M3 hardware.

1. Start with connecting the STM32N6570-DK STLinkV3 (CN8) to your Mac, and check if and how it recognizes the USB device (see the link below) https://www.youtube.com/watch?v=aXd7FsjcIpI
2. Confirm that you are using the latest version STM32CubeProgrammer v2.19.0?
3. On Mac computer, Update Rosetta: $> softwareupdate --install-rosetta
4. Update the STLink Firmware to V3J16M7 of your STM32N6570-DK.
5. Ensure that your board is in DEV_BOOT (BOOT1=H) and that the Red LED2 is on after a RESET.
6. Try changing the ST-LINK configuration to Mode=Hot plug and Reset Mode=Software reset.
7. Change the USB cable.
8. Try on another computer.

Good luck.

Romain,

[Avgerinos]

Hello @RomainR. 

I have not been able to make it work.

 

1. I have connect it using a usb-c to usb-c cable to my computer and it seems that it recognises it as in the following picture. (I think you mean STLINK-V3EC USB Type-C CN6 connector. is this right?)

2. I am using STM32CubeProgrammer v2.19.0

3. Rosetta is installed on my computer as in the following picture

4. The firmware version is the V3J16M6 but it seems that it can not be updated. I have tried the following

Using a usb-c to usb-c cable:

I get the following error in the next picture:

 

Using a usb-c to usb-a cable with an adaptor for my Mac (usb-a to usb-c):

It seems that it recognises my device as in the following picture:

 

But when I press update I get the following:

Although it says Upgrade successful, when I refresh it shows again the first picture, meaning that the firmware has not been updated and it is still in the V3J16M6 version.

 

5. I confirm that the DEV_BOOT (BOOT1=H) and the Red LED2 is on after a RESET.

 

6. I tried the Mode=Hot plug and Reset Mode=Software reset but again I get an error as in the following picture:

(I get the same error using both cables as described above (usb-c to usb-c cable and usb-c to usb-a cable with an adaptor for my Mac (usb-a to usb-c))

 

 

7. I changed the usb cable as described above. I bought a usb-c to usb-c cable which I did not have before.

 

8. Well, I have not tried on another computer yet, because this is the one I have and I am able to work on. I would like to make it work on my computer since I would not be able to work on another computer.

 

Please let me know in case you have any other suggestions in mind.

Thank you for your help

 

[RomainR.]

Hi @Avgerinos 

The actual STLink-V3 version (the one on your N6-DK) is V3J15M6, this can be checked with the STM32CubeProgrammer capture you shared in the previous post.

I confirm that the USB-C must be connected on CN6 which correspond to STLink-V3 on the DK board.

Now, concerning the STLink firmware update, Do you have clicked "Open in update mode " before starting update?
These steps are needed to configure the STLink-V3 mcu (the STM32F7 on board) in DFU mode, and then program the new firmware version in the flash.
In the Update to firmware, the version should be V3J16M7, and not the V3J15M7.

Otherwise, it seems that your computer detects well STLink. I suggest you to:

- Apply the firmware upgrade as I explained. First clic on "Open in update mode" then "Update"

- Try to uninstall, the install again STM32CubeProgrammer.
Did the board was already used in the past with STM32CubeProgrammer ou STM32CubeIDE ? If yes, it worked?
Do you change anything on the hardward?

Sorry, I don't have other solution to suggest.
Best regards
Romain

[PMera.1]

Ubuntu. Windows 10. Windows 11? Same behavior. All the other dev boards I have (including the latest U5s) work perfectly. Not this one.

I can sometimes connect to the board - most of the time the board's COM Led (LD4) blinks green - red. Power Status (LD3) is off. Unplugging and re-plugging the board does nothing. Sometimes both LEDs are red. But I can connect to the board. Sometimes LD4 is red, LD3 is green and the board's connectable (shows up in CubeProgrammer).

Essentially, this feels less like a development board and more like a Temu plug-and-pray 2.99 dollars (shipping included) device.

Anyway, after invoking the Gods of embedded, I can connect to the board, but any flashing attempt issues an immediate disconnection (logs below). After that, I can no longer connect to the board. It continues to show up in CubeProgrammer. But any connection attempt is followed by an immediate disconnection, with the same error.

After that, I need to do voodoo to have it enumerate again. Like unplug the usb-c stlink cable, plug it in the user usb-c port, switch the power supply select to 5V_USB, than back to stlink. Or something like that.

I tried using an unpowered USB HS hub. I tried using a different, powered hub. I tried using a HS port directly. A 3.0 port directly. I tried almost every port on my PC. Nope.  

I tried powering the board via USB_5V and programming via the dedicated usb-c connector. Nope.

The FAQ referenced by @STTwo-32 is useless (for me). I tried around 10 different usb-c cables: 2.0 cables, 3.0 cables, 3.1 cables, all of which work with all my other dev boards, phones, 5G routers etc.

The only thing I haven't yet tried is using an external programmer. Which I'll be doing tomorrow.

Huge disappointment though.

18:46:47 : UR connection mode is defined with the SWrst reset mode
18:46:47 : ST-LINK SN : 002B00423234510E37333934
18:46:47 : ST-LINK FW : V3J15M7
18:46:47 : Board : STM32N6570-DK
18:46:47 : Voltage : 3.29V
18:46:47 : SWD freq : 8000 KHz
18:46:47 : Connect mode: Hot Plug
18:46:47 : Reset mode : Software reset
18:46:47 : Device ID : 0x486
18:46:47 : Revision ID : Rev B
18:46:47 : UPLOADING ...
18:46:47 : Size : 1024 Bytes
18:46:47 : Address : 0x8000000
18:46:47 : Read progress:
18:46:47 : Data read successfully
18:46:47 : Time elapsed during the read operation is: 00:00:00.003
18:46:54 : Opening and parsing file: x-cube-n6-ai-h264-usb-uvc-dk.hex
18:46:54 : Memory Programming ...
18:46:54 : File : x-cube-n6-ai-h264-usb-uvc-dk.hex
18:46:54 : Size : 11.11 MB 
18:46:54 : Address : 0x70000000
18:46:54 : Erasing memory corresponding to segment 0:
18:46:54 : Erasing memory corresponding to segment 1:
18:46:54 : Erasing memory corresponding to segment 2:
18:46:54 : Download in Progress:
18:46:54 : Error: failed to download Sector[0]
18:46:54 : Error: failed to download the File
18:46:54 : Warning: Connection to device 0x486 is lost
18:46:54 : Disconnected from device.

 

 

[Andrew Neil]

---

@PMera.1 wrote:

I tried using an unpowered USB HS hub. I tried using a different, powered hub. I tried using a HS port directly. A 3.0 port directly. I tried almost every port on my PC. Nope.  

I tried powering the board via USB_5V and programming via the dedicated usb-c connector. Nope.

The FAQ referenced by @STTwo-32 is useless (for me). I tried around 10 different usb-c cables: 2.0 cables, 3.0 cables, 3.1 cables, all of which work with all my other dev boards, phones, 5G routers etc.

---

Have you tried disconnecting all other USB devices from the Host ?

 

[PMera.1]

Yes.

And even when using an external SWD programmer (via MIPI20 connector, i believe) I still get the same error. I've tried with three different PCs now.