BUG REPORT: 'Update PCB' fails for nested reuse block DTL_RS_FF_1.0 in EasyEDA Pro 2.2
Bug Report: High-Level Workflow Summary
Issue: In EasyEDA Pro 2.2 on Windows, a top-level reuse block (DTL_RS_FF_1.0) fails to maintain its pre-routed PCB layout when updated from the schematic to the PCB, instead "exploding" into individual components. A subordinate, single-level block (DTL_NOR_1.0) behaves correctly.
Files Available For This Report:
- This report in MSWord and PDF format with illustrations
- The files for the subject reuse blocks: DTLl_NOR_1.0.eprj and DTL_RS_FF_1.0 These are from the EasyEDA-Pro\libraries directory. They were the only blocks in my EasyEDA libraries at the time.
- The files for the subject test projects, BugReport_NestedReuseBlock_Test.eprj and BugReport_NestedReuseBlock_Failure.eprj . They were the only projects in my EasyEDA directories at the time.
Objective: To provide step-by-step, reproducible evidence using a clean project file to demonstrate the failure of the nested reuse block feature.
Step |
Description |
Documentation Method |
1 |
Environment Audit: Verify global and project-specific settings (grids, layers, units) in a pristine project setup to rule out configuration errors. |
Screenshots & Narrative |
2 |
Initial Setup Verification: Place a simple header component, sync to PCB, and place it to confirm basic tool functionality (Update PCB, synchronization, ground planes). |
Screenshots & Narrative |
3 |
Demonstrate Success Case: Place the working DTL_NOR_1.0 reuse block on the schematic, update PCB, and show the layout transfers correctly as a single unit. |
Screenshots & Narrative |
4 |
Demonstrate Failure Case: Place the failing DTL_RS_FF_1.0 reuse block on the schematic, update PCB, and show that only individual components appear, not the pre-routed layout. |
Screenshots & Narrative |
5 |
Conclude and Submit: Summarize the observed behavior, attach supporting files, and submit the report via the OSHWLab forum or email. |
Final Summary & File Attachments |
Initial Conditions: Before beginning the test case, a pristine environment was established. The user interface for EasyEDA Pro 2.2.43 (Half Offline mode) on Windows is shown below. The relevant reuse blocks, DTL_NOR_1.0 and DTL_RS_FF_1.0, are confirmed to be available in the local library view. The goal is to create a new, blank project to test the behavior of these blocks.

Figure 1 EasyEDA Pro 2.2 Start Page confirming library assets are available.
The New Project Dialog
Procedure: A new local project is being created via the 'File' -> 'New' -> 'Project' menu path. This ensures a clean slate, separate from any previous attempts or configurations in other projects.
Figure 2 Creating the new test project "BugReport_NestedReuseBlock_Test"
Result: The new project is successfully created and loaded. The interface confirms a blank Schematic1 and PCB1 are ready for documentation of the bug reproduction steps.
Figure 3 The main EasyEDA Pro interface immediately after creating the new, empty test project.
Procedure: To ensure standard design practices are used and rule out configuration errors, the global system preferences for Units/Grids were audited. The settings are configured to conventional sizes in both millimeters (mm) and thousandths of an inch (mil). A common snap size of 50.0 mil (1.270 mm) is selected for general PCB work.
Figure 4 Global 'Units/Grids' settings accessed via the 'E' menu -> Preferences.
Procedure: The properties for the local PCB1 project file were updated to match the conventional grid and snap settings previously audited in the global preferences. A bold, visible grid (dot type) was selected to improve clarity during the demonstration. These settings ensure a consistent and standard working environment for the PCB layout phase.
Figure 5 Local PCB properties showing consistent grid, snap, and display settings.
Prodedure: The desired physical boundary for the PCB was defined using the Design -> Board Outline tool. The resulting outline was selected to confirm its dimensions in the properties panel, ensuring the test area is appropriately sized for the components involved in the demonstration.
Figure 6 The defined board outline selected, showing dimensions in the Properties panel.
Procedure: The PCB was configured as a 4-layer board using the Design -> Layer Stack Manager. Inner layers 1 and 2 were correctly assigned as dedicated PlaneZone layers for GND and VCC respectively. This configuration is necessary to support the integrated vias within the subordinate reuse blocks.
Figure 7 Layer Stack Manager confirming the 4-layer VCC and GND plane configuration.
Demonstration Step 2: Initial Setup Verification:
Place a simple header component, sync to PCB, and place it to confirm basic tool functionality (Update PCB, synchronization, ground planes).
Procedure: A simple 2-pin header (J1) was placed on the schematic to act as a synchronization component for the VCC and GND nets established in the PCB layer manager. The nets were assigned to the respective pins using the Properties panel, linking the schematic symbol to the VCC and GND plane layers and assigning the correct PCB footprint.
Figure 8 Schematic view showing the placed 2-pin header with VCC and GND nets assigned in the Properties panel.
Procedure: The Design -> Update PCB command was issued from the schematic view. The 'Confirm Importing changes information' dialog correctly identifies that a new component (H1, the 2-pin header) needs to be added to the PCB. The option "Also update track's net" was left unchecked, as no existing nets were being renamed.
Figure 9 The 'Confirm Importing changes information' dialog confirming the addition of the new header component (H1).
Procedure:
The changes were applied successfully, and the header footprint (H1) was moved onto the board area. Selecting the component in the PCB view and auditing the Properties panel confirms that the VCC and GND nets were correctly transferred from the schematic. The visible ratsnest lines confirm connectivity to the defined power planes within the board outline. Basic functionality of the "Update PCB" process is verified.
Figure 10 The header component (H1) placed on the PCB, with properties confirming correct net assignments and footprint.
3 Demonstrate Success Case: Place the working DTL_NOR_1.0 reuse block on the schematic, update PCB, and show the layout transfers correctly as a single unit.
Procedure:
Place the DTL_NOR_1.0 reuse block symbol onto the main schematic canvas from the "Reuse Blocks" library tab. Mark all input and output pins of the placed symbol with "NC" (No Connection) indicators to ensure the schematic satisfies DRC without requiring immediate electrical connections. The schematic is now prepared for the subsequent step of updating the PCB.
Figure 11: DTL_NOR_1.0 Selected in Device/Reuse Block libraries
Next, Place Block Symbol and NC connections:
Figure 12: DTL_NOR_1.0 placed and ready for PCB update
Procedure:
The PCB was updated and the imported layout was examined.
With the schematic correctly configured and saved, the "Update PCB" button (located in the top toolbar) was selected, switching the view to the PCB document.
A dialog window titled "Update PCB" or "Import Changes" appeared, displaying a list of synchronization actions. This list indicated that the components within the DTL_NOR_1.0 reuse block were being added. “Also update track’s net” was deselected. All actions were ensured to be selected, and the update process was confirmed.
A second dialog, "Update successfully," confirmed the synchronization was complete. This dialog was then closed.
Figure 13: Import Changes From Schematic dialog
The layout area was observed; the components, associated traces, vias, and silkscreen from the DTL_NOR_1.0 reuse block were present, imported as a single, grouped entity near the board outline and header. This area was examined closely to verify that the imported layout correctly incorporated all design elements as a cohesive unit. The parts, traces, silkscreen and vias are all intact and move as a unit. The nets between the header and the block, and the traces in the block are intact. This is the desired and expected behavior.
Figure 14: Correct result of adding DTL_NOR_1.0 reuse block
Step 4: Demonstrate Failure Case:
Procedure: Place the failing DTL_RS_FF_1.0 reuse block on the schematic, update PCB, and show that only individual components appear, not the pre-routed layout.
First Steps 1 and 2 were repeated to create a new, pristine test project. It was be named BugReport_NestedReuseBlock_Failure. At that moment, the prior Bug_Report_NestedReuseBlock_Test was be saved and closed for inclusion in the report
Figure 15: BugReport_NestedReuseBlock_Failure project setup
Procedure: Place the failing DTL_RS_FF_1.0 reuse block symbol on the schematic.
The DTL_RS_FF_1.0 was located using the Component tool. The Device/Reuse Block dialog was used to select the DTL_RS_FF_1.0 reuse block.
Figure 16: Selecting the failing DTL_RS_FF_1.0 reuse block
The Block symbol was placed in the schematic.
To prepare the schematic for the PCB update without making immediate connections, "NC" (No Connection) indicators were placed on all input and output pins of the DTL_RS_FF_1.0 symbol to satisfy Design Rule Checks (DRC). There were expected warnings about pins that had only one connection. That is expected when building up a design from blocks when not all components are present yet.
The schematic was saved, and the Update/Convert Schematic to PCB operation was performed, with “Also update track’s net” deselected. There were no tracks before this operation.
Figure 17: Update dialog that was applied
When the update was applied, disarranged parts were added to the PCB. The traces, silkscreen and vias were not brought over. The expected behavior was that the PCB layout of DTL_RS_FF_1.0 would be preserved, but it was not.
Figure 18: The result of a failed PCB conversion of DTL_RS_FF_1.0
Procedure: Attempt "Update Place And Route from Template" to recover the layout.
With the unrouted, exploded components from the DTL_RS_FF_1.0 reuse block visible on the PCB canvas, navigate to the "Update Place And Route from Template" function within the EasyEDA Pro interface. Select the corresponding DTL_RS_FF_1.0 template from the available options. Select the sole instance of DTL_RS_FF_1.0$1e175 in the dialog. Perform the command and observe the resulting behavior to determine if this function can correctly force the reassembly and routing of the layout where the standard "Update PCB" process failed.
Figure 19: Ready to try Update Place and Route from Template, with parts selected.
Figure 20: Ready to attempt the Update Place and Route from Reuse Template
Result: Update Place and Route from Reuse Template had no effect:
Figure 21: Update Place and Route from Reuse Template had no effect.
Step 5. Conclude and submit
Summarize the observed behavior, attach supporting files, and submit the report via the OSHWLab forum or email.
Summary of Observed Behavior:
The test project BugReport_NestedReuseBlock_Test demonstrated a significant inconsistency in how EasyEDA Pro 2.2 handles different reuse blocks during the "Update PCB" process.
In the "Demonstrate Success Case" (Step 3), the simple DTL_NOR_1.0 reuse block was added to the schematic and successfully imported into the PCB layout. The process correctly grouped the components and preserved the pre-routed traces, vias, and silkscreen as a single cohesive unit, which was the expected behavior.
In the "Demonstrate Failure Case" (Step 4), the more complex DTL_RS_FF_1.0 reuse block was introduced using an identical procedure in a pristine project environment. The standard "Update PCB" function failed to import the layout information. Instead, only the individual, unplaced, and unrouted components appeared on the PCB canvas.
A subsequent attempt to manually force the layout using the "Update Place And Route from Template" function was performed. This operation had no observable effect; the components remained unplaced and unrouted.
The results indicate that the standard "Update PCB" mechanism inconsistently fails to incorporate the layout data for certain, potentially more complex, reuse blocks in EasyEDA Pro 2.2 on Windows.
End of report.
#PCB#
Sign In Or Register Comment after
No comments yet. Be the first to comment!