Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
8e919137
Commit
8e919137
authored
11 years ago
by
Gregory Nutt
Browse files
Options
Downloads
Patches
Plain Diff
cosmetic updates to comments
parent
4410deb8
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
arch/arm/src/sama5/sam_boot.c
+10
-6
10 additions, 6 deletions
arch/arm/src/sama5/sam_boot.c
with
10 additions
and
6 deletions
arch/arm/src/sama5/sam_boot.c
+
10
−
6
View file @
8e919137
...
...
@@ -135,15 +135,19 @@ static const struct section_mapping_s section_mapping[] =
* mapping to map the boot region at 0x0000:0000 to virtual address
* 0x0000:00000
*
*
T
he first level bootloader is supposed
to provide the AXI MATRIX
* mapping for us at boot time base on the state
of the BMS pin. However,
* I have found that in the test environments
that I use, I cannot always
* be assured of that physical address mapping.
*
When executing from NOR FLASH, t
he first level bootloader is supposed
*
to provide the AXI MATRIX
mapping for us at boot time base on the state
*
of the BMS pin. However,
I have found that in the test environments
*
that I use, I cannot always
be assured of that physical address mapping.
*
* So we do both here. If we are executing from FLASH, then we provide
* the MMU to map the physical address of FLASH to address 0x0000:0000;
* if we are executing from the internal SRAM, then we trust the bootload
* to setup the AXI MATRIX mapping.
*
* If we are executing out of ISRAM, then the SAMA5 primary bootloader
* probably copied us into ISRAM. If we are executing from external
* SDRAM, then a secondary bootloader must have loaded us into SDRAM. In
* either case we trust the bootloader to setup the AXI MATRIX mapping on
* our behalf.
*/
#if defined(CONFIG_ARCH_LOWVECTORS) && !defined(CONFIG_SAMA5_BOOT_ISRAM) && \
...
...
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