# Dfu for non supported micros

**URL:** <https://discuss.blues.com/t/dfu-for-non-supported-micros/1772>\
**Category:** Firmware\
**Created:** [November 7, 2023, 10:16am UTC](https://discuss.blues.com/t/dfu-for-non-supported-micros/1772 "2023-11-07T10:16:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Embedded\_iceman](https://avatars.discourse-cdn.com/v4/letter/e/a698b9/32.png) [@Embedded\_iceman](https://discuss.blues.com/u/Embedded_iceman)\
**Post date:** [November 7, 2023, 10:16am UTC](https://discuss.blues.com/t/dfu-for-non-supported-micros/1772/1 "2023-11-07T10:16:52Z")

</div>

Hi

My host is not of the supported dfu architectures. I am looking into populating an incircuit programmer in the middle that would receive a binary from the notecard and pipe that into my host via its serial bootloader.

So my question is, is it possible to transfer a firmware binary from notehub that can be buffered in a micro say stm32 for later downstream data handling? Is card.binary the solution I should be using for that?

Thanks

---

<div class="post-metadata">

**Author:** ![RobLauer](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/roblauer/32/1567_2.png) [@RobLauer](https://discuss.blues.com/u/RobLauer)\
**Post date:** [November 13, 2023, 3:20pm UTC](https://discuss.blues.com/t/dfu-for-non-supported-micros/1772/2 "2023-11-13T15:20:16Z")

</div>

Hi @Embedded_iceman,

You actually don’t have to get as granular as issuing `card.binary` requests to manage host DFU updates with Notecard/Notehub. When you say “my host is not of the supported dfu architectures”, I assume you mean not supported with [Notecard Outboard Firmware Update](https://dev.blues.io/guides-and-tutorials/notecard-guides/notecard-outboard-firmware-update/)? If that’s the case, you can still use the IAP (in application programming) DFU method. I recommend [reading this doc article](https://dev.blues.io/notecard/notecard-walkthrough/host-firmware-update-requests/), but reach out with any additional questions!

Rob

---

<div class="post-metadata">

**Author:** ![zfields](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.blues.com/zfields/32/29_2.png) [@zfields](https://discuss.blues.com/u/zfields)\
**Post date:** [November 13, 2023, 7:10pm UTC](https://discuss.blues.com/t/dfu-for-non-supported-micros/1772/3 "2023-11-13T19:10:30Z")

</div>

To pile on, and answer your questions directly…

> is it possible to transfer a firmware binary from notehub that can be buffered in a micro say stm32 for later downstream data handling?

Yes.

> Is card.binary the solution I should be using for that?

Yes.

However, it is also preferable to partition your flash in such a way that you can run your firmware in half of the flash and download the new firmware into the unused partition (this is the solution Rob put forward). If your microcontroller can support this behavior, then you should be able to use [the `card.dfu` API](https://dev.blues.io/api-reference/notecard-api/card-requests/#card-dfu) mentioned in the doc Rob provided.

---

<div class="post-metadata">

**Author:** ![Embedded\_iceman](https://avatars.discourse-cdn.com/v4/letter/e/a698b9/32.png) [@Embedded\_iceman](https://discuss.blues.com/u/Embedded_iceman)\
**Post date:** [November 13, 2023, 7:32pm UTC](https://discuss.blues.com/t/dfu-for-non-supported-micros/1772/4 "2023-11-13T19:32:33Z")

</div>

Thanks for looking into this. My host is an msp430fr6xx and it comes with a ROM BSL bootloader.

Partitioning is not an option unfortunately. Program memory is too limited.

> **[slau550ab.pdf](https://www.ti.com/lit/ug/slau550ab/slau550ab.pdf?ts=1699890853379)**
>
> 972.25 KB