diff options
| author | Leo Yu-Chi Liang <ycliang@andestech.com> | 2021-11-04 04:53:26 +0300 |
|---|---|---|
| committer | Leo Yu-Chi Liang <ycliang@andestech.com> | 2021-12-02 11:43:45 +0300 |
| commit | 666da85dc98931b82efa68b0c1a96fc654b7a40b (patch) | |
| tree | 8f707310de096fbb7efa32328d902873a0ed18e5 /drivers | |
| parent | 4a14bfffd42f968ed9d72a780a8d44a9053c5b95 (diff) | |
| download | u-boot-666da85dc98931b82efa68b0c1a96fc654b7a40b.tar.xz | |
board: ae350: Support autoboot from RAM
Add boot command "bootcmd_ram" to support autoboot from RAM.
This feature could be useful at the very initial state of chip design
when there is only a minimal set of peripheral. (e.g. without mmc and mac ..etc)
The kernel image is default to be loaded at 0x2000000 via debug port,
and the following script serves as an example:
spl()
{
cmd="riscv64-linux-gdb -q \
-ex \"target remote $host:$port\" \
-ex \"load\" \
-ex \"thread apply all set \\\$pc=&_start\" \
-ex \"thread apply all set \\\$a0=\\\$mhartid\" \
-ex \"thread apply all set \\\$a1=<dtb address>\" \
-ex \"restore u-boot.itb binary 0x200000\" \
-ex \"restore Image binary 0x2000000\" \
-ex \"c\" \
spl/u-boot-spl
"
echo $cmd
eval $cmd
}
The address where the kernel is loaded can be altered by
changing the value of KERNEL_IMAGE_ADDR.
Signed-off-by: Leo Yu-Chi Liang <ycliang@andestech.com>
Reviewed-by: Rick Chen <rick@andestech.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions