Silicon Prawn

User Tools

Site Tools

Trace: • mcmaster
mcmaster:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
mcmaster:start [2022/05/25 16:06] – [Table] mcmastermcmaster:start [2025/08/04 21:23] (current) – external edit 127.0.0.1
Line 17: Line 17:
  
 Relevant equipment list: Relevant equipment list:
-  * pr0nscope: CNC microscope.  Typically BF imaging, but also have DF, polarized, DIC+  * prawnscope: CNC microscope.  Typically BF imaging, but also have DF, polarized, DIC
   * k2scope: K2 IND CNC confocal microscope   * k2scope: K2 IND CNC confocal microscope
   * brainscope: laser microscope / probe station.  532 nm, 355 nm Nd:YAG   * brainscope: laser microscope / probe station.  532 nm, 355 nm Nd:YAG
Line 47: Line 47:
     * Decapping involves harsh chemicals, direct expenses, high NRE, and time so contributions are greatly appreciated     * Decapping involves harsh chemicals, direct expenses, high NRE, and time so contributions are greatly appreciated
   * Any potential legal issues associated with the chip?   * Any potential legal issues associated with the chip?
-    * Ex: DRM, crypto+    * If so, it will be evaluated on a case by case basis 
 +    * Ex: DRM, crypto can be problematic
     * Ex: a typical sound chip or microcontroller is not an issue     * Ex: a typical sound chip or microcontroller is not an issue
 +    * I will not work on: satellite, cable TV
   * Clearly identify the chips, especially if you are sending more than one   * Clearly identify the chips, especially if you are sending more than one
     * Ex: specify "344S0061-A" instead of"SWIM", since that's what's printed on it     * Ex: specify "344S0061-A" instead of"SWIM", since that's what's printed on it
Line 59: Line 61:
   * Do you have a particular timeline in mind?   * Do you have a particular timeline in mind?
     * Coordinate with me for best results     * Coordinate with me for best results
-  * By default I retain copyright and publish work CC BY on siliconpr0n.org+  * By default I retain copyright and publish work CC BY on siliconprawn.org
  
 In short, I focus on chips that are of interest to me.  I do lots of chips for others, but I give priority to people that are able to provide funds. This section is written with open source projects as the main audience, but note I also offer services through my embedded security consulting service. In short, I focus on chips that are of interest to me.  I do lots of chips for others, but I give priority to people that are able to provide funds. This section is written with open source projects as the main audience, but note I also offer services through my embedded security consulting service.
Line 67: Line 69:
 Delayering is typically more risky to the chip and myself (toxic chemicals like hydrofluoric acid). Similar issues with staining and lapping.  Lapping is currently extremely labor intensive and not very well refined (although I can get a small area easily). Delayering is typically more risky to the chip and myself (toxic chemicals like hydrofluoric acid). Similar issues with staining and lapping.  Lapping is currently extremely labor intensive and not very well refined (although I can get a small area easily).
  
-I prefer to focus on chips that I can (eventually) release on siliconpr0n.org, ideally under CC licenses.+I prefer to focus on chips that I can (eventually) release on siliconprawn.org, ideally under CC licenses.
  
 In general I want to focus on R&D / labwork and not hand digitization.  I do have some limited semi-automatic digitization capabilities for planarized chips though that I'd like to develop (ex: works on PS1 chipset). In general I want to focus on R&D / labwork and not hand digitization.  I do have some limited semi-automatic digitization capabilities for planarized chips though that I'd like to develop (ex: works on PS1 chipset).
  
-Most of this is targeted towards small chips up to the mid 90's.  If the die is obnoxiously large (ex: 486 CPU) it will be difficult for me to photograph and stitch the entire thing.  Similarly most of my equipment is targeted towards larger processes (say 180+nm), although I do have a small SEM if required. See [[https://siliconpr0n.org/map/xilinx/xc2c32a/lap4-04_mit20x/|XC2C32A]] for an example 180 nm chip taken with a relatively low power objective, noting in theory I can get about 11x the detail (NA 0.42 => 1.4).+Most of this is targeted towards small chips up to the mid 90's.  If the die is obnoxiously large (ex: 486 CPU) it will be difficult for me to photograph and stitch the entire thing.  Similarly most of my equipment is targeted towards larger processes (say 180+nm), although I do have a small SEM if required. See [[https://siliconprawn.org/map/xilinx/xc2c32a/mcmaster_lap4-04_mit20x/|XC2C32A]] for an example 180 nm chip taken with a relatively low power objective, noting in theory I can get about 11x the detail (NA 0.42 => 1.4).
  
 Other: most of the work is in decapping, not actual imaging. If you happen to already have a bare, clean die and would be satisfied with a quick / lower quality scan, feel free to send me a few dies. This also can work out well since most of the NRE cost is in the microscope, not the decapping supplies. Other: most of the work is in decapping, not actual imaging. If you happen to already have a bare, clean die and would be satisfied with a quick / lower quality scan, feel free to send me a few dies. This also can work out well since most of the NRE cost is in the microscope, not the decapping supplies.
Line 101: Line 103:
  
 ^ Scope      ^ Objective  ^ NA  ^ Resolving power (nm)  ^ Camera  ^ nm / pix  ^ Notes               ^ ^ Scope      ^ Objective  ^ NA  ^ Resolving power (nm)  ^ Camera  ^ nm / pix  ^ Notes               ^
-| pr0nscope  | mit2x      |     | 5000                  | MU800   | 3550      |                     | +| prawnscope  | mit2x      |     | 5000                  | MU800   | 3550      |                     | 
-| pr0nscope  | mit5x      |     | 2000                  | MU800   | 1420      |                     | +| prawnscope  | mit5x      |     | 2000                  | MU800   | 1420      |                     | 
-| pr0nscope  | mit10x     |     | 1000                  | MU800   | 710       |                     | +| prawnscope  | mit10x     |     | 1000                  | MU800   | 710       |                     | 
-| pr0nscope  | mit20x     |     | 700                   | MU800   | 355       |                     |+| prawnscope  | mit20x     |     | 700                   | MU800   | 355       |                     |
 |            | mit20x2    |     |                       | 20MP    |           | New camera setup    | |            | mit20x2    |     |                       | 20MP    |           | New camera setup    |
-| pr0nscope  | ns50xu     |     |                       | MU800   | 142?      |                     | +| prawnscope  | ns50xu     |     |                       | MU800   | 142?      |                     | 
-| pr0nscope  | nd50x      |     |                       | MU800   | 142?      |                     | +| prawnscope  | nd50x      |     |                       | MU800   | 142?      |                     | 
-| pr0nscope  | mit50xn    |     | 700                   | MU800   | 142       |                     | +| prawnscope  | mit50xn    |     | 700                   | MU800   | 142       |                     | 
-| pr0nscope  | mit100x    |     | 400                   | MU800   | 71        | FIXME: correct NA?  |+| prawnscope  | mit100x    |     | 400                   | MU800   | 71        | FIXME: correct NA?  |
  
  
mcmaster/start.1653494793.txt.gz · Last modified: 2022/05/25 16:06 by mcmaster