# DFU with STM32CubeProgrammer fails

**URL:** <https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199>\
**Category:** Hardware\
**Created:** [June 30, 2024, 6:05pm UTC](https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199 "2024-06-30T18:05:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ralphjy](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@ralphjy](https://discuss.blues.com/u/ralphjy)\
**Post date:** [June 30, 2024, 6:05pm UTC](https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199/1 "2024-06-30T18:05:03Z")

</div>

I was attempting to update the firmware on an NB GL 500 using the STM32CubeProgrammer and the update failed when it had a communication error. Now nothing works - not recognized by the programmer and doesn’t show up as a COM port. I had missed the note about not using v2.16.0 of the programmer.

I assume that I have bricked the notecard. Is there any way that I can recover? Can I manually get it into bootloader mode?

---

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [July 1, 2024, 1:14pm UTC](https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199/2 "2024-07-01T13:14:36Z")

</div>

Hey @ralphjy,

You can manually get the Notecard into bootloader mode with some of our Notecarrier boards. See this guide [Recovering a Bricked Notecard - Blues Developers](https://dev.blues.io/datasheets/application-notes/recovering-a-bricked-notecard/).

TJ

---

<div class="post-metadata">

**Author:** ![ralphjy](https://avatars.discourse-cdn.com/v4/letter/r/47e85d/32.png) [@ralphjy](https://discuss.blues.com/u/ralphjy)\
**Post date:** [July 1, 2024, 3:26pm UTC](https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199/3 "2024-07-01T15:26:50Z")

</div>

Thanks TJ. That worked and I successfully updated the firmware using v2.15 of the STMCubeprogrammer.

I used a NoteCarrier-A 2.0. I also have a NoteCarrier-F 1.0 but the Boot Pin is labeled GND. Does this also work?

Ralph

---

<div class="post-metadata">

**Author:** ![tjvantoll](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/tjvantoll/32/231_2.png) [@tjvantoll](https://discuss.blues.com/u/tjvantoll)\
**Post date:** [July 2, 2024, 4:07pm UTC](https://discuss.blues.com/t/dfu-with-stm32cubeprogrammer-fails/2199/4 "2024-07-02T16:07:02Z")

</div>

> That worked and I successfully updated the firmware using v2.15 of the STMCubeprogrammer.

🎉

> I also have a NoteCarrier-F 1.0 but the Boot Pin is labeled GND. Does this also work?

It does not. Exposing `N_BOOT` was one of the changes we made with the 1.3 version of the F.

TJ