(no commit message)

[libreriscv.git] / 22nm_PowerPI.mdwn

diff --git a/22nm_PowerPI.mdwn b/22nm_PowerPI.mdwn
index 35725cbbb3c0fa3c82b720132c3cc22b93caf49a..c479bf11d408ed7654e73ac74c37ad98277bc659 100644 (file)
--- a/22nm_PowerPI.mdwn
+++ b/22nm_PowerPI.mdwn
@@ -25,7 +25,7 @@ in the Silicon Industry.
 
 * Basic "Pi" style SBC role (aka POWER-Pi)
   - Power consumption to be **strictly** limited to under 3.5 watts
-    so as to be passively-cooled and significantly reduce product costs,
+    so as to be passively-cooled and significantly reduce OEM product costs,
     as well as increase reliability
 * Libre-style smartphone, tablet, netbook and chromebook products
   - Pine64, Purism, FairPhone, many others
@@ -44,7 +44,7 @@ up to 12-14 different products.
 **Three different pin packages:**
 
 * 400-450 pin FBGA 18mm 0.8mm and 14mm 0.6mm pitch
-  - single 32-bit DDR3/4 interface.
+  - single 32-bit DDR3/4 interface (appx 120 pins incl. VSS/VDD)
   - Suitable for smaller products.
   - 0.8mm pitch is easier for low-cost China PCB manufacturing
   - This lesson is learned from Freescale's 19-year-LTS iMX6 SoC
@@ -102,7 +102,7 @@ NREs are still required**
 
 # Functionality
 
- - 4 Core dual-issue LibreSOC OpenPOWER CPU
+ - 4 Core SMP dual-issue LibreSOC OpenPOWER CPU
  - SimpleV Capability with VPU and GPU Instructions *no need for separate GPU*
  - IOMMU
  - PCIe Host Controller
@@ -120,7 +120,7 @@ NREs are still required**
 
 # Interfaces
 
-Much of the advanced section is "under consideration" because there are proprietary firmware issues involved as well as high power consumption and high costs involved.  OpenCAPI for example would, in 22nm, at 25 ghz, be an enourmous power draw (IBM used 14nm for the POWER9 25ghz SERDES)
+Much of the advanced section is "under consideration" because there are proprietary firmware issues involved as well as high power consumption and high costs involved.  OpenCAPI for example would, in 22nm, at 25 ghz, be an enormous power draw (IBM used 14nm for the POWER9 25ghz SERDES)
 
 HDCP is present in HDMI, as well as being optional in eDP and by extension USB-C as well.  Licensing of any of these Controllers therefore introduces the risk of closed firmware which will be viewed unfavourably by the educational markets, libre/open supporters and advocates, as well as cause Customer Support issues and introduce security vulnerabilities that *cannot be fixed or evaluated*.
 
@@ -138,13 +138,14 @@ with [USB3300 PHY](https://www.microchip.com/wwwproducts/en/USB3300#datasheet-to
 
 ## Basic
 
- - [OpenFSI](https://openpowerfoundation.org/?resource_lib=field-replaceable-unit-fru-service-interface-fsi-openfsi-specification) instead of JTAG
+ - [OpenFSI](https://openpowerfoundation.org/?resource_lib=field-replaceable-unit-fru-service-interface-fsi-openfsi-specification) instead of / as well as JTAG
   - [Raptor HDL](https://gitlab.raptorengineering.com/raptor-engineering-public/lpc-spi-bridge-fpga)
   - [Raptor Libsigrok](https://gitlab.raptorengineering.com/raptor-engineering-public/dsview/-/tree/master/libsigrokdecode4DSL/decoders/fsi)
 
 These should be easily doable with LiteX.
 
 * [[shakti/m_class/UART]]
+* [[shakti/m_class/JTAG]]
 * [[shakti/m_class/I2C]]
 * [[shakti/m_class/GPIO]]
 * [[shakti/m_class/SPI]]