examples/ota: add documentation on how to deliver update via ethos #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow handling full dependencies in cpu
Prepare to move some dependencies out of Makefile.include
It allows module (not in the application) which require the periph_flashpage feature to correctly also require periph_flash_common TODO: fix this, it should not be a dependency on FEATURES but USEMODULE.
TODO Rebase message edit at the end. * updated to edbg/openocd new variables * Use RIOTBOOT_FW_SLOT_SIZE: upcomming PRs should remove RIOTBOOT_SLOT1_SIZE and RIOTBOOT_SLOT2_SIZE * Use ROM_START_ADDR for 'firmware' to handle iotlab-m3 * Use ROM_OFFSET and FW_ROM_LEN * Info on non supported existing bootloader for the moment in dist/riotboot * dist/riotboot: allow running different targets and not only flash * RIOTBOOT_HDR_LEN as hexadecimal and can be overwritten
It creates a binary with
bootloader + slot1-signature + slot1
…nctions * Except the bootloader, only one slot size is supported * export RIOTBOOT_ variables * Set the header length to FIRMWARE_METADATA_SIZE * Add a warning that 'dist/tools/firmware' should be compiled with the same options as the current board
Calculate RIOTBOOT_FW_SLOT_SIZE is calculated as an hexadecimal value and handles ROM_LEN defined as kilobytes like '512K'
…sh pages Fix support when FIRMWARE_METADATA_SIZE < FLASHPAGE_SIZE.
On `samr21-xpro` it used 1040 for previously 1024 bytes. Now it has 2048 bytes.
Adapt from shell/commands/sc_gnrc_netif
`RIOTBOOT_FW_SLOT_SIZE` contains both the metadata and the firmware. TODO describe somewhere.
Variables must be exported for `openocd.sh` on `iotlab-m3`.
Variables must be exported for `openocd.sh` on `iotlab-m3`.
As it us using 'export' to the shell for openocd, it does not work properly. Replace it with calculating the value in a subshell.
make is a bit strange sometimes and considers various factors to decide the precedence of the rule to be applied: definition order is one (and the %.signed.bin is after %.bin, and would be also if we put it at the end of Makefile.include), but also if a rule is implicit is then preferred no matter the order. A quite complete and coincise overview of the topic can be found here: https://stackoverflow.com/questions/28842851/force-make-to-use-a-more-specific-rule Given the inclusion mechanism used in RIOT it should be safer to explicitly state things, although may seem ugly sometimes.
makefiles/riotboot.mk: enforce rule precedence (first signed.bin over .bin) for gnu make
|
Excellent! Thank you so much for the information. I'll test it asap and merge it. |
kYc0o
force-pushed
the
wip/rebase/ota_work_branch
branch
from
314a05f to
359ee2e
Compare
|
I was trying without success, I have the following output when I try to ping the node: vagrant@vagrant:~$ ping6 fe80::22e:ceff:fe65:942%tap0
PING fe80::22e:ceff:fe65:942%tap0(fe80::22e:ceff:fe65:942) 56 data bytes
From fe80::70bc:3cff:fe39:e4f3 icmp_seq=1 Destination unreachable: Address unreachable
From fe80::70bc:3cff:fe39:e4f3 icmp_seq=2 Destination unreachable: Address unreachable
From fe80::70bc:3cff:fe39:e4f3 icmp_seq=3 Destination unreachable: Address unreachableDid you configure the network somehow before running the test? |
|
BTW sorry for the rebase! I think the best is to remove all commits, rebase on the wip branch and then apply your commit. |
|
I'm closing this and opening #15 since with rebasing it became quite messy |
|
Great! And sorry again for the mess! |
|
As for your question: hmm no I didn't do anything particular except what written in the readme. I see you run in a vagrant box, I wonder if that has some networking limitations. Can you in case send me the "ifconfig tap0" and "route -n" output to see how things look? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
Add documentation on how the OTA procedure can be tested delivering the update via serial interface using the ethos driver
Issues/PRs references
See comments in RIOT-OS#9969