# Sharing mender update between multiple devices

**URL:** <https://hub.mender.io/t/sharing-mender-update-between-multiple-devices/2231>\
**Category:** General Discussions\
**Tags:** yocto, warrior\
**Created:** [July 24, 2020, 2:44pm UTC](https://hub.mender.io/t/sharing-mender-update-between-multiple-devices/2231 "2020-07-24T14:44:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Austriker](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/austriker/32/511_2.png) [@Austriker](https://hub.mender.io/u/Austriker)\
**Post date:** [July 24, 2020, 4:31pm UTC](https://hub.mender.io/t/sharing-mender-update-between-multiple-devices/2231/3 "2020-07-24T16:31:41Z")

</div>

Ok.

With a proxy can I say look at the other mender client for the update ? or should I try to handle something like this

> [@How to do a proxy deployment to an FRDM-K64F device connected to a Raspberry Pi 3 / 4](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3/1619):
>
> Introduction When designing products based on Linux, it is a common design pattern to have external MCU that handles real-time critical tasks. The external MCU could be mounted on the same PCB as the Linux SoC, or it could be an external component that is connected to the Linux capable device, e.g over USB or a serial line. The external MCU obviously then is another software component in the device system that should be possible to update over the lifetime of the product. In this tutorial we w…

---

_[View the full topic](https://hub.mender.io/t/sharing-mender-update-between-multiple-devices/2231)._
