total for SU
[libreriscv.git] / SEP-210803722-Libre-SOC-8-core.mdwn
1 
2 # SEP-210803722 Libre-SOC 8 core
3
4 List of participants
5
6
7 |Part# |Contact |Participant Name |Country |Short Name |
8 |----- |------------- |--------------------- |--------- |------------- |
9 | 1 |David Calderwood |RED Semiconductor Ltd |UK |1/RED |
10 | 2 |Luke Leighton |The Libre-SOC Project |Netherlands |2/Libre-SOC |
11 | 3 |Céline Ghibaudo |Sorbonne Université (LIP6 Lab) |France |3/SU |
12 | 4 |Céline Ghibaudo |Sorbonne Université (CNRS Lab) |France |4/CNRS |
13 | 5 |Michiel Lenaars |NLnet |Netherlands |5/NLnet |
14 | 6 |James Lewis |Helix Technology Ltd |UK |6/Helix |
15
16
17 Please note: CNRS is an "Affiliated Entity" of Sorbonne Université
18
19
20 # 1 Excellence
21
22
23 ## 1.1 Objectives and ambition
24
25
26 Throughout this Grant Proposal, you will note that we are making
27 significant use of ideas from the early days of Computing. Due to
28 the limitations of physical technology at that time, these ideas were
29 categorised into "technology that was beyond delivery". Industry-standard
30 computing from then to today missed many of those opportunities and
31 has consequently ploughed narrow "technological ruts" in an incremental
32 fashion that has detrimentally impacted and constrained all world-wide
33 Computing end-users as a result. Modern hardware technology performance
34 is now allowing us to revisit the best of the "Sea of ideas" from the
35 history of the past 60 years of computing. Our Grant Application is
36 therefore based on firm, practical proven foundations, backed up by a
37 real-world customer requirement: Advanced high-accuracy GPS Sensor-Fusion,
38 to prove the core's capabilities and energy efficiency.
39
40
41 We have chosen to evolve core technology to develop a Next-Generation
42 Supercomputer-scale Microprocessor family based on an existing
43 2-decades-proven base (the Power ISA), with Advanced Cray-style Vectors,
44 providing energy-efficient advanced computational power by a unique
45 methodology not currently being achieved by any current general-purpose
46 computing device. We have been working on this strategy for over three
47 years and our grant application is now evolutionary but was revolutionary.
48
49
50 Libre-SOC has, for over three years, been backed by EU Funding through
51 NLnet and now NGI POINTER, and at the core of our work we have been
52 developing a novel Draft Vector ISA Extension to the OpenPOWER ISA,
53 called SVP64. https://libre-soc.org/openpower/sv/svp64/ and an enhanced
54 processor core architecture on which it will run.
55
56
57 As an aside we must acknowledge the research work of IBM labs who designed
58 and then Open-Licensed their Power ISA: the foundation on which we have
59 been building. Standing on the shoulders of greatness is never a bad
60 place to start.
61
62
63 SVP64 contains features and capabilities never seen in any Instruction
64 Set Architecture (ISA) of the past sixty years. With NLnet's help we have
65 TRL (3) implementations and simulations demonstrating a 75% reduction in
66 the program size of core algorithms for Video and Audio DSP Processing
67 (FFT, DCT, Matrix Multiply), and these still need optimized, which if
68 successfully expanded to general-purpose algorithms would result in huge
69 power savings if deployed in mass-volume end-user products.
70
71
72 Why we are leveraging the Power ISA as the fundamental basis instead of
73 "completely novel non-standard computing architecture" requires some
74 explanation, best illustrated by reference to other historic high
75 capability designs. Aspex Microelectronics ASP was a 4096-wide SIMD
76 Array of 2-bit processors. It could be programmed at a rate of one
77 instruction per 5-10 days. Elixent also had a similar 2D Grid Array of
78 4-bit processors. Both were ultra-power-efficient (2 orders of magnitude
79 for certain specialist tasks) but were impossible to program even for the
80 best programming minds and required critical assistance from a severely
81 limited pool of specialists for best exploitation. The Industry-standard
82 rate for general-purpose High-Level programming (C, C++) is around 150
83 lines of code per day, not 5-10 days per line of assembler. We seek to
84 deliver a much more accessible "general-purpose" Microprocessor that
85 contains Supercomputing elements and consequently stands a much more
86 realistic chance of general world-wide adoption (including Europe).
87
88
89 An additional insight: OpenRISC 1200 took 12 years to reach maturity.
90 The team developed the entire processor architecture, low-level software
91 and compiler technology, entirely from scratch. We considered this
92 approach and, due to the long timescales, rejected it, choosing
93 instead to leverage and be compatible with a pre-existing Open ISA:
94 OpenPOWER. We also considered RISC-V however it turns out to be too
95 simplistic (https://news.ycombinator.com/item?id=24459041) and it is
96 far too late to retrospectively add Supercomputer-grade power-efficient
97 functionality to its design or instruction set. With the IBM-inspired
98 Power ISA already being a Supercomputer-grade ISA, it is a natural fit for
99 an energy-efficient Cray-style Vector upgrade, and comes with 25 years
100 of pre-existing software, libraries, compilers and customers. By being
101 backwards-compatible with the existing Power ISA 3.0 (which is now an
102 Open ISA managed by the OpenPOWER Foundation), European businesses will
103 benefit from that pre-existing decades-established stability and pedigree.
104
105
106 As hinted at, above: Great hardware is nothing without the corresponding
107 compiler technology and support libraries. Consequently we need to engage
108 with Compiler Service Companies (Embecosm Gmbh, Vrull.eu) to evaluate the
109 feasibility of adding Vectorisation support to gcc, llvm and low-level
110 standard libraries. Whilst Libre-SOC has already demonstrated TRL (3)
111 successful assembly-level SVP64 algorithms (MP3 CODEC in particular),
112 assembler is far too low-level for general-purpose compute. C, C++
113 and other programming language support is required to be evaluated
114 and developed. Also given that the Libre-SOC Core is being long-term
115 designed for energy-efficient 3D GPU and Video Processing workloads,
116 two 3D Vulkan Drivers (Kazan and MESA3D) need to be taken beyond
117 proof-of-concept (TRL 2/3).
118
119
120 We consider it strategically critical to develop processors in an entirely
121 transparent fashion. The current Silicon Industry chooses secrecy to mask
122 technology shortcuts and restrictive cross licencing, which inevitably and
123 systematically fails to provide trustable hardware: Intel's Management
124 Engine; Qualcomm making 40% of the world's smartphones vulnerable to
125 hacking; Apple drive-by Zero-day Wireless exploits; Super-Micro being
126 delisted from NASDAQ for failing to be able to prove the provenance of
127 all hardware and software components. We consider Libre / Open Hardware
128 ASICs and the full Libre/Open VLSI toolchain itself to be fundamental
129 to end-user trust and security as well as Digital Sovereignty.
130
131
132 In addition to this, Libre-SOC has already been developing Mathematical
133 Formal Correctness Proofs for the HDL of its early prototype designs,
134 which, in combination with unrestricted access to the HDL Source Code,
135 allow third parties including customers to perform their own verification
136 of the ASIC's purpose (as opposed to the customer having to trust a
137 manufacture that inherently has a direct conflict-of-interest in the form
138 of its Shareholders and profits). Furthermore, we aim to experiment with
139 built-in "tamper-checking" circuits that, on running a test programme on
140 our evaluation test bed, will provide an Electro-Magnetic "signature".
141 By publishing this "signature" and the test programs, customers can
142 verify that their purchased ASICs have the same EMF "signature" and can
143 detect immediately if the ASIC has been tampered with. In addition we
144 will continue existing (TRL 2) research into Hardware-level Speculative
145 Execution mitigation techniques. We feel that the full combination of
146 these objectives meets the Hardware Security requirements of this Call.
147
148
149 This strategy does not end with just the HDL: thanks (again) to NLnet
150 we have been collaborating already with Chips4Makers, LIP6 and CNRS
151 (all funded by EU Grants), to advance the state-of-the-art for European
152 VLSI Tool Technology, which is important to European Silicon Sovereignty.
153
154
155 https://www.europarl.europa.eu/RegData/etudes/BRIE/2020/651992/EPRS_BRI(2020)651992_EN.pdf
156
157
158 We are however significantly concerned that the LIP6 Department, as
159 an Academic body, is inevitably underfunded, particularly when it is the
160 sole provider of Libre/Open VLSI Silicon-proven software in the whole
161 of Europe. This is why we have included an Engineering Supplement for
162 LIP6 and CNRS in the Libre-SOC budget, to contract engineering support
163 for them and to avoid employment complications due to the French Civil
164 Service Regulations, which lack the flexibility needed. These engineers,
165 who are in high demand, will work for Libre-SOC/RED Semiconductor Ltd
166 but be fully available to assist in the development work covered by the
167 grant being done by LIP6 and CNRS.
168
169
170 The consequential effect of this tool development will be to help
171 create VLSI tools that can be directly substituted for the existing
172 commercial (and geopolitically constrained) tools from companies such as
173 Cadence and Mentor, giving a Euro-centric independence from “technology
174 constraining” acts.
175
176
177 We are currently awaiting the return of our first 180 nm architecture
178 test ASIC (TRL 4) from TSMC, through IMEC. It is the first major
179 silicon in Europe of its size (5.1 x 5.9 mm^2 and 130,000 cells)
180 to be entirely developed using a Libre-Licensed VLSI ASIC toolchain,
181 and the world's first Power ISA 3.0 outside of IBM to reach Silicon in
182 over 12 years. We have already started to push (drive) the evolution of
183 Europe's only silicon-proven Libre/Open VLSI toolchain, something this
184 Grant application will support and will allow LIP6 and CNRS to enhance
185 it to lower geometries and larger ASIC sizes which will be critical to
186 European businesses' Digital and Silicon Sovereignty.
187
188 For the avoidance of confusion the use of the word "Cell" refers to a
189 bounded piece of electronic design that when used together, like bricks,
190 form larger more complicated electrical functions.
191
192 To help advance Digital Sovereignty, LIP6 and CNRS need to once
193 again push the boundaries of the Libre/Open VLSI toolchain, coriolis2
194 Place-and-Route, https://coriolis2.lip6.fr and HITAS/YAGLE Static Timing
195 Analyser https://www-soc.lip6.fr/equipe-cian/logiciels/tasyagle/ both
196 of which are, at the lower 360 and 180 nm geometries, at TRL 9, but are
197 at TRL 2 for lower geometries 90, 65, 45 nm and below.
198
199
200 Chips4Makers (also NLnet funded) created FlexLib Libre/Open Cell
201 Libraries which allows porting of Standard Cell Libraries to any geometry.
202 An NDA'd TSMC 180nm version of FlexLib was created for the Libre-SOC
203 180nm test ASIC. To achieve our objectives, LIP6 and CNRS will need to
204 create smaller geometry ports of FlexLib. These Cell Libraries need to
205 be tested in actual Silicon, and consequently we will be working with
206 IMEC as a sub-contractor and partner to deliver MPW Shuttle Runs for
207 these critical Libraries, using Libre-SOC Cores as a "proving-ground".
208
209 https://europractice-ic.com/wp-content/uploads/2021/01/Pricelist-EUROPRACTICE-General-MPW_8.pdf
210
211
212 In addition, NLnet, a Stichting / Foundation, has been so successful
213 in supporting "Works for the Public Good" that we feel that their approach
214 and service fulfilment are extremely relevant to this Call. During the
215 36 month duration of the proposal, NLnet is in a position to engage
216 with Libre/Open Hardware and Software developers which, for our team,
217 will mitigate the risk of unanticipated issues requiring specialist but
218 small-scope funding, that yet still meets the well-defined objectives
219 of this Call.
220
221 To put all of this to practical use, Helix Technologies, by defining
222 an advanced GPS Correlator, will set a Computational capability objective
223 for the core technology and be a Reference test-bed. Helix will then
224 be able to carry out the comparative studies which show that the core
225 technology meets significant performance/watt improvements. The ultimate
226 destination for some of these devices will be Satellites (Space).
227
228 Helix Technologies biography:
229
230 Helix develops antennas and electronic systems for PNT (Position,
231 Navigation, Timing) applications. Markets include defence/security,
232 asset tracking, autonomous systems/vehicles/drones/robotics, critical
233 infrastructure (network sync – 5G, V2X, etc), fintech (blockchain
234 timestamping) and many other industrial applications.
235
236 Helix solutions defend against the vulnerabilities and threats to
237 global dependency on GNSS (Global Navigation Satellite Systems), where
238 disruption to services would cost the world’s major economies £10s
239 of Billions every single day. Our patented technology enables filtering
240 antennas to mitigate multi-path, RF and electrical interference and
241 reduce the impact of jamming and spoofing, meaning that the receiver
242 electronics becomes a streamlined high performance, low-power/low-cost
243 correlator/processor to deliver highly accurate and resilience x,y,z
244 and time data as its output. We are developing sophisticated anti-
245 jamming/spoofing hardware that uses targeted nulling to ignore jamming,
246 and enable system-level resilience. This capability can be co-designed
247 with the receiver chipset for ultimate resilience.
248
249 Summary of why our work is pertinent to Call HORIZON-CL4-2021-DIGITAL-EMERGING-01-01:
250
251
252 * High-performance energy-efficient computing: SVP64 is a Cray-style Vector ISA. Cray-style Vector ISAs are known to produce smaller and more compact programs. Smaller programs means less L1 Cache misses, and overall, smaller L1 Caches are needed. This results inherently in greatly-reduced power consumption, whilst also remaining practical and general-purpose programmable.
253 * Targeted applications: We are developing a general-purpose Hybrid Architecture suitable for 3D, Video, Digital Signal Processing, Cryptographic applications, AI and many more. As it is general-purpose it covers all these areas. However in certain areas "specialist" instructions are needed (particularly 3D) and we seek additional funding to complete them. This includes Helix's high-accuracy GPS application which qualifies as a step-improvement in "Sensor fusion".
254 * Hardware-software co-design and Libre/Open Hardware-Software: as all participants are trained as Software Engineers, we inherently and automatically bring Software Engineering practices and techniques to Hardware design, and consequently achieve a far greater effectiveness and flexibility. Additionally, all participants are long-term contributors to Libre/Open Software and Hardware Projects. This shall continue throughout this Grant proposal. The involvement of RED Semiconductor Ltd brings further semiconductor hardware experience, bringing balance to the overall team.
255 * Moore's Law and changing Economics: as a general-purpose Cray-style Vector Supercomputer ISA, what we are designing may deploy either "Fast and Narrow" back-end (internal) micro-architecture, or "Slow and Wide": huge numbers of SIMD ALUs running at a much slower clock rate. The beauty and elegance of a Vector ISA is that, unlike SIMD ISAs such as AVX-512, NEON and to a partial extend SVE2, is that the programmer doesn't need to know about the internal micro-architecture, but their programs achieve the same throughput, even on larger geometries.
256 * Hardware-based security: We consider it deeply unwise to follow the false practice of "adding more complexity to achieve more security". Security is achieved through simplicity and transparency. Simplicity: we studied historic Supercomputer designs dating back to 1965 (CDC 6600) where pure pragmatism required simpler and more elegant designs. Transparency: Fully Libre/Open designs that customers can themselves verify by running Formal Correctness Proofs (where those tools are also Libre/Open Source). Fully Libre/Open VLSI toolchains and Cell Libraries (no possibility of insertion of spying at the Silicon level). "Tripwires" embedded into the silicon to gauge area-local EMF "Signatures". Additionally, we already have work underway into Out-of-Order Execution and seek to explore Speculative Execution Mitigation techniques at the hardware level, to increase security. These are practical achievable demonstrable ways to achieve Hardware-based trust.
257 * Security and Safety-critical Guidelines: Due to our overall approach, although potentially inherently achievable by others utilising our work as the basis for ongoing Research, the main participants consider it out of scope due to practical time constraints. Security Certification typically takes 5 to 7 years: The scope of this project is only 3. NLnet however may fund work that does indeed take into account these criteria.
258 * ASIC (Chip) prototyping: We are developing RTL including High-Level (core designs) as well as Low-Level (Cell Libraries). Nobody in any European Company will use a Cell Library if it has not been demonstrated as Silicon-Proven. As we already did with the 180nm ASIC, the best way to prove that a Cell Library (and an innovative approach - using Libre/Open VLSI toolchains) works is to do an actual ASIC.
259
260
261 Additional notes:
262
263
264 1. With regard to "Improve by two orders of magnitude the performance/watt for targeted Edge Applications", subject to Moore's Law and other limitations, such as geometry of devices we are moving in this direction, and whether we can achieve it will be subject to the available manufacturing processes we can afford during the scope of this Grant. We have already achieved one magnitude of improvement in simulation (TRL 3) of FFT, DCT and other DSP calculations. As already indicated above, the output of our design can be run on many different geometries of significantly-different performances.
265 2. You will note that a significant number of our technology collaborators and the technology and services that we rely on are already funded by EU Grants. Through RED Semiconductor Ltd, we are going to be the conduit to commercial realisation of value for this investment, with subsequent commercial benefits of employment and tax revenues across the EU. We know not to lose sight of the fact all EU funding is fundamentally focused on future commercial success.
266
267 Grant numbers:
268
269 * Fed4Fire.eu Grant Agreement No: 732638
270 * NLnet Grant Agreements No: 825310 and 825322
271 * NGI-POINTER. Grant agreement No: 871528
272 * StandICT.eu Grant agreement No: 951972.
273 * Sorbonne Université: 163 FP7 projects and 195 H2020 projects
274
275
276 ## 1.2 Methodology
277
278
279 * Everything that Libre-SOC does is published as Libre/Open Information at https://libre-soc.org/ - source code (https://git.libre-soc.org) is open and available under the LGPLv3+ License and other appropriate Libre/Open Licenses.
280 * LIP6 likewise discloses all source code at https://gitlab.lip6.fr/vlsi-eda
281 * LIP6's toolkit containing existing large-geometry Cell Libraries and test benches at https://gitlab.lip6.fr/vlsi-eda/alliance-check-toolkit.
282 * CNRS's HITAS/YAGLE is also Open Source https://www-soc.lip6.fr/equipe-cian/logiciels/tasyagle/.
283 * Symbiyosys and its subcomponents for Formal Correctness Proofs are Libre/Open https://symbiyosys.readthedocs.io/.
284 * GPS GNSS-SDR is also Open Source https://gnss-sdr.org/ and can be adapted for Helix's requirement
285 * Chips4Makers FlexLib is also Open Source https://gitlab.com/Chips4Makers but the NDA'd "ports" are not.
286 * To solve the above problem, all Libre/Open Developers will work with an Academic "Ghost" version, called C4M-FreePDK45 https://gitlab.com/Chips4Makers/c4m-pdk-freepdk45. This "ghost" version will allow full (parallel-track) collaboration between Libre/Open Developers and those Participants creating "real" GDS-II Files, without violating Foundry NDAs.
287
288
289 This methodology is based on an established process that has already
290 allowed us to deliver demonstrable software and hardware results,
291 the manifestation of which is our 180nm architecture test chip now
292 in manufacture. This has involved a significant amount of cooperative
293 development among the applicants, and others beyond, and the development
294 of core supporting technology that this grant application can now
295 efficiently build upon.
296
297
298 We refer to other supporting technology sources further in this
299 application and whilst they are not the core team they will critically
300 contribute to the overall success. In particular, these groups can be
301 supported by NLnet, whose "Works for the Public Good" remit is 100%
302 compatible with the full transparency objectives (that the project's
303 participants are already committed to) which will help by providing
304 additional non-core-team development on an on-demand basis, on the back
305 of NLnet's already-trusted commitment to fulfil European Union objectives
306 under Grant Agreements No 825310 and 825322.
307
308
309 Additionally, Libre-SOC is working closely with the OpenPOWER Foundation
310 ISA Working Group Chair, having attended regular bi-weekly meetings for
311 over 18 months. As mentioned above, the entirety of our work of greater
312 than 3 years on this Vector Extension, SVP64, is entirely transparent
313 and open: https://libre-soc.org/openpower/sv/svp64/. Both NLnet
314 (and StandICT.eu through a proposal under consideration at the time of
315 writing) are supporting our efforts to submit the Draft SVP64 and its
316 subcomponents through the RFC (Request for Change) process being developed
317 by the OpenPOWER Foundation. For long-term stability and impact it is a
318 necessary prerequisite that Draft SVP64 become an official part of the
319 Power ISA: this decision is however down to the OpenPOWER Foundation
320 and requires considerable preparation and planning, which this Grant
321 will help support.
322
323
324 One huge benefit of Libre-SOC's core being Power ISA 3.0 Compliant is that
325 IBM contributed a huge patent pool through the OpenPOWER EULA. Compliant
326 Designs enjoy the protection of this patent pool. By contributing SVP64
327 to the Power ISA it falls under this same umbrella. Libre-SOC shall be
328 entering into an agreement with the OpenPOWER Foundation, here, as part
329 of the ISA RFC process. European businesses clearly benefit from the
330 long-term stability of this arrangement.
331
332
333 Whilst we clearly need, ultimately, to prove our design's power-efficiency
334 in silicon, we would however consider it unwise and extremely costly to
335 tape-out to Silicon without having gone through a proper early-evaluation
336 process, weeding out ineffective strategies and designs. To that end, we
337 learned from Jeff Bush's work on the Nyuzi 3D core to perform estimates
338 on power consumption and clock cycles. This is a highly-effective
339 feedback process that allows identification and targeting of the most
340 urgent (inefficient) areas, and we have taken it on-board and adopted
341 it throughout the project.
342
343
344 Part of that involves Peter Hsu's cavatools (another NLnet Grant) which
345 is (at present) a cycle-accurate Simulator for RISC-V. A (new) NLnet
346 Grant (not yet approved at the time of writing) is targeted at porting
347 cavatools to the Power ISA. This proposal would allow NLnet-funded work to
348 be extended into 3D, Video, DSP and other areas, to simulate (test) out
349 the feasibility, power-efficiency and effectiveness of different Custom
350 SVP64 Extensions to the Power ISA, long before they reach actual Silicon.
351
352
353 # 2 Impact
354
355
356 ## 2.1 Project’s pathways towards impact
357
358
359 The core of modern computing is the capability of the computational
360 element of the systems and the microprocessors they are based around.
361 Every twenty years there has been a significant evolutionary step in the
362 technical concepts employed by these microprocessor devices. For example
363 the last big step was the concept of RISC (Reduced Instruction Set)
364 processors. These developments have been driven by many forces from
365 cost of devices to limitations of the available technology of the time.
366
367
368 The Libre-SOC core is capable of becoming the next significant step
369 change in microprocessor speed, technology, and reduction in equivalent
370 computational power (Watts).
371
372
373 To illustrate this, we need to go back in history to early computing.
374 The first microprocessors were reliant on expensive core then bipolar
375 memory and even with the advent of DRAMS (Dynamic Random-Access Memories)
376 the primary focus of microprocessor processor core designs was to
377 optimise the minimal use of memory and focus on the power of the core.
378 Over time, memory became cheaper and reliance on memory to improve
379 processing increased with techniques like RAMdisk stores were developed.
380 This cheap memory also resulted in the evolution of RISC and similar
381 computing technology concepts. Today the problem is epitomized by speed,
382 where microprocessors have evolved to be much faster than the fastest
383 memories, and to increase performance, the state of the art computing
384 requires coming full-circle: once again minimising the use of memory,
385 which is now a log jam, and looking again at the core optimisation
386 solutions devised in the 1960’s by luminaries such as Seymour Cray.
387 The Libre-SOC core is an optimal adoption of this category of core
388 processor performance enhancement.
389
390
391 Libre-SOC has the benefit that its development relies on fundamental
392 research that has been known and proven for nearly 60 years. SVP64 has
393 input from and takes on-board lessons learned from NEC SX-Aurora, Cray-I,
394 Mitch Alsup's MyISA 66000, RISC-V RVV Vectors, MRISC32, AVX-512, ARM
395 SVE2, Qualcomm Hexagon and TI's DSP range, as well as other more esoteric
396 Micro-architectures such as Aspex's Array-String Processor and Elixent's
397 2D Grid design.
398
399
400 As a Hybrid (merged) CPU-VPU-GPU Micro-architecture (similar to
401 ICubeCorp's IC3128) there is a huge reduction in the complexity
402 of 3D Graphics and Video Driver and overall hardware. NVidia, ARM
403 (MALI), AMD, PowerVR, Vivante: these are all dual (ISA-incompatible)
404 architectures with staggering levels of hardware-software complexity.
405 Like ICubeCorp's design, Libre-SOC 3D and Video binaries are executed
406 directly on the actual main (one) core.
407
408
409 The end-result here is, if deployed in mass-volume products world-wide
410 including for European end-users of ubiquitous Computing devices, a
411 significant energy saving results on a massive scale, particularly in
412 battery-operated (mobile, tablet, laptop) appliances. Demonstrating this
413 however requires, ultimately, that we actually create real silicon,
414 and measure its performance and power consumption.
415
416
417 ## 2.2 Measures to maximise impact - Dissemination,
418 exploitation and communication
419
420
421 As the Libre-SOC core is the result of a Libre/Open Source project
422 by default all of our development work has been published for the last
423 four years. This was also a requirement of our EU funding through NLnet.
424 In addition we have undertaken a full program of conference presentations,
425 technology awareness activities and cooperation with key bodies such as
426 the OpenPOWER Foundation and OpenPOWER Members (Libre-SOC is participating
427 in a world-wide Open University Course about the OpenPOWER ISA, an
428 activity led by IBM). Examples:
429
430
431 * https://openpowerfoundation.org/events/openpower-summit-2020-north-america/
432 * https://openpowerfoundation.org/libre-soc-180nm-power-isa-asic-submitted-to-imec-for-fabrication/
433
434
435 Marie-Minerve Louerat (CNRS) and Jean-Paul Chaput's and Professor
436 Galayko's (Sorbonne Université LIP6 Lab) Academic Publications will
437 continue https://www.lip6.fr/actualite/personnes-fiche.php?ident=P109
438 https://www.lip6.fr/actualite/personnes-fiche.php?ident=P98
439 https://www.lip6.fr/actualite/personnes-fiche.php?ident=P230 as will
440 their continued Conference participation (example: FOSDEM 2021 coriolis2
441 https://av.tib.eu/media/52401?hl=coriolis2)
442
443
444 Luke Leighton also releases videos of his Libre-SOC talks on
445 youtube https://www.youtube.com/user/lkcl and a full list of all
446 conferences (past and present) are maintained on the Libre-SOC website
447 https://libre-soc.org/conferences/
448
449
450 The Libre-SOC bugtracker (where we track our TODO actions) is
451 public access (https://bugs.libre-soc.org), and the Mailing
452 lists are also public access (https://lists.libre-soc.org).
453 LIP6's alliance/coriolis2 mailing lists are also public access
454 (https://www-soc.lip6.fr/wws/info/alliance-users)
455
456
457 These are ongoing activities that actively encourage world-wide Open
458 Participation, and shall remain so indefinitely. We will continue to
459 grow these activities along with a commercial thread of publicity by RED
460 Semiconductor Ltd to publicise and determine product family opportunities
461 where RED Semiconductor Ltd will focus on potential product and market
462 development built upon the Libre-SOC core technology.
463
464
465 ## 2.3 Summary
466
467
468 ### Specific needs
469
470
471 Modern computing technology is designed in secrecy and released to
472 the market without the ability of the user base to vet or validate.
473 When problems arise it is usually due to “discovery” and usually
474 driven by technical curiosity or malice. What is clear is that to those
475 on the inside these problems were visible from the outset, however
476 time resource and unwillingness to explore (and unethical Commercial
477 pragmatism) has left these vulnerabilities open to be exploited. As a
478 general principle we have taken the view that any new design should be
479 open to review and able to be corrected (every design has some bugs)
480 before mass adoption and the inevitable loss and crisis.
481
482
483 In practical terms: as indicated in sections above there have
484 been a number of security incidents involving ubiquitous computing
485 devices, impacting millions to hundreds of millions of end-users,
486 world-wide. Qualcomm failed last year to provide adequate secure firmware,
487 leaving 40% of the entire world's Android smartphones vulnerable to
488 attack. With the majority of smartphones being "fire-and-forget" products
489 with non-upgradeable firmware, the end-user's only solution is to throw
490 away a perfectly good electronics product and purchase a new one.
491 For Intel products - all Intel products - the exact same thing has
492 occurred (Master Firmware Key, Spectre, Meltdown), but at an unfixable
493 hardware level, and there are no replacement Intel products that can be
494 purchased in the market to "fix" their fundamental design flaws.
495
496
497 Not only that, but all of the ubiquitous Computing products (Apple, Intel,
498 IBM, NVidia, AMD being the most well-known) are 100% non-EU-based. As far
499 as EU Digital Sovereignty is concerned, this is an extremely serious
500 and alarming situation, compounded by critical Foundries and know-how
501 to run those Foundries also not being part of a Sovereign European remit.
502
503
504 If that was not enough, Foundries and the Semiconductor Industry requires
505 NDAs that at the minimum prohibit full publication of Academic results,
506 stifling innovation and research, in turn driving up the cost for EU
507 businesses of the cost of ASIC products by creating artificial cost,
508 overhead and knowledge barriers.
509
510
511 The entire Computing and Semiconductor Industry needs a new approach.
512
513
514 Taking the initiative, the end goal of the Libre-SOC/RED Semiconductor
515 Ltd project is therefore to deliver high performance, security auditable,
516 supercomputer class computing devices to the market. As this is not
517 currently available it will prompt a step change in low power (Watts)
518 high performance computing. This will be achieved through:
519
520
521 * Energy/Power consumption measurement: we need to verify that performance/watt is lowered
522 * Draft SVP64 inclusion in Power ISA: this is needed to indicate "Official long-term Status"
523 * Auditability and Transparency: needed for end-users and EU businesses to trust the hardware.
524 * Power ISA 3.0 Interoperability: to leverage over 2 decades of existing business software tools.
525 * FPGA and Simulator demonstrators: to demonstrate feasibility of the HDL and the ISA
526 * VLSI toolchain and Cell Library: MPW Shuttle runs are needed to reach "Silicon-proven" status
527 * NLnet mini-grants: Effectively this is a "Reserve" budget for the Project, managed by NLnet
528
529
530 ### Dissemination, exploitation and Communication
531
532 Energy/Power consumption measurement:
533
534
535 Just as Jeff Bush showed by publishing Nyuzi Research at Conferences we
536 shall follow the same proven incremental performance/watt measures and
537 procedures, and publish the results.
538
539 https://ieeexplore.ieee.org/document/7095803/
540
541
542 Draft SVP64 inclusion in Power ISA:
543
544
545 We are already working with the OpenPOWER ISA Working Group, and have
546 already begun publishing the Draft SVP64 Specification as it is being
547 developed. This will become official RFCs (Request for Changes) leading
548 to adoption. This includes development of Compliance Test Suites,
549 low-level libraries, compilers etc. which shall be announced through
550 Conferences, Press Releases (by RED Semiconductor Ltd, NLnet and the
551 OpenPOWER Foundation) and standard Libre/Open development practices
552 (Mailing list Announcements).
553
554
555 Auditability and Transparency:
556
557
558 Using symbiyosys we have already established a number of Formal
559 Correctness Proofs for the TRL 3 HDL used in the 180nm ASIC: This
560 needs to be extended right the way throughout all future work and be
561 published for other OpenPOWER Foundation Members and European businesses
562 to be able to independently verify the correct functionality of not just
563 Libre-SOC ASIC designs but other Power ISA 3.0 compliant designs as well.
564 Libre-SOC HDL and the associated Formal Correctness Proofs are published
565 as-they-are-developed in real-time and consequently dissemination is
566 implicit and automatic.
567
568
569 For the Silicon-level "EMF signature" measurement system Libre-SOC
570 will define and publish Reference Standards, test applications and
571 methodology documentation. RED Semiconductor Ltd will establish
572 and make available a "expected results" database for its commercial
573 products, as part of its Product Application Documentation, so that
574 European Businesses may independently verify that their commercial
575 off-the-shelf RED Semiconductor Ltd products have not been tampered with
576 at the Silicon level. (It is beyond the scope of this Grant however RED
577 Semiconductor Ltd will publish its overall Quality Standards Strategy).
578 In concept, the "EMF Signature" strategy is very similar to Hewlett
579 Packard's "Signature Analysis Strategy" that has been around since
580 1949. https://www.hpl.hp.com/hpjournal/pdfs/IssuePDFs/1977-05.pdf
581
582
583 Power ISA 3.0 Interoperability:
584
585
586 Standing on the shoulders of Giants (IBM and other OPF Members in
587 this case) is always a good starting point. The familiarity and
588 decades-long-term stability of the existing Power ISA 3.0 gives us a vast
589 existing-established user audience to whom we can provide training and
590 experience upgrades from an existing high-level of knowledge. In this
591 we already have the cooperation of IBM (through the OpenPOWER University
592 Education Course that Libre-SOC has helped to create - to be first run
593 from 18th-29th October 2021).
594
595
596 We will take the Interoperability further at a practical level
597 by developing a Libre/Open Power ISA 3.0 "Compliance Test
598 Suite" that meets the OpenPOWER Foundation documented standards
599 (https://openpowerfoundation.org/openpower-isa-compliance-definition/)
600 and make it entirely public and available to all without limit, and invite
601 other OpenPOWER Foundation Members to participate in its development
602 and use. This will then be, again, announced through Press Releases
603 and Mailing List as well as Conference Presentations.
604
605
606 FPGA and Simulator demonstrators:
607
608
609 Again: all new software tools created, and existing ones used and modified
610 to both develop and use resultant devices will be published as an inherent
611 part of the OpenSource real time publishing strategy.
612
613
614 VLSI Toolchain and Cell Library verification:
615
616
617 Again: the results of the development are, to date and in the future,
618 part of Libre/Open Source projects, and are therefore fully-visible, even
619 though they are Hardware-related we treat them as Open Source Software.
620 Conference presentations shall therefore be given, announcements on
621 Mailing Lists, as part of the overall communications strategy.
622
623
624 In this particular case however, the communication has to involve the
625 results of the MPW Shuttle runs, testing the actual ASICs, because it
626 is critical to demonstrate and communicate that the Cell Libraries are
627 Silicon-Proven and that the VLSI tools were capable of successfully
628 creating that Silicon-Proven layout. However the caveat here: anything
629 involving NDA'd material as required by the Foundry has to remain
630 confidential (note that this is not something that can be addressed
631 within the funding scope of this Call)
632
633
634 NLnet mini-grants:
635
636
637 NLnet's website has already been established with communication facilities
638 for around 19 years. NLnet are experienced in the effective evaluation
639 and management of small-scale Grants. They are also extremely familiar
640 with the work that we are doing, and with the detail of EU Grant
641 Procedures. Following those procedures they will add a new section to
642 the website for Grant Proposals that inherently meet the objectives of
643 this Call, and will use their existing communications infrastructure to
644 maximum benefit.
645
646
647 ### Expected results
648
649
650 Energy/Power consumption measurement:
651
652
653 We anticipate in the actual ASIC a significant measurable reduction in
654 performance/watt. Early predictions shall be based on Instruction-level
655 Simulations, but these need to be validated against the "real thing".
656 Due to the iterative process (outlined by Jeff Bush) we simply cannot
657 state exactly in advance the full magnitude of improvement that will
658 occur. The process itself, and how it was successfully applied, however,
659 will be considered to be part of the results themselves as part of
660 publications online and at Conferences.
661
662
663 Draft SVP64 inclusion in Power ISA:
664
665
666 The ultimate outcome here is that SVP64 becomes an officially-adopted
667 part of the OpenPOWER ISA, including a full compliance test suite,
668 documentation in a future revision of the official Power ISA Technical
669 Reference Manual. This process is, however, by necessity and being an
670 extremely important responsibility of the OpenPOWER Foundation (not of
671 any of the Participants), very slow and outside of our control, and may
672 take longer than the 36 month duration of the Grant to complete.
673
674
675 Therefore, the critical Milestone shall be our submission to the
676 OpenPOWER Foundation's ISA Working Group, as well as the development of
677 the required Compliance Test Suites. Both of these shall be published
678 under appropriate Libre/Open Licenses.
679
680
681 Auditability and Transparency:
682
683
684 We will have completed the Formal Correctness Proofs and published them
685 and the results of running them against the Libre-SOC HDL. We will also
686 have received the ASICs back from MPW Shuttle runs, which will contain
687 "EMF detection" wires routed strategically throughout it, and run the
688 pre-arranged unit tests that will create "Signatures" that shall be
689 recorded and published. This task is another critical reason why we
690 need actual Silicon, because only with an ASIC can we demonstrate the
691 viability of Signature Analysis (and similar) Strategies for ASICs.
692
693
694 Power ISA 3.0 Interoperability:
695
696
697 We will have completed an implementation of the Compliance Test
698 Suite as a Libre-Licensed application that can test multiple different
699 implementations: FPGA, Simulators (including our own as well as qemu), and
700 actual Silicon implementations including IBM POWER9, POWER10, Microwatt.
701 In addition we will have extended our own interoperability "Test API"
702 that allows comparisons of any arbitrary user-generated application
703 against any other arbitrary Power ISA compliant devices (whether FPGA,
704 Simulator, or Silicon): the OpenPOWER Compliance Test Suite implementation
705 shall simply be one of those applications.
706
707
708 We expect the Libre-SOC core to pass the full OpenPOWER ISA 3.0 Test
709 Suite, and the results to be published. We will also communicate with
710 OpenPOWER Foundation Members and make them aware of the existence of
711 the Test Suite and document how it may be used to test their own Power
712 ISA 3.0 implementations for Compliance.
713
714
715 FPGA and Simulator demonstrators:
716
717
718 Successful software simulation (emulation) of the augmented Power 3.0 ISA
719 with the Draft SVP64 Extensions, and successful demonstration of the HDL
720 of a multi-core SMP processor implementing the same, running in a large
721 FPGA (the size of the commercially-available FPGAs constraining what
722 is possible, here). Each shall help verify the other's correctness.
723 This will be a rapid iterative cycle of development and shall always
724 produce early results, feeding back to continued improvement.
725
726
727 VLSI Toolchain and Cell Library verification:
728
729
730 Multiple demonstrator 2-core ASICs and a proven path to an 8-core ASIC
731 (as we anticipate that the 8-core is likely to be beyond the scope of the
732 Grant due to Silicon costs). Where the 2-core ASIC MPW is multi-purpose
733 (proving the HDL, proving the VLSI toolchain, proving the Cell Library)
734 and shall use the FPGA and Simulations to check its correctness before
735 proceeding, the 8-core shall remain in FPGA only, due to cost, but a
736 VLSI Layout for the 8-core will still be attempted, in order to "test
737 the limits" of the VLSI tools. If funding was available we could take
738 the 8-core to full MPW rather than just to FPGA and GDS-II. As the 8
739 core Layout develops, if it (and the coriolis2 toolchain) progresses
740 to viability in the 36 months one option might be for RED Semiconductor
741 to apply for a EUR 500,000 NLnet mini-grant, payment terms to meet
742 requirements set by IMEC, from their budget allocated under this proposal.
743
744
745 NLnet mini-grants:
746
747
748 NLnet will receive and review potentially hundreds of small Grant
749 Proposals to ensure that they meet both the Call's Objectives and meet
750 NLnet's responsibilities as a Stichting / Foundation to fund "Works
751 for the Public Good". They shall request that the successful Grant
752 Applicant create Milestones and that Grant Applicant communicate those
753 results, thus requiring that it is the Grant Applicant that fulfils the
754 requirement herein. This process is already established and already in
755 effect under Grant Agreements No 825310 and 825322.
756
757
758 In the case of the Participants, if we need "reserve" budgets for
759 unforseen activities, we commit to following that exact same procedure
760 and thus also shall meet the Objectives of this Call (examples include
761 the MPW 8-core, above). We are aware that new technology beneficial to
762 the project may not be currently apparent but will be available within
763 the 36 months duration, and the methodology of funding it through NLnet
764 may prove optimal and a cost-effective use of EU funds, as NLnet would
765 (as they do now) only draw the budget down as needed.
766
767
768 ### Target groups
769
770
771 Due to our Open real time publishing of the Libre-SOC project, our work
772 can be forked by anyone at any time as a starting point or as a building
773 block for new projects, potentially taking the ideas and concepts in any
774 direction. These can be individuals or teams and they can be academics
775 or industrialists, the point being that if we trigger a step change in
776 the technology everyone should be able to benefit.
777
778
779 This is in addition to our own commercialisation plans.
780
781
782 Open Source methodology leads to Open standards which leads to Open
783 understanding and rapid adoption of new ideas in academia and industry.
784 The Eurocentric nature and benefit of the work should not be overlooked
785 either.
786
787
788 ### Outcomes
789
790
791 As the development chain includes elements of commercialisation, beyond
792 the immediate benefit to similar projects by the enhancement of the
793 Libre/Open Source tool chain and the educational uplift provided directly
794 and by example to other groups and European businesses and Educational
795 Establishments planning Software-to-Silicon projects, the most direct
796 outcome will be the availability, as devices in the market through RED
797 Semiconductor Ltd, of a new concept in supercomputing power that is also
798 completely security auditable and transparent.
799
800
801 We are already aware of a commercial venture formed recently, who are
802 aware and already benefiting from our work over the last three years to
803 improve the Software-to-Silicon toolchain, that is now focusing on the
804 finessing of the toolchain and its human interface to widen access to the
805 methodology and IMEC are using our architectural test chip, currently in
806 production, to validate and test their new cloud based chip design suite.
807 The outcomes are already happening and are bound to magnify.
808
809
810 ### Impacts
811
812
813 We believe the market demand for our step change in core architecture
814 thinking is so great it will force the world's leading microprocessor
815 companies to follow. The result will be a greater step change in the
816 performance and security of computer hardware across the world.
817
818
819 Additionally the confirmation of Silicon-proven Cell Libraries and
820 a European-led functional Libre-Licensed VLSI toolchain in lower
821 geometries will significantly reduce the cost of ASIC development for
822 European businesses and reduce to zero the risk of critical dependence
823 on non-Sovereign (geo-politically constrained) Commercial VLSI tools
824 and Cell Libraries.
825
826
827 # 3 Quality and efficiency of the implementation
828
829
830 https://online.visual-paradigm.com/diagrams/tutorials/pert-chart-tutorial/
831
832
833 Work Packages:
834
835
836 1. NLnet
837 2. SVP64 Standards
838 3. Power ISA Simulator and Compliance Test Suite
839 4. Compilers and Libraries
840 5. Enhancement of Libre-SOC HDL
841 6. EMF Signature Hardware security
842 7. Cell Libraries
843 8. Improve Coriolis2 for smaller geometries
844 9. VLSI Layout, Tape-outs and ASIC testing
845 10. Project Management
846 11. Helix GPS Application
847
848
849 # 3.1 Work plan and resources
850
851 Tables for section 3.1
852
853
854 Table 3.1a: List of work packages
855
856
857 |Wp# |Wp Name |Lead # |Lead Part# Name |Pe Months|Start |End |
858 |----- |------------- |------------ |--------- |--- |----- |--------- |
859 |1 |NLnet |5 |NLnet |18 |1 |36 |
860 |2 |SVP64 |2 |Libre-SOC |21 |1 |36 |
861 |3 |Sim/Test |2 |Libre-SOC |64 |1 |18 |
862 |4 |Compilers |1 |RED |32 |1 |36 |
863 |5 |HDL |2 |Libre-SOC |193 |1 |36 |
864 |6 |EMF Sig |4 |4/CNRS |84 |1 |18 |
865 |7 |Cells |2 |Libre-SOC |109 |1 |24 |
866 |8 |Coriolis2 |3 |3/SU |338 |1 |36 |
867 |9 |Layout |3 |3/SU |220 |8 |36 |
868 |10 |Mgmt, Fin, Legal |1 |RED |185 |1 |36 |
869 |11 |Helix GPS Cor. |6 |Helix |248 |1 |36 |
870 | | | |Total months |1512 | | |
871
872 ## 1. NLnet
873
874 Table 3.1b(1)
875
876 |Work Package Number |1 |
877 | ---- | -------- |
878 |Lead beneficiary |NLnet |
879 |Title |NLnet mini-grants |
880 |Participant Number |5 |
881 |Short name of participant |NLnet |
882 |Person months per participant |18 |
883 |Start month |1 |
884 |End month |36 |
885
886
887 Objectives:
888
889
890 To manage the people who put in supplementary (by timescale) proposals
891 intended to support the core objectives of our proposal, ensuring that
892 those proposals also honour and meet the objectives outlined in the
893 original call:
894
895 https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/horizon-cl4-2021-digital-emerging-01-01
896
897
898 This will allow us to address and deploy new ideas and concepts not
899 immediately available to us at the time of this submission, and have
900 them properly vetted by an Organisation both familiar with our work,
901 and already trusted by the EU to fulfil the same role for other EU Grants.
902
903
904 Description of work:
905
906
907 These descriptions effectively mirror the light-weight grant mechanism
908 NLnet manages for the NGI research and development calls (EU Grants
909 825310 and 825322) and does not deviate from those pre-established
910 procedures except to define the context of the work to be carried out
911 by the Grant Recipient to fall within the criteria defined by this call
912 (HORIZON-CL4-2021-DIGITAL-EMERGING-01-01) not those of the previous Grants
913
914
915 * To include on the NLnet website a dedicated Call for mini-grant (EUR 50,000) Proposals, meeting the criteria of this existing Call (HORIZON-CL4-2021-DIGITAL-EMERGING-01-01) where the wording shall be written by NLnet and approved by the EU.
916 * To analyse and vet the Proposals to ensure that they match the criteria, through a multi-stage process including validating appropriateness to the Libre-SOC Project and running each application through an Independent Review by the EU.
917 * To notify successful Applicants, to ensure that they sign a Memorandum of Understanding with attached pre-agreed Milestones, and to fulfil Requests for Payment on 100% successful completion of those same pre-agreed Milestones.
918 * To produce Audit and Transparency Reports and to engage the services of Auditors to ensure compliance.
919
920
921 Deliverables:
922
923
924 Again these deliverables are no different from NLnet's existing
925 deliverables to the EU under Grant Agreements 825310 and 825322
926
927
928 * 1.1. A functioning Call-for-Proposals on the NLnet website.
929 * 1.2. Inclusion of the new CfP within the existing NLnet infrastructure
930 * 1.3. Progress Reports and Independent Audit Reports to the EU
931
932
933 ## 2. SVP64 Standards, RFC submission to OPF ISA WG
934
935
936 Table 3.1b(2)
937
938
939 |Work Package Number |2 |
940 | ---- | -------- |
941 |Lead beneficiary |Libre-SOC |
942 |Title |SVP64 Standards, RFC submission to OPF ISA WG |
943 |Participant Number |2 |
944 |Short name of participant |Libre-SOC |
945 |Person months per participant |21 |
946 |Start month |1 |
947 |End month |36 |
948
949
950 Objectives:
951
952
953 To advance Draft SVP64 Standards, to work with the OpenPOWER Foundation
954 ISA Working Group to comply with deliverable requirements as defined
955 by the OPF ISA WG within their Request For Change (RFC) Process, and to
956 deliver them.
957
958
959 Description of work:
960
961
962 * Extend Draft SVP64 into other areas necessary for fulfilment of this Call (including Zero-Overhead Loop Control)
963 * Prepare SVP64 Standards Documentation for RFC Submission, including identifying appropriate subdivisions of work.
964 * Create presentations and explanatory material for OpenPOWER Foundation ISA WG Members to help with their Review Process
965 * Complete OPF ISA WG RFC submission requirements and submit the RFCs (Note: Compliance Test Suites are also required but are part of Work Package 3)
966 * Publish the results of the decision by the ISA WG (whether accepted or not) and adapt to feedback if necessary
967 * Repeat for all portions of all SVP64 Standards.
968
969
970 Deliverables:
971
972
973 Note: some of these deliverables may not yet be determined due to
974 the OpenPOWER Foundation having not yet finalised and published its
975 procedures, having not yet completed their Legal Review. In addition,
976 although we can advise and consult with them, it will be the OPF ISA
977 WG who decides what final subdivisions of SVP64 are appropriate (not
978 the Participants). This directly impacts and determines what the actual
979 Deliverables will be: They will however fit the following template:
980
981
982 * 2.1. Publish report on appropriate subdivisions of SVP64 subdivisions into multiple distinct OPF RFCs
983 * 2.2. Publish presentations and explanatory materials to aid in the understanding of SVP64 and its value
984 * 2.3. Attend Conferences to promote SVP64 and its benefits
985 * 2.4. Complete the documentation and all tasks required for each SVP64 RFC and submit them to the OPF
986 * 2.5. For each RFC, publish a report on the decision and all other permitted information that does not fall within the Commercial Confidentiality Requirements set by the OpenPOWER Foundation (these conditions are outside of our control).
987
988
989 ## 3. Power ISA Simulator and Compliance Test Suite
990
991
992 Table 3.1b(3)
993
994
995 |Work Package Number |3 |
996 | ---- | -------- |
997 |Lead beneficiary |Libre-SOC |
998 |Title |Power ISA Simulator and Compliance Test Suite |
999 |Participant Number |2 |1 |
1000 |Short name of participant |Libre-SOC |RED |
1001 |Person months per participant |32 |32 |
1002 |Start month |1 |
1003 |End month |18 |
1004
1005
1006 Objectives:
1007
1008
1009 To advance the state-of-the-art in high-speed (near-real-time)
1010 hardware-cycle-accurate ISA Simulators to include the Power ISA and the
1011 SVP64 Draft Vector Extensions, and to create Test Suites and Compliance
1012 Test Suites with a view to aiding and assisting OpenPOWER Foundation
1013 Members including other European businesses and Academic Institutions
1014 to be able to check the interoperability and compliance of their Power
1015 ISA designs, and to have a stable base from which to accurately and
1016 cost-effectively test out experimental energy-efficient and performance
1017 advancements in computing, in close to real-time, before committing to
1018 actual Silicon.
1019
1020
1021 Description of work:
1022
1023
1024 1. Supplement the work under NLnet "Assure" Grant No 2021-08-071 (part of EU Grant no 957073) to further advance a cavatools port to the Power ISA 3 with newer Draft SVP64 features not already covered by NLnet 2021-08-071 (Note: this particular NLnet Grant has not yet been approved at the time of writing)
1025 2. Advancement of the Hardware-Cycle-Accuracy for Out-of-Order Execution simulation in cavatools, and the addition of other appropriate Hardware models.
1026 3. Addition of other relevant Libre-SOC Draft Power ISA Extensions in cavatools for 3D, Video, Cryptography and other relevant Extensions.
1027 4. Advancement of the Libre-SOC (TRL 3/4) "Test API" to other Simulators, HDL Simulators and existing ASICs (IBM POWER 9/10) and designs (Microwatt)
1028 5. Implement Compliance Test Suite suitable for Libre-SOC according to OpenPOWER Foundation requirements (for Work Package 2: SVP64 Standards)
1029 6. Develop an SVP64 Compliance Test Suite suitable for submission to the relevant OpenPOWER Workgroup, to a level that meets their requirements.
1030
1031
1032 Deliverables:
1033
1034
1035 * 3.1. Delivery of an updated version of cavatools with new Draft SVP64 features
1036 * 3.2. Delivery of a version of cavatools with hardware-accurate models including Out-of-Order Execution
1037 * 3.3. Delivery of additional co-simulation and co-execution options to the Libre-SOC "Test API" including at least IBM POWER 9 (and POWER 10 if access can be obtained), and Microwatt.
1038 * 3.4. Delivery of an implementation of a Compliance Test Suite that meets the OpenPOWER Foundation's criteria
1039 * 3.5. Delivery of the documentation and an implementation of a Compliance Test Suite for Draft SVP64 Extensions for submission to the relevant OpenPOWER Foundation Workgroup.
1040 * 3.6. Public reports on all of the above at Conferences and on the Libre-SOC website.
1041
1042
1043 ## 4. Compilers and Software Libraries
1044
1045
1046 Table 3.1b(4)
1047
1048 |Work Package Number |4 |
1049 | ---- | -------- |
1050 |Lead beneficiary |RED Semiconductor Ltd |
1051 |Title |Compilers and Software Libraries |
1052 |Participant Number |1 |2 |
1053 |Short name of participant |RED |Libre-SOC |
1054 |Person months per participant |20 |12 |
1055 |Start month |1 |
1056 |End month |36 |
1057
1058
1059 Objectives:
1060
1061
1062 To create usable prototype compilers including the advanced Draft SVP64
1063 Vector features suitable for programmers using C, C++ and other High-level
1064 Languages, and to provide the base for the 3D Vulkan Drivers (IR -
1065 Intermediate Representation). To advance the 3D Vulkan Drivers with Draft
1066 SVP64 support. To add support for SVP64 Vectors into low-level software
1067 such as libc6, u-boot, the Linux Kernel and other critical infrastructure
1068 necessary for general-purpose computing software development.
1069
1070
1071 Description of work:
1072
1073
1074 * Feasibility Study of each of the Compilers and Libraries
1075 * Draft SVP64 Vector support in the gcc compiler
1076 * Draft SVP64 Vector support in the llvm compiler
1077 * Advancement of the Kazan 3D Vulkan Driver including using Draft SVP64
1078 * Advancement of the MESA3D Vulkan Driver including using Draft SVP64
1079 * Draft SVP64 Vector and Libre-SOC core support in low-level software including: libc6, u-boot, Linux Kernel.
1080
1081
1082 Deliverables:
1083
1084
1085 * 4.1. Feasibility report on the viability and scope of achievable work within the available respective budgets for each deliverable
1086 * 4.2. Prototype compilers for each of gcc, llvm, Kazan and MESA3D meeting the scope of achievable work defined in the Feasibility study, delivered in source code form under appropriate Libre-Licenses and including unit test bench source code demonstrating successfully meeting the objectives
1087 * 4.3. Prototype ports of libc6, u-boot, Linux Kernel and other software demonstrated to meet the scope of achievable work, delivered in source code form under appropriate Libre-Licenses with unit tests.
1088 * 4.4. Public reports on the above and presentations at suitable Conferences
1089
1090
1091 ## 5. Enhancement of Libre-SOC HDL
1092
1093
1094 Table 3.1b(5)
1095
1096
1097 |Work Package Number |5 |
1098 | ---- | -------- |
1099 |Lead beneficiary |Libre-SOC |
1100 |Title |Enhancement of Libre-SOC HDL |
1101 |Participant Number |2 |1 |3 |
1102 |Short name of participant |Libre-SOC |RED |3/SU |
1103 |Person months per participant |94 |83 |27 |
1104 |Start month |1 |
1105 |End month |36 |
1106
1107
1108 Objectives:
1109
1110
1111 To create progressively larger processor designs, implementing the
1112 Power ISA 3, augmented by Draft SVP64 Cray-style Vectors, in order to
1113 act as real-world test cases for coriolis2 VLSI.
1114
1115
1116 Description of work:
1117
1118
1119 1. Review and potentially revise the existing Libre-SOC SIMD ALU HDL library, for optimisation and gate-level efficiency.
1120 2. Review and revise the existing Libre-SOC IEEE754 Floating-Point HDL Library, for the same, to scale up to meet commercial performance/watt in targeted 3D GPU workloads.
1121 3. Implement Out-of-order Multi-issue Execution Engine using Mitch Alsup's advanced Scoreboard design
1122 4. Implement Speculative Execution Models and Checkers to ensure resistance from Spectre, Meltdown and other hardware security attacks
1123 5. Implement advanced 3D and Video Execution Engines and Pipelines (Texture caches, Z-Buffers etc.)
1124 6. Integrate advanced "Zero-Overhead-Loop-Control" (TRL9) features deployed successfully by STMicroelectronics into the Libre-SOC Core
1125 7. Implement fully-automated "Pinmux" and Peripheral / IRQ Fabric Generator suitable for System-on-a-Chip semi-automated HDL.
1126 8. Implement large-scale Memory Management Unit (MMU), IOMMU, SMP-aware L1 Caches and L2 Cache suitable for multi-core high-performance Vector throughput
1127 9. Formal Correctness Proofs and Modular Unit Tests for all HDL.
1128 10. Implement Verification, Validation and Simulations for HDL
1129
1130
1131 Deliverables:
1132
1133
1134 * 5.1. Advanced HDL SIMD Library with appropriate documentation, unit tests and Formal Correctness Proofs, suitable for general-purpose wide adoption outside of Libre-SOC's use-case, under appropriate Libre Licenses
1135 * 5.2. Advanced HDL IEEE754 Library with appropriate documentation, unit tests and Formal Correctness Proofs, , suitable for general-purpose wide adoption outside of Libre-SOC's use-case, under appropriate Libre Licenses
1136 * 5.3. Advanced Libre-SOC SMP-capable Core, capable of multi-issue Out-of-Order Execution and implementing the Power ISA and Draft SVP64 Custom Extensions, with full unit tests and appropriate Formal Correctness Proofs.
1137 * 5.4. "Peripheral" HDL including PHYs+Controllers including Pinmux / Fabric Inter-connect Autogenerator
1138 * 5.5. Verification, Validation and Simulation of HDL
1139 * 5.6. Appropriate publications and reports on all of the above at Conferences and on the Libre-SOC website.
1140
1141
1142 ## 6. EMF Signature Hardware security
1143
1144
1145 Table 3.1b(6)
1146
1147
1148 |Work Package Number |6 |
1149 | ---- | -------- |
1150 |Lead beneficiary |CNRS |
1151 |Title |EMF Signature Hardware security |
1152 |Participant Number |3 |4 |2 |1 |
1153 |Short name of participant |3/SU |4/CNRS |Libre-SOC |RED |
1154 |Person months per participant |35 |11 |13 |25 |
1155 |Start month |1 |
1156 |End month |18 |
1157
1158
1159 Objectives:
1160
1161
1162 To create a Electro-Magnetic "Signature" system that threads all the
1163 way through an ASIC VLSI layout that is sensitive to localised signal
1164 conditions, without adversely impacting the ASIC's behavioural integrity.
1165 For the "Signature" system to be sufficiently sensitive to change its
1166 output depending what program the ASIC is running at the time, in real
1167 time. To integrate the "threading" into the coriolis2 VLSI toolchain
1168 such that the "Signature" system's deployment is fully automatic.
1169 To demonstrate its successful functionality through a small (low-cost,
1170 large geometry) MPW test runs prior to deployment in the larger ASIC at
1171 lower geometries.
1172
1173
1174 Description of work:
1175
1176
1177 * Feasibility study of different types of EMF "Signature" systems (including Hewlett Packard's 1949 technique) and the design of the test methodology.
1178 * Design the Mixed Analog / Digital Cells required
1179 * Design and implement an automated integration and layout module in coriolis2 to deploy the Signature System on any ASIC.
1180 * Create a suitable VLSI layout with an existing small example alliance-check-toolkit HDL design, with the Signature System threaded through it, and test the resultant MPW ASIC
1181 * Work with the Libre-SOC and VLSI Layout team to deploy the "Signature" system in the smaller geometry layout, ensuring for security reasons that only authorised access to the System is allowed, and help test the resultant MPW ASIC.
1182 * Publish the results in an Academic Paper as well as present at Conferences
1183
1184
1185 Deliverables:
1186
1187
1188 * 6.1. Feasibility and test methodology Report
1189 * 6.2. Mixed Analog / Digital Cells for the Signature System
1190 * 6.3. SPICE Simulation report on the expected behaviour of the "Signature" system
1191 * 6.4. coriolis2 module for automated deployment of Signature System within any ASIC
1192 * 6.5. small ASIC in large geometry and test report on the results
1193 * 6.6. large Libre-SOC ASIC in small geometry with Signature System and test report on its behaviour
1194 * 6.7. Academic Paper on the whole system.
1195
1196
1197 ## 7. Cell Libraries
1198
1199
1200 Table 3.1b(7)
1201
1202
1203 |Work Package Number |7 |
1204 | ---- | -------- |
1205 |Lead beneficiary |Libre-SOC |
1206 |Title |Cell Libraries for smaller geometries |
1207 |Participant Number |3 |2 |1 |
1208 |Short name of participant |3/SU |Libre-SOC |Red |
1209 |Person months per participant |33 |13 |63 |
1210 |Start month |1 |
1211 |End month |24 |
1212
1213
1214 Objectives:
1215
1216
1217 To create, simulate, and test in actual silicon the low-level Cell
1218 Libraries in multiple geometries needed for advancing Libre/Open VLSI,
1219 using this proposals' other Work Packages as a test and proving platform,
1220 with a view to significantly reducing the cost for European Businesses in
1221 the creation of ASICs, for European Businesses and Academic Institutions
1222 to be able to publish the results of Security Research in full without
1223 impediment of Foundry NDAs, and to aid and assist in meeting the Digital
1224 Sovereignty Objectives outlined in EPRS PE 651,992 of July 2020.
1225
1226
1227 Description of work:
1228
1229
1230 Please Note: Work Packages 7, 8 and 9 are highly interdependent and
1231 will cross fertilise their results in an iterative manner as the design
1232 complexity increases, starting from smaller rapid-prototype test ASIC
1233 layouts and progressing to full designs.
1234
1235
1236 * Analog PLL, ADC and DAC Cells
1237 * Differential-pair Transmit / Receiver Cell
1238 * LVDS (current-driven) Transmit / Receiver Cell
1239 * Advanced GPIO IO Pad Cell (w/ Schottky etc.)
1240 * Clock Gating Cell
1241 * SR NAND Latch Cell
1242 * Standard Cells (MUX, DFF, XOR, etc)
1243 * SERDES Transmit / Receiver Cell (Gigabit / Multi-Gigabit)
1244 * Other Cells to be developed as required for other Work Packages
1245
1246
1247 Deliverables:
1248
1249
1250 * 7.1. Design of all Cells needed
1251 * 7.2. SPICE Model Simulations of all Cells
1252 * 7.3. Creation of Test ASIC Layouts and submission for MPW Shuttles in various geometries
1253 * 7.4. Generate and publish reports (Academic and others) and disseminate results
1254
1255
1256 ## 8. Improve Coriolis2 for smaller geometries
1257
1258
1259 Table 3.1b(8)
1260
1261
1262 |Work Package Number |8 |
1263 | ---- | -------- |
1264 |Lead beneficiary |Sorbonne Université (LIP6 Lab) |
1265 |Title |Improve Coriolis2 for smaller geometries |
1266 |Participant Number |3 |2 |1 |
1267 |Short name of participant |3/SU |Libre-SOC |RED |
1268 |Person months per participant |112 |128 |98 |
1269 |Start month |1 |
1270 |End month |36 |
1271
1272
1273 Objectives:
1274
1275
1276 To improve coriolis2 for lower geometries (to be decided on evaluation)
1277 such that it performs 100% DRC-clean (Design Rule Check) GDS-II files
1278 at the chosen geometry for the chosen Foundry, for each ASIC.
1279
1280
1281 Note: Commercial "DRC" will confirm that the GDS-II layout meets timing,
1282 electrical characteristics, ESD, spacing between tracks, sizes of vias
1283 etc. and confirms that the layout will not damage the Foundry's equipment
1284 during Manufacture.
1285
1286
1287 Description of work:
1288
1289
1290 Please Note: Work Packages 7, 8 and 9 are highly interdependent and
1291 will cross fertilise their results in an iterative manner as the design
1292 complexity increases, starting from smaller rapid-prototype test ASIC
1293 layouts and progressing to full designs.
1294
1295
1296 * The main focus (absolute priority) should be put on timing closure
1297 that becomes critical in the lower nodes. And if we can only achieve
1298 this alone, it will be a great success. That entails:
1299 - Improve the clock tree (change from H-Tree to a dynamically
1300 balanced one).
1301 - Improve High Fanout Net Synthesis.
1302 - Prevent hold violations.
1303 - Resizing of the gates (adjust power).
1304 - Logical resynthesis along the critical path, if needed.
1305 - Add a whole timing graph infrastructure.
1306 * To be able to implement those features has deep consequences on P&R:
1307 - We must have an "estimator" of the timing in the wires
1308 (first guess: Elmore).
1309 - The placer algorithm SimPL needs to be upgraded/rewritten
1310 to take on more additional constraints (adding and resizing
1311 gates on the fly).
1312 * Better power supply. Control of IR-drop.
1313 * Protection against cross-coupling.
1314 * During all that process, we must work on a stable database.
1315 So correct speed bottleneck only in algorithms built upon it,
1316 not the DB itself. For this kind of design, it is acceptable
1317 to run a full day on a high end computer.
1318 * Start a parallel project about to redesign the database (providing a backward
1319 compatibility API to Hurricane). But we must not make depend the timing closure
1320 on the database Rewrite.
1321
1322
1323 Deliverables:
1324
1325
1326 The key deliverables are measured by the successful passing of DRC
1327 (Design Rule Checks) against Commercial VLSI tools (Mentor, Synopsis), and
1328 is so critically inter-dependent on all components working 100% together
1329 that there can only be one deliverable, here, per ASIC Layout. Completion
1330 of sub- and sub-sub-tasks shall however be recorded in an easily-auditable
1331 Standard Libre/Open Task Tracking Database (gitlab, bugzilla) and
1332 appropriate structured progress reports created. As is the case with
1333 all Libre/Open Projects, "continuous" delivery is inherent through the
1334 ongoing publication of all source code in real-time. Full delivery is
1335 expected around 30 months.
1336
1337
1338 * 8.1. Coriolis2 VLSI improvements
1339 * 8.2. multiple small test ASIC layouts, to be added to LIP6 alliance-check-toolkit, potentially to be taped out and act as a preliminary test of prototype Cell Libraries
1340 * 8.3. large 2-core ASIC layout to be specifically taped-out in an MPW Shuttle Run
1341 * 8.4. Very large 8-core ASIC layout, not necessarily to be taped-out (MPW) due to size and cost, designed to push the limits.
1342 * 8.5. Academic and other reports
1343
1344
1345 ## 9. VLSI Layout, Tape-outs and ASIC testing
1346
1347
1348 Table 3.1b(9)
1349
1350
1351 |Work Package Number |9 |
1352 | ---- | -------- |
1353 |Lead beneficiary |Sorbonne Université (LIP6 Lab) |
1354 |Title |VLSI Layout, Tape-outs and ASIC testing |
1355 |Participant Number |3 |2 |1 |
1356 |Short name of participant |3/SU |Libre-SOC |RED |
1357 |Person months per participant |64 |94 |62 |
1358 |Start month |8 |
1359 |End month |36 |
1360
1361
1362 Objectives:
1363
1364
1365 To create 100% DRC-clean VLSI Layouts, to perform the necessary
1366 Validation of HDL as to its correctness at the transistor level, to
1367 submit them for MPW Shuttle Runs at the appropriate geometry through IMEC,
1368 and to test the resultant ASICs. This to confirm that the advancements
1369 to the entire coriolis2 VLSI Toolchain is in fact capable of correctly
1370 producing ASICs at both smaller geometries than it can already do,
1371 and at much larger sizes than it can already handle. To publish reports
1372 that serve to inform European Businesses and Academic Institutions of
1373 the results such that, if successful, those Businesses will potentially
1374 save hugely on the cost of development of ASICs, and the dependence
1375 on geo-political commercial tools is mitigated and the EU's Digital
1376 Sovereignty Objectives met.
1377
1378
1379 Description of work:
1380
1381
1382 Please Note: Work Packages 7, 8 and 9 are highly interdependent and
1383 will cross fertilise their results in an iterative manner as the design
1384 complexity increases, starting from smaller rapid-prototype test ASIC
1385 layouts and progressing to full designs.
1386
1387
1388 * To create VLSI Layouts using Libre-SOC HDL
1389 * To prepare and submit GDS-II Files to IMEC under appropriate MPW Shuttle Runs
1390 * To develop a Test jig, including custom test socket and supporting test software for each ASIC and to produce an appropriate report
1391 * To publish Academic Papers and other materials, on websites and at Conferences, on the results of each Tape-out.
1392
1393
1394 Deliverables:
1395
1396
1397 Note that due to the strong inter-dependence, these are the same Deliverables as Work Package 8.
1398
1399
1400 * 9.1. Multiple small test ASIC layouts, to be added to LIP6 alliance-check-toolkit, potentially to be taped out and act as a preliminary test of prototype Cell Libraries
1401 * 9.2. Large 2-core ASIC layout to be specifically taped-out in an MPW Shuttle Run
1402 * 9.3. Very large 8-core ASIC layout, not to be taped-out due to size and cost, designed to push the limits.
1403 * 9.4. Academic and other reports
1404
1405
1406 ## 10. Management
1407
1408
1409 Table 3.1b(10)
1410
1411
1412 |Work Package Number |10 |
1413 | ---- | -------- |
1414 |Lead beneficiary |RED |
1415 |Title |VLSI Layout, Tape-outs and ASIC testing |
1416 |Participant Number |1 |3 |2 |5 |
1417 |Short name of participant |RED |3/SU |Libre-SOC |NLnet |
1418 |Person months per participant |116 |12 |15 |42 |
1419 |Start month |1 |
1420 |End month |36 |
1421
1422
1423 Objectives:
1424
1425
1426 * Achieve competent management and control of the project
1427 * Account for activities and spending, and generate reports
1428 * Oversee legal relationships within the group and with external organisations
1429
1430
1431 Description of work:
1432
1433
1434 With a multi discipline project across five organisations it is
1435 essential that there is management and direction, as well as adequate
1436 training of new individuals introduced within each team. Each individual
1437 organisation will be responsible for their own activities with a central
1438 focus being maintained by RED Semiconductor Ltd and Libre-SOC jointly.
1439
1440
1441 Deliverables:
1442
1443
1444 * 10.1. Management, Administration and Training team
1445 * 10.2. Reporting
1446
1447
1448 ## 11. Helix GPS Correlator
1449
1450
1451 Table 3.1b(11)
1452
1453
1454 |Work Package Number |11 |
1455 | ---- | -------- |
1456 |Lead beneficiary |Helix |
1457 |Title | |
1458 |Participant Number |1 |6 | |
1459 |Short name of participant |RED |Helix | |
1460 |Person months per participant |136 |112 | |
1461 |Start month |1 |
1462 |End month |36 |
1463
1464
1465 Objectives:
1466
1467
1468 To focus the Libre-SOC 2-core ASIC onto a real-word customer
1469 requirement: GPS. To integrate both an FPGA as an early prototype and
1470 the final ASIC into a Demonstrator connecting to Helix's high-accuracy
1471 GPS Antenna Arrays. To confirm functionality, and confirm energy savings
1472 (performance/watt) compared to other solutions.
1473
1474 This programme will enable Helix to research, specify and ultimately
1475 realise, test and deploy a PNT processor single-chip that enables
1476 encrypted millimetre precision GNSS position and <nanosecond time data
1477 to be delivered from today’s GNSS constellations, and to be ready for
1478 next generation LEO (low earth orbit) PNT constellations being planned.
1479
1480 Helix’s comprehensive anti-jamming/spoofing and self-correcting
1481 capabilities will be designed into the same chip, enabling single-die
1482 total solution to accurate/resilient PNT, allowing Helix to integrate
1483 the electronics functionality into its antennas to create an ultra-
1484 compact ultra-low-power PNT solution that can be utilised globally
1485 in the next wave of applications like autonomous vehicles, urban air
1486 mobility, micro-transportation, and critical communications network
1487 synchronisation where market size runs into the tens or hundreds of
1488 million units per year.
1489
1490 Description of work:
1491
1492
1493 1. Scoping Report by Helix to research a Technical Architecture and the full Mathematical Requirements
1494 2. Creating from Scoping an agreed definition of the GPS ASIC requirement, by Helix, to be given to Libre-SOC and RED.
1495 3. Software, Hardware, Documentation, FPGA Prototypes, Test and QA for the Libre-SOC 2-core to be focussed on GPS as a real-word customer Application.
1496 4. Software Development and Hardware compatibility design through the GPS Antenna Arrays, and testing to confirm functionality in both FPGA and ASIC. To confirm reduction in performance/watt of the ASIC.
1497 5. Reporting
1498
1499
1500 Deliverables:
1501
1502
1503 * 11.1 Scoping Report
1504 * 11.2 NRE: Adapt 2-core to working demonstrator GPS Application
1505 * 11.3 Helix Management of NRE
1506 * 11.4 Helix Internal Engineering for GPS Antenna connectivity and testing.
1507 * 11.5 Reports
1508
1509
1510 ## Table 3.1c List of Deliverables
1511
1512 Essential deliverables for effective project monitoring.
1513
1514 |Deliv. #|Deliverable name |Wp # | Lead name |Type |Diss. |Del Mon |
1515 |------ |----------- |------ | ------- |------ |----------- | ---- |
1516 |1.3 |Reports |1 |5/NLnet |R |PU |12/24/36 |
1517 |2.4 |SVP64 RFCs |2 |2/Libre-SOC |R |PU |multiple |
1518 |3.4 |Compliance |3 |1/RED |R |PU |24 |
1519 |3.6 |Reports |3 |1/RED |R |PU |24/36 |
1520 |4.1 |Feasibility |4 |1/RED |R |PU |3 |
1521 |4.4 |Reports |4 |1/RED |R |PU |12/24/36 |
1522 |5.3 |Libre-SOC Core |5 |2/Libre-SOC |OTHER|PU |18 |
1523 |5.5 |HDL Validation |5 |2/Libre-SOC |R |PU |18 |
1524 |5.6 |Reports |5 |2/Libre-SOC |R |PU |12/24/36 |
1525 |6.1 |Feasibility |6 |4/CNRS |R |PU |3 |
1526 |6.7 |Academic Paper |6 |4/CNRS |R |PU |36 |
1527 |7.2 |SPICE Models |7 |4/CNRS |DATA |PU |12 |
1528 |7.4 |Academic Papers |7 |4/CNRS |R |PU |36 |
1529 |8.3 |2-core readiness |8 |3/SU |R |PU |15 |
1530 |8.5 |Academic Papers |8 |3/SU |R |PU |36 |
1531 |9.2 |2-core GDS-II |9 |3/SU |OTHER|PU |26 |
1532 |9.4 |Academic Papers |9 |3/SU |R |PU |36 |
1533 |10.2 |Reporting |10 |1/RED |R |PU |12/24/36 |
1534 |11.2 |Requirements |11 |6/Helix |R |PU |12 |
1535 |11.5 |Reporting |11 |6/Helix |R |PU |12/24/36 |
1536
1537 ## Table 3.1d: List of milestones
1538
1539
1540 |M/stone #|Milestone name |WP# |Due date |Means of verification |
1541 |------ | ------ | ----- | ------ | ------ |
1542 |2.4 |SVP64 RFCs |2 |multiple |OpenPOWER Foundation ISA WG |
1543 |3.1 |cavatools/SVP64 |3 |12 |Deliverable 3.5 (Compliance tests) |
1544 |4.2 |compilers |4 |24 |Deliverable 4.3 (software tests) |
1545 |5.3 |Libre-SOC Core |5 |18 |Deliverable 5.5 (HDL Validation) |
1546 |6.2 |Signature Cells |6 |12 |Deliverables 6.3 / 6.5(SPICE, ASIC) |
1547 |7.1 |Cell designs |7 |12 |Deliverables 7.2 / 7.3 (SPICE, ASIC) |
1548 |8.1 |coriolis2 |8 |18 |Deliverables 8.2-8.4 |
1549 |9.1 |coriolis2 ongoing|9 |12 |Deliverables 9.2-9.3 (ASICs) |
1550 |6.7 |Academic report |6 |36 |self-verifying (peer review) |
1551 |7.4 |Academic report |7 |36 |self-verifying (peer review) |
1552 |8.5 |Academic report |8 |36 |self-verifying (peer review) |
1553
1554
1555 ## Table 3.1e: Critical risks for implementation
1556
1557
1558 Risk level: (i) likelihood L/M/H,(ii) severity: Low/Medium/High
1559
1560
1561 |Description of risk |Wp# |Proposed risk-mitigation measures |
1562 |----------------- | ----- | ------ |
1563 |loss of personnel |1-11 |L/H key-man insurance |
1564 |4/CNRS availability |7 |H/H Additional personnel from 1/RED, at market rates |
1565 |Unforeseen Technical |2-11 |L/H 5/NLnet "reserve" mini-grant budget (Wp#1) |
1566 |Geopolitical adversity |4,6-9,11 |M/H Use lower geometries, or switch Foundry (via IMEC) |
1567 |Access to Foundries |4,6-9,11 |M/M Use IMEC as a Sub-contractor |
1568 |Pandemic |1-11 |L/H current mitigation continued (isolation of teams) |
1569 | | | |
1570
1571
1572
1573
1574 ## Table 3.1f: Summary of staff effort
1575
1576
1577 |Part#/name |Wp1 |Wp2 |Wp3 |Wp4 |Wp5 |Wp6 |Wp7 |Wp8 |Wp9 |Wp10 |Wp11 |Total |
1578 |------------- |----- |----- |----- |----- |----- |----- |----- |----- |----- |----- |----- |----- |
1579 |1/RED | | |32 |20 |94 |25 |63 |98 |62 |116 |136 |646 |
1580 |2/Libre-SOC | |21 |32 |12 |72 |13 |13 |128 |94 |15 | |400 |
1581 |3/SU | | | | |27 |35 |33 |112 |64 |12 | |283 |
1582 |4/CNRS | | | | | |11 | | | | | |11 |
1583 |5/NLnet |18 | | | | | | | | |42 | |60 |
1584 |6/Helix | | | | | | | | | | |112 |112 |
1585 |Totals |18 |21 |64 |32 |193 |84 |109 |338 |220 |185 |248 |1512 |
1586
1587
1588 ## 3.1g Subcontracting
1589
1590 These are the subcontracting costs for the participants
1591
1592 ### Table 3.1g: 1/RED ‘Subcontracting costs’ items
1593
1594
1595 |Cost EUR |description and justification |
1596 | ----- | ------ |
1597 |60000 |feasibility and scope studies for compilers |
1598 |1500000 |gcc compiler (1) |
1599 |1500000 |llvm compiler (1) |
1600 |500000 |Kazan Vulkan 3D compiler (1) |
1601 |500000 |MESA 3D Vulkan compiler (1) |
1602 |400000 |libc6, u-boot, linux kernel software (1) |
1603 |50000 |smaller (180/130 nm) ASIC MPWs (IMEC) (2) |
1604 |280000 |larger (low geometry) ASIC MPWs (IMEC) (2) |
1605 |4790000 | total |
1606
1607 (1) These software and compiler costs are to develop extremely specialist
1608 software, where it is Industry-standard normal to spend EUR 25 million
1609 to achieve TRL (9). Contracting of an extremely small pool of specialist
1610 Companies (Embecosm Gmbh, Vrull.EU) is therefore Industry-standard normal
1611 practice.
1612
1613 (2) IMEC is one of Europe's leading Sub-contractors for ASIC MPW Shuttle
1614 runs, and they handle the NDA relationships with Foundries that are almost
1615 impossible to otherwise establish.
1616
1617 https://europractice-ic.com/wp-content/uploads/2021/01/Pricelist-EUROPRACTICE-General-MPW_8.pdf
1618
1619 ### Table 3.1g: 5/NLnet ‘Subcontracting / Sub-Grant costs’ items
1620
1621
1622 |Cost EUR |description and justification |
1623 | ----- | ------ |
1624 |5000000 |NLnet "mini-grants" |
1625
1626
1627 ## Purchase costs
1628
1629 These are the purchasing costs for the participants
1630
1631 ### Table 3.1h: 1/RED Purchase Costs
1632
1633
1634 | |Cost EUR |Justification |
1635 | ------ | ----- | ------ |
1636 |travel / subst |48000 |3yr World-wide travel to conferences/meetings/interviews |
1637 |equipment |140000 |High-end Servers for Layouts, High-end FPGAs for testing |
1638 |Other/Good/work/Svc. |90000 |Legal/Accountancy/Insurance +prof. business services |
1639 |remaining purch. cst. | | |
1640 |Total |278000 | |
1641
1642
1643 ### Table 3.1h: 2/Libre-SOC Purchase costs
1644
1645
1646 | |Cost EUR |Justification |
1647 | ------ | ----- | ------ |
1648 |travel / subst |48000 | |
1649 |equipment |90000 |High-end Servers for Layouts, FPGA Boards for testing |
1650 |Other/Good/work/Svc. |12000 |I.T. Management of Libre-SOC Server |
1651 |remaining purch. cst. | | |
1652 |Total |150000 | |
1653
1654
1655 ### Table 3.1h: 3/SU Purchase costs
1656
1657
1658 | |Cost EUR |Justification |
1659 | ------ | ----- | ------ |
1660 |travel / subst | | |
1661 |equipment |100000 |High-end Servers for Layouts, Simulations |
1662 |Other/Good/work/Svc. |10500 |Office Administration |
1663 |remaining purch. cst. | | |
1664 |Total |110500 | |
1665
1666
1667 ### Table 3.1h: 5/NLnet
1668
1669
1670 | |Cost EUR |Justification |
1671 | ------ | ----- | ------ |
1672 |travel / subst |48000 |3yr EU-wide travel to conferences and meetings |
1673 |equipment | | |
1674 |Other/Good/work/Svc. | | |
1675 |remaining purch. cst. | | |
1676 |Total |48000 | |
1677
1678
1679 # 3.2 Capacity of participants and consortium as a whole
1680
1681
1682 The majority of the consortium have been working together for over
1683 three years on the precursor technical development of the Libre-SOC core
1684 project, the evolution of which is the lynch-pin and "proving-ground"
1685 of this grant application. The public record of their achievements
1686 and team involvement can be found in their public Open Source record
1687 https://libre-soc.org/.
1688
1689 The Libre-SOC team are internationally experienced software professionals
1690 who have strong familiarity with state of the art software to silicon
1691 technologies. They have been supported by two of the co-applicants labs
1692 CNRS and LIP6 (The applicants being Sorbonne Université and Affiliated
1693 Entity, CNRS), and many other European based technology development
1694 groups, which each provide key elements of the project from specialist
1695 programs such as coriolis2, alliance, HITAS, YAGLE and more, and the
1696 manufacturing expertise of Imec. Their versatility and experience with
1697 Libre/Open Source Software also means that they can adapt to unforeseen
1698 circumstances and can navigate the ever-changing and constantly-evolving
1699 FOSS landscape with confidence.
1700
1701 The above is critically important in light of the requirement to
1702 demonstrate access to critical infrastructure, resources and the
1703 ability to fulfil: with the sole exception of NDA'd Foundry PDKs
1704 (Physical Design Kits), the entirety of this project is Libre/Open
1705 Source, both in the tools it utilises, components that it uses, and
1706 the results that are generated. With there being no restriction on
1707 the availability of Libre/Open Source software needed to complete the
1708 project, the Participants correspondingly have no impediment. We also
1709 have a proven strategy to deal with the NDA's: a "parallel track" where
1710 at least one Participant (Sorbonne Université, LIP6 Lab) has signed
1711 TSMC Foundry NDAs, and consequently there is no impediment there, either.
1712
1713 Sorbonne Université (SU) is a multidisciplinary, research-intensive
1714 and world class academic institution. It was created on January 1st
1715 2018 as the merger of two first-class research intensive universities,
1716 UPMC (University Pierre and Marie Curie) and Paris-Sorbonne. Sorbonne
1717 Université is now organized with three faculties: humanities, medicine
1718 and science each with the wide-ranging autonomy necessary to conduct
1719 its ambitious programs in both research and education. SU counts 53,500
1720 students, 3,400 professor-researchers and 3,600 administrative and
1721 technical staff members. SU is intensively engaged in European research
1722 projects (163 FP7 projects and 195 H2020 projects). Its computer
1723 science laboratory, LIP6, is internationally recognized as a leading
1724 research institute.
1725
1726 LIP6 is a Joint Research Unit of both SU (Sorbonne Université)
1727 and CNRS. Both entities invest resources within LIP6 so CNRS is then
1728 an Affiliated Entity linked to SU. According to SU-CNRS agreement
1729 regarding LIP6, SU, as a full partner, manages the grant for its
1730 Affiliated Entity, CNRS.
1731
1732 RED Semiconductor Ltd has been established as a commercialisation vehicle,
1733 sharing the Libre principles of the core Libre-SOC team and bringing
1734 Semiconductor industry commercial management and technology experience.
1735 This includes the founders of two successful semiconductor companies
1736 and a public company chairman. There is also a cross directorship of
1737 Luke Leighton (of Libre-SOC) giving the company an extensive technology
1738 market and leadership experience.
1739
1740 NLnet is a Netherlands based public benefit organisation that brings
1741 to the table over 35 years of European internet history and well over
1742 two decades of unique real-world experience in funding and supporting
1743 bottom up internet infrastructure projects around the world - engaging
1744 some of the best independent researchers and developers. NLnet has
1745 funded essential work on important infrastructure parts of the internet,
1746 from the technologies with which the answers from the DNS root of the
1747 internet can now be trusted, all the way up to key standards for email
1748 security, transport layer security, email authenticity, and a lot more
1749 - on virtually every layer of the internet, from securing core routing
1750 protocols to browser security plugins, from firmware security to open
1751 source LTE networks.
1752
1753 Most recently NLnet is hosting the NGI0 Discovery, NGI0 PET and NGI
1754 Assure open calls as part of the Next Generation Internet research and
1755 development initiative, of which NLnet supports 300+ open source software,
1756 open hardware and open standards projects to build a more resilient,
1757 sustainable and trustworthy internet.
1758
1759 NLnet, a Stichting / Foundation, has been Libre-SOC’s funding source
1760 from the beginning and fundamentally understands our technology and
1761 direction of travel. As well as providing augmentation under existing
1762 EU Grants funding for technology opportunities that we will benefit from
1763 but are yet to be identified, they are a fundamental sounding board that
1764 will be invaluable to the project moving forward.
1765
1766 Regarding the extreme high-end computing resources necessary to complete
1767 the exceptionally-demanding task of VLSI development and Layout, we
1768 find that high-end modern laptops and desktop computers (with 64 to
1769 256 GB of RAM) are perfectly adequate. However in the event that our
1770 immediately-accessible computing resources are not adequate, both Sorbonne
1771 Université (LIP6 and CNRS) and Libre-SOC qualify for access to Fed4Fire
1772 (https://www.fed4fire.eu/- grant agreement No 732638) which gives us
1773 direct access to large clusters (100+) high-end servers. Additionally,
1774 we are specifying some of these high-end computers in our budget, and
1775 the software to run on them is entirely Libre-Licensed and within our
1776 combined experience to deploy.
1777
1778 We have established that Embecosm Gmbh and Vrull.eu are some of the
1779 world's leading experts in Compiler Technology. We will put out to
1780 tender a Contract with an initial evaluation phase, followed by a TRL
1781 4/5 Research phase for the prerequisite compilers (gcc, llvm, Kazan,
1782 MESA3D) necessary to support the core design work.
1783
1784 The OpenPOWER Foundation is a part of the Linux Foundation,
1785 and is directly responsible for the long-term protection
1786 and evolution of the Power ISA. Members include IBM, Google,
1787 NVidia, Raptor Engineering, University of Oregon and many more.
1788 https://openpowerfoundation.org/membership/current-members/.
1789
1790 The Chair of the newly-formed ISA Working Group is Paul Mackerras, and
1791 the Technical Chair is Toshaan Bharvani. Both of these people have
1792 been kindly attending bi-weekly meetings with the Libre-SOC Team for
1793 over 18 months, and we have kept them apprised of ongoing developments,
1794 particularly with the Draft SVP64 ISA Extension. They are both going
1795 out of their way to regularly advise us on how to go about a successful
1796 RFC Process for SVP64, and we deeply appreciate their support.
1797
1798 Helix Technology's involvement, as a potential customer and potential
1799 user of the Libre-SOC technology, will give focus to the deliverable of
1800 the project. They have world-leading expertise in Antenna Technology,
1801 and in the mathematics behind the Signal Processing required for
1802 GNSS/GPS. We have deliberately selected them to ensure the ambition of
1803 our overall project.
1804
1805 We therefore have a cohesive cooperative team of experience from concept
1806 to customer product and a supporting cast of specialist technical support
1807 that are an established practiced team.
1808
1809 As a last point: the creation of the teams for this project is critical
1810 for RED Semiconductors Limited and Libre-SOC. We have the benefit of
1811 having the core of an International Technology Headhunter Research
1812 Team amongst the directors of RED Semiconductor Limited, giving us
1813 the capability to ensure the project is fully manned in the required
1814 timescales without the need to externally resource recruitment services,
1815 and this is included in RED’s management manpower.
1816