"
```
Configure the Mender client:
```bash
sudo mender setup \
--demo \
--device-type raspberrypi4 \
--hosted-mender \
--tenant-token ${TENANT_TOKEN}
```
In case of a Raspberry Pi 3, change `--device-type` to `raspberrypi3`
Restart the Mender client:
```bash
sudo systemctl restart mender-client
```
Install `dfu-util` which is required by the DFU Update Module:
```bash
sudo apt-get update && sudo apt-get install dfu-util
```
## Step 1 - Installing the DFU Update Module
Download the latest version of the DFU Update Module by running the following on the Raspberry Pi:
```bash
mkdir -p /usr/share/mender/modules/v3 && wget -P /usr/share/mender/modules/v3 https://raw.githubusercontent.com/mendersoftware/mender-update-modules/master/dfu/module/dfu && chmod +x /usr/share/mender/modules/v3/dfu
```
## Step 2 - Getting the update artifacts
There are already a set of artifacts prepared based on the [Device Firmware Update (DFU)](https://hub.mender.io/t/device-firmware-update-dfu/1617) and [Updating device firmware using DFU in Zephyr Project on a FRDM-K64F board](https://hub.mender.io/t/updating-device-firmware-using-dfu-in-zephyr-project-on-a-frdm-k64f-board/1618) tutorials for the Raspberry Pi 3.
Download the archive containing the pre-built Artifacts by running the following on your PC:
```bash
wget https://d1b0l86ne08fsf.cloudfront.net/mender-k64f-update-artifacts/k64f-firmware-artifacts.tar.gz
```
Unpack the archive:
```bash
tar xvf k64f-firmware-artifacts.tar.gz
```
You should now have the following Mender Artifacts:
> ```bash
> blinky-blue.mender
> blinky-green.mender
> blinky-red.mender
>
> ```
Inspecting one of the Artifacts we can see that is of an `dfu` type:
> ```bash
> $ mender-artifact read blinky-blue.mender
> Mender artifact:
> Name: blinky-blue
> Format: mender
> Version: 3
> Signature: no signature
> Compatible devices: '[raspberrypi3]'
> Provides group:
> Depends on one of artifact(s): []
> Depends on one of group(s): []
> State scripts:
>
> Updates:
> 0:
> Type: dfu
> Provides: Nothing
> Depends: Nothing
> Metadata: Nothing
> Files:
> name: signed-blinky-blue.bin
> size: 13548
> modified: 2020-03-06 13:34:28 +0100 CET
> checksum: 3350fc78c6bbe946ddfca2fc5630a0f1728281bddde26c3e870a547ac2357f59
>
> ```
These Artifacts can now be uploaded to the Mender server and one can create a proxy deployment to the FRDM-K64F device using Mender.
## Conclusion
In this tutorial we have demonstrated the possibility of using Mender to proxy firmware updates to external components.
The setup we have used in the tutorial supports end-to-end verification, as the Mender client is able to verify the signature of the Mender Artifact, and MCUboot used on the FRDM-K64F is also able to verify the signature of the provided update images. Additionally MCUboot is able to verify the signature on each boot, meaning that it is able to detect tampering of the firmware.
Obviously the communication between the Mender client and the Mender server are also encrypted (TLS) which adds an extra layer of security that you can leverage when you proxy the firmware update.
* * *
_If this tutorial was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!_
---
### Author:  [@arun](https://hub.mender.io/u/arun)
#### Post date: [July 20, 2020, 11:10am UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/2 "2020-07-20T11:10:44Z")
Hi @mirzak,
its okay to update firmware with FRDM-K64F device connected to a Raspberry Pi 3.
but i want to test the firmware update in raspberrypi3 itself(raspbian buster image) with mender is there any possibility to do that any help on that or any link which i can follow.
thanks & regards
arun
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [July 20, 2020, 1:29pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/3 "2020-07-20T13:29:47Z")
Hi @arun
Of course we support that. 😉 See [Raspberry Pi 3 Model B/B+ Raspbian](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/51) for more details
Drew
---
### Author:  [@giacomoravagli](https://hub.mender.io/u/giacomoravagli)
#### Post date: [September 7, 2020, 4:00pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/4 "2020-09-07T16:00:29Z")
Hi. I have a question that is closely related to that topic. Currently I am realizing a prototype consisting of a Raspberry Pi 3b+ (running Mender) and an additional device connected to the Raspberry Pi over CAN bus. Basically, the RaspberryPi can update the firmware of the device connected to it (executing a Python script that I realized).
My idea is to use the RaspberryPi as a proxy: once the new firmware is received, I want the Python script to be executed automatically. The system is meant to be used by human beings.
Basically I am missing two features:
1. how the Python script can be started automatically after the new firmware is received at Raspberry side using Mender? I guess that the most simple option (as the user interact with the Raspberry Pi) would be to realize an “application” running on the Raspberry Pi that the user can execute to check if updates have been released on the Mender server; if yes, the firmware is downloaded and the Python script used to flash the firmware is executed. This would require the possibility to “avoid update download if the user is not executing the application” at server side, and the possibility to mark (at server side) the update as failed if the “custom update application” does not exit as expected (e.g. the Python script is interrupted, or the device is not available e.g. due to a disconnection).
2. there would be the need to have a list of “secondary devices” which do not run Mender client, but are associated to a device that run Mender. In my example, I would like to see the RaspberryPi listed on the server, and by clicking on it see that also an additional device is connected to the Raspberry. This is useful to see the software version that each device is running.
I would like to specify that I have carefully read the guides on single file update, script update, and this one on proxy deployment of course. I am sorry for the long message, I hope everything is clear.
Thank you in advance! 😃
---
### Author:  [@nico](https://hub.mender.io/u/nico)
#### Post date: [May 19, 2022, 7:18am UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/5 "2022-05-19T07:18:35Z")
Dear @giacomoravagli
Did you find a solution for your setup? I am considering something quite similar. I am especially interested if Mender is able to show software versions in the Mender Server of the “main” device (the one where mender client is running) and also software versions of “child” or “secondary” controllers which are connected to this main device?
---
### Author:  [@nico](https://hub.mender.io/u/nico)
#### Post date: [May 19, 2022, 7:30am UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/6 "2022-05-19T07:30:05Z")
Dear @mirzak
On a machine we plan to run an embedded linux with internet connectivity (maybe a Raspberry CM or similar) together with a companion microcontroller for the real-time control application. The real-time application is rather simple, I plan to use a bare-metal Rust application and no real-time OS like Zephyr. The microcontroller will not require a bootloader, it will just run the plain application. Do you suggest to use a custom module to perform the flashing of the microcontroller from the embedded linux device? Or what else do you suggest?
And the other question: Is it possible to see both software versions (embedded linux version and real-time app firmware version) in the Mender Server dashboard?
Thanks for your help!
Nico
---
### Author:  [@nico](https://hub.mender.io/u/nico)
#### Post date: [May 20, 2022, 8:22am UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/7 "2022-05-20T08:22:29Z")
Or maybe @drewmoseley you have a hint for me for the above questions? Thanks in advance!
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [May 20, 2022, 12:27pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/8 "2022-05-20T12:27:37Z")
Hi @nico,
I _think_ using a custom update module here makes sense and I am pretty sure there is a way to see both versions after installing. @TheYoctoJester can you help further here?
Drew
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [May 20, 2022, 3:02pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/9 "2022-05-20T15:02:48Z")
@nico + @drewmoseley,
Thanks for the heads up! Yes, a custom update module makes perfect sense here. The way to see both artifacts in the device inventory is providing a custom [device inventory script](https://docs.mender.io/client-installation/inventory#example-inventory-script) which gathers all the desired data and puts it into the inventory, therefore making it accessible on the management UI. Together with the custom column update that was rolled out recently this should have you covered.
Greetz,
Josef
---
### Author:  [@nico](https://hub.mender.io/u/nico)
#### Post date: [May 20, 2022, 4:52pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/10 "2022-05-20T16:52:54Z")
Thanks a lot for that advice. I will look into the docs for the device inventory scripts. Have a good weekend!
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [October 2, 2023, 7:40pm UTC](https://hub.mender.io/t/how-to-do-a-proxy-deployment-to-an-frdm-k64f-device-connected-to-a-raspberry-pi-3-4/1619/11 "2023-10-02T19:40:03Z")
A post was merged into an existing topic: [Need to understand the integration of the mender-client with DFU](https://hub.mender.io/t/need-to-understand-the-integration-of-the-mender-client-with-dfu/6236/6)