Skip to content

[DOC+RTL] Vendor Test Partition Size Update in Markdown file-Patch 2.0#918

Merged
ekarabu merged 2 commits intopatch_ss_v1p0from
user/ekarabulut/Vend_test_md_file_fix
Nov 18, 2025
Merged

[DOC+RTL] Vendor Test Partition Size Update in Markdown file-Patch 2.0#918
ekarabu merged 2 commits intopatch_ss_v1p0from
user/ekarabulut/Vend_test_md_file_fix

Conversation

@ekarabu
Copy link
Collaborator

@ekarabu ekarabu commented Nov 18, 2025

  • VENDOR_TEST_PARTITION is listed 64-byte overall, while VENDOR_TEST is listed 32-byte in otp_ctrl_mmap.md file. This markdown file was updated.
  • This update does not change RTL logic but changes addressing for unused Fuse macro spaces and therefore some package files also got updated
  • Tackling VENDOR_TEST_PARTITION Markdown File Inconsistency [v2.0 and v2.1] #915

@ekarabu ekarabu changed the title [DOC+RTL Vendor Test Partition Size Update in Markdown file [DOC+RTL] Vendor Test Partition Size Update in Markdown file Nov 18, 2025
@ekarabu ekarabu changed the title [DOC+RTL] Vendor Test Partition Size Update in Markdown file [DOC+RTL] Vendor Test Partition Size Update in Markdown file-Patch 2.0 Nov 18, 2025
swenson
swenson previously approved these changes Nov 18, 2025
…e_fix' with updated timestamp and hash after successful run
@ekarabu ekarabu merged commit 2739cd5 into patch_ss_v1p0 Nov 18, 2025
7 checks passed
@ekarabu ekarabu deleted the user/ekarabulut/Vend_test_md_file_fix branch November 18, 2025 20:28
kgugala pushed a commit to antmicro/caliptra-ss that referenced this pull request Dec 12, 2025
chipsalliance#918)

* updated fuse mmap for vendor test partition

* MICROSOFT AUTOMATED PIPELINE: Stamp 'user/ekarabulut/Vend_test_md_file_fix' with updated timestamp and hash after successful run
kgugala pushed a commit to antmicro/caliptra-ss that referenced this pull request Dec 16, 2025
chipsalliance#918)

* updated fuse mmap for vendor test partition

* MICROSOFT AUTOMATED PIPELINE: Stamp 'user/ekarabulut/Vend_test_md_file_fix' with updated timestamp and hash after successful run
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants