diff options
| -rw-r--r-- | Lessons_uncategorized/Lesson_FDF_FV/README.md | 19 |
1 files changed, 11 insertions, 8 deletions
diff --git a/Lessons_uncategorized/Lesson_FDF_FV/README.md b/Lessons_uncategorized/Lesson_FDF_FV/README.md index d2469c7..00b78b2 100644 --- a/Lessons_uncategorized/Lesson_FDF_FV/README.md +++ b/Lessons_uncategorized/Lesson_FDF_FV/README.md @@ -410,7 +410,17 @@ If you look to `VolInfo` output, you'll see that out FV has two attributes set: - `EFI_FVB2_ERASE_POLARITY` (set by default, means that uninitialized data bits in volume are set to 1) - `EFI_FVB2_ALIGNMENT_16` (set by our `FvAlignment=16` setting) -Other possible attribute fro FV that you can come across is `FvNameGuid`: +Similar to FD, the FV has an attribute that defines an address at which flash volume would be mapped to the CPU memory: +``` +FvBaseAddress = <...> +``` +And the tokens that define flash block structure: +``` +BlockSize = <...> +NumBlocks = <...> +``` + +Other possible attribute for the FV that you can come across is `FvNameGuid`: ``` FvNameGuid = <GUID> # Example: @@ -418,13 +428,6 @@ FvNameGuid = <GUID> ``` This attribute would lead to the creation of a file of type `EFI_FV_FILETYPE_FFS_PAD` (padding file) with a GUID value in its data. This file would be placed first in the FV. -And `BlockSize` attribute: -``` -BlockSize = <...> -``` -This token define flash chip attribute similar to the one in FD. - - # Links - [\[FV\] Sections](https://edk2-docs.gitbook.io/edk-ii-fdf-specification/2_fdf_design_discussion/25_-fv-_sections) |