nDBOOT OB over UART broke after v2.14

[dnugent]

Hello,

This is a pretty straightforward bug report. For F767 Devices, when trying to configure dual boot mode over UART, the nDBOOT Option byte doesnt appear for Cubeprogrammer versions greater than v2.14

The typically workflow is

1) uncheck nDBANK

2) apply

3) restart/reconnect

4) nDBOOT option byte appears

5) uncheck nDBOOT

6) apply.

This works on all versions of Cubeprogrammer using an STlink - good! But when executing this same sequence using the UART Bootloader on version v2.15 to v2.22, the nDBOOT option bytes never appears after step 3. 

This regression is preventing us from using newer versions of CubeProgrammer.

Best,

Daniel

[dnugent]

Interesting discovery. Looks like the issue flips around v2.15. 

v2.14 and before

- We CAN see the nDBOOT over UART

- (NEW OBSERVATION) we can NOT see nDBOOT over STLink

v2.15 and after

- We can NOT see the nDBOOT over UART

- We CAN see nDBOOT over STLink

[dnugent]

Another thought:

This entire issue thread exists because of the constraint where the nDBANK must be unchecked & applied for the nDBOOT option byte to appear. I've always found this behavior odd and disruptive to our option byte setting workflow. Ideally, the nDBOOT would be settable regardless of the value of nDBANK. I think if dual boot mode configuration was streamlined to a single option byte write, this bug report wouldnt need to exist.

Last note on the nDBOOT conditional availability: Changing back from dual bank mode to single bank mode (something I've done a lot while debugging this issue) is basically impossible & dangerous. It causes cubeprogrammer to be bricked and prevents you from connecting to your chip ever again. The only way to "unbrick" it is to modify the option bytes using the CLI mode of the tool. This probably deserves it's own bug report given the severity of the issue but its exposure it pretty low and not currently blocking our development. 

[Kouthair]

Hello there @dnugent  and thank you for bringing this to our attention.
I have reproduced this on v2.22 and I have now reported this to the dedicated team. (internal ticket n°0061110).
We'll let you know ASAP whenever the fix is live.

However, I was unsuccessful tried reproducing this behavior:

Last note on the nDBOOT conditional availability: Changing back from dual bank mode to single bank mode (something I've done a lot while debugging this issue) is basically impossible & dangerous. It causes cubeprogrammer to be bricked and prevents you from connecting to your chip ever again. 

---

Could you please provide me with more details (affected version, connection mode, steps to reproduce etc.)? That would be of great help to this investigation and would be greatly appreciated.

PS: Ticket number: 0061110 is an internal tracking number and is not accessible or usable by customers.