review FSBL boot #118
Labels
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: M-Labs/artiq-zynq#118
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It seems that FSBL would enable FPU but the L2 cache is not enabled. Unit tests passed, the performance is not as good as when L2 cache is enabled but should be acceptable...
I wonder if we should enable the L2 cache in
artiq-zynq
rather thanzynq-rs
, as I'm not sure what would happen if you enable L2 cache twice...Another workaround would be to boot szl with FSBL, and use netboot as network bootloader for
artiq-zynq
. But it may require adding some config forszl
to prevent it from loading itself indefinitely.OK, and SZL does the same, and ARTIQ does not re-enable it - correct?
This sounds like the correct solution for FSBL compatibility/consistency.
What's the impetus here? Being able to cross-check with ARTIQ booted from FSBL in case of any issues?
ARTIQ would re-enable it for core1. Maybe we should just drop that, and enable fpu for both cores in szl.
OK
See #94, currently there are some issues with the RAM initialization for a board, and it has to use FSBL for initialization. Still need some time to fix the issue.
Yes, if FSBL enables it on both cores.
Also make SZL more general and able to boot non-ARTIQ payloads.
Sorry, no.
Currently both FSBL and SZL would not enable fpu on core1.
Also, apart from L2 cache, SZL would also some CPU options that improves performance. I'm not sure if FSBL would enable those.
E.g. prefetch, branch prediction, etc.