Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
firmware
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
q3k
firmware
Commits
e0529893
Commit
e0529893
authored
5 years ago
by
q3k
Browse files
Options
Downloads
Patches
Plain Diff
l0der: support more alignment options
parent
18f942e6
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
epicardium/l0der/l0der.c
+13
-2
13 additions, 2 deletions
epicardium/l0der/l0der.c
with
13 additions
and
2 deletions
epicardium/l0der/l0der.c
+
13
−
2
View file @
e0529893
...
...
@@ -33,6 +33,8 @@ struct _pie_load_info {
// Addresses within ELF file.
uint32_t
image_start
;
uint32_t
image_limit
;
// Highest alignment request for a segment.
uint32_t
strictest_alignment
;
/// Populated by _get_load_addr
// Load address of ELF file.
...
...
@@ -259,6 +261,12 @@ static int _get_load_addr(struct _pie_load_info *li)
li
->
image_load_start
=
li
->
load_address
+
li
->
image_start
;
li
->
image_load_limit
=
li
->
load_address
+
li
->
image_limit
;
// Ensure within alignment requests.
if
((
li
->
load_address
%
li
->
strictest_alignment
)
!=
0
)
{
LOG_ERR
(
"l0der"
,
"_get_load_addr: too strict alignment request for %ld bytes"
,
li
->
strictest_alignment
);
return
-
ENOEXEC
;
}
// Place stack at top of core1 memory range.
li
->
stack_top
=
core1_mem_limit
;
...
...
@@ -378,7 +386,7 @@ static int _run_relocations(FIL *fp, struct _pie_load_info *li, Elf32_Ehdr *hdr)
static
int
_load_pie
(
FIL
*
fp
,
Elf32_Ehdr
*
hdr
,
struct
l0dable_info
*
info
)
{
int
res
;
struct
_pie_load_info
li
;
struct
_pie_load_info
li
=
{
0
}
;
// First pass over program headers: sanity check sizes and calculate
// memory image bounds. l0der currently only supports loading the image into
...
...
@@ -410,10 +418,13 @@ static int _load_pie(FIL *fp, Elf32_Ehdr *hdr, struct l0dable_info *info)
if
(
phdr
.
p_type
==
PT_LOAD
)
{
// Check alignment request.
if
(
phdr
.
p_align
>
4
)
{
if
(
(
phdr
.
p_vaddr
%
phdr
.
p_align
)
!=
0
)
{
LOG_ERR
(
"l0der"
,
"_load_pie: phdr %d alignment too strict"
,
i
);
return
-
ENOEXEC
;
}
if
(
phdr
.
p_align
>
li
.
strictest_alignment
)
{
li
.
strictest_alignment
=
phdr
.
p_align
;
}
uint32_t
mem_start
=
phdr
.
p_vaddr
;
uint32_t
mem_limit
=
phdr
.
p_vaddr
+
phdr
.
p_memsz
;
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment