Skip to content

ota_update module for firmware downloading#7167

Closed
kYc0o wants to merge 23 commits intoRIOT-OS:masterfrom
kYc0o:firmware_updates
Closed

ota_update module for firmware downloading#7167
kYc0o wants to merge 23 commits intoRIOT-OS:masterfrom
kYc0o:firmware_updates

Conversation

@kYc0o
Copy link
Contributor

@kYc0o kYc0o commented Jun 9, 2017

Based on #6922 and #7007.

This module enables firmware downloading using TFTP, but making the version requests using CoAP.

The server which is ready to answer such request is from @aabadie available here. You can follow the instructions there to set up a OTA server for the images produced by this PR.

Basically the instructions are the same as explained on #6922, but if you want to include the ota_update module you need to add it as any other module with:

USEMODULE += ota_update_tftp

The module will set up a CoAP client which will ask a server given by OTA_SERVER_ADDRESS (IPv6 address) and a CoAP port given by OTA_SERVER_COAP_PORT, which is the one configured on the OTA server.

Afterwards, it asks every OTA_PERIODIC_REQ_TIME seconds for an update (it "pulls" the update from the server). Push updates will be added in following PRs.

For now, it only works for iotlab-m3 boards, since the previous PRs work also only for this board.

Thanks to #7128 and #5366 it will be soon possible to use this in samr21-xpro boards. Stay tuned.

@kYc0o kYc0o added Type: new feature The issue requests / The PR implemements a new feature for RIOT State: waiting for other PR State: The PR requires another PR to be merged first labels Jun 9, 2017
@kYc0o kYc0o force-pushed the firmware_updates branch from c162261 to 24c9c85 Compare July 10, 2017 17:00
@kYc0o kYc0o force-pushed the firmware_updates branch from 24c9c85 to f6b44b9 Compare July 10, 2017 17:02
@kYc0o kYc0o removed this from the Release 2017.10 milestone Oct 16, 2017
@emmanuelsearch
Copy link
Member

@kYc0o should we close this one in favor of #7398 ?

@kYc0o
Copy link
Contributor Author

kYc0o commented Feb 23, 2018

Yes, safely, however I'm afraid #7398 is too outdated, thus maybe I'll open a new one with the most recent work.

@kYc0o kYc0o closed this Feb 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

State: waiting for other PR State: The PR requires another PR to be merged first Type: new feature The issue requests / The PR implemements a new feature for RIOT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants