Skip to main content
B
bsuthar
Associate III
July 2, 2026
Question

CubeProgrammer V2.23 Issue

  • July 2, 2026
  • 5 replies
  • 136 views

One Quick Observation , V2.23 takes so much time as compare to V2.22 ( windows 64 ) , for Reconnecting MCU & Throwing Error  after setting RDP2. approx 45 seconds by V2.23. while 5 seconds for V2.22 version.

 

 

    5 replies

    Aziz BRIGUI
    Aziz BRIGUI
    ST Technical Moderator
    July 2, 2026

    Hello ​@bsuthar,

    Could you specify the MCU you’re using? Or are you seing this across multiple devices?

    Aziz 

    In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
      Andrew Neil
      Andrew Neil
      Super User
      July 2, 2026

      What is the target, and what debug probe?

       

       

      A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
      B
      bsutharAuthor
      Associate III
      July 2, 2026

      MCU : STM32F303Rb

      Debugger : STLINK-V2 

      I tried with same MCU with 11 Different Custom boards.

        Andrew Neil
        Andrew Neil
        Super User
        July 2, 2026

        I tried with same MCU with 11 Different Custom boards.

        How “different”?  11 instances of the same design, or 11 different designs?

        What about ST boards ?

         

        Debugger : STLINK-V2 

        A genuine one ?

         

        A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
          B
          bsutharAuthor
          Associate III
          July 2, 2026

          ​@Andrew Neil 

          Debugger : STLINK-V2  , yes Genuine Only. has Back side series Number. Also, all other operation works fine with V2.23 itself.

          we tested on same design board of 11 pcs.

          Tried back with V2.22 , and ALL works fine, now.

           

          Andrew Neil
          Andrew Neil
          Super User
          July 2, 2026

          ​@bsuthar - What about ST boards ?

          A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
          B
          bsutharAuthor
          Associate III
          July 3, 2026

          ​@Andrew Neil 

          Are you suggesting me to set RDP2 level on ST Nucleo Boards and then check ?

          Or just wanna to use it as external debugger ?

           

           

           

          Aziz BRIGUI
          Aziz BRIGUI
          ST Technical Moderator
          July 6, 2026

          Hi ​@bsuthar,

          No need to lose boards on your side, I could reproduce what you’re seing (You can reproduce without setting RDP to 0xCC by unplugging power on STM32CubeProgrammer reconnect).

          I’m studying why the timeout has been increased and will get back to you ASAP.

          PS: Since you’re setting RDP to level 2, you can use the noreconnect option in CLI as a temporary workaround.

          Aziz 

          In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
            B
            bsutharAuthor
            Associate III
            July 15, 2026

            Okay, ​@Aziz BRIGUI ,

            Will await your update.

            Reconnecting is just for ensuring that RDP2 set action executed succesfully.

            Aziz BRIGUI
            Aziz BRIGUI
            ST Technical Moderator
            July 20, 2026

            Hi ​@bsuthar,

            After investigation, turns out that this happened after the upgrade of QT6 in STM32CubeProgrammer v2.23 (from QT6.6 to QT6.10). 

            This is logged internally (internal tracking number 0064471). My guess is that some delay implementation changed inside the framework (But this is just a guess, issue is being investigated by our development team).

            Kind regards,

            Aziz 

            In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
            Terms & ConditionsAccessibility statement