Could be override in boot_from_devices().
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: Ifbfac5903ec61e65739732949f9e6b8a2704155d
(cherry picked from commit f8ca32e1ca)
The spl can bring up uboot & kernel, and their entry points are diffirent,
so pass their entry points by entry_point_os.
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: I625d135d219cfbfb620ff1e3d0de5278143f4079
(cherry picked from commit 78628ac9a9)
1. the arm32 trust firmware is diffirent with arm64, support it.
2. add entry_point_os to indicate the uboot or kernel entry point.
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: I24d1601323e99f40e81d18f1937f762b2ecc137f
(cherry picked from commit a64fd729d4)
Change-Id: I3b1420989d158c52259365d90011524b047b5750
Create a new flag to indicate mux route is from topgrf or pmugrf.
* INVALID: means do not need to set mux route
* DEFAULT: means same regmap as pin iomux
* TOPGRF: means mux route setting in topgrf
* PMUGRF: means mux route setting in pmugrf
Change-Id: I1620054f1af915b9495e16b2d10a3f9cf9fd5980
Signed-off-by: Jianqun Xu <jay.xu@rock-chips.com>
Use it to make sure which firmware can be bring up.
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: Ib2cec8bf7c78fa436efade0518b07c3193170c7b
Add next_stage to indicate the next boot stage is uboot or kernel.
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: I9104ede143c5a9c7f0bff6869e67d5e605e596ca
"verified-boot" is more clearly for developers.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: Ib8a87af18480f2d5e765b9007eb5f8473ee424fb
It is added in image-fit.c as a common function.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I105e0a7cacde226da1bb787ba1f4f320d6daa55d
This property is verified to support rollback index protect
for verified-boot.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I54c5baaa275189ca96f18be66753b1292a395df6
The MMC is initialized by pre-loader or bootrom, so it is no need to
initialize it again. Open this config to skip some unused initialized
process.
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: If00fc3ce7df4d15e71ecfd8f8717a59640c3b7a9
If the switch is enabled, it's voltage is same as parent supply.
Signed-off-by: shengfei Xu <xsf@rock-chips.com>
Change-Id: I8fb60bd5aa3bb0a47cac84982113663e2bf5941e
Usage:
scripts/fit-resign.sh [signed fit image] [new signature]
It replaces the /configurations/conf@1/signature@1/value.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I73ff5ec9a625a87ef91f29773ad241f833ef1758
error: implicit declaration of function ‘fdt_get_base_address’
[-Werror=implicit-function-declaration]
Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
Change-Id: Ic950b9382bd200d854028773b7a4c63b4bed5c16
Before this, we always get the 1st of BUCK range group which
brings the problems we face now.
Let's traverse all the possible BUCK ranges to fix this issue.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I61a341fcbd190bcc0baff8267a94063c15abcc30
if data address and data len is meet crypto v2
hardware requirements, data will be calculated
without cache.
Change-Id: Ifc5acc5b449c581dbf3ac5f20ad6b8d932954aa7
Signed-off-by: Lin Jinhan <troy.lin@rock-chips.com>
Support packing optional second level boot-loader:
$ ./tools/mkimage -n rk3399 -T rksd -d \
rk3399_ddr_800MHz_v1.24.bin:rk3399_miniloader_v1.19.bin out -v
Adding Image rk3399_ddr_800MHz_v1.24.bin
Size 116492(pad to 116736)
Adding Image rk3399_miniloader_v1.19.bin
Size 88060(pad to 88064)
Image Type: Rockchip RK33 (SD/MMC) boot image
Init Data Size: 116736 bytes
Boot Data Size: 88064 bytes
Mainly parse init file and boot file from datafile option, copy them to
the image, and padding each one to 2KB boundary.
NOTE:
I don't know much about rknand.c, and there's no way to verify it now.
The output image is unchanged though (with a few extra padding).
Haven't got any feedback from upstream yet...But whatever, let's do this!
Change-Id: I0ce98a44634cfcd8acfe9a3e2cfbe3ee0107fba4
Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
It's not friendly to handle the fail event in a bootcmd list,
let's handle this in C function.
Entering rockusb/fastboot mode after verified-boot failed.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: Ib617582e1cc386f5c30abe1a8bbd2b5f353c0e49
Maybe user need to do some job when bootcmd failed, they
could override it.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I1c32c1ad37700e66d45fe033fbfa46d3f350205d
Joseph Chen
Jason Zhu
Jianqun Xu
shengfei Xu
Lin Jinhan
Jeffy Chen