Re-Generating with CubeMX sets the project to ST-LinkV2 instead of ST-LinkV3. It will not recover until I delete the generated folders. Initially CubeMX generates correctly.

[FZida.1]

I am working with IAR EWARM 9.10.1 and STM32CubeMX 6.2.1 on a NUCLEO-H743ZI2.

To reproduce:

1. Create NUCLEO-H743ZI2 project in STM32CubeMX
2. Generate it
3. Start IAR
4. Download to target (compile & flash succeed)
5. Change something in IAR, e.g. add a source file to project tree.
6. Save project.
7. Download to target (compile & flash succeed)
8. Go to STM32CubeMX and generate again.
9. HERE my git tool shows the change from ST-LinkV3 to ST-LinkV2
10. Go to IAR
11. Download to target (will compile, but fail to flash, as it is now falsely set to ST-Link V2)

STM32CubeMX generation falsely changes the EWARM/<projectname>.ewd file, when working with modified EWARM project files.

<option>

                    <name>CCSTLinkProbeList</name>

                    <version>1</version>

                    <state>3</state> //this needs to stay at 3 for the NUCLEO-H743ZI2, but gets changed to 2

                </option>

3 -> ST-Link V3

2 -> ST-Link V2

I am happy to help, as this is really annoying for my daily work.

[Khouloud ZEMMELI]

Hello @FZida.1​ 

Thank you for your post,

I'll check it then I'll get back to you 🙂

Khouloud

[Khouloud ZEMMELI · Accepted solution]

Hi again @FZida.1​ ,

I reproduced the issue and I confirm it, each time the code is re-generated, the  <state>X</state> needs to conserve the change made by user.

I would like to take this opportunity to explain you the writing done in this configuration, in fact, the <state>0</state> means STLINK 1, <state>1</state> means STLINK2 and <state>2</state> means STLINK3.

Thanks @FZida.1​  for reporting the problem, issue will be fixed.

Khouloud