Support wolfBoot on Renesas RZN2L #411
Conversation
miyazakh
force-pushed
the
renesas_rz2
branch
from
62c90f5
to
048505e
Compare
|
@danielinux and @dgarske will review this wolfBoot port. PR cap, no action needed. |
-- update based on readme
fix spelling errors
miyazakh
force-pushed
the
renesas_rz2
branch
from
6f8a08d
to
3683ad0
Compare
src/boot_renesas.c
Outdated
| @@ -66,6 +66,10 @@ void do_boot(const uint32_t *app_offset) | |||
| */ | |||
| app_entry = (void(*)(void))(*VECTOR_Reset_Handler); | |||
| (*app_entry)(); | |||
| #elif defined(_RENESAS_RZN_) | |||
| app_entry = (void(*))(0x10010000); | |||
There was a problem hiding this comment.
Please avoid hard coding. This should come from .config or a linker script.
There was a problem hiding this comment.
Thanks. I use an address value of linker script.
There was a problem hiding this comment.
Looks good. Could you please add a short paragraph in docs/Targets.md, so it's consistent with the other Renesas ports, and the target is properly tracked in the docs?
[edit] ideally the section in Targets.md could also introduce the "verify/select candidate/load to ram" strategy required by the target, which is not obvious at first glance.
clean up
|
Hi @danielinux |
|
Looks good now, off to @dgarske for final comments & merge. |
Initial Support wolfBoot on Renesas RZN2L