Visible to Intel only — GUID: xsh1692193299334
Ixiasoft
4.4.1. Editing the Packaged Subsystem
4.4.2. Step 4a: Add Two Checkbox Controls
4.4.3. Step 4b: Enable or Disable Modules and Checkboxes
4.4.4. Step 4c: Run run_system_script
4.4.5. Step 4d: Iterate Over All Parameters
4.4.6. Step 4e: Setting DisplayPort IP Functionality
4.4.7. Step 4f: Make Packaged Subsystem Unlockable
4.4.8. Step 4g: Sync System Infos, Assign Base Addresses, and Save
Visible to Intel only — GUID: xsh1692193299334
Ixiasoft
3.1. User Personas for Packaged Subsystems
The packaged subsystem flow defines the following user personas and flows that this document describes in detail:
- Packaged subsystem author—the packaged subsystem author creates and saves the packaged subsystem .qcp file in Platform Designer. The packaged subsystem author defines the components, connections, parameters, and the external interfaces of the packaged subsystem. The packaged subsystem author can specify desired component parameters, and whether the packaged subsystem can be unlocked for modification, or just divable which allows the packaged subsystem user to dive in and view the internals of the packaged subsystem.
- Packaged subsystem user—the packaged subsystem user reuses the packaged subsystem by instantiating and connecting it to other components in another Platform Designer system. The packaged subsystem user may be able to modify the parameters or unlock the packaged subsystem for full editing control, depending on the packaged subsystem author specifications. The packaged subsystem author also determines whether the packaged subsystem is divable, which allows users to view the internals of the packaged subsystem.