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