Minor update to AT25BOOT; Updated README file
This commit is contained in:
parent
c3c8c86873
commit
2dad150289
@ -424,6 +424,11 @@ Creating and Using DRAMBOOT
|
|||||||
you don't have SAM-BA, an alternative is to use the AT25BOOT program
|
you don't have SAM-BA, an alternative is to use the AT25BOOT program
|
||||||
described in the next section.
|
described in the next section.
|
||||||
|
|
||||||
|
STATUS: I don't have a working SAM-BA at the moment and there are issues
|
||||||
|
with my AT25BOOT (see below). I currently work around these issues by
|
||||||
|
putting DRAMBOOT on a microSD card (as boot.bin). The RomBOOT loader does
|
||||||
|
boot that image without issue.
|
||||||
|
|
||||||
Creating and Using AT25BOOT
|
Creating and Using AT25BOOT
|
||||||
===========================
|
===========================
|
||||||
|
|
||||||
@ -513,6 +518,11 @@ Creating and Using AT25BOOT
|
|||||||
Serial Flash. (2) If using SAM-BA, make sure that you load the DRAM
|
Serial Flash. (2) If using SAM-BA, make sure that you load the DRAM
|
||||||
boot program into the boot area via the pull-down menu.
|
boot program into the boot area via the pull-down menu.
|
||||||
|
|
||||||
|
STATUS: While this program works great and appears to correctly write
|
||||||
|
the binary image onto the AT25 Serial FLASH, the RomBOOT loader will
|
||||||
|
not boot it! I believe that is because the secure boot loader has some
|
||||||
|
undocumented requirements that I am unaware of. (2014-6-28)
|
||||||
|
|
||||||
Running NuttX from SDRAM
|
Running NuttX from SDRAM
|
||||||
========================
|
========================
|
||||||
|
|
||||||
@ -3038,6 +3048,11 @@ Configurations
|
|||||||
The usage is different, otherwise I believe the notes for the dramboot
|
The usage is different, otherwise I believe the notes for the dramboot
|
||||||
configuration should all apply.
|
configuration should all apply.
|
||||||
|
|
||||||
|
STATUS: While this program works great and appears to correctly write
|
||||||
|
the binary image onto the AT25 Serial FLASH, the RomBOOT loader will
|
||||||
|
not boot it! I believe that is because the secure boot loader has some
|
||||||
|
undocumented requirements that I am unaware of. (2014-6-28)
|
||||||
|
|
||||||
dramboot:
|
dramboot:
|
||||||
|
|
||||||
This is a little program to help debug of code in DRAM. It does the
|
This is a little program to help debug of code in DRAM. It does the
|
||||||
@ -3119,6 +3134,11 @@ Configurations
|
|||||||
gdb> mon reg pc (make sure that the PC is 0x200040
|
gdb> mon reg pc (make sure that the PC is 0x200040
|
||||||
gdb> ... and debug ...
|
gdb> ... and debug ...
|
||||||
|
|
||||||
|
STATUS: I don't have a working SAM-BA at the moment and there are issues
|
||||||
|
with my AT25BOOT (see above). I currently work around these issues by
|
||||||
|
putting DRAMBOOT on a microSD card (as boot.bin). The RomBOOT loader does
|
||||||
|
boot that image without issue.
|
||||||
|
|
||||||
nsh:
|
nsh:
|
||||||
|
|
||||||
This configuration directory provide the NuttShell (NSH). This is a
|
This configuration directory provide the NuttShell (NSH). This is a
|
||||||
|
@ -184,6 +184,13 @@ int at25_main(int argc, char *argv)
|
|||||||
return EXIT_FAILURE;
|
return EXIT_FAILURE;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
/* Replace the vector at offset 0x14 with the size of the image to load
|
||||||
|
* into SRAM. The RomBOOT loader expects to find this size at that
|
||||||
|
* location.
|
||||||
|
*/
|
||||||
|
|
||||||
|
*(uint32_t *)(SAM_DDRCS_VSECTION + 0x14) = memoutstream.public.nput;
|
||||||
|
|
||||||
/* The HEX file load was successful, write the data to FLASH */
|
/* The HEX file load was successful, write the data to FLASH */
|
||||||
|
|
||||||
printf("Successfully loaded the Intel HEX file into memory...\n");
|
printf("Successfully loaded the Intel HEX file into memory...\n");
|
||||||
|
Loading…
Reference in New Issue
Block a user