7100 - Propel Builder: Why is the Switch Verification and SOC Design icon greyed out and the Radiant/Diamond and Propel icons are missing?
When the default folder structure of the project is followed, user will be able to see all of the icons on Propel Builder Tool bar from the Switch Verification and SoC Design to the Propel SDK button.
There are two ways that this Switch Verification and SoC Design icon can be inactivated or greyed out.
1. No verification design/project on the verification folder: This icon is only activated or clickable when there is already a verification design (SBX file) created for the SoC design. This verification design is located in a verification folder.
The verification design typically has a *_v suffix on its design name.
Removing the whole verification folder or even just the verification design (in this case, Dual_Processor_Proj_v.sbx) inactivates or greys out the Switch Verification and SoC design buttons. Thus, the folder structure is very important for the tool to recognize the verification design.
To create a verification project, simply go to File-->New Design. Select the SoC Verification type for the project.
2. The .socproject file is not found in the project directory: .socproject is a file that ties an SoC project with a verification project. This file should be in the project directory and on the same level as the SoC project folder and verification project folder.
If the user has multiple projects in a single folder, this .socproject file will be overwritten, since the file name will be the same for all SoC projects.
Removing this file or putting it in another directory or folder, will replicate the issue. This will also remove the other icons (Radiant, Propel SDK, etc.).
Thus, the user must follow the folder structure to avoid this issue. In addition, users must have separate project folder per SoC project (SBX file) to avoid overwriting the .socproject file.
Related Articles
7230 - Lattice Propel: Why is my Propel Builder soft IP not available/missing in IP Catalog?
Description: Observing some soft IP version is not available to select in Propel Builder IP Catalog. Solution: This is an expected behavior. Lattice Propel Builder IP Server will only list out the specific compatible soft IP version. If you open an ...6223 - Propel: Why does Radiant not start when invoked via Propel Builder?
Kindly check in the Propel Builder tool settings if the Radiant software directory is already set. In Propel Builder, go to Designs>Options>Directories and set the Radiant location to <radiant install path>/lscc/radiant/<version>7133 - Propel Builder: Error (suppressible): xxx/lib/latticesemi.com/ip/cpu0/2.2.0/rtl/cpu0.sv(515): (vlog-2388) '<protected>' already declared in this scope (<protected>) at <protected>(<protected>).
Description: User may encounter cpu.v compilation error in Model Sim if directly run the Simulation Wizard from Radiant software for any RISC-V project. Solution: The correct method is to leverage the verification tool provided in Propel Builder to ...7053 - Propel: Why I unable to run debugger with Propel SDK on my RISC-V Project?
Description: 1. RISC-V reset vector is fixed at address 0x00000000, thus instruction memory must start at address 0x0. 2. RISC-V instruction port is a read only port. To run debugger with Propel SDK, the SoC design must support writes to the ...6898 - CertusPro-NX / Propel version 2022.1: Will there be an available GPIO IP with an AXI interface similar to what is observed on the CPNX FreeRTOS template design?
The GPIO with AXI interface on the CPNX FreeRTOS Template design is created initially for the template to test the AXI4 interconnect but it is not part of the available IPs. When a FreeRTOS template for AVANT devices, the user can see that the ...