-
Notifications
You must be signed in to change notification settings - Fork 123
Open
Description
At https://doc-en.rvspace.org/VisionFive2/Boot_UG/JH7110_SDK/boot_address_allocation.html
I find that in 16M QSPI, I can reach U-Boot fw env block by reading from
0xF0000 0x10000 U-Boot environment variables
Now,
data@f00000 { |
0
. It shall be defined as:
data@f0000 {
reg = <0xf0000 0x10000>;
};
With this, fw_printenv
from Linux succeeds, I can see/edit U-Boot config.
My proposal would also be to define whole QSPI flash:
partitions {
compatible = "fixed-partitions";
#address-cells = <0x01>;
#size-cells = <0x01>;
spl@0 {
reg = <0x00 0x20000>;
};
env@f0000 {
reg = <0xf0000 0x10000>;
};
uboot@100000 {
reg = <0x100000 0x400000>;
};
bootdata@500000 {
reg = <0x500000 0xb00000>;
};
flashall@0 {
reg = <0x00 0x1000000>;
};
};
Especially with flashall, I can read/write whole QSPI if desired.
Please review this. Thank you.
MichaIng and Headcrabed
Metadata
Metadata
Assignees
Labels
No labels