Thursday, September 23, 2021

How to use Altium Layer Stack Planner for 8 Layer, 16 Layer PCBs


  • Layer stack planning guide
    • usual go to stackups
    • impedance profile
    • ask for the best layer stack from PCB house
  • Minimizing noises by choosing best layers stack-ups practices

  • Adding vias
    • set via settings - hole diameter/outer diameter/copper fill
    • adding vias between layers
    • name them 
    • set netlabels
    • set colors
    • bind vias/ defalut vias
    • impedance profile

Checklist for designed PCB before sending to PCB House




Check List Before Sending to PCB house

Follow this procedure before releasing files. Confirm every action with a date.

1) I confirm that PCB Project compiles with no errors [DAY-MONTH-YEAR]

2) I confirm that Update PCB Document no differences between Schematic and PCB [DAY-MONTH-YEAR]

3) I confirm that Impedance check track width/gap to match required impedance [DAY-MONTH-YEAR]

4) I confirm that Polygons have been repoured [DAY-MONTH-YEAR]

5) I confirm that Run Design Rule Check no errors [DAY-MONTH-YEAR]

6) I confirm that Gerber check visually checked Gerber files placed in \PCB Manufacturing\Gerber Output\ [DAY-MONTH-YEAR]

7) I confirm that I have Checked files placed in subdirectories [DAY-MONTH-YEAR]


Refrerance 

https://www.circuits.dk/electronics-design-checklist/



How to troubleshoot visual studio debugging

 


When debugging check the followings 

  • Debug can be done in release x64/ release_opt x64/debug x64 configuration does not matter as default configurations are used 

Method 1 Attach to process 

  • Check all dependencies are placed to exe working directory
    • .lib, .dll, PDB
  • Run the exe to be debug
  • Then go to the project to be debugged
  • Toolbar->debug-> attach to process-> select the exe
  • Set debug points in the code run local windows debugger

Method 2 - Set working directory in properties 

 

  • Make sure to put \ at the end of the working directory path 

When debug points are not hit check below 

This section provides information to troubleshoot issues when the debugger isn’t displaying any warnings – the breakpoint is a solid red circle while actively debugging, yet the breakpoint isn’t being hit. 
  • Disable optimization on debugging project and all relevant projects (DLLs, libs, exe) 

 

  • Check your project properties under Linker > Debugging > Generate Program Database File and Generate Debug Info. Be sure these two are set properly. 

 

  • Also, check if C/C++ > General > Debug Information Format is set to Program Database for Edit and Continue (/ZI) or something similar. 

 

  • Check your symbol file exists, ensure you have the right version of your symbol in the right place. 

Reference 

 

LeetCode C++ Cheat Sheet June

🎯 Core Patterns & Representative Questions 1. Arrays & Hashing Two Sum – hash map → O(n) Contains Duplicate , Product of A...