rockchip64: fix OrangePi 4 LTS boot with BTF, bump uboot to 2024.10 #7887
+22
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
At last I found, after quite a lot of headaches, that the OrangePi4 LTS booting issues with BTF-enabled kernels was not due to old u-boot, relocation issues or overlapping segments. Instead it was the utterly crappy (but woking) DMC driver that, when BTF is enabled, becomes an utterly crappy non working driver.
I disabled it and - magically - everything is fixed now.
In the meantime, believing the issue was in u-boot, I bumped u-boot to v2024.10 with little to almost no pain.
Some considerations:
BOOT_SCENARIO=binman
is already available for rockchip64 targets, idbloader and u-boot.itb are built by u-boot/binman, without doing it "manually" in the armbian family include scriptCONFIG_ROCKCHIP_EXTERNAL_TPL=y
in u-boot config if the board wants the proprietary ddrbin, otherwise u-boot will use its own TPL as ddr initialization binaryGitHub issue reference:
Jira reference number AR-2618
How Has This Been Tested?
Checklist: