Incomplete bsp description/bringup explanation
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
Start with Hardware/Star64/index.md and the referenced genimage.cfg setup, then compare the documented microSD boot flow with the image layout described in the issue. Update the bringup instructions so the required image placement and relevant target-specific steps are explicit, and verify that the documented procedure matches the supported target behavior.
由索引模型根据 Issue 内容生成。
描述
I am about to port seL4 to Visionfive 2 (v1.3b) . Since this board has the same SoC like Star64, I used it as a starting point.
One major issue I had to deal with is, that the description for the Star64 lacks some essential steps.
- The description is mainly based on star64_sdcard, but for Booting via microSD card it does not explain how to get the sel4 image on the sd card. I changed the
genimage.cfgto create a partition holding the image.
image data.vfat {
vfat {
files = {
"sel4test-driver-image-riscv-star64"
}
}
size = 8M
}
image sdcard.img {
hdimage {
gpt = true
}
partition spl {
image = "u-boot/spl/u-boot-spl.bin.normal.out"
partition-type-uuid = 2E54B353-1271-4842-806F-E436D6AF6985
offset = 2M
size = 2M
}
partition uboot {
image = "build/opensbi_uboot_payload.img"
partition-type-uuid = 5B193300-FC78-40CD-8002-E86C45580B47
offset = 4M
size = 4M
}
partition fatdata {
image = "data.vfat"
}
}
- The image generated by the sel4test suit contains its own openSBI partition. At least for the new target
visionfive2-1.3b, I had to rundd if=images/sel4test-driver-image-riscv-visionfive2-1.3b of=images/temp.image bs=1024 skip=2048to omit the first 2 MiB (openSBI). The resulting file could be loaded to 0x60000000 like the description said.
I can not verify that it behaves the same way on Star64 (I do not have a board) but I can tell that sel4test-driver-image-riscv-star64 starts with openSBI, too. It might be possible to skip the dd step and adjust the addresses in the u-boot console or change the build behavior of sel4test for the star64 target.
I did not check thoroughly on all supported targets but I can imagine that similar information is missing for other targets. I hope this helps others with first steps on seL4 :)
:~) now I continue debugging do get visionfive 2 running
EDIT: Forget about the second point. I forgot to use the -DUseRiscVOpenSBI=OFF flag for the ../init-build.sh.
- 主要语言
- HTML
- 星标
- 19
- 派生
- 67
- 平均合并
- 17 小时 11 分钟
- 30 天内合并 PR
- 5
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
seL4/docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 62/100
-
难度 1/5 1 小时以内 新手友好度 55/100
-
CI
难度 3/5 1-2 天 新手友好度 45/100
-
CI
难度 3/5 1-2 天 新手友好度 48/100
-
难度 4/5 3-5 天 新手友好度 42/100
相似的 Issue
-
难度 1/5 1-3 小时 新手友好度 86/100
g1331/phantom-circuit#93 ·
维护者通常 1 天内回复
-
[OperatorHub] Add OLM installation method to the documentation #1193可能已有人在做 @NiccoloFei 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
cloudnative-pg/plugin-barman-cloud#1233 ·
维护者通常 1 天内回复
-
15.0
难度 2/5 1-3 小时 新手友好度 68/100
-
[workshop-sim] Repair: Make Copilot access and billing path decision self-contained in Steps 07/07d未关闭feedback simulation workshop
难度 2/5 1-3 小时 新手友好度 72/100
githubnext/gh-aw-workshop#5597 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
Icinga/icinga-notifications-web#645 ·
维护者通常 1 天内回复