Dear SEGGER-Team,
is there a way to abort flash download when the wrong mcu is connected to the J-Link?
In our scenario we have two boards which are based on STM32 MCUs from the same family "STM32F765".
However on the first board is the STM32F765_NI and on the second is the STM32F765_IG.
We have a firmware project in SES with a build configuration for each board.
Lets say a "NI" board is connected to our J-Link.
Then we try to debug the "IG" build configuration.
Result: The "IG" firmware is downloaded onto the "NI" board ROM.
Our desired result would be, that the flash download is aborted because the wrong mcu variant is connected.
Best regards,
inv_sma
is there a way to abort flash download when the wrong mcu is connected to the J-Link?
In our scenario we have two boards which are based on STM32 MCUs from the same family "STM32F765".
However on the first board is the STM32F765_NI and on the second is the STM32F765_IG.
We have a firmware project in SES with a build configuration for each board.
Lets say a "NI" board is connected to our J-Link.
Then we try to debug the "IG" build configuration.
Result: The "IG" firmware is downloaded onto the "NI" board ROM.
Our desired result would be, that the flash download is aborted because the wrong mcu variant is connected.
Best regards,
inv_sma