On 6/7/19 1:08 PM, Brenton Chetty wrote:
Please ignore my previous email. I forgot to add '$()' for $(IMAGE_OFFSET).
Everything seems fine now. Just need to find out how to erase the necessary
flash instead of a complete erase.
The `-e` option is used by default, if it works without it at al
Please ignore my previous email. I forgot to add '$()' for $(IMAGE_OFFSET).
Everything seems fine now. Just need to find out how to erase the necessary
flash instead of a complete erase.
Regards
Brenton
On Fri, Jun 7, 2019 at 11:20 AM Brenton Chetty wrote:
> Hi Gaëtan
>
> I managed to get riotb
Hi Gaëtan
I managed to get riotboot to select the newer image between slots 0 and 1.
I had to first flash "riotboot.bin" (from $RIOTBASE/bootloaders), then
slots 0 and 1 without doing a full erase.
How do i link the Makefile in (boards/cc2538dk/Makefile.include) to
(sys/riotboot/Makefile.include)
Hi Brenton,
I noticed there is `-e` in `FFLAGS` which performs a full erase of the
rom so flashing a second slot while the first one or the bootloader is
there cannot work.
We removed this full erase from all flashers for boards using
`riotboot`. If the flasher erases only what is required
Hi Gaëtan, i managed to get the tests/riotboot to pass whilst using
'riotboot/flash-combined-slot0'. I also used the '-a' option For
'cc2538-bsl.py'. This allowed me to use the 'riotboot/flash-slot0'
successfully. However, i couldn't get slot 1 working. How do think i should
approach this problem.
Hey guys, i kind of managed to get the riotboot tests to pass. Whenever i
program via terminal (gcc-arm) i receive the error "[FAILED] You're not
running riotboot". But when i program via the UniFlash tool, it works.
Note, so far only "tests_riotboot-slot0-combined.bin" works. I assume its
an offse
Thanks for the advice guys, but I'm still struggling to get the cc2538dk to
pass the riotboot tests.
To: Francisco Acosta
I provided the length and start variables to link the slots.
I used the cc2538sf53.ld Linker Script.
I was not sure how to get the offset required, so i used 255 as the offset,
FYI I opened a PR adding a WIP porting guide:
https://github.com/RIOT-OS/RIOT/pull/11597
On Mon, May 27, 2019 at 2:43 PM Gaëtan Harter
wrote:
> On 5/27/19 2:36 PM, Emmanuel Baccelli wrote:
> > Seems to me that a quick riotboot porting guide could be useful somewhere
> > in the wiki.
> >
>
> More
On 5/27/19 2:36 PM, Emmanuel Baccelli wrote:
Seems to me that a quick riotboot porting guide could be useful somewhere
in the wiki.
More in the `riotboot` documentation in the repository I would say.
On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter
wrote:
Hi Brenton,
if you only use the de
Seems to me that a quick riotboot porting guide could be useful somewhere
in the wiki.
On Mon, May 27, 2019 at 2:30 PM Gaëtan Harter
wrote:
> Hi Brenton,
>
> if you only use the default `riotboot/flash` or `flash` in
> `tests/riotboot` targets, you do not need flasher changes.
> But you should
Hi Brenton,
if you only use the default `riotboot/flash` or `flash` in
`tests/riotboot` targets, you do not need flasher changes.
But you should not use `riotboot/flash-slot0` and `riotboot/flash-slot1`
targets for the moment.
To have the support declared and merged in RIOT, it also needs to
Hi Brenton!
So far I remember we didn't take it into account, and I don't know if
someone is taking care of it.
As far as I know, there are two ways of supporting that CPU:
1. The way we do it now, which is linking the image in another start
address so the bootloader can recognise it and boot i
Hey guys, has anyone succeeded in providing riotboot support for the
cc2538dk board as yet?
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
13 matches
Mail list logo