├── .gitignore ├── CONTRIBUTING.md ├── LICENSE ├── LICENSE.CC-BY-SA-4.0 ├── README.md ├── charter.md ├── ecosystem ├── README.md ├── ashling.md ├── embecosm.md ├── ide.md ├── imperas.md ├── os.md ├── simulation.md ├── thales.md └── toolchains.md ├── meetings ├── 2020 │ ├── 2020-05-11-agenda.md │ ├── 2020-05-11-minutes.md │ ├── 2020-06-08-agenda.md │ ├── 2020-06-08-minutes.md │ ├── 2020-07-13-agenda.md │ ├── 2020-07-13-minutes.md │ ├── 2020-08-10-agenda-a.md │ ├── 2020-08-10-agenda-b.md │ ├── 2020-08-10-minutes-a.md │ ├── 2020-08-10-minutes-b.md │ ├── 2020-09-14-agenda.md │ ├── 2020-09-14-minutes.md │ ├── 2020-10-01-minutes.md │ ├── 2020-10-12-agenda.md │ ├── 2020-10-12-minutes.md │ ├── 2020-11-09-agenda.md │ ├── 2020-11-09-minutes.md │ ├── 2020-12-14-agenda.md │ └── 2020-12-14-minutes.md ├── 2021 │ ├── 2021-01-11-agenda.md │ ├── 2021-01-11-minutes.md │ ├── 2021-02-08-agenda.md │ ├── 2021-02-08-minutes.md │ ├── 2021-03-08-agenda.md │ ├── 2021-03-08-minutes.md │ ├── 2021-04-12-agenda.md │ ├── 2021-04-12-minutes.md │ ├── 2021-05-10-agenda.md │ ├── 2021-05-10-minutes.md │ ├── 2021-06-14-agenda.md │ ├── 2021-06-14-minutes.md │ ├── 2021-06-21-agenda.md │ ├── 2021-06-21-minutes.md │ ├── 2021-07-12-agenda.md │ ├── 2021-07-12-minutes.md │ ├── 2021-08-09-agenda.md │ ├── 2021-08-09-minutes.md │ ├── 2021-09-13-agenda.md │ ├── 2021-09-13-minutes.md │ ├── 2021-10-11-agenda.md │ ├── 2021-10-11-minutes.md │ ├── 2021-11-08-agenda.md │ └── 2021-11-08-minutes.md ├── 2022 │ ├── 2022-01-10-agenda.md │ ├── 2022-01-10-minutes.md │ ├── 2022-02-14-agenda.md │ ├── 2022-02-14-minutes.md │ ├── 2022-03-14-agenda.md │ ├── 2022-03-14-minutes.md │ ├── 2022-04-11-agenda.md │ ├── 2022-04-11-minutes.md │ ├── 2022-05-09-agenda.md │ ├── 2022-05-09-minutes.md │ ├── 2022-06-13-agenda.md │ ├── 2022-07-11-agenda.md │ ├── 2022-07-11-minutes.md │ ├── 2022-08-08-agenda.md │ ├── 2022-08-08-minutes.md │ ├── 2022-10-10-agenda.md │ ├── 2022-10-10-minutes.md │ ├── 2022-11-14-agenda.md │ └── 2022-11-14-minutes.md ├── 2023 │ ├── 2023-01-09-agenda.md │ ├── 2023-01-09-minutes.md │ ├── 2023-03-13-agenda.md │ ├── 2023-03-13-minutes.md │ ├── 2023-05-08-agenda.md │ ├── 2023-05-08-minutes.md │ ├── 2023-06-05-agenda.md │ ├── 2023-07-10-agenda.md │ ├── 2023-07-10-minutes.md │ ├── 2023-09-11-agenda.md │ ├── 2023-09-11-minutes.md │ ├── 2023-11-13-agenda.md │ └── 2023-11-13-minutes.md ├── 2024 │ ├── 2024-01-08-agenda.md │ ├── 2024-01-08-minutes.md │ ├── 2024-03-11-agenda.md │ ├── 2024-03-11-minutes.md │ ├── 2024-05-13-agenda.md │ ├── 2024-05-13-minutes.md │ ├── 2024-07-08-agenda.md │ ├── 2024-07-08-minutes.md │ ├── 2024-09-09-agenda.md │ ├── 2024-09-09-minutes.md │ ├── 2024-11-11-agenda.md │ └── 2024-11-11-minutes.md ├── 2025 │ ├── 2025-01-13-agenda.md │ ├── 2025-01-13-minutes.md │ ├── 2025-03-10-agenda.md │ └── 2025-03-10-minutes.md ├── README.md └── supplementary-materials │ ├── 2021 │ └── imperas-models-for-openhw-sw-developers-feb21-0.pdf │ ├── 2020.07 - Eclipse IoT and Eclipse Edge Native Overview-14-sep-2020.pdf │ ├── 2020.09 - OSDForum - Being Productive with Open Source Eclipse Development Tools-14-sep-2020.pdf │ ├── 2020.11 - FreeRTOS.pdf │ ├── 2020.11 - Rust for CORE-V.pdf │ └── SW TG Approaches Aug 10 2020.ppt ├── planning ├── gnu-toolchain-effort-estimate-13-jul-2020.md └── openhw-ide-requirement.md ├── projects ├── README.md ├── clang-llvm │ ├── 2020 │ │ └── monthly-report-2020-12-14.md │ ├── 2021 │ │ ├── monthly-report-2021-01-11.md │ │ ├── monthly-report-2021-02-08.md │ │ ├── monthly-report-2021-03-08.md │ │ ├── monthly-report-2021-04-12.md │ │ ├── monthly-report-2021-05-10.md │ │ ├── monthly-report-2021-06-14.md │ │ └── monthly-report-2021-07-12.md │ ├── 2022 │ │ └── monthly-report-2022-08-08.md │ ├── 2023 │ │ ├── monthly-report-2023-01-09.md │ │ ├── monthly-report-2023-02-13.md │ │ ├── monthly-report-2023-03-13.md │ │ ├── monthly-report-2023-05-08.md │ │ ├── monthly-report-2023-06-05.md │ │ ├── monthly-report-2023-07-14.md │ │ ├── monthly-report-2023-08-16.md │ │ ├── monthly-report-2023-09-12.md │ │ ├── monthly-report-2023-10-12.md │ │ ├── monthly-report-2023-11-13.md │ │ └── monthly-report-2023-12-13.md │ ├── 2024 │ │ ├── monthly-report-2024-01-08.md │ │ ├── monthly-report-2024-03-14.md │ │ ├── monthly-report-2024-04-22.md │ │ └── monthly-report-2024-05-13.md │ └── README.md ├── freertos │ ├── 2020 │ │ └── monthly-report-14-dec-20.md │ ├── 2021 │ │ ├── monthly-report-08-aug-21.md │ │ ├── monthly-report-08-feb-21.md │ │ ├── monthly-report-08-march-21.md │ │ ├── monthly-report-08-nov-21.md │ │ ├── monthly-report-10-may-21.md │ │ ├── monthly-report-11-jan-21.md │ │ ├── monthly-report-11-oct-21.md │ │ ├── monthly-report-12-april-21.md │ │ ├── monthly-report-12-july-21.md │ │ ├── monthly-report-13-sept-21.md │ │ └── monthly-report-14-june-21.md │ ├── 2022 │ │ ├── monthly-report-08-aug-22.md │ │ ├── monthly-report-09-may-22.md │ │ ├── monthly-report-10-jan-22.md │ │ ├── monthly-report-10-oct-22.md │ │ ├── monthly-report-11-april-22.md │ │ ├── monthly-report-11-july-22.md │ │ ├── monthly-report-14-feb-22.md │ │ └── monthly-report-14-march-22.md │ ├── 2023 │ │ ├── monthly-report-13-feb-23.md │ │ └── monthly-report-13-nov-23.md │ └── README.md ├── gnu-tools │ ├── 2020 │ │ ├── gnu-tools-update-14-sep-2020.pdf │ │ ├── monthly-report-2020-10-12.md │ │ ├── monthly-report-2020-11-09.md │ │ ├── monthly-report-2020-12-14.md │ │ └── two-week-update-report-2020-11-27.md │ ├── 2021 │ │ ├── monthly-report-2021-01-10.md │ │ ├── monthly-report-2021-02-08.md │ │ ├── monthly-report-2021-03-08.md │ │ ├── monthly-report-2021-04-09.md │ │ ├── monthly-report-2021-05-10.md │ │ ├── monthly-report-2021-06-14.md │ │ ├── monthly-report-2021-07-12.md │ │ ├── monthly-report-2021-08-09.md │ │ ├── monthly-report-2021-09-13.md │ │ ├── monthly-report-2021-10-11.md │ │ └── monthly-report-2021-11-8.md │ ├── 2022 │ │ ├── monthly-report-2022-02-14.md │ │ ├── monthly-report-2022-03-14.md │ │ ├── monthly-report-2022-04-11.md │ │ ├── monthly-report-2022-05-09.md │ │ └── monthly-report-2022-08-08.md │ ├── 2023 │ │ ├── monthly-report-2023-01-09.md │ │ ├── monthly-report-2023-02-13.md │ │ ├── monthly-report-2023-03-13.md │ │ ├── monthly-report-2023-04-10.md │ │ ├── monthly-report-2023-05-08.md │ │ ├── monthly-report-2023-06-05.md │ │ ├── monthly-report-2023-07-10.md │ │ ├── monthly-report-2023-08-14.md │ │ ├── monthly-report-2023-09-11.md │ │ ├── monthly-report-2023-10-09.md │ │ ├── monthly-report-2023-11-13.md │ │ └── monthly-report-2023-12-11.md │ ├── 2024 │ │ ├── monthly-report-2024-01-08.md │ │ └── monthly-report-2024-05-13.md │ ├── README.md │ └── additional-materials │ │ └── supplementary-notes.md ├── hal │ ├── 2021 │ │ ├── .gitignore │ │ ├── monthly-report-2021-04-12.md │ │ ├── monthly-report-2021-05-10.md │ │ ├── monthly-report-2021-06-14.md │ │ ├── monthly-report-2021-07-12.md │ │ └── monthly-report-2021-08-09.md │ ├── 2022 │ │ ├── 2022-02-10-HAL-Reqiurements-minutes.md │ │ ├── monthly-report-2022-05-09.md │ │ ├── monthly-report-2022-06-13.md │ │ ├── monthly-report-2022-07-11.md │ │ └── monthly-report-2022-12-12.md │ ├── 2023 │ │ └── monthly-report-2023-01-09.md │ ├── HAL_Comparison.md │ └── README.md ├── ide │ ├── 2021 │ │ ├── monthly-report-2021-02-08.md │ │ ├── monthly-report-2021-03-08.md │ │ ├── monthly-report-2021-04-12.md │ │ ├── monthly-report-2021-06-11.md │ │ ├── monthly-report-2021-07-12.md │ │ ├── monthly-report-2021-08-09.md │ │ ├── monthly-report-2021-09-13.md │ │ ├── monthly-report-2021-11-08.md │ │ └── monthly-report-2021-12-13.md │ ├── 2022 │ │ └── monthly-report-2021-02-14.md │ └── README.md ├── qemu │ ├── 2022 │ │ ├── monthly-report-2022-08-08.md │ │ ├── monthly-report-2022-09-12.md │ │ └── monthly-report-2022-10-10.md │ └── 2023 │ │ ├── monthly-report-2023-01-09.md │ │ └── monthly-report-2023-03-13.md ├── sdk │ ├── 2022 │ │ ├── 2022-02-14-report.md │ │ ├── 2022-03-14-report.md │ │ ├── 2022-05-09-report.md │ │ ├── 2022-06-13-report.md │ │ ├── 2022-07-11-report.md │ │ ├── 2022-08-08-report.md │ │ ├── 2022-09-12-report │ │ ├── 2022-10-10-report │ │ ├── 2022-11-14-report │ │ └── 2022-4-11-report.md │ ├── 2023 │ │ ├── 05-06-2023-report.md │ │ ├── 08-05-2023-report.md │ │ ├── 09-01-2023-report.md │ │ ├── 10-07-2023-report.md │ │ ├── 11-09-2023-report.md │ │ ├── 13-02-2023-report.md │ │ ├── 13-03-2023-report.md │ │ └── 13-11-2023-report.md │ └── 2024 │ │ └── 08-01-2024-report.md └── verilator │ └── 2023 │ ├── 2023-09-11-verilator-modeling-report.md │ └── 2023-11-13-verilator-modeling-report.md └── specifications ├── README.md ├── corev-builtin-spec.md └── corev-isa-extension-naming.md /.gitignore: -------------------------------------------------------------------------------- 1 | # Ignore editor backup files 2 | *~ 3 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group 2 | 3 | This is the main repository for the [OpenHW 4 | Group](https://www.openhwgroup.org/) Software Task Group. Our work is governed by our [Charter](charter.md). 5 | 6 | ## Commercial ecosystem for CORE-V software 7 | 8 | The #1 goal in our charter is to create a thriving commercial ecosystem for CORE-V software tools, models and operating systems, both open source and proprietary. We thus provide our [list of CORE-V software providers](ecosystem/README.md). If your company is missing and you think you should be there, please submit a pull request with your details added. 9 | 10 | ## Contributing 11 | 12 | We highly appreciate community contributions. At present the most valuable contributions are to our meetings, mailing list and Mattermost discussion groups as we plan the work of the group. 13 | 14 | In the future we shall have specific projects. Individual work-items within a project will be defined as issues with a task label and pull requests to contribute to those tasks are welcomed. 15 | 16 | ### Contribution guidelines 17 | 18 | The Open Hardware Group follows the [Eclipse Development Process](https://www.eclipse.org/projects/handbook/#edp). Our practical approach to this can be found in the file [CONTRIBUTING.md](CONTRIBUTING.md). 19 | 20 | The key points when submitting a pull request are as follows. 21 | 22 | - Smaller commits containing sets of changes which are related are easier to review. Larger contributions are best split into several smaller commits. 23 | - Explanatory commit messages help us understand your work when reviewing. While we don't have separate ChangeLogs, the [GNU ChangeLog](https://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs) format provides a useful discipline for structuring commit messages, with an overview of the changes and then details for each file and function that has been changed. 24 | - Don't forget to sign your commits (the `-s` flag to `git commit`) so we know it is your work! 25 | - After reviewing you may need to make some changes. To help keep a clean commit history, please rebase your branch on `master` after making the changes. Just ask if you need help on doing this. 26 | -------------------------------------------------------------------------------- /charter.md: -------------------------------------------------------------------------------- 1 | # OpenHW Group Software Task Group Charter 2 | 3 | ## Ratification status 4 | 5 | Version 1: Ratified by the Software TG 13 July 2020, pending 6 | confirmation by ballot of the TWG. 7 | 8 | ## Responsibilities 9 | 10 | The software task group is responsible for the following parts of the OpenHW Group ecosystem. This includes direct support for the CORE-V instruction set extensions and a process to support users' custom instruction set extensions. 11 | 12 | - Compiler tool chains (GNU, LLVM, proprietary) and Operating systems (RTOS, *nix, *bsd) 13 | - the compiler tool chain includes the assembler, linker, debugger and libraries as well as the compiler. 14 | - Processor and platform models (ISS, cycle accurate, QEMU, OVPSim) 15 | - IDEs (Eclipse family, PlatformIO, proprietary), their integration with the debug environment and support tools 16 | - Benchmarking (specifically including Embench) 17 | - Demonstration applications, both bare metal and for specific operating systems. 18 | - Support of the software ecosystem for the two OpenHW Group reference platforms, one MCU class, one APU class. 19 | 20 | ## Goals 21 | 22 | The software task group has the following two goals. 23 | 24 | 1. To create a thriving commercial ecosystem for CORE-V software tools, models and operating systems. 25 | 2. To see those tools, models and operating systems which are open source maintained as part of official upstream distributions. 26 | 27 | ## How we achieve our goals 28 | 29 | We expect the work to be achieved in two ways. 30 | 31 | - Contributions in kind from member companies. 32 | - Commercial development driven by CORE-V users. 33 | 34 | The work will need to be carried out by the wider OpenHW community and others. The role of the Software Task Group is to be the "shepherd" of this activity. 35 | 36 | **Note.** Because this is a very large task, the Software Task Group will need to set priorities, with early selection of the software to be supported first. 37 | 38 | ## How we measure progress 39 | 40 | We identify one short term measure of progress. 41 | 42 | - Meeting the needs of the Verification Task Group 43 | 44 | Strategic progress will be measured in the following ways. 45 | 46 | - How many commercial offerings for tools are seen. 47 | - Acceptance of open source CORE-V tools upstream. 48 | -------------------------------------------------------------------------------- /ecosystem/README.md: -------------------------------------------------------------------------------- 1 | # The CORE-V Software Ecosystem 2 | 3 | CORE-V will rely on developing a vibrant commercial ecosystem for software, both proprietary and open source. This will ensure that designgers of CORE-V based projects can always find the software and software services they need to support their product development. 4 | 5 | ## Software by supplier 6 | 7 | | Supplier | Product type | License | Description | 8 | |:-------- |:-------------|:-------:|:----------- | 9 | | [Ashling](ashling.md) | [IDE/Debug](ide.md) | Proprietary | [RiscFree](ashling.md#riscfree) | 10 | | [Embecosm](embecosm.md) | [Tool chain and libraries](toolchains.md) | Open Source | [GNU tools](embecosm.md#core-v-gnu-tool-chains-and-services) | 11 | | | | Open source | [Clang/LLVM tools](embecosm.md#core-v-clangllvm-tool-chains-and-services) | 12 | | [Imperas](imperas.md) | [Simulation and modeling](simulation.md) | Proprietary | [OVPSim](imperas.md#ovpsim) | 13 | | [Thales](thales.md) | [Tool chain and libraries](toolchains.md) | Open Source | [GNU tools](thales.md#gnu-tool-chains) | 14 | 15 | ## Software by product/service type 16 | 17 | | Product type | Supplier | License | Description | 18 | |:------------ |:---------|:-------:|:----------- | 19 | | [IDE/Debug](ide.md) | [Ashling](ashling.md) | Proprietary | [RiscFree](ashling.md#riscfree) | 20 | | [Operating systems](os.md) | | | | 21 | | [Simulation and modeling](simulation.md) | [Imperas](imperas.md) | Proprietary | [OVPSim](imperas.md#ovpsim) | 22 | | [Tool chain and libraries](toolchains.md) | [Embecosm](#embecosm.md) | Open Source | [GNU tools](embecosm.md#core-v-gnu-tool-chains-and-services) | 23 | | | | Open source | [Clang/LLVM tools](embecosm.md#core-v-clangllvm-tool-chains-and-services) | 24 | | | [Thales](thales.md) | Open Source | [GNU tools](thales.md#gnu-tool-chains) | 25 | 26 | ## Add your company 27 | 28 | If your company is missing, please submit a pull requests. The only 29 | requirements are: 30 | 31 | 1. this must be CORE-V software; 32 | 2. the software must be suitable for use in commercial development; and 33 | 3. the software must be maintained. 34 | -------------------------------------------------------------------------------- /ecosystem/ashling.md: -------------------------------------------------------------------------------- 1 | # Ashling 2 | 3 | Ashling is a global, world-class technology partner providing integrated 4 | solutions includng tools and design services that are at the heart of the 5 | embedded environment. 6 | 7 | ## RiscFree 8 | 9 | RiscFree™ is Ashling’s Eclipse-based Integrated Development Environment (IDE) for RISC-V and provides a complete, seamless environment for RISC-V software development. 10 | 11 | * [product page](https://www.ashling.com/ashling-riscv/) 12 | -------------------------------------------------------------------------------- /ecosystem/embecosm.md: -------------------------------------------------------------------------------- 1 | # Embecosm 2 | 3 | Delivering open source software tool chain and embedded operating system 4 | services. 5 | 6 | # CORE-V GNU tool chains and services 7 | 8 | Pre-built CORE-V GNU tool chains, scripts, sources and test results 9 | 10 | * [download page](https://www.embecosm.com/resources/tool-chain-downloads/#corev) 11 | 12 | # CORE-V Clang/LLVM tool chains and services 13 | 14 | Pre-built generic RISC-V Clang/LLVM tool chains, scripts, sources and test results suitable for use with CORE-V. 15 | 16 | * [download page - stable versions](https://www.embecosm.com/resources/tool-chain-downloads/#riscv-stable) 17 | * [download page - development versions](https://www.embecosm.com/resources/tool-chain-downloads/#riscv) 18 | -------------------------------------------------------------------------------- /ecosystem/ide.md: -------------------------------------------------------------------------------- 1 | # IDE and Debug Suppliers 2 | 3 | | Supplier | License | Description | 4 | |:---------|:-------:|:----------- | 5 | | [Ashling](ashling.md) | Proprietary | [RiscFree](ashling.md#riscfree) | 6 | -------------------------------------------------------------------------------- /ecosystem/imperas.md: -------------------------------------------------------------------------------- 1 | # Imperas 2 | 3 | Welcome to Imperas - revolutionizing embedded software solutions. 4 | 5 | # OVPSim 6 | 7 | riscvOVPsim allows the development and debug of code for the target RISC-V processor on an x86 host PC with the minimum of setup and effort. It simply requires the cross compilation of your application and running riscvOVPsim with an argument to specify the name of the application object. 8 | 9 | * [product page](https://www.imperas.com/riscvovpsim-free-imperas-riscv-instruction-set-simulator) 10 | -------------------------------------------------------------------------------- /ecosystem/os.md: -------------------------------------------------------------------------------- 1 | # Operating systems 2 | 3 | At present there are no suppliers of operating systems listed. 4 | -------------------------------------------------------------------------------- /ecosystem/simulation.md: -------------------------------------------------------------------------------- 1 | # Simulation and Modeling Suppliers 2 | 3 | | Supplier | License | Description | 4 | |:---------|:-------:|:----------- | 5 | | [Imperas](imperas.md) | Proprietary | [OVPSim](imperas.md#ovpsim) | 6 | -------------------------------------------------------------------------------- /ecosystem/thales.md: -------------------------------------------------------------------------------- 1 | # Thales 2 | 3 | Leader in the aerospace, transport and defense & security segments. 4 | 5 | # GNU tool chains 6 | 7 | Scripts for building CORE-V GNU tool chains from upstream sources, 8 | particularly for the CORE-V CVA6 processors. 9 | 10 | * [Repository link](https://github.com/ThalesGroup/cva6-tools) 11 | -------------------------------------------------------------------------------- /ecosystem/toolchains.md: -------------------------------------------------------------------------------- 1 | # CORE-V Tool Chains and Libraries 2 | 3 | | Supplier | License | Description | 4 | |:-------- |:-------:|:----------- | 5 | | [Embecosm](embecosm.md) | Open Source | [GNU tools](embecosm.md#core-v-gnu-tool-chains-and-services) | 6 | | | Open source | [Clang/LLVM tools](embecosm.md#core-v-clangllvm-tool-chains-and-services) | 7 | | [Thales](thales.md) | Open Source | [GNU tools](thales.md#gnu-tool-chains) | 8 | 9 | ## GNU tool chain open source components 10 | 11 | * [binutils-gdb](https://github.com/openhwgroup/corev-binutils-gdb) 12 | * [gcc](https://github.com/openhwgroup/corev-gcc) 13 | * [newlib](https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git) 14 | (upstream) 15 | 16 | ## Clang/LLVM tool chain open source components 17 | 18 | * [llvm-project](https://github.com/llvm/llvm-project) 19 | (upstream) 20 | -------------------------------------------------------------------------------- /meetings/2020/2020-05-11-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | **Date:** Monday 11 May 2020 4 | 5 | **Time:** 6 | 7 | - 07:00-08:00 Pacific Time 8 | - 10:00-11:00 East Coast Time 9 | - 15:00-16:00 UK Time 10 | - 16:00-17:00 Central European Time 11 | - 22:00-23:00 Beijing Time 12 | 13 | **Location:** Zoom meeting 14 | 15 | - [us02web.zoom.us/j/85194416761](https://us02web.zoom.us/j/85194416761) 16 | - Meeting ID: 851 9441 6761 17 | - Find your local number: [us02web.zoom.us/u/kcVlqVA9vi](https://us02web.zoom.us/u/kcVlqVA9vi) 18 | 19 | **Chair:** Jeremy Bennett 20 | 21 | **Vice-Chair:** Yunhai Syh 22 | 23 | # Agenda 24 | 25 | 1. Introduction 26 | 27 | 2. Charter 28 | 29 | Our first objective is to agree our charter. An outline will be presented for discussion at the meeting. We should agree 30 | - what we are responsible for 31 | - what our goals are 32 | - how we will achieve those goals 33 | - how we will measure progress and success 34 | 35 | 3. Migration of software repositories 36 | 37 | Notwithstanding our charter, OpenHW Group has agreed to take responsibility for the PULP software repositories. The existing repositories are three years out of date with respect to the upstream projects. The following suggested approach is for discussion. It addresses the subject of the GCC tool chain, but the approach should be capable of being generalized to other software. 38 | - all tool components should be moved upstream. 39 | - for GCC, this is binutils-gdb, gcc, newlib and glibc 40 | - OpenHW should maintain only a repository with scripts to allow users to build an OpenHW version of the tool chain from source. 41 | 42 | Volunteers with expertise in upstream binutiles, GDB, GCC, newlib and gLibC are sought. 43 | 44 | 4. Dates for future meetings 45 | 46 | It is proposed that the group meet monthly at 07:00 Pacific Time on the second Monday of the month. Discussion between times will be via Mattermost and mailing list (the latter to be set up). The monthly meetings will focus on taking decisions to progress the work of the charter. Where needed, additional meetings can be organized ad hoc. The dates for the next 6 meetings will be. 47 | 48 | - 11 May 2020 (this meeting) 49 | - 8 Jun 2020 50 | - 13 Jul 2020 51 | - 10 Aug 2020 52 | - 14 Sep 2020 53 | - 12 Oct 2020 54 | 55 | 5. AOB 56 | 57 | 58 | Jeremy Bennett 59 | -------------------------------------------------------------------------------- /meetings/2020/2020-06-08-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | **Date:** Monday 8 Jun 2020 4 | 5 | **Time:** 6 | 7 | - 07:00-08:00 Pacific Time 8 | - 10:00-11:00 East Coast Time 9 | - 15:00-16:00 UK Time 10 | - 16:00-17:00 Central European Time 11 | - 22:00-23:00 Beijing Time 12 | 13 | **Location:** Zoom meeting 14 | 15 | - [us02web.zoom.us/j/85194416761](https://us02web.zoom.us/j/85194416761) 16 | - Meeting ID: 851 9441 6761 17 | - Find your local number: [us02web.zoom.us/u/kcVlqVA9vi](https://us02web.zoom.us/u/kcVlqVA9vi) 18 | 19 | **Chair:** Jeremy Bennett 20 | 21 | **Vice-Chair:** Yunhai Syh 22 | 23 | ## Agenda 24 | 25 | 1. Review of actions 26 | 27 | - **Jeremy Bennett (lead), Yunhai Syh, Jim Parisien:** Prepare candidate charter in light of comments from the meeting for review on the mailing list and ratification at the next meeting. 28 | 29 | - **Craig Blackmore:** Carry out a detailed analysis of the work required to migrate the tool chains to the current upstream baseline and then submit the changes for incorporation. 30 | 31 | 2. Charter 32 | 33 | A draft charter will be presented, based on the comments made at the inaugural meeting. Comments are invited at the meeting. The charter will then be circulated on the mailing list for ratification. 34 | 35 | 3. Tool chain support for the verification group 36 | 37 | As a matter of urgency, the CORE-V verification group asked for assistance with a tool chain set up for their [Test Program Environment](https://core-v-docs-verif-strat.readthedocs.io/en/latest/test_program_environment.html). 38 | 39 | Craig Blackmore has worked on this and will report on progress. 40 | 41 | 4. Program of work to upstream CORE-V tool chains 42 | 43 | Craig Blackmore will give an update. **Note.** The need for urgent support of verification has limited Craig's availability to work on this. 44 | 45 | 5. AOB 46 | 47 | 6. Dates for future meetings 48 | 49 | The group meets monthly at 07:00 Pacific Time on the second Monday of the month. 50 | 51 | - 13 Jul 2020 52 | - 10 Aug 2020 53 | - 14 Sep 2020 54 | - 12 Oct 2020 55 | - 09 Nov 2020 56 | - 14 Dec 2020 57 | 58 | 59 | Jeremy Bennett 60 | -------------------------------------------------------------------------------- /meetings/2020/2020-08-10-agenda-a.md: -------------------------------------------------------------------------------- 1 | # Joint OpenHW Software and Cores Task Groups Meeting Agenda 2 | 3 | Monday 10 August 2020 4 | 5 | - 05:00-05:30 Pacific Time 6 | - 08:00-08:30 East Coast Time 7 | - 13:00-13:30 UK Time 8 | - 14:00-14:30 Central European Time 9 | - 20:00-20:30 Beijing Time 10 | 11 | ## Location 12 | 13 | Zoom meeting 14 | 15 | - [us02web.zoom.us/j/84309061282](https://us02web.zoom.us/j/84309061282?pwd=MHZYTjBZN21uM2Y0eU8rd1JQMHNHZz09) 16 | - Meeting ID: 843 0906 1282 17 | - Passcode: 315236 18 | - Find your local number: [us02web.zoom.us/u/kc8GipE4dH](https://us02web.zoom.us/u/kc8GipE4dH) 19 | 20 | # Agenda topics 21 | 22 | ## Register of attendance 23 | 24 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records are can be seen in the [program](https://github.com/openhwgroup/core-v-docs/tree/master/program) directory of the [core-v-docs repository](https://github.com/openhwgroup/core-v-docs). 25 | 26 | ## Priorities for GNU tool chain development 27 | 28 | Embecosm is committing 3 additional engineers to the project for the next 8 weeks to work on the GNU tool chain. @craigblackmore provided an initial plan (https://github.com/openhwgroup/core-v-sw/blob/master/planning/gnu-toolchain-effort-estimate-13-jul-2020.md). Just to achieve minimal support represents 15 engineer months of work, so we need to prioritise which extensions to work on first. 29 | 30 | 1. **Always enabled features** 31 | 32 | - bit manipulation (2 engineer months) 33 | - SIMD (5 engineer months) 34 | - post increment load/store (2 engineer months) 35 | - PULP ALU extensions (3 engineer months) 36 | - PULP immediate branch (1 engineer month) 37 | 38 | 2. **Optional features** 39 | 40 | - HW loops (2 engineer months) 41 | 42 | 3. **Tentative features** 43 | 44 | - Xpulpzfinx (2 engineer months + 8 engineer months to hand-code `libgcc`) 45 | - Xpulpcluster (2 engineer weeks) 46 | 47 | 4. Other features (not in CV32E40* spec) 48 | 49 | - pipeline model (2 engineer weeks) 50 | 51 | 5. Undocumented features (found in source code, no effort estimate) 52 | 53 | - custom relocations 54 | - custom `-m` options, many conflicting with upstream 55 | - custom `__attribute__ ((interrupt))` 56 | - overwriting multilib list 57 | 58 | Jeremy Bennett, Chair SW TG 59 | Arjan Bink, Chair Cores TG 60 | -------------------------------------------------------------------------------- /meetings/2020/2020-08-10-minutes-a.md: -------------------------------------------------------------------------------- 1 | # Combined OpenHW Software and Cores Task Group Meeting Minutes 2 | 3 | Monday 10 August 2020, 12:00 UTC 4 | 5 | ## Attendees 6 | 7 | See separate [attendance register](https://github.com/openhwgroup/core-v-docs/blob/master/program/TGSoftware_Attendance_2020.md) 8 | 9 | ## Summary of actions 10 | 11 | - **Jeremy Bennett:** Introduce the Embecosm team to Zbigniew Chamski 12 | - **Jeremy Bennett:** Request limitations of software support to be added to the next TWG meeting agenda. 13 | - **Craig Blackmore:** Produce definitive list of opcodes which are problem and share with the Cores TG. 14 | 15 | # Meeting topics 16 | 17 | ## Priorities for GNU tool chain development 18 | 19 | Question: Can we use other contributors beyond the Embecosm team? 20 | 21 | - yes 22 | - Zbigniew Chamski of Thales is working on CV64 tool chain support 23 | - there will be overlap of work between CV32 CV64 24 | 25 | **Action:** Jeremy Bennett to introduce Embecosm team to Zbigniew Chamski 26 | 27 | Proposed program of work 28 | 29 | - get existing PULP binutils-gdb tested (12 engineer weeks) 30 | - roll GCC patches forward to current top-of-tree (12 engineer weeks) 31 | - roll PULP binutils-gdb forward to current top-of-tree 32 | - not currently scheduled 33 | - will likely be CGEN based for efficiency 34 | 35 | Cores TG priorities (Arjan Bink) 36 | 37 | - don't spend time on bitmanip/SIMD 38 | - will be replaced by standard B/P extensions 39 | 40 | - bitmanip upstream is advanced 41 | - SIMD not so advanced (although Davide Schiavione noted it is a key differentiator) 42 | 43 | - no preference between post-increment, PULP ALU or immediate branch extensions 44 | - HW loop is now always enabled, and equial priority to previous items 45 | - tentatative things 46 | 47 | - Xpulpzfinx low priority 48 | - Xpulpcluster only one instruction 49 | 50 | - no comment on undocumented features 51 | 52 | - observe that upstream `interrupt` attribute may be suitable now 53 | 54 | Overall i) post-increment, ii) PULP ALU, iii) immediate branch and iv) HW loop extensions (total 8 engineer months work) have the same priority. Embecosm GCC team will choose from these to maximize return. 55 | 56 | Observations from Verification TG (Mike Thompson) 57 | 58 | - PULP extensions get best effort verification by end September 2020 59 | - will not be fully verified 60 | 61 | Arjan Bink noted that the next core will have none of these features, but will have a general extension interface. There will be no prepackaged extensions. 62 | 63 | - will want a process for supporting that with software 64 | 65 | Discussion of why have SIMD hardware without compiler support. 66 | 67 | - Jeremy Bennett and Arjan Bink argued that extensions cannot be promoted without tested compiler 68 | - Jeremy Bennett noted that there was the opportunity for commercially funded development by anyone choosing that extension 69 | - example of general extension process 70 | - Arjan Bink suggested we treat all extensions this way 71 | 72 | Arjan Bink noted that we need to raise with the TWG that two features will have no SW support. 73 | 74 | **Action:** Jeremy Bennett to get this added to the next TWG meeting agenda. 75 | 76 | There was a discussion that some instructions use reserved opcodes 77 | 78 | - may break code from the upstream compiler 79 | - will make upstreaming impossible 80 | - needs urgent agreement and should drive software priorities 81 | 82 | - avoid extensions with problems 83 | 84 | **Action:** Craig Blackmore to produce definitive list of opcodes which are problem and share with the Cores TG. 85 | -------------------------------------------------------------------------------- /meetings/2020/2020-10-01-minutes.md: -------------------------------------------------------------------------------- 1 | # Software TG : GNU Tools PPL review Meeting Minutes 2 | 3 | Thursday 1st October 2020, 17:00 (BST) 4 | 5 | ## Attendees 6 | 7 | - Jeremy Bennett, Embecosm (chair) 8 | - Jessica Mills, Embecosm (project manager) 9 | - Duncan Bees, OpenHW Group (program management oversight) 10 | - Simon Cook, Embecosm 11 | - Craig Blackmore, Embecosm 12 | - Ed Jones, Embecosm 13 | - John Martin, EMUS 14 | - Mary Bennett, Embecosm 15 | - Pietra Ferreira, Embecosm 16 | - William Jones, Embecosm 17 | 18 | Since this was a specialist meeting, it does not count towards the register of 19 | participants in the Software Task Group. 20 | 21 | ## Meeting Summary 22 | 23 | Members of the Software TG reviewed the draft Preliminary Project Proposal for CORE-V GNU Tool Chain development before the launch meeting. 24 | 25 | The draft Preliminary Project Proposal can be viewed at https://github.com/jeremybennett/core-v-docs/blob/jpb-gnu-tools-ppl/program/core-v-gnu-tools-ppl.md 26 | 27 | Phase 1 and 2 may be run in parallel (with Thales leading on phase 2) - subject to confirmation. 28 | 29 | Whether hardware will be developed which will use the CORE-V additional instructions is not yet known. Thus there may be no interest in the additional instructions and the project may not be required. 30 | 31 | As hardware may not exist for testing, code can be unstreamed having only been tested on a simulator 32 | 33 | ## Actions 34 | 35 | * Duncan Bees will add the topic of whether CV32E40P cores will be created which utilise the CORE-V additional instructions to the agenda for the upcoming TWG meeting. This must be confirmed before proceeding. 36 | 37 | * The proposal will be reviewed by the TWG on Monday 5th October 38 | 39 | * The Project Lauch (PL) will be at end October 2020 40 | -------------------------------------------------------------------------------- /meetings/2020/2020-10-12-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | Monday 12 October 2020 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 14:00-15:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 22:00-23:00 Beijing Time 11 | 12 | ## Location 13 | 14 | Zoom meeting 15 | 16 | - [us02web.zoom.us/j/85194416761](https://us02web.zoom.us/j/85194416761) 17 | - Meeting ID: 851 9441 6761 18 | - Find your local number: [us02web.zoom.us/u/kcVlqVA9vi](https://us02web.zoom.us/u/kcVlqVA9vi) 19 | 20 | # Agenda topics 21 | 22 | ## Register of attendance 23 | 24 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records are can be seen in the [program](https://github.com/openhwgroup/core-v-docs/tree/master/program) directory of the [core-v-docs repository](https://github.com/openhwgroup/core-v-docs). 25 | 26 | ## Review of actions 27 | 28 | - **Jeremy Bennett:** Submit preliminary project proposal for GNU Tools development to TWG meeting on 28 September 2020. 29 | 30 | - complete - see agenda item [Update from TWG](#update-from-twg). 31 | 32 | - **Jeremy Bennett:** Revise the commercial ecosystem page in light of comments for review via Mattermost, with a view to sign-off at next month's meeting. 33 | 34 | - in progress - see agenda item [Promoting the software ecosystems](#promoting-the-software-ecosystem). 35 | 36 | ## Update from TWG 37 | 38 | Report by the chair 39 | 40 | - approval of the CORE-V GNU Tools preliminary project proposal on 5 October 2020. 41 | - pending approval of the CORE-V IDE preliminary project proposal. 42 | - proposal from John Martin of EMUS for ISA extension support in the CV32E40P core. 43 | 44 | ## Reports from current projects 45 | 46 | Active projects will give a 5 minute status report each month. 47 | 48 | - CORE-V GNU Tools - Jessica Mills 49 | - CORE-V IDE - Alexander Fedorov 50 | 51 | - subject to Alexander being back from vacation 52 | 53 | ## New potential projects 54 | 55 | - CORE-V Clang/LLVM - Jean-Roch Coulon 56 | 57 | - Jean-Roch will outline his ideas for a project to develop Clang/LLVM support for CORE-V. If there is general aggreement from this meeting, he will prepare a preliminary project proposal for submission to TWG. 58 | 59 | ## Promoting the software ecosystem 60 | 61 | An initial proposal for presenting the commercial ecosystem within the main repository was presented last month. This was welcomed and many proposals were made to improve the framework. These improvements will be reviewed this month. 62 | 63 | ## AOB 64 | 65 | ## Dates for future meetings 66 | 67 | The group meets monthly at 07:00 Pacific Time on the second Monday of the month. 68 | 69 | - 09 Nov 2020 70 | - 14 Dec 2020 71 | - 11 Jan 2020 72 | - 08 Feb 2020 73 | - 08 Mar 2020 74 | - 12 Apr 2020 75 | - 10 May 2020 76 | - 14 Jun 2020 77 | - 12 Jul 2020 78 | - 09 Aug 2020 79 | - 13 Sep 2020 80 | - 11 Oct 2020 81 | - 08 Nov 2020 82 | - 13 Dec 2020 83 | 84 | Jeremy Bennett, Chair 85 | -------------------------------------------------------------------------------- /meetings/2020/2020-11-09-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | Monday 9 November 2020 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-24:00 Beijing Time 11 | 12 | ## Location 13 | 14 | Zoom meeting 15 | 16 | - [us02web.zoom.us/j/85194416761](https://us02web.zoom.us/j/85194416761) 17 | - Meeting ID: 851 9441 6761 18 | - Find your local number: [us02web.zoom.us/u/kcVlqVA9vi](https://us02web.zoom.us/u/kcVlqVA9vi) 19 | 20 | # Agenda topics 21 | 22 | ## Register of attendance 23 | 24 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records are can be seen in the [program](https://github.com/openhwgroup/core-v-docs/tree/master/program) directory of the [core-v-docs repository](https://github.com/openhwgroup/core-v-docs). 25 | 26 | ## Review of actions 27 | 28 | - **Zbigniew and Jean-Roch:** Prepare a preliminary project proposal for TWG 29 | on 26 October 2020. 30 | 31 | - see agenda item [Reports from current projects](#reports-from-current-projects). 32 | 33 | - **Jeremy Bennett:** Commit ecosystem to main `core-v-sw` repo. 34 | 35 | - complete. 36 | 37 | - **Zbigniew Chamski:** Make a pull request to add logos to the ecosystem. 38 | 39 | - Zbigniew to report. 40 | 41 | - **Jingliang (Leo) Wang:** Consider whether to add FORCE-RISCV ISG to the ecosystem. 42 | 43 | - Leo to report. 44 | 45 | ## Report back from TWG 46 | 47 | Report by the chair and Duncan Bees (5 minutes allocated). 48 | 49 | - request for more information on Clang/LLVM preliminary project proposal 50 | - FORCE-RISCV preliminary project proposal approved 51 | 52 | - supported as possible additional tool for assembler/linker verification 53 | 54 | ## Reports from current projects 55 | 56 | Active projects under the SW TG give a 5 minute status report each month. 57 | 58 | - CORE-V GNU Tools - Jessica Mills 59 | - CORE-V IDE - Alexander Fedorov 60 | - CORE-V Clang/LLVM - Jean-Roch Coulon 61 | 62 | ## New potential projects 63 | 64 | 5-10 minutes per project. 65 | 66 | - PlatformIO 67 | 68 | - Ivan Kravets, CEO of PlatformIO will present the technology and its potential as a CORE-V software project 69 | 70 | - FreeRTOS 71 | 72 | - Robert Balas of ETH Zürich will present FreeRTOS and explore what is needed to develop a CORE-V specific version. 73 | 74 | - Rust for CORE-V 75 | 76 | - Philipp Krones of Embecosm and lead of the Rust linter, Clippy, will present the technology, to explore whether there is interest from members in a CORE-V specific version. 77 | 78 | ## AOB 79 | 80 | ## Dates for future meetings 81 | 82 | The task group meets monthly at 07:00 Pacific Time on the second Monday of the month. 83 | 84 | - 14 Dec 2020 85 | - 11 Jan 2020 86 | - 08 Feb 2020 87 | - 08 Mar 2020 88 | - 12 Apr 2020 89 | - 10 May 2020 90 | - 14 Jun 2020 91 | - 12 Jul 2020 92 | - 09 Aug 2020 93 | - 13 Sep 2020 94 | - 11 Oct 2020 95 | - 08 Nov 2020 96 | - 13 Dec 2020 97 | 98 | Jeremy Bennett, Chair\ 99 | Yunhai Shang, Vice-Chair 100 | -------------------------------------------------------------------------------- /meetings/2021/2021-06-21-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | Monday 21 June 2021 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 14:00-15:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 22:00-23:00 Beijing Time 11 | 12 | ## Location 13 | 14 | Zoom meeting to consider only the Project Concept proposal for submission to 15 | TWG on Monday 28 June. **Note.** This is a different link to our regular meeting. 16 | 17 | - [us02web.zoom.us/j/88581208813?pwd=N0prdHlES0RNdzhrSXJ3NWxQSWkxdz09](https://us02web.zoom.us/j/88581208813?pwd=N0prdHlES0RNdzhrSXJ3NWxQSWkxdz09) 18 | - Meeting ID: 885 8120 8813 19 | - Find your local number: [us02web.zoom.us/u/kJ8AJCWyS](https://us02web.zoom.us/u/kJ8AJCWyS) 20 | 21 | # Agenda topics 22 | 23 | ## Register of attendance and introductions 24 | 25 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records are can be seen in the [program](https://github.com/openhwgroup/core-v-docs/tree/master/program) directory of the [core-v-docs repository](https://github.com/openhwgroup/core-v-docs). 26 | 27 | ## Hardware abstraction layer (45 minutes allocated) 28 | 29 | The requirements for this project will have been agreed at the meeting of 14 June 2021. The purpose of this meeting is to agree the project concept proposal for submission to the TWG on 28 June 2021. 30 | 31 | ## Dates for future meetings 32 | 33 | The task group meets monthly at 07:00 Pacific Time on the second Monday of the month. 34 | 35 | - 12 Jul 2021 36 | - 09 Aug 2021 37 | - 13 Sep 2021 38 | - 11 Oct 2021 39 | - 08 Nov 2021 40 | - 13 Dec 2021 41 | 42 | Jeremy Bennett, Chair\ 43 | Yunhai Shang, Vice-Chair 44 | -------------------------------------------------------------------------------- /meetings/2021/2021-06-21-minutes.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Minutes 2 | 3 | Monday 21 June 2021, 14:00 UTC 4 | 5 | Meeting to consider only the HAL Project Concept proposal for submission to TWG on Monday 28 June. 6 | 7 | ## Attendees and welcome new members 8 | 9 | See separate [attendance register](https://github.com/openhwgroup/core-v-docs/blob/master/program/TGSoftware_Attendance_2021.md) 10 | 11 | ## Summary of actions 12 | 13 | **Yunhai Shang** to lead finalizing the HAL Project Concept document via a PR on GitHub, for submission to the TWG on 28 June 2021. 14 | 15 | # Meeting topics 16 | 17 | ## Hardware abstraction layer 18 | 19 | A draft Project Concept was proposed and discussed. 20 | 21 | **Action** Yunhai Shang to lead finalizing the HAL Project Concept document via a PR on GitHub, for submission to the TWG on 28 June 2021. 22 | 23 | ## Dates for future meetings 24 | 25 | The task group meets monthly at 07:00 Pacific Time on the second Monday of the month. 26 | 27 | - 12 Jul 2021 28 | - 09 Aug 2021 29 | - 13 Sep 2021 30 | - 11 Oct 2021 31 | - 08 Nov 2021 32 | - 13 Dec 2021 33 | 34 | Jeremy Bennett, Chair\ 35 | Yunhai Shang, Vice-Chair 36 | -------------------------------------------------------------------------------- /meetings/2022/2022-02-14-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | Monday 14 February 2022 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-00:00 Beijing Time 11 | 12 | ## Location 13 | 14 | Zoom meeting. 15 | 16 | - [us02web.zoom.us/j/85194416761?pwd=M2kwRzNCUG82UFlJT0NMbnJPSXBCZz09](https://us02web.zoom.us/j/85194416761?pwd=M2kwRzNCUG82UFlJT0NMbnJPSXBCZz09) 17 | - Meeting ID: 851 9441 6761 18 | - Find your local number: [us02web.zoom.us/u/kuUW3yscL](https://us02web.zoom.us/u/kuUW3yscL) 19 | 20 | # Agenda topics 21 | 22 | ## Register of attendance and introductions 23 | 24 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records are can be seen in the [program](https://github.com/openhwgroup/core-v-docs/tree/master/program) directory of the [core-v-docs repository](https://github.com/openhwgroup/core-v-docs). 25 | 26 | ## Review of actions (15 minutes allocated) 27 | 28 | - **All** to suggest software projects to **Duncan Bees** for consideration for the roadmap. 29 | 30 | - **Olive Zhao** to convene a standalone meeting to discuss requirements for the HAL, which we bring in as many HAL experts as possible. Be sure to invite the AWS team (Richard Barry, Joe Julicher). 31 | 32 | - **Maxim Blinov** to roll forward GCC to include the B extension support. 33 | 34 | - **Maxim Blinov** assisted by **Duncan Bees** to take CORE-V GNU Tools project through Project Launch gate. 35 | 36 | - **Duncan Bees** to have conversation with Hugh O'Keeffe, Robert Balas, Shterana Shopova and Richard Barry about moving CORE-V FreeRTOS project to Project Launch gate. Meeting scheduled for 14 January at 15:00 UTC. 37 | 38 | - **Jeremy Bennett** to take CORE-V Verilator Modeling project through Project Launch gate. 39 | 40 | - **Greg Martin** to review issues [#149](https://github.com/openhwgroup/core-v-mcu/issues/149) and [#115](https://github.com/openhwgroup/core-v-mcu/issues/115) raised by Robert Balas for the FreeRTOS project. 41 | 42 | - Action held open pending confirmation of resolution. 43 | 44 | ## Report back from TWG (5 minutes allocated) 45 | 46 | Duncan Bees to report. 47 | 48 | ## Reports from current projects (15 minutes allocated) 49 | 50 | Active projects under the Software Task Group will have provided a written report in advance. We also have one project under the Hardware Task Group which also reports into us. Each project leader is asked to present any key issues for which community input from the meeting is required. Project leaders will also take any questions. 51 | 52 | - CORE-V IDE - Alexander Fedorov 53 | - CORE-V GNU Tools - Maxim Blinov 54 | - CORE-V FreeRTOS - Robert Balas and Shteryana Shopova 55 | - CORE-V Clang/LLVM - Philipp Krones and Zbigniew Chamski 56 | - Hardware Abstraction Layer - Yunhain Shang and Olive Zhao 57 | - Software Development Kit - Hugh O'Keefe 58 | - CORE-V Verilator modeling (HW TG project) - Jeremy Bennett 59 | 60 | ## AOB 61 | 62 | ## Dates for future meetings 63 | 64 | The task group meets monthly at 07:00 Pacific Time on the second Monday of the month. 65 | 66 | - 14 Mar 2022 67 | - 11 Apr 2022 68 | - 9 May 2022 69 | - 13 Jun 2022 70 | - 11 Jul 2022 71 | - 8 Aug 2022 72 | - 12 Sep 2022 73 | - 10 Oct 2022 74 | - 14 Nov 2022 75 | 76 | Noting how busy December can be, I have again proposed no meeting in that month. 77 | 78 | Jeremy Bennett, Chair\ 79 | Yunhai Shang, Vice-Chair 80 | -------------------------------------------------------------------------------- /meetings/2024/2024-11-11-minutes.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Minutes 2 | 3 | Monday 11 November 2024 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-00:00 Beijing Time 11 | 12 | ## Attendees and welcome new members 13 | 14 | See the separate [attendance register](https://github.com/openhwgroup/programs/blob/master/TWG-and-TG-Attendance-Tracking/TGSoftware_Attendance_2024.md) 15 | 16 | # Meeting topics 17 | 18 | ## Review of actions (5 minutes allocated) 19 | 20 | - **Paolo Savini** and **Chunyu Liao** to use upstream QEMU for CORE-V to test respectively the GNU and LLVM tool chains. 21 | - IN PROGRESS, **Paolo Savini** to review a Weiwei's work and update QEMU. 22 | 23 | ## Reports from current projects (10 minutes allocated) 24 | 25 | Active projects under the Software Task Group will have provided a written report in advance (see the [project specific directories](https://github.com/openhwgroup/core-v-sw/blob/master/projects) of the [core-v-sw](https://github.com/openhwgroup/core-v-sw) repository. We also have one project under the Hardware Task Group which also reports into us. 26 | 27 | Each project leader is asked to present any key issues for which community input from the meeting is required. Project leaders will also take any questions. 28 | 29 | - CORE-V GNU Tools for CV32E40PV2 - Nandni Jamnadas/Mary Bennett 30 | - Ongoing work to land the last patches. 31 | - CORE-V FreeRTOS - Joe Julicher 32 | - No further development. 33 | - CORE-V Clang/LLVM for CV32E40PV2 - Paolo Savini and Chunyu Liao 34 | - Ongoing work to land the last patches. 35 | - CORE-V SDK/IDE - Hugh O'Keefe and Promod Kumar 36 | - No further development. 37 | - CORE-V CV32E40PV2 Verilator modeling for software - Jeremy Bennett 38 | - No updates at the moment. 39 | - Vote pending on the project proposal. 40 | 41 | ## Review of previous topics (10 minutes allocated) 42 | 43 | - CVE20: 44 | - We might need a new project to for the CVE20 model. 45 | - No updates. 46 | 47 | - CVA6-Platform for SW development and regression - **Jonathan Balkind**, **Moiz Hussain**, **Redbeard**, **Flo Wohlrab**. 48 | - back-pressure from RISE. 49 | - smaller deliverables should have more success. 50 | - we'll go back with a proposal broken down into smaller projects/tasks. 51 | 52 | - Eclipse Theia & CDT Cloud. 53 | - no updates. 54 | 55 | ## Dates for future meetings 56 | 57 | The task group meets every two months at 15:00 UK Time on the second Monday of odd numbered months. On other even numbered months projects submit reports. 58 | 59 | | Date | Activity | 60 | | :---------- | :------------------------------------ | 61 | | 11 Nov 2024 | Meeting and report | 62 | | 9 Dec 2024 | Report only | 63 | | 13 Jan 2025 | Meeting and report | 64 | | 10 Feb 2025 | Report only | 65 | | 10 Mar 2025 | Meeting and report | 66 | | 14 Apr 2025 | Report only | 67 | 68 | 69 | ## AOB 70 | 71 | 72 | Paolo Savini, Chair 73 | -------------------------------------------------------------------------------- /meetings/2025/2025-01-13-minutes.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Minutes 2 | 3 | Monday 13 January 2025 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-00:00 Beijing Time 11 | 12 | ## Attendees and welcome new members 13 | 14 | See the separate [attendance register](https://github.com/openhwgroup/programs/blob/master/TWG-and-TG-Attendance-Tracking/TGSoftware_Attendance_2024.md) 15 | 16 | # Meeting topics 17 | 18 | ## Review of actions (5 minutes allocated) 19 | 20 | - **Paolo Savini** and **Chunyu Liao** to use upstream QEMU for CORE-V to test respectively the GNU and LLVM tool chains. 21 | - IN PROGRESS, **Paolo Savini** to review a Weiwei's work and update QEMU. 22 | 23 | ## Reports from current projects (10 minutes allocated) 24 | 25 | Active projects under the Software Task Group will have provided a written report in advance (see the [project specific directories](https://github.com/openhwgroup/core-v-sw/blob/master/projects) of the [core-v-sw](https://github.com/openhwgroup/core-v-sw) repository. We also have one project under the Hardware Task Group which also reports into us. 26 | 27 | Each project leader is asked to present any key issues for which community input from the meeting is required. Project leaders will also take any questions. 28 | 29 | - CORE-V GNU Tools for CV32E40PV2 - Nandni Jamnadas/Mary Bennett 30 | - Ongoing work to land the last patches. 31 | - CORE-V FreeRTOS - Joe Julicher 32 | - No further development. 33 | - CORE-V Clang/LLVM for CV32E40PV2 - Paolo Savini and Chunyu Liao 34 | - Ongoing work to land the last patches. 35 | - CORE-V SDK/IDE - Hugh O'Keefe and Promod Kumar 36 | - No further development. 37 | - CORE-V CV32E40PV2 Verilator modeling for software - Jeremy Bennett 38 | - No updates at the moment. 39 | 40 | ## Review of previous topics (10 minutes allocated) 41 | 42 | - CVE20: 43 | - We might need a new project to for the CVE20 model. 44 | - No updates. 45 | 46 | - CVA6-Platform for SW development and regression - **Jonathan Balkind**, **Moiz Hussain**, **Redbeard**, **Flo Wohlrab**. 47 | - The RISE team is not very interested in an FPGA platform to run their tests. They'd rather use "real hardware" or an emulation (QEMU) model. We have neither of these things for the CVA6 Platform at the moment. 48 | - The OpenPiton configuration of the CVA6 no longer boot Linux, see [CVA6 Issues #2700](https://github.com/openhwgroup/cva6/issues/2700). 49 | 50 | - Eclipse Theia & CDT Cloud. 51 | - no updates. 52 | 53 | ## Other topics. 54 | 55 | Adiyta Tiwari from Circuitsutra proposed a 45 minutes presentation of their work for next meeting. 56 | We have arranged to organize a dedicated meeting on 10th February so that Umesh Sisodia, Adiyta Tiwari and Ayush Mewati have the chance to demonstrate their work to the SW task group. 57 | 58 | ## Dates for future meetings 59 | 60 | The task group meets every two months at 15:00 UK Time on the second Monday of odd numbered months. On other even numbered months projects submit reports. 61 | 62 | | Date | Activity | 63 | | :---------- | :------------------------------------ | 64 | | 10 Feb 2025 | Presentation by the Circuitsutra Team | 65 | | 10 Mar 2025 | Meeting and report | 66 | | 14 Apr 2025 | Report only | 67 | | 12 May 2025 | Meeting and report | 68 | | 09 Jun 2025 | Report only | 69 | | 14 Jul 2025 | Meeting and report | 70 | 71 | 72 | ## AOB 73 | 74 | 75 | Paolo Savini, Chair 76 | -------------------------------------------------------------------------------- /meetings/2025/2025-03-10-agenda.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Agenda 2 | 3 | Monday 10 March 2025 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-00:00 Beijing Time 11 | 12 | ## Location 13 | 14 | Zoom meeting. 15 | 16 | - [us02web.zoom.us/j/85194416761?pwd=M2kwRzNCUG82UFlJT0NMbnJPSXBCZz09](https://us02web.zoom.us/j/85194416761?pwd=M2kwRzNCUG82UFlJT0NMbnJPSXBCZz09) 17 | - Meeting ID: 851 9441 6761 18 | - Find your local number: [us02web.zoom.us/u/kuUW3yscL](https://us02web.zoom.us/u/kuUW3yscL) 19 | 20 | # Agenda topics 21 | 22 | ## Register of attendance, introductions and apologies 23 | 24 | We are recording attendance at meetings, so OpenHW Group can track membership in accordance with article 4 of the membership agreement. This matters particularly when email ballots are held, to ensure the voters represent member organizations who are active on the group. The attendance records can be seen in the [program](https://github.com/openhwgroup/programs) directory. 25 | 26 | ## Succession planning (5 minutes allocated) 27 | 28 | I am standing down as chair of the SW task group. Anyone interested in taking up the role feel free to contact me. 29 | 30 | ## Review of actions (5 minutes allocated) 31 | 32 | - **Paolo Savini** and **Chunyu Liao** to use upstream QEMU for CORE-V to test respectively the GNU and LLVM tool chains. 33 | - IN PROGRESS, **Paolo Savini** to review a Weiwei's work and update QEMU. 34 | 35 | ## Reports from current projects (10 minutes allocated) 36 | 37 | Active projects under the Software Task Group will have provided a written report in advance (see the [project specific directories](https://github.com/openhwgroup/core-v-sw/blob/master/projects) of the [core-v-sw](https://github.com/openhwgroup/core-v-sw) repository. We also have one project under the Hardware Task Group which also reports into us. 38 | 39 | Each project leader is asked to present any key issues for which community input from the meeting is required. Project leaders will also take any questions. 40 | 41 | - CORE-V GNU Tools for CV32E40PV2 - Nandni Jamnadas/Mary Bennett 42 | - CORE-V FreeRTOS - Joe Julicher 43 | - CORE-V Clang/LLVM for CV32E40PV2 - Paolo Savini and Chunyu Liao 44 | - CORE-V SDK/IDE - Hugh O'Keefe and Promod Kumar 45 | - CORE-V CV32E40PV2 Verilator modeling for software - Jeremy Bennett 46 | 47 | ## Report back from TWG (5 minutes allocated) 48 | 49 | Report of key issues affecting the Software TG from the TWG meetings. 50 | 51 | ## CV64A60AX requirements discussion (20 minutes allocated) - **Tanuj Khandelwal** 52 | 53 | ## Review of previous topics (10 minutes allocated) 54 | 55 | - CVE20 model. 56 | 57 | - CVA6-Platform for SW development and regression - **Jonathan Balkind**, **Moiz Hussain**, **Redbeard**. 58 | 59 | - Eclipse Theia & CDT Cloud. 60 | 61 | ## Dates for future meetings 62 | 63 | The task group meets every two months at 15:00 UK Time on the second Monday of odd numbered months. On other even numbered months projects submit reports. 64 | 65 | | Date | Activity | 66 | | :---------- | :------------------------------------ | 67 | | 14 Apr 2025 | Report only | 68 | | 12 May 2025 | Meeting and report | 69 | | 09 Jun 2025 | Report only | 70 | | 14 Jul 2025 | Meeting and report | 71 | | 11 Aug 2025 | Report only | 72 | | 08 Sep 2025 | Meeting and report | 73 | 74 | 75 | ## AOB 76 | 77 | 78 | Paolo Savini, Chair 79 | -------------------------------------------------------------------------------- /meetings/2025/2025-03-10-minutes.md: -------------------------------------------------------------------------------- 1 | # OpenHW Software Task Group Meeting Minutes 2 | 3 | Monday 10 March 2025 4 | 5 | - 07:00-08:00 Pacific Time 6 | - 10:00-11:00 East Coast Time 7 | - 15:00-16:00 UTC 8 | - 15:00-16:00 UK Time 9 | - 16:00-17:00 Central European Time 10 | - 23:00-00:00 Beijing Time 11 | 12 | ## Attendees and welcome new members 13 | 14 | See the separate [attendance register](https://github.com/openhwgroup/programs/blob/master/TWG-and-TG-Attendance-Tracking/TGSoftware_Attendance_2024.md) 15 | 16 | # Meeting topics 17 | 18 | ## Succession planning (5 minutes allocated) 19 | 20 | **Paolo Savini** is standing downa as chair of the SW task group. Anyone interested in the role should contact him. 21 | 22 | Since a lot of contributions to the SW projects are coming from Asia it would be good to have a chair or co-chair from that geographical region and possibly to arrange the meetings so to allow larger groups from Asia to join the calls. 23 | 24 | ## Review of actions (5 minutes allocated) 25 | 26 | - **Paolo Savini** and **Chunyu Liao** to use upstream QEMU for CORE-V to test respectively the GNU and LLVM tool chains. 27 | - IN PROGRESS, **Paolo Savini** to review a Weiwei's work and update QEMU. 28 | 29 | ## Reports from current projects (10 minutes allocated) 30 | 31 | Active projects under the Software Task Group will have provided a written report in advance (see the [project specific directories](https://github.com/openhwgroup/core-v-sw/blob/master/projects) of the [core-v-sw](https://github.com/openhwgroup/core-v-sw) repository. We also have one project under the Hardware Task Group which also reports into us. 32 | 33 | Each project leader is asked to present any key issues for which community input from the meeting is required. Project leaders will also take any questions. 34 | 35 | - CORE-V GNU Tools for CV32E40PV2 - Nandni Jamnadas/Mary Bennett 36 | - Ongoing work to land the last patches. 37 | - CORE-V FreeRTOS - Joe Julicher 38 | - No further development. 39 | - CORE-V Clang/LLVM for CV32E40PV2 - Paolo Savini and Chunyu Liao 40 | - Ongoing work to land the last patches. 41 | - CORE-V SDK/IDE - Hugh O'Keefe and Promod Kumar 42 | - No further development. 43 | - CORE-V CV32E40PV2 Verilator modeling for software - Jeremy Bennett 44 | - No updates at the moment. 45 | 46 | ## Review of previous topics (10 minutes allocated) 47 | 48 | - CVE20: 49 | - No updates. 50 | 51 | - CVA6-Platform for SW development and regression - **Jonathan Balkind**, **Moiz Hussain**, **Redbeard**, **Flo Wohlrab**. 52 | - Following the negative response from RISE we'll look for other routes to get funding for the project. 53 | 54 | - Eclipse Theia & CDT Cloud. 55 | - **Mike Thompson** to reach out to ** Frederic Desbiens**. 56 | 57 | ## Dates for future meetings 58 | 59 | The task group meets every two months at 15:00 UK Time on the second Monday of odd numbered months. On other even numbered months projects submit reports. 60 | 61 | | Date | Activity | 62 | | :---------- | :---------------------------------------------------- | 63 | | 14 Apr 2025 | Report only | 64 | | 12 May 2025 | Meeting (in person at Paris RISC-V Summit) and report | 65 | | 09 Jun 2025 | Report only | 66 | | 14 Jul 2025 | Meeting and report | 67 | | 11 Aug 2025 | Report only | 68 | | 08 Sep 2025 | Meeting and report | 69 | 70 | 71 | ## AOB 72 | 73 | 74 | Paolo Savini, Chair 75 | -------------------------------------------------------------------------------- /meetings/README.md: -------------------------------------------------------------------------------- 1 | A directory for agendas and minutes of meetings and associated meeting 2 | materials (presentations etc). 3 | -------------------------------------------------------------------------------- /meetings/supplementary-materials/2020.07 - Eclipse IoT and Eclipse Edge Native Overview-14-sep-2020.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/2020.07 - Eclipse IoT and Eclipse Edge Native Overview-14-sep-2020.pdf -------------------------------------------------------------------------------- /meetings/supplementary-materials/2020.09 - OSDForum - Being Productive with Open Source Eclipse Development Tools-14-sep-2020.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/2020.09 - OSDForum - Being Productive with Open Source Eclipse Development Tools-14-sep-2020.pdf -------------------------------------------------------------------------------- /meetings/supplementary-materials/2020.11 - FreeRTOS.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/2020.11 - FreeRTOS.pdf -------------------------------------------------------------------------------- /meetings/supplementary-materials/2020.11 - Rust for CORE-V.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/2020.11 - Rust for CORE-V.pdf -------------------------------------------------------------------------------- /meetings/supplementary-materials/2021/imperas-models-for-openhw-sw-developers-feb21-0.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/2021/imperas-models-for-openhw-sw-developers-feb21-0.pdf -------------------------------------------------------------------------------- /meetings/supplementary-materials/SW TG Approaches Aug 10 2020.ppt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/meetings/supplementary-materials/SW TG Approaches Aug 10 2020.ppt -------------------------------------------------------------------------------- /planning/openhw-ide-requirement.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/planning/openhw-ide-requirement.md -------------------------------------------------------------------------------- /projects/README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group: Projects 2 | 3 | This directory contains a separate subdirectory for each active/completed 4 | project to hold materials related to the progress of that project. 5 | -------------------------------------------------------------------------------- /projects/clang-llvm/2020/monthly-report-2020-12-14.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * PPL was accepted 8 | 9 | * CVA6 10 | * None 11 | 12 | * CV32E40P 13 | * Added Hardware Loop support in LLVM integrated assembler 14 | * Added HWLP support to `clang` (not merged) 15 | * Added `memcpy` optimization with HWLP (not merged) 16 | * Added MAC support in LLVM integrated assembler (not merged) 17 | * Added three `-march` flags (`xcorev`, `xcorevhwlp`, `xcorevmac`) to LLVM (not 18 | merged) 19 | 20 | ### Test results (LLVM) 21 | 22 | | Category | Last Month | This Month | Delta | 23 | | -----------:| ----------:| ----------:| -----:| 24 | | PASS | 34121 | 34183 | +62 | 25 | | FAIL | 0 | 0 | 0 | 26 | | XPASS | - | - | - | 27 | | XFAIL | 151 | 151 | 0 | 28 | | UNSUPPORTED | 539 | 539 | 0 | 29 | | UNTESTED | - | - | - | 30 | | UNRESOLVED | - | - | - | 31 | 32 | * One test means one regression test file with multiple test cases in it. 33 | 34 | ### Planned activities for coming month 35 | 36 | * Get things merged 37 | * MAC builtins 38 | * ALU operations support 39 | 40 | ### Risk Register 41 | 42 | | Risk | Impact (1-3) | Likelihood (1-10) | Risk (I\*L) | Mitigation | 43 | |:------------------------------------------ | ------------:| -----------------:| -----------:|:------------------------------------------------------------------------ | 44 | | Unable to test execution due to lack of HW | 3 | 3 | 9 | HW parts are arriving at Embecosm | 45 | | Too few resources | 3 | 7 | 21 | Get interested parties to invest time and/or money in the project | 46 | | No project manager | 3 | 7 | 21 | Get a project manager to step forward from one of the interested parties | 47 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-01-11.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * None 9 | 10 | * CV32E40P 11 | * Clean up code for PRs (awaiting review) 12 | * Add MAC builtins (WIP) 13 | 14 | ### Test results (LLVM) 15 | 16 | | Category | This Month | Last Month | Delta | 17 | | -----------:| ----------:| ----------:| -----:| 18 | | PASS | 34183 | 34183 | 0 | 19 | | FAIL | 0 | 0 | 0 | 20 | | XPASS | - | - | - | 21 | | XFAIL | 151 | 151 | 0 | 22 | | UNSUPPORTED | 539 | 539 | 0 | 23 | | UNTESTED | - | - | - | 24 | | UNRESOLVED | - | - | - | 25 | 26 | * One test means one regression test file with multiple test cases in it. 27 | 28 | ### Planned activities for coming month 29 | 30 | * Get things merged 31 | 32 | ### Risk Register 33 | 34 | * No changes 35 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-02-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * None 9 | 10 | * CV32E40P 11 | * Add MAC instructions to integrated assembler (merged) 12 | * Add patterns for MAC instructions (awaiting review) 13 | * Add MAC builtins (WIP) 14 | 15 | ### Test results (LLVM) 16 | 17 | | Category | This Month | Last Month | Delta | 18 | | -----------:| ----------:| ----------:| -----:| 19 | | PASS | 34229 | 34183 | +46 | 20 | | FAIL | 0 | 0 | 0 | 21 | | XPASS | - | - | - | 22 | | XFAIL | 151 | 151 | 0 | 23 | | UNSUPPORTED | 539 | 539 | 0 | 24 | | UNTESTED | - | - | - | 25 | | UNRESOLVED | - | - | - | 26 | 27 | * One test means one regression test file with multiple test cases in it. 28 | 29 | ### Planned activities for coming month 30 | 31 | * Port implementations from 32 | [ekut-es/pulp-llvm](https://github.com/ekut-es/pulp-llvm) to 33 | [openhwgroup/corev-llvm-project](https://github.com/openhwgroup/corev-llvm-project) 34 | 35 | ### Risk Register 36 | 37 | * No changes 38 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-03-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * None 9 | 10 | * CV32E40P 11 | * Add patterns for MAC instructions (merged) 12 | * Add Load & Store instructions to integrated assembler (merged) 13 | * Add ALU instructions to integrated assembler (merged) 14 | * Add patterns for Load & Store instructions (merged) 15 | * Add patterns for ALU instructions (merged) 16 | * Completed porting implementations of extensions from [ekut-es/pulp-llvm] 17 | * Add MAC builtins (WIP) 18 | * Add HWLP memcpy optimization (needs testing) 19 | 20 | [ekut-es/pulp-llvm]: https://github.com/ekut-es/pulp-llvm 21 | [openhwgroup/corev-llvm-project]: https://github.com/openhwgroup/corev-llvm-project 22 | 23 | ### Test results (LLVM) 24 | 25 | | Category | This Month | Last Month | Delta | 26 | | -----------:| ----------:| ----------:| -----:| 27 | | PASS | 34268 | 34229 | +39 | 28 | | FAIL | 0 | 0 | 0 | 29 | | XPASS | - | - | - | 30 | | XFAIL | 151 | 151 | 0 | 31 | | UNSUPPORTED | 538 | 539 | -1 | 32 | | UNTESTED | - | - | - | 33 | | UNRESOLVED | - | - | - | 34 | 35 | * One test means one regression test file with multiple test cases in it. 36 | * Table changed from tests in `master` + PRs to just the tests in `master` 37 | 38 | ### Planned activities for coming month 39 | 40 | * Port builtins from [ekut-es/pulp-llvm] 41 | * Potentially port HWLP code generation from [ekut-es/pulp-llvm] 42 | 43 | ### Risk Register 44 | 45 | * No changes 46 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-04-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * review of directions 9 | * focus: base RV32gc/RV64gc, then extensions B, V (and later K) 10 | * objective: single multitarget toolchain for CV64A6 and CV32A6 11 | * outlook: use Linux as additional means of functional validation 12 | * current activity 13 | * QA assessment of LLVM 12.0.0-rc1 (review of status for bugs identified in v10/v11 using `riscv-dv`) 14 | 15 | * CV32E40P 16 | * Add HWLP code generation (WIP, waiting on review) 17 | * Add MAC builtins (WIP) 18 | * Add HWLP memcpy optimization (WIP) 19 | 20 | ### Test results (LLVM) 21 | 22 | | Category | This Month | Last Month | Delta | 23 | | -----------:| ----------:| ----------:| -----:| 24 | | PASS | 34272 | 34268 | +4 | 25 | | FAIL | 0 | 0 | 0 | 26 | | XPASS | - | - | - | 27 | | XFAIL | 151 | 151 | 0 | 28 | | UNSUPPORTED | 538 | 538 | 0 | 29 | | UNTESTED | - | - | - | 30 | | UNRESOLVED | - | - | - | 31 | 32 | * One test means one regression test file with multiple test cases in it. 33 | * Table changed from tests in `master` + PRs to just the tests in `master` 34 | 35 | ### Planned activities for coming month 36 | 37 | * Port builtins from [ekut-es/pulp-llvm] 38 | * Do automated builds of the toolchain (Embecosm) 39 | 40 | [ekut-es/pulp-llvm]: https://github.com/ekut-es/pulp-llvm 41 | 42 | ### Risk Register 43 | 44 | * No changes 45 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-05-10.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * Decision to use upstream compiler unmodified (except bug fixes - to be contributed back to upstream) 9 | * Initial QA review of LLVM 12.0.0 on CVA6 test suites 10 | * smoke tests using an all-LLVM toolchain (Clang + LLVM + LLD) 11 | * identified 1 (one) known issue related to LLD: relaxation not supported in presence of alignment directives 12 | * identified mandatory changes to end-user projets (explicit `--sysroot=` option) 13 | * Concern about size of prebuild binaries 14 | * current size of 'release' distribution including C library: 1GB compressed 15 | 16 | * CV32E40P 17 | * None 18 | 19 | ### Test results (LLVM) 20 | 21 | * No changes 22 | 23 | ### Planned activities for coming month 24 | 25 | * CVA6: 26 | * complete the QA assessment on all CVA6 test suites (64b and 32b) 27 | * qualification tests on libs (newlib, GMP, etc.) 28 | * validate end-to-end toolchain flow including BSP integration 29 | 30 | * CV32E40P: 31 | * Do automated builds of the toolchain (Embecosm) 32 | * Port builtins from [ekut-es/pulp-llvm] 33 | 34 | [ekut-es/pulp-llvm]: https://github.com/ekut-es/pulp-llvm 35 | 36 | ### Risk Register 37 | 38 | * No changes 39 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-06-14.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 8 | * Check status of Clang+LLVM+LLD wrt. core-v-verif tests; key issues: floating-point, out-of-bound relocations 9 | 10 | * CV32E40P 11 | * Port hardware loop code generation 12 | 13 | ### Test results (LLVM) 14 | 15 | | Category | This Month | Last Month | Delta | 16 | | -----------:| ----------:| ----------:| -----:| 17 | | PASS | 34273 | 34272 | +1 | 18 | | FAIL | 0 | 0 | 0 | 19 | | XPASS | - | - | - | 20 | | XFAIL | 151 | 151 | 0 | 21 | | UNSUPPORTED | 538 | 538 | 0 | 22 | | UNTESTED | - | - | - | 23 | | UNRESOLVED | - | - | - | 24 | 25 | ### Planned activities for coming month 26 | 27 | * CVA6: 28 | * Finalise LLVM / core-v-verif evaluation 29 | * Automate builds of the toolchain (Thales, externally accessible) 30 | * Basic benchmarking (performance, code size) 31 | 32 | * CV32E40P: 33 | * Do automated builds of the toolchain (Embecosm) 34 | * Port builtins from [ekut-es/pulp-llvm] 35 | 36 | [ekut-es/pulp-llvm]: https://github.com/ekut-es/pulp-llvm 37 | 38 | ### Risk Register 39 | 40 | * No changes 41 | -------------------------------------------------------------------------------- /projects/clang-llvm/2021/monthly-report-2021-07-12.md: -------------------------------------------------------------------------------- 1 | oftware TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CVA6 (Thales) 8 | * automate LLVM builds using same scripts as for GNU binutils, GCC and newlib 9 | * supports both LLD and GNU binutils linking 10 | * Extend floating point support at assembly level (handle signaling NaNs) 11 | * to be upstreamed 12 | * Introduce dual testing path according to the choice of linker: with LLD and with GNU ("BFD") binutils 13 | * Adapt LLVM-specific CI (Continuous Integration) to CVA6 project restructuring (`cva6_reorg`) 14 | 15 | * CV32E40P 16 | * ... 17 | 18 | ### Test results (LLVM) 19 | 20 | TBA 21 | 22 | ### CVA6 test results on Thales "new" CI (GCC/LLVM+LLD/LLVM, PASS/FAIL only) 23 | 24 | | Test suite, arch | GCC | LLVM+LLD | LLVM+BFD.LD | 25 | | -----------:| ----------:| ----------:|------------:| 26 | | riscv-compliance, rv64gc | 171/0 | 171/0 | 171/0 | 27 | | riscv-compliance, rv32imac | N/A yet | N/A yet | N/A yet | 28 | | riscv-compliance, rv32ima | N/A yet | N/A yet | N/A yet | 29 | | riscv-tests, rv64gc-p | 106/0 | N/A yet | N/A yet | 30 | | riscv-tests, rv64gc-v | 117/0 | N/A yet | N/A yet | 31 | | riscv-tests, rv32imac-p | N/A yet | N/A yet | N/A yet | 32 | | riscv-tests, rv32imac-p | N/A yet | N/A yet | N/A yet | 33 | | riscv-tests, rv32ima-p | N/A yet | N/A yet | N/A yet | 34 | | riscv-tests, rv32ima-p | N/A yet | N/A yet | N/A yet | 35 | 36 | ### Planned activities for coming month 37 | 38 | * CVA6 (Thales) 39 | * Finalise `cva6_reorg` changes to CI 40 | * Complete the test result matrix 41 | * Publish updated scripts for automated builds of the toolchain (@Thales, externally accessible) 42 | * Basic benchmarking (performance, code size) 43 | 44 | * CV32E40P 45 | * ... 46 | 47 | ### Risk Register 48 | 49 | * No changes 50 | -------------------------------------------------------------------------------- /projects/clang-llvm/2022/monthly-report-2022-08-08.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CV32E40P (Embecosm) 8 | * In process of rolling forward repository. 9 | * Finished merge from LLVM upstream (as of Aug 5th) to existing OpenHW clang-llvm repository. 10 | * Fixing incompatibilities as they are discovered as build failure occurs. 11 | * Goal of improving repository with upstream enhancements. 12 | * Adding march string parser support for expanding xcorev target feature to the extensions it enables 13 | 14 | ### Planned activities for coming month 15 | 16 | * CV32E40P (Embecosm) 17 | * Plan to have made significant progress towards rolling forward repository. 18 | * Plan to have finished adding xcorev target feature support. 19 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-01-09.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CV32E40P (Embecosm) 8 | * Overall effort focused on fixing failing test. 9 | * Initial fix for generation of clipu instruction from ALU extension is in development. 10 | 11 | * CV32E40P (PLCT) 12 | * Overall effort focused on fixing encodings. 13 | * Committed fix for encoding of alu instructions. 14 | * Submitted fix for encoding of mem instruction. 15 | 16 | ### Planned activities for coming month 17 | 18 | * CV32E40P (Embecosm) 19 | * Plan to have submitted and commited fix for failing tests. 20 | 21 | * CV32E40P (PLCT) 22 | * Plan to find and develop fixes for other erroneous instruction encodings. 23 | 24 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-02-13.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * CV32E40P (Embecosm) 8 | * Committed fix for failing test (clipu). 9 | * Reviewing support for encoding of SIMD instructions. 10 | 11 | * CV32E40P (PLCT) 12 | * Overall effort focused on fixing encodings. 13 | * Committed fix for encoding of mem instruction. 14 | * Submitted support for encoding of SIMD instructions (In review). 15 | * Responding to reviews for patch on support for encoding of SIMD instructions. 16 | 17 | ### Planned activities for coming month 18 | 19 | * CV32E40P (Embecosm) 20 | * Plan to finish reviewing of patch on support for encoding of SIMD instructions. 21 | * Plan to review commit for update hwlp instructions. 22 | 23 | * CV32E40P (PLCT) 24 | * Plan to finish responding to reviews of support for encoding of SIMD instructions appropriately. 25 | * Plan to find and develop fixes for other erroneous instruction encodings. 26 | 27 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-03-13.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | * CV32E40P (Embecosm) 6 | * Committed support for encoding of cv32e40p SIMD instructions. 7 | * Committed fix for hwlp instructions (#26). 8 | * Committed fix to update MAC instructions. 9 | * Committed CI for CORE-V llvm testing. 10 | * Committed fix for wrong encodings of MAC instructions. 11 | * Committed support for xcvsimd option. 12 | * Developed, submitted, and committed CI fix to remove unneeded .github files. 13 | * Developed and submitted patch to re-enable Windows testing as part of CI. 14 | * Developed and submitted patch to remove xcv extension. 15 | * Developed and submitted patch to update CORE-V Extension name prefix from xcorev to xcv. 16 | * Developed and submitted patch to replace the tags in CORE-V Commits with [RISCV]. 17 | 18 | * CV32E40P (PLCT) 19 | * Developed and submitted patch to match behavior for Hardware Loop. 20 | * Developed and submitted patch to implement writeback and signedness for CORE-V SIMD. 21 | * Developed and submitted patch to support CORE-V SIMD builtins in clang. 22 | * Developed and submitted fix for MAC instructions. 23 | * Developed and submitted support for xcvsimd option. 24 | * Developed and submitted patch to update MAC instructions. 25 | 26 | ### Planned activities for coming month 27 | 28 | * CV32E40P (Embecosm) 29 | 30 | * Plan to review patch to match the behavior for hardware loop. 31 | * Plan to review patch for implementing writeback and signedness for CORE-V SIMD extension. 32 | * Plan to review patch to support CORE-V SIMD builtins in Clang. 33 | 34 | * CV32E40P (PLCT) 35 | * Plan to review patch to re-enable Windows testing as part of CI. 36 | * Plan to review patch to remove xcv extension. 37 | * Plan to review patch to update CORE-V Extension name prefix from xcorev to xcv. 38 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-05-08.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | * CV32E40P (Embecosm) 6 | * Prepared for presentation on CORE-V LLVM at EuroLLVM. 7 | * Rolled forward patches for changing march prefix. 8 | * Rolled forward patches for removing xcv extension group. 9 | * Reviewed patch to match the behavior for hardware loop. 10 | * Reviewed patch for implementing writeback and signedness for CORE-V SIMD extension. 11 | * Reviewed patch to support CORE-V SIMD Builtins in Clang. 12 | 13 | * CV32E40P (PLCT) 14 | * Committed patch to match behavior for Hardware Loop. 15 | * Committed patch to implement writeback and signedness for CORE-V SIMD. 16 | * Committed patch to support CORE-V SIMD builtins in clang. 17 | * Committed fix for MAC instructions. 18 | * Committed support for xcvsimd option. 19 | * Committed patch to update MAC instructions. 20 | 21 | ### Planned activities for coming month 22 | 23 | * CV32E40P (Embecosm) 24 | 25 | * Plan to review patch to implement xcvelw encoding and intrinsics. 26 | 27 | * CV32E40P (PLCT) 28 | * Plan to review patch to re-enable Windows testing as part of CI. 29 | * Plan to review patch to remove xcv extension. 30 | * Plan to review patch to update CORE-V Extension name prefix from xcorev to xcv. 31 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-06-05.md: -------------------------------------------------------------------------------- 1 | Software TG monthly meeting - CORE-V LLVM Tool Chain 2 | 3 | ## Overview 4 | 5 | * CV32E40P (Embecosm) 6 | * Reviewed and committed patch to update SIMD builtins. 7 | * Reviewed and committed patch to update immediate branching extension. 8 | * Reviewed and committed patch to fix signedness of CORE-V SIMD instructions. 9 | * Developed and committed patch to update CORE-V extension name prefix from xcorev to xcv. 10 | * Reviewed and committed patch to implement xcvmac intrinsics. 11 | * Reviewed and committed patch to update CORE-V SIMD instructions. 12 | * Reviewed and committed patch to implement XcvElw encoding. 13 | * Reviewed and committed patch to update xcvmac pseudo instruction. 14 | * Rolled forward patches for removing xcv extension group. 15 | 16 | * CV32E40P (PLCT) 17 | * Developed patch to update immediate branching extension. 18 | * Developed patch to fix signedness of CORE-V SIMD instructions. 19 | * Reviewed patch to update CORE-V extension name prefix from xcorev to xcv. 20 | * Reviewed patch to remove xcv extension group. 21 | * Reviewed patch to replace the tags in CORE-V commits with [RISCV]. 22 | * Developed patch to update CORE-V SIMD instructions. 23 | * Developed patch to implement xcvmac intrinsics. 24 | * Developed patch to implement xcvelw encoding. 25 | * Developed patch to update xcvmac pseudo instructions. 26 | 27 | ### Planned activities for coming month 28 | 29 | * CV32E40P (Embecosm) 30 | 31 | * Plan to review and commit patch to implement xcvelw intrinsics. 32 | * Plan to commit patch to remove xcv extension group. 33 | 34 | * CV32E40P (PLCT) 35 | * Plan to respond to review for patch to implement xcvelw intrinsics. 36 | -------------------------------------------------------------------------------- /projects/clang-llvm/2023/monthly-report-2023-07-14.md: -------------------------------------------------------------------------------- 1 | 1. Summary 2 | - Title of the project: CORE-V LLVM Tool Chain 3 | - Date of the report: 2023-07-14 4 | - Prepared by: Paolo Savini 5 | 6 | 7 | 2. Activities and progress since last report 8 | - Planned 9 | - Embecosm 10 | - Review and commit patch to implement xcvelw intrinsics. COMPLETE. 11 | - Commit a patch to remove the xcv extension group. COMPLETE. 12 | - PLCT 13 | - Respond to review for patch to implement xcvelw intrinsics. COMPLETE. 14 | - Unplanned 15 | - Uploaded patches to phabricator for: 16 | - xcvalu encodings (D153748) 17 | - xcvbi encodings (D154412) 18 | - xcvsimd encodings (D153721) 19 | Now under review. 20 | 21 | 3. Planned activities 22 | - Embecosm: 23 | - Review clang builtins for xcvmac 24 | - Review clang builtins for xcvelw 25 | - Review upstream patches: 26 | - xcvalu encodings (D153748) 27 | - xcvbi encodings (D154412) 28 | - xcvsimd encodings (D153721) 29 | 30 | - PLCT: 31 | - Clang builtins for xcvmac 32 | - Clang builtins for xcvelw 33 | - Get upstream patches to be accepted: 34 | - xcvalu encodings (D153748) 35 | - xcvbi encodings (D154412) 36 | - xcvsimd encodings (D153721) 37 | 38 | 4. Milestones 39 | 40 | Milestone listed here come from the 2023 workplan [here](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/LLVM-Toolchain/COREV_LLVM_Plan_Approved_2023.md) 41 | 42 | Milestones here are coded as XXY with XX one or two characters to mean the category of mylestone (Assembler, Compiler Options, CodeGen, Hardware Loop) and Y the number of the milestone. 43 | 44 | The completion state of a milestone is a percentage that depends on the internal stages of the work. E.g. for CG patches LLVM intrinsics and Clang builtins need to be created, so the progress can be measured as 50% for a merged patch with LLVM instrinsics and 100% for a consecutive merged patch with Clang builtins. 45 | 46 | | Milestone | Target | Completion | 47 | | --------- | ---------- | ---------- | 48 | | A1 | 2023-02-28 | COMPLETE | 49 | | A2 | 2023-03-30 | COMPLETE | 50 | | A3 | 2023-04-30 | COMPLETE | 51 | | CO | 2023-05-30 | COMPLETE | 52 | | CG1 | 2023-07-30 | COMPLETE | 53 | | CG2 | 2023-09-30 | 50% | 54 | | CG3 | 2023-10-30 | 0% | 55 | | CG4 | 2023-11-30 | 0% | 56 | | HL | 2023-12-30 | 0% | 57 | 58 | 5. Gate status & schedule 59 | 60 | | Gate | Original plan | Current plan | Achieved | Link to last gate document and notes | 61 | | ---- | ------------- | ------------- | ----------- | ------------------------------------ | 62 | | PC | 2020-11-21 | 2020-11-21 | 2020-11-21 | Approved on 2020-11-21 as PPL [LLVM-Toolchain-PPL](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/LLVM-Toolchain/llvm-toolchain-ppl.md) | 63 | | PL | 2020-11-21 | 2023-01-11 | 2023-01-11 | [LLVM-Toolchain-PL](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/LLVM-Toolchain/llvm-toolchain-pl.md) | 64 | | PA | 2023-01-11 | 2023-02-14 | 2023-02-14 | [LLVM-Toolchain-approved](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/LLVM-Toolchain/COREV_LLVM_Plan_Approved_2023.md) | 65 | | PA | 2024-xx-xx | 2023-02-14 | 2023-02-14 | 2024 and beyond. Workplan TBD | 66 | 67 | -------------------------------------------------------------------------------- /projects/clang-llvm/README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group: Clang/LLVM Project 2 | 3 | A directory for materials associated with reporting progress with the CORE-V 4 | Clang/LLVM project 5 | -------------------------------------------------------------------------------- /projects/freertos/2020/monthly-report-14-dec-20.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FreeRTOS 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * PULP FreeRTOS open-sourced under Apache-2.0 (including some re-licensing requests) 8 | * Basic FreeRTOS Demo app toggling a LED on/off on the board depending on compile time switch 9 | * Started work on adding platform specific timer support to FreeRTOS kernel 10 | 11 | ### Test results 12 | 13 | 14 | ### Planned activities for coming month 15 | 16 | * Open repository with basic boot boilerplate 17 | * boot-to-main runtime (crt0.S, board initialization) 18 | * Add FreeRTOS kernel and get basic blinky working 19 | * Get hello world over uart working 20 | 21 | ### Risk Register 22 | 23 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-08-aug-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (August 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Provided support for getting `core-v-mcu` working with `FreeRTOS` 6 | ### Test results 7 | ### Risk Register 8 | 9 | No changes. 10 | 11 | ### Next stages 12 | * Merge kernel changes upstream 13 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` ontop of latest 14 | upstream freertos release of the kernel (or master if we really need this) 15 | 2. Do some cleanups of the branch (for example there are references to PULPissimo etc.) 16 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 17 | 4. Make a PR from `core-v-freertos-kernel` to upstream 18 | * Blocked by [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 19 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115) 20 | * Continue work on Component 1 as per the [original FreeRTOS PPL 21 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/Project%20Descriptions%20and%20Plans/Free%20RTOS/core-v-free-rtos-ppl.md) 22 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-08-feb-21.md: -------------------------------------------------------------------------------- 1 | ## Overview 2 | 3 | ### Key activities 4 | 5 | * Work on Component 1 as per the [original FreeRTOS PPL proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) is still ongoing 6 | * A clean version of Core-V-MCU FreeRTOS published on Github under https://github.com/bluewww/core-v-freertos, work to move the project under the OpenHW Group github organization is in progress 7 | * Timer interrupts are currently working when TIMER_CFG_HI & the relevant external interrupt /11/ are used instead of the TIMER_CFG_LO is currently being configured by the public code 8 | * A discussion on current Core-V timer implementation vs RISC-V ISA Specification definiton for mtime & proposed timer implementation improvements was held - RTL changes expected that will require some modifications to the current FreeRTOS timer handling code 9 | 10 | ### Test results 11 | 12 | 13 | ### Planned activities for coming month 14 | 15 | * Move Core-V-Freertos repository to the OpenHW Group github organization 16 | * boot-to-main runtime (crt0.S, board initialization) 17 | * FreeRTOS kernel and get basic blinky working following RTL changes in timer implementation 18 | 19 | ### Risk Register 20 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-08-march-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (March 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | 6 | * Work on Component 1 as per the [original FreeRTOS PPL 7 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) 8 | is still ongoing 9 | * A clean version of core-v-mcu freertos was published under the OpenHW github 10 | organization as https://github.com/openhwgroup/core-v-freertos (full 11 | distribution) and https://github.com/openhwgroup/core-v-freertos-kernel 12 | (downstream for kernel changes). The core-v-freertos is self-contained to make 13 | it easier to use (i.e. no download scripts or git submodules). 14 | 15 | ### Test results 16 | ### Risk Register 17 | 18 | No changes. 19 | 20 | 21 | ### Next stages 22 | 23 | * Use new timer interface. We are currently waiting for a bitstream/rtl changes 24 | to be able to develop against it. Related PR is 25 | https://github.com/openhwgroup/timer_unit/pull/3. 26 | * Add FreeRTOS kernel and get basic blinky working. 27 | * core-v GCC toolchain should be used 28 | * Add an Eclipse launch configuration to core-v freertos 29 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-08-nov-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (November 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * No progress on project during the previous month 6 | 7 | ### Test results 8 | 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | Plan remains unchanged - 15 | 16 | * Merge kernel changes upstream 17 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` on top of latest 18 | upstream freertos release of the kernel 19 | 2. Cleanups of the main branch 20 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 21 | 4. Make a PR from `core-v-freertos-kernel` to upstream 22 | * Blocked by [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 23 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115)/ Need up-to-date status of [open Core-V issues](https://github.com/openhwgroup/core-v-mcu/issues) 24 | * Blocked by [IDCODE change](https://github.com/openhwgroup/core-v-mcu/issues/168) - need an example OpenOCD configuration and ideally published pre-built bitstreams with latest RTL changes 25 | * Continue work as per the [original FreeRTOS PPL 26 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/Project%20Descriptions%20and%20Plans/Free%20RTOS/core-v-free-rtos-ppl.md) 27 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-10-may-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (May 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Restructuring of repository layout for cva6 support 6 | * Recorded openhw TV episode 7 | 8 | ### Test results 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | * The core-v-mcu repository got a complete overhault this month including more 15 | detailed documentation. Evaluate ongoing hardware changes, generate new 16 | bitstreams & test/re-validate current CORE-V FreeRTOS implementation 17 | * Continue work on Component 1 as per the [original FreeRTOS PPL 18 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) 19 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-11-jan-21.md: -------------------------------------------------------------------------------- 1 | ## Overview 2 | 3 | ### Key activities 4 | 5 | * PULP FreeRTOS published on Github under https://github.com/pulp-platform/pulp-freertos-kernel and https://github.com/pulp-platform/pulp-freertos 6 | * Unmodified pulp-freertos tested on Nexus A7 - the code making bad memory accesses while configuring the FLL revealed an error in the RTL emulating the FLL - fixed here - https://github.com/openhwgroup/core-v-mcu/pull/36/commits/7f3402058eda1dce9ca8f75831aab0ea86ae70a8 ; 7 | * A new prebuilt bitstream for Nexus A7 with applied change uploaded at https://github.com/shteryana/core-v-mcu/tree/bitstream-update 8 | * Work on proper timer interrupt configuration ongoing 9 | * Prototyping a more simplified version of pulp-freertos (removing all off the pulp-specific code such as cluster, custim insn, unnecessary abstractions, etc) is ongoing. 10 | 11 | ### Test results 12 | 13 | 14 | ### Planned activities for coming month 15 | 16 | * Genesys2 pre-built bitstream from latest RTL 17 | * Open repository with basic boot boilerplate 18 | * boot-to-main runtime (crt0.S, board initialization) 19 | * Add FreeRTOS kernel and get basic blinky working 20 | 21 | ### Risk Register 22 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-11-oct-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (October 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * No progress on project during the previous 4 weeks 6 | 7 | ### Test results 8 | 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | Plan remains unchanged - 15 | 16 | * Merge kernel changes upstream 17 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` on top of latest 18 | upstream freertos release of the kernel (or master if we really need this) 19 | 2. Further cleanups of the main branch 20 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 21 | 4. Make a PR from `core-v-freertos-kernel` to upstream 22 | * Blocked by [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 23 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115)/ Need up-to-date status of [open Core-V issues](https://github.com/openhwgroup/core-v-mcu/issues/149) 24 | * Continue work as per the [original FreeRTOS PPL 25 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/Project%20Descriptions%20and%20Plans/Free%20RTOS/core-v-free-rtos-ppl.md) 26 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-12-april-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (April 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Present Core-V FreeRTOS port during OpenHW Day at 2nd RISC-V Week 6 | * Hardware changes to the Core-V MCU are ongoing at https://github.com/openhwgroup/core-v-mcu, https://github.com/openhwgroup/timer_unit/pull/3 7 | 8 | ### Test results 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | * Evaluate ongoing hardware changes, generate new bitstreams & 15 | test/re-validate current Core-V FreeRTOS implementation 16 | * Add an Eclipse launch configuration to core-v freertos 17 | * Continue work on Component 1 as per the [original FreeRTOS PPL proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) 18 | * Add FreeRTOS kernel and get basic blinky working. 19 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-12-july-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (July 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Added build time configuration switches 6 | [options](https://github.com/openhwgroup/core-v-freertos/pull/2) to make 7 | addtional targets such as the cva6 easier. 8 | * Updated tests accordingly 9 | * Formulated plan for merging kernel changes upstream 10 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` ontop of latest 11 | upstream freertos release of the kernel (or master if we really need this) 12 | 2. Do some cleanups of the branch (for example there are references to PULPissimo etc.) 13 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 14 | 4. Make a PR from `core-v-freertos-kernel` to upstream 15 | 16 | ### Test results 17 | ### Risk Register 18 | 19 | No changes. 20 | 21 | ### Next stages 22 | * Blocked by [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 23 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115) 24 | * Continue work on Component 1 as per the [original FreeRTOS PPL 25 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) 26 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-13-sept-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (September 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * No major activity on the project during the previous month besides minor testing with latest RTL changes 6 | 7 | ### Test results 8 | ### Risk Register 9 | 10 | No changes. 11 | 12 | ### Next stages 13 | Plan remains unchanged compared to August - 14 | 15 | * Merge kernel changes upstream 16 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` on top of latest 17 | upstream freertos release of the kernel (or master if we really need this) 18 | 2. Do some cleanups of the branch (for example there are references to PULPissimo etc.) 19 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 20 | 4. Make a PR from `core-v-freertos-kernel` to upstream 21 | * Blocked by [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 22 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115)/ Need up-to-date status of [open Core-V issues](https://github.com/openhwgroup/core-v-mcu/issues/149) 23 | * Continue work on Component 1 as per the [original FreeRTOS PPL 24 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/Project%20Descriptions%20and%20Plans/Free%20RTOS/core-v-free-rtos-ppl.md) 25 | -------------------------------------------------------------------------------- /projects/freertos/2021/monthly-report-14-june-21.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (June 2021) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Regenerate new bitstream from [latest rtls](https://github.com/openhwgroup/core-v-mcu/tree/master/rtl) 6 | * Re-tested current CORE-V FreeRTOS implementation with new bitstream on Nexus 7 | A7-100 - timer interrupts are not triggered, GPIO LED not working (possibly due 8 | to register changes); basic programming examples (using pseudocode) are needed 9 | 10 | ### Test results 11 | ### Risk Register 12 | 13 | No changes. 14 | 15 | ### Next stages 16 | * Update register definitions & hardware setup routine as per the 17 | [updated documentation](https://github.com/openhwgroup/core-v-mcu/tree/master/docs] & 18 | test/re-validate current CORE-V FreeRTOS implementation 19 | * Continue work on Component 1 as per the [original FreeRTOS PPL 20 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/core-v-free-rtos-ppl.md) 21 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-08-aug-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (July 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Ported the FreeRTOS Demo application(s) to the core-v-mcu. Currently, 6 | development happens at https://github.com/bluewww/Freertos/tree/core-v-mcu. as 7 | a fork of the classic FreeRTOS distribution. A simple hello world works. 8 | Blinky doesn't work due to the periodic timer interrupt not firing. Needs more 9 | analysis. 10 | * Working on getting questasim setup for core-v-mcu running. We had trouble with 11 | loading binaries into the simulation. Added jtag testbench that is able to 12 | load srec files to core-v-mcu at 13 | https://github.com/bluewww/core-v-mcu/commits/jtag-tb. Still working in progress. 14 | * Debugging silent UART on genesys2 15 | 16 | ### Test results 17 | 18 | ### Risk Register 19 | 20 | No changes. 21 | 22 | ### Next stages 23 | 1. Analyze and fix timer interrupt issue. Move from custom timer code to 24 | `mtime` based solution. 25 | 2. Get blinky and full demo to work 26 | 3. Test with core-v-mcu verilator / questa and on nexys fpga 27 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-09-may-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (May 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * No progress on the FreeRTOS project during the previous month. 6 | 7 | ### Test results 8 | 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | 1. Analyze and fix timer interrupt issues with latest [core-v-mcu FreeRTOS port](https://github.com/bluewww/Freertos/tree/core-v-mcu). 15 | Move from custom timer code to `mtime` based solution. 16 | 2. Get blinky and full demo to work 17 | 3. Test with core-v-mcu verilator / questa and on nexys fpga 18 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-10-jan-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (January 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Minor testing of latest Core-V-MCU bitstream (built at commit [ff468b90](https://github.com/openhwgroup/core-v-mcu/commit/ff468b90) ) - with CPU id of 0x10001c05 and JTAG connected to the lower pins of JB, OpenOCD sucessfully connects to Nexys-A7-100T board and debugging FreeRTOS via GDB is working as expected 6 | 7 | ### Test results 8 | 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | Plan for comming weeks - 15 | 16 | * Merge kernel changes upstream 17 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` on top of latest 18 | upstream freertos release of the kernel 19 | 2. Cleanups of the main branch 20 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 21 | 4. Make a PR from `core-v-freertos-kernel` to upstream 22 | * Double check [RTL simulation](https://github.com/openhwgroup/core-v-mcu/issues/149) and 23 | [interrupt handling](https://github.com/openhwgroup/core-v-mcu/issues/115) issues 24 | * Continue work as per the [original FreeRTOS PPL 25 | proposal](https://github.com/openhwgroup/core-v-docs/blob/master/program/Project%20Descriptions%20and%20Plans/Free%20RTOS/core-v-free-rtos-ppl.md) 26 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-10-oct-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (October 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Ported the FreeRTOS Demo application(s) to the core-v-mcu. Currently, 6 | development happens at https://github.com/bluewww/Freertos/tree/core-v-mcu. as 7 | a fork of the classic FreeRTOS distribution. A simple hello world works. 8 | Blinky doesn't work due to the periodic timer interrupt not firing. Needs more 9 | analysis. 10 | * Working on getting questasim setup for core-v-mcu running. We had trouble with 11 | loading binaries into the simulation. Added jtag testbench that is able to 12 | load srec files to core-v-mcu at 13 | https://github.com/bluewww/core-v-mcu/commits/jtag-tb. Still working in progress. 14 | 15 | ### Test results 16 | 17 | ### Risk Register 18 | 19 | No changes. 20 | 21 | ### Next stages 22 | 1. Analyze and fix timer interrupt issue. Move from custom timer code to 23 | `mtime` based solution. 24 | 2. Get blinky and full demo to work 25 | 3. Test with core-v-mcu verilator / questa and on nexys fpga 26 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-11-april-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (April 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Ported the FreeRTOS Demo application(s) to the core-v-mcu. Currently, 6 | development happens at https://github.com/bluewww/Freertos/tree/core-v-mcu. as 7 | a fork of the classic FreeRTOS distribution. A simple hello world works. 8 | Blinky doesn't work due to the periodic timer interrupt not firing. Needs more 9 | analysis. 10 | * Reviewed changes in core-v-freertos-kernel that qualify for upstreaming. 11 | Currently, no changes need to be upstreamed to get a rv32imc baseline 12 | working. 13 | 14 | ### Test results 15 | 16 | ### Risk Register 17 | 18 | No changes. 19 | 20 | ### Next stages 21 | 1. Analyze and fix timer interrupt issue. Move from custom timer code to 22 | `mtime` based solution. 23 | 2. Get blinky and full demo to work 24 | 3. Test with core-v-mcu verilator / questa and on nexys fpga 25 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-11-july-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (July 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Ported the FreeRTOS Demo application(s) to the core-v-mcu. Currently, 6 | development happens at https://github.com/bluewww/Freertos/tree/core-v-mcu. as 7 | a fork of the classic FreeRTOS distribution. A simple hello world works. 8 | Blinky doesn't work due to the periodic timer interrupt not firing. Needs more 9 | analysis. 10 | * Reviewed changes in core-v-freertos-kernel that qualify for upstreaming. 11 | Currently, no changes need to be upstreamed to get a rv32imc baseline 12 | working. 13 | 14 | ### Test results 15 | 16 | ### Risk Register 17 | 18 | No changes. 19 | 20 | ### Next stages 21 | 1. Analyze and fix timer interrupt issue. Move from custom timer code to 22 | `mtime` based solution. 23 | 2. Get blinky and full demo to work 24 | 3. Test with core-v-mcu verilator / questa and on nexys fpga 25 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-14-feb-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (February 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Two meeting were held to discuss current status of project, revise goals/milestones & agree on a plan to move the project ahead 6 | 7 | ### Test results 8 | 9 | ### Risk Register 10 | 11 | No changes. 12 | 13 | ### Next stages 14 | Plan for comming weeks - 15 | 16 | * Working software CORE-V emulation needed & explanation how to be run to interested parties 17 | * Merge kernel changes upstream 18 | 1. In `core-v-freertos-kernel` rebase `pulp-project-devel` on top of latest 19 | upstream freertos release of the kernel 20 | 2. Cleanups of the main branch 21 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 22 | 4. Make a PR from `core-v-freertos-kernel` to upstream 23 | 24 | -------------------------------------------------------------------------------- /projects/freertos/2022/monthly-report-14-march-22.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (March 2022) 2 | ## Overview 3 | 4 | ### Key activities 5 | * Further meetings to discuss FreeRTOS Project Launch Preparation 6 | * Tested out latest upstream FreeRTOS on FPGA w/ up-to-date Core-V-MCU bitstream - with minor changes a blinky application is mostly functional (using riscv mtime counters) - send/receive tasks are properly context-switched, timers are firing properly, GPIO LED adjustments still TBD, uart is still TBD (curently getting garbage output with uart_test application) 7 | * A preliminary startup guide & prebuilt bitstream for core-v-mcu and Nexys A7 FPGA available at https://github.com/MikeOpenHWGroup/core-v-mcu/blob/qsg/emulation/quickstart/README.md 8 | 9 | ### Test results 10 | 11 | ### Risk Register 12 | 13 | No changes. 14 | 15 | ### Next stages 16 | Plan for comming weeks - 17 | * Merge kernel changes upstream 18 | 1. Separate individual tasks & delegate to people involved 19 | 2. Update core-v-freertos-kernel, align it with upstream 20 | 3. Merge this updated kernel into the `core-v-freertos` repo and test it. 21 | 4. Fork freertos demo and add core-v-mcu demo using code from core-v-freertos 22 | 5. Test with core-v-mcu verilator / questa and on nexys fpga 23 | 6. Make a PR from `core-v-freertos-kernel` to upstream 24 | -------------------------------------------------------------------------------- /projects/freertos/2023/monthly-report-13-feb-23.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (February 2023) 2 | ## Overview 3 | * Getting caught up with prior progress by other teams. 4 | * I hope to see a PR to the freertos repo from bluewww with the risc-v demo work. 5 | 6 | ### Key activities 7 | * updating project plans to match current progress and effort 8 | 9 | ### Test Results 10 | 11 | No changes 12 | 13 | ### Risk Register 14 | 15 | No changes 16 | 17 | ### Next stages 18 | * publish the updates to the freertos project plan 19 | -------------------------------------------------------------------------------- /projects/freertos/2023/monthly-report-13-nov-23.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - FREERTOS (November 2023) 2 | 3 | ## Overview 4 | 5 | All changes have been merged with the main repo at github.com/freertos/freertos-kernel. 6 | 7 | The tip of the repo is being used to create the SDK for the CORE-V MCU devkit with the goal 8 | of ensuring the next Long Term Support (LTS) version is supplied with the SDK when the LTS 9 | update happens in April. 10 | 11 | ### Key activities 12 | 13 | No activities. The development SDK is operating with the latest kernel. 14 | 15 | ### Test Results 16 | 17 | No changes 18 | 19 | ### Risk Register 20 | 21 | No changes 22 | 23 | ### Next stages 24 | 25 | None 26 | -------------------------------------------------------------------------------- /projects/freertos/README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group: FreeRTOS Project 2 | 3 | A directory for materials associated with reporting progress with the CORE-V 4 | FreeRTOS project. 5 | -------------------------------------------------------------------------------- /projects/gnu-tools/2020/gnu-tools-update-14-sep-2020.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/openhwgroup/core-v-sw/857f4789ce6f055fb9114594fba245577e721bd2/projects/gnu-tools/2020/gnu-tools-update-14-sep-2020.pdf -------------------------------------------------------------------------------- /projects/gnu-tools/2020/monthly-report-2020-10-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain (October) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Preliminary Project Plan approved 8 | * Added CORE-V hardware loop support to GNU Binutils - current version in openhw development repository 9 | * Added CORE-V hardware loop support to GNU GCC, including a memcpy utilising hw loops for speed optimisation - not yet in openhw repos 10 | * Added two -march options: xcorev (intended to support all extensions once added) and xcorevhwlp (supports the hw loop subset) in both Binutils and GCC 11 | 12 | ### Testing status 13 | 14 | **GNU Binutils** 15 | 16 | * CORE-V hw loops fully tested including failure cases for both GAS (assembler) and LD (linker) 17 | 18 | GAS 19 | 20 | | Category | This Month | Last Month | Delta | Baseline | Delta | 21 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 22 | | PASS | 304 | 304 | - | 288 | 16 | 23 | | FAIL | - | - | - | - | - | 24 | | XPASS | - | - | - | - | - | 25 | | XFAIL | 15 | 15 | - | 15 | - | 26 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 27 | | UNTESTED | - | - | - | - | - | 28 | | UNRESOLVED | - | - | - | - | - | 29 | 30 | LD 31 | 32 | | Category | This Month | Last Month | Delta | Baseline | Delta | 33 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 34 | | PASS | 361 | 361 | - | 357 | 4 | 35 | | FAIL | - | - | - | - | - | 36 | | XPASS | - | - | - | - | - | 37 | | XFAIL | 4 | 4 | - | 4 | - | 38 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 39 | | UNTESTED | 26 | 26 | - | 26 | - | 40 | | UNRESOLVED | - | - | - | - | - | 41 | 42 | **GNU GCC** 43 | 44 | * CORE-V hw loops awaiting simulator testing before upstreamable 45 | 46 | ### Next stages 47 | 48 | * Finalise testing for GNU GCC CORE-V hw loops 49 | * Adding GCC changes to the OpenHW Group GCC mirror 50 | * Upstreaming CORE-V support to binutils-gdb 51 | * Upstreaming CORE-V support to gcc 52 | * Repeat the process of hw loops for each of the following groups of instructions, as per the preliminary project plan. i.e. 53 | * multiply-accumulate: xcorevmac 54 | * post-increment and register-indexed load/store: xcorevpostinc 55 | * direct branches: xcorevbi 56 | * general ALU operations: xcorevalu -------------------------------------------------------------------------------- /projects/gnu-tools/2020/monthly-report-2020-11-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain (November 2020) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * University of Bologna and ETH Zurich to contribute 2 engineering months towards the project 8 | * Added CORE-V multiply accumulate support to GNU Binutils incl. full testing - not yet in OpenHW repos 9 | * Added CORE-V multiply accumulate support to GNU GCC, not tested as awaiting simulator - not yet in OpenHW repos 10 | * Added new -march options: xcorevmac (supports the multiply accumulate subset) in both binutils and GCC 11 | 12 | ### Testing status 13 | 14 | **GNU Binutils** 15 | 16 | * Added 28 tests for multiply accumulate 17 | * Added 6 new tests for hw loop to include -march options 18 | 19 | GAS 20 | 21 | | Category | This Month | Last Month | Delta | Baseline | Delta | 22 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 23 | | PASS | 304 | 338 | 34 | 288 | 50 | 24 | | FAIL | - | - | - | - | - | 25 | | XPASS | - | - | - | - | - | 26 | | XFAIL | 15 | 15 | - | 15 | - | 27 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 28 | | UNTESTED | - | - | - | - | - | 29 | | UNRESOLVED | - | - | - | - | - | 30 | 31 | LD 32 | 33 | | Category | This Month | Last Month | Delta | Baseline | Delta | 34 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 35 | | PASS | 361 | 361 | - | 357 | 4 | 36 | | FAIL | - | - | - | - | - | 37 | | XPASS | - | - | - | - | - | 38 | | XFAIL | 4 | 4 | - | 4 | - | 39 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 40 | | UNTESTED | 26 | 26 | - | 26 | - | 41 | | UNRESOLVED | - | - | - | - | - | 42 | 43 | **GNU GCC** 44 | 45 | * CORE-V hw loops and mac awaiting simulator testing before adding to OpenHW repos 46 | 47 | ### Next stages 48 | 49 | * Finalise testing for GNU GCC CORE-V hw loops and mac 50 | * Adding binutils-gdb and GCC changes to the OpenHW Group mirrors 51 | * Upstreaming CORE-V support to binutils-gdb - awaiting mechanism of psABI vendor specific linker relocations 52 | * Upstreaming CORE-V support to GCC - reliant on testing with simulator 53 | * Repeat the process for each of the following groups of instructions as a joint effort between the University of Bologna and Embecosm, as per the preliminary project plan. i.e. 54 | * post-increment and register-indexed load/store: xcorevpostinc 55 | * direct branches: xcorevbi 56 | * general ALU operations: xcorevalu -------------------------------------------------------------------------------- /projects/gnu-tools/2020/two-week-update-report-2020-11-27.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain monthly meeting (27 November 2020) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Added multiply accumulate support to GNU Binutils incl. full testing to OpenHW repos 8 | * Added general ALU operations to GNU Binutils incl. full testing to OpenHW repos 9 | * Added general ALU operations support to GNU GCC, not tested as awaiting simulator 10 | * Added new -march option: xcorevalu (supports the general ALU operations subset) in both binutils and GCC 11 | * Added post-increment and register-indexed load/store to GNU Binutils and begun adding tests 12 | * Updated documentation to include all CORE-V extensions (found at: https://github.com/openhwgroup/core-v-docs/tree/master/cores/cv32e40p/user_manual) 13 | 14 | ### Testing status 15 | 16 | **GNU Binutils** 17 | 18 | GAS 19 | 20 | | Category | This Month | Last Month | Delta | Baseline | Delta | 21 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 22 | | PASS | 394 | 338 | +56 | 288 | +106 | 23 | | FAIL | - | - | - | - | - | 24 | | XPASS | - | - | - | - | - | 25 | | XFAIL | 15 | 15 | - | 15 | - | 26 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 27 | | UNTESTED | - | - | - | - | - | 28 | | UNRESOLVED | - | - | - | - | - | 29 | 30 | LD 31 | 32 | | Category | This Month | Last Month | Delta | Baseline | Delta | 33 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 34 | | PASS | 361 | 361 | - | 357 | +4 | 35 | | FAIL | - | - | - | - | - | 36 | | XPASS | - | - | - | - | - | 37 | | XFAIL | 4 | 4 | - | 4 | - | 38 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 39 | | UNTESTED | 26 | 26 | - | 26 | - | 40 | | UNRESOLVED | - | - | - | - | - | 41 | 42 | **GNU GCC** 43 | 44 | * CORE-V hw loops, mac and alu awaiting simulator testing before adding to OpenHW repos 45 | 46 | ### Risk register changes 47 | 48 | * Two new risks added: 49 | * No suitable target to test against - high risk as limits GCC testing 50 | * University of Bologna / ETH Zurich cannot get FSF assignment - low risk as mitigation plan in place 51 | 52 | ### Next stages 53 | 54 | * Finish testing for post-increment and register-indexed load/store in GNU Binutils and add instruction set to GNU GCC 55 | * Finalise testing for GNU GCC CORE-V hw loops, mac and alu 56 | * Adding binutils-gdb and GCC changes to the OpenHW Group mirrors 57 | * Upstreaming CORE-V support to binutils-gdb - awaiting mechanism of psABI vendor specific linker relocations 58 | * Upstreaming CORE-V support to GCC - reliant on testing with simulator 59 | * Repeat the process for direct branches (xcorevbi) as per the preliminary project plan -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-01-10.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (January 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Pull request created for post-increment and register-indexed load/store support in GNU Binutils - pending changes from review (UOB/ETHZ) 8 | * Began adding immediate branching instruction tests (UOB/ETHZ) 9 | * Updated tests in all previously added instruction subsets to follow UOB/ETHZ and Embecosm agreed format (Embecosm) 10 | 11 | ### Task status 12 | 13 | | Category | This Month | Last Month | Delta | 14 | | -----------:| ----------:| ----------:| --------:| 15 | | Unstarted | 7 | 8 | -1 | 16 | | In progress | 4 | 3 | +1 | 17 | | Complete | 11 | 11 | - | 18 | 19 | In progress: 20 | * Add PI & RI L/S tests to binutils-gdb 21 | * Add IB support to binutils-gdb 22 | * Add IB tests to binutils-gdb (Updated status) 23 | * Project management - ongoing 24 | 25 | ### Testing status 26 | 27 | **GNU Binutils** 28 | 29 | GAS 30 | 31 | | Category | This Month | Last Month | Delta | Baseline | Delta | 32 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 33 | | PASS | 376 | 394 | -18 | 288 | +88 | 34 | | FAIL | - | - | - | - | - | 35 | | XPASS | - | - | - | - | - | 36 | | XFAIL | 15 | 15 | - | 15 | - | 37 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 38 | | UNTESTED | - | - | - | - | - | 39 | | UNRESOLVED | - | - | - | - | - | 40 | 41 | Not incl. PI & RI L/S and IB tests 42 | 43 | LD 44 | 45 | | Category | This Month | Last Month | Delta | Baseline | Delta | 46 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 47 | | PASS | 361 | 361 | - | 357 | +4 | 48 | | FAIL | - | - | - | - | - | 49 | | XPASS | - | - | - | - | - | 50 | | XFAIL | 4 | 4 | - | 4 | - | 51 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 52 | | UNTESTED | 26 | 26 | - | 26 | - | 53 | | UNRESOLVED | - | - | - | - | - | 54 | 55 | **GNU GCC** 56 | 57 | * CORE-V hardware loops, multiply accumulate and general ALU operations awaiting hardware testing 58 | 59 | ### Risk register changes 60 | 61 | No changes. 62 | 63 | ### Next stages 64 | 65 | * Update post-increment and register-indexed load/store from review comments (UOB/ETHZ) 66 | * Finish adding tests for immediate branching instructions (UOB/ETHZ) 67 | * Add PI & RI L/S and IB support in binutils-gdb to OpenHW repos (UOB/ETHZ) 68 | * Add PI & RI L/S and IB support to GNU GCC (UOB/ETHZ) 69 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations (Embecosm) 70 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations and reliant on successful hardware testing (UOB/ETHZ and Embecosm) -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-03-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (March 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Existing PULP simulator is being adapted to support CORE-V extensions 8 | * Work on integrating GCC regression testsuite with simulator begun 9 | * UOB team begin Embecosm consultancy 10 | 11 | ### Task status 12 | 13 | | Category | This Month | Last Month | Delta | 14 | | -----------:| ----------:| ----------:| --------:| 15 | | Unstarted | 13 | 13 | - | 16 | | In progress | 6 | 4 | +2 | 17 | | Complete | 17 | 17 | - | 18 | 19 | New tasks: 20 | * Adapt existing PULP simulator to support CORE-V extentions (In progress) 21 | * Integrate testing for GCC regression testsuite with simulator (In progress) 22 | 23 | ### Testing status 24 | 25 | **GNU Binutils** 26 | 27 | GAS 28 | 29 | | Category | This Month | Last Month | Delta | Baseline | Delta | 30 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 31 | | PASS | 434 | 434 | - | 288 | +146 | 32 | | FAIL | - | - | - | - | - | 33 | | XPASS | - | - | - | - | - | 34 | | XFAIL | 15 | 15 | - | 15 | - | 35 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 36 | | UNTESTED | - | - | - | - | - | 37 | | UNRESOLVED | - | - | - | - | - | 38 | 39 | LD 40 | 41 | | Category | This Month | Last Month | Delta | Baseline | Delta | 42 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 43 | | PASS | 363 | 363 | - | 357 | +6 | 44 | | FAIL | - | - | - | - | - | 45 | | XPASS | - | - | - | - | - | 46 | | XFAIL | 4 | 4 | - | 4 | - | 47 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 48 | | UNTESTED | 26 | 26 | - | 26 | - | 49 | | UNRESOLVED | - | - | - | - | - | 50 | 51 | **GNU GCC** 52 | 53 | * Hardware loops, multiply accumulate and general ALU operations awaiting testing 54 | 55 | ### Risk register changes 56 | 57 | No changes. 58 | 59 | ### Next stages 60 | 61 | * Finalise CORE-V simulator incl. testing integration 62 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 63 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 64 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 65 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-04-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (April 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Existing PULP simulator continues to be adapted to support CORE-V extensions - nearing completion 8 | * Working on integrating GCC regression testsuite with simulator 9 | 10 | ### Task status 11 | 12 | | Category | This Month | Last Month | Delta | 13 | | -----------:| ----------:| ----------:| --------:| 14 | | Unstarted | 13 | 13 | - | 15 | | In progress | 6 | 6 | - | 16 | | Complete | 17 | 17 | - | 17 | 18 | ### Testing status 19 | 20 | **GNU Binutils** 21 | 22 | GAS 23 | 24 | | Category | This Month | Last Month | Delta | Baseline | Delta | 25 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 26 | | PASS | 434 | 434 | - | 288 | +146 | 27 | | FAIL | - | - | - | - | - | 28 | | XPASS | - | - | - | - | - | 29 | | XFAIL | 15 | 15 | - | 15 | - | 30 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 31 | | UNTESTED | - | - | - | - | - | 32 | | UNRESOLVED | - | - | - | - | - | 33 | 34 | LD 35 | 36 | | Category | This Month | Last Month | Delta | Baseline | Delta | 37 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 38 | | PASS | 363 | 363 | - | 357 | +6 | 39 | | FAIL | - | - | - | - | - | 40 | | XPASS | - | - | - | - | - | 41 | | XFAIL | 4 | 4 | - | 4 | - | 42 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 43 | | UNTESTED | 26 | 26 | - | 26 | - | 44 | | UNRESOLVED | - | - | - | - | - | 45 | 46 | **GNU GCC** 47 | 48 | * Hardware loops, multiply accumulate and general ALU operations awaiting testing 49 | 50 | ### Risk register changes 51 | 52 | No changes. 53 | 54 | ### Next stages 55 | 56 | * Finalise CORE-V simulator incl. testing integration 57 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 58 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 59 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 60 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-05-10.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update / Bologna SW Team (May 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Existing PULP simulator adapted to support CORE-V extensions - completion 8 | * Writing blog post on PULP simulator - In progress 9 | * Working on integrating GCC regression testsuite with PULP simulator - In progress 10 | 11 | ### Testing status 12 | 13 | **GNU Binutils** 14 | 15 | GAS 16 | 17 | | Category | This Month | Last Month | Delta | Baseline | Delta | 18 | | -----------: | -----------: | -----------: | -----: | ---------: | ------:| 19 | | PASS | 434 | 434 | - | 288 | +146 | 20 | | FAIL | - | - | - | - | - | 21 | | XPASS | - | - | - | - | - | 22 | | XFAIL | 15 | 15 | - | 15 | - | 23 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 24 | | UNTESTED | - | - | - | - | - | 25 | | UNRESOLVED | - | - | - | - | - | 26 | 27 | LD 28 | 29 | | Category | This Month | Last Month | Delta | Baseline | Delta | 30 | | -----------: | -----------: | -----------: | -----: | ---------: | ------:| 31 | | PASS | 363 | 363 | - | 357 | +6 | 32 | | FAIL | - | - | - | - | - | 33 | | XPASS | - | - | - | - | - | 34 | | XFAIL | 4 | 4 | - | 4 | - | 35 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 36 | | UNTESTED | 26 | 26 | - | 26 | - | 37 | | UNRESOLVED | - | - | - | - | - | 38 | 39 | **GNU GCC** 40 | 41 | * Hardware loops, multiply accumulate and general ALU operations awaiting testing 42 | 43 | ### Next stages 44 | 45 | * Finalise integrating GCC regression testsuite with PULP simulator 46 | * Finalise PULP simulator blog post 47 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 48 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 49 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 50 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-06-14.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (June 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Working on integrating GCC regression testsuite with PULP simulator 8 | * Began rebase of CORE-V binutils-gdb 9 | * Editting blog post about using the PULP simulator 10 | 11 | ### Task status 12 | 13 | | Category | This Month | Last Month | Delta | 14 | | -----------:| ----------:| ----------:| --------:| 15 | | Unstarted | 13 | 13 | - | 16 | | In progress | 5 | 6 | -1 | 17 | | Complete | 18 | 17 | +1 | 18 | 19 | Details: 20 | Adapt PULP simulator to support CORE-V - Complete 21 | 22 | ### Testing status 23 | 24 | **GNU Binutils** 25 | 26 | GAS 27 | 28 | | Category | This Month | Last Month | Delta | Baseline | Delta | 29 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 30 | | PASS | 434 | 434 | - | 288 | +146 | 31 | | FAIL | - | - | - | - | - | 32 | | XPASS | - | - | - | - | - | 33 | | XFAIL | 15 | 15 | - | 15 | - | 34 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 35 | | UNTESTED | - | - | - | - | - | 36 | | UNRESOLVED | - | - | - | - | - | 37 | 38 | LD 39 | 40 | | Category | This Month | Last Month | Delta | Baseline | Delta | 41 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 42 | | PASS | 363 | 363 | - | 357 | +6 | 43 | | FAIL | - | - | - | - | - | 44 | | XPASS | - | - | - | - | - | 45 | | XFAIL | 4 | 4 | - | 4 | - | 46 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 47 | | UNTESTED | 26 | 26 | - | 26 | - | 48 | | UNRESOLVED | - | - | - | - | - | 49 | 50 | **GNU GCC** 51 | 52 | * Hardware loops, multiply accumulate and general ALU operations awaiting testing 53 | 54 | ### Risk register changes 55 | 56 | No changes. 57 | 58 | ### Next stages 59 | 60 | * Finalise CORE-V simulator incl. testing integration 61 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 62 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 63 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 64 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-07-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (July 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Working on integrating GCC regression testsuite with PULP simulator 8 | - currently able to run GCC regression, however, ironing out issues with unresolved tests 9 | * Began writing CORE-V GCC tests 10 | 11 | ### Task status 12 | 13 | | Category | This Month | Last Month | Delta | 14 | | -----------:| ----------:| ----------:| --------:| 15 | | Unstarted | 13 | 13 | - | 16 | | In progress | 5 | 5 | - | 17 | | Complete | 18 | 18 | - | 18 | 19 | ### Testing status 20 | 21 | **GNU Binutils** 22 | 23 | GAS 24 | 25 | | Category | This Month | Last Month | Delta | Baseline | Delta | 26 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 27 | | PASS | 434 | 434 | - | 288 | +146 | 28 | | FAIL | - | - | - | - | - | 29 | | XPASS | - | - | - | - | - | 30 | | XFAIL | 15 | 15 | - | 15 | - | 31 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 32 | | UNTESTED | - | - | - | - | - | 33 | | UNRESOLVED | - | - | - | - | - | 34 | 35 | LD 36 | 37 | | Category | This Month | Last Month | Delta | Baseline | Delta | 38 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 39 | | PASS | 363 | 363 | - | 357 | +6 | 40 | | FAIL | - | - | - | - | - | 41 | | XPASS | - | - | - | - | - | 42 | | XFAIL | 4 | 4 | - | 4 | - | 43 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 44 | | UNTESTED | 26 | 26 | - | 26 | - | 45 | | UNRESOLVED | - | - | - | - | - | 46 | 47 | **GNU GCC** 48 | 49 | * Hardware loops, multiply accumulate and general ALU operations awaiting testing 50 | 51 | ### Risk register changes 52 | 53 | No changes. 54 | 55 | ### Next stages 56 | 57 | * Finalise integration of GCC regression with PULP simulator 58 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 59 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 60 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 61 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-08-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (August 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Working on integrating GCC regression testsuite with PULP simulator 8 | - currently able to run GCC regression, however, ironing out issues with unresolved tests 9 | * Binutils rebase pushed to OpenHW development branch 10 | - rebasing remaining instructions (post-increment & register-indexed load/store and immediate branching) before merge 11 | * Writing GCC regression tests for multiply-accumulate and alu ops 12 | - finished MAC builtin tests and 80% of ALU builtin tests 13 | 14 | ### Task status 15 | 16 | | Category | This Month | Last Month | Delta | 17 | | -----------:| ----------:| ----------:| --------:| 18 | | Unstarted | 13 | 13 | - | 19 | | In progress | 5 | 5 | - | 20 | | Complete | 18 | 18 | - | 21 | 22 | ### Testing status 23 | 24 | **GNU Binutils** 25 | 26 | GAS 27 | 28 | | Category | This Month | Last Month | Delta | Baseline | Delta | 29 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 30 | | PASS | 434 | 434 | - | 288 | +146 | 31 | | FAIL | - | - | - | - | - | 32 | | XPASS | - | - | - | - | - | 33 | | XFAIL | 15 | 15 | - | 15 | - | 34 | | UNSUPPORTED | 10 | 10 | - | 10 | - | 35 | | UNTESTED | - | - | - | - | - | 36 | | UNRESOLVED | - | - | - | - | - | 37 | 38 | LD 39 | 40 | | Category | This Month | Last Month | Delta | Baseline | Delta | 41 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 42 | | PASS | 363 | 363 | - | 357 | +6 | 43 | | FAIL | - | - | - | - | - | 44 | | XPASS | - | - | - | - | - | 45 | | XFAIL | 4 | 4 | - | 4 | - | 46 | | UNSUPPORTED | 171 | 171 | - | 171 | - | 47 | | UNTESTED | 26 | 26 | - | 26 | - | 48 | | UNRESOLVED | - | - | - | - | - | 49 | 50 | **GNU GCC** 51 | 52 | * Hardware loops, multiply accumulate and general ALU operations testing in progress 53 | 54 | ### Risk register changes 55 | 56 | No changes. 57 | 58 | ### Next stages 59 | 60 | * Finalise integration of GCC regression with PULP simulator 61 | * Merge post-increment & register-indexed load/store and immediate branching support in binutils-gdb to OpenHW repo 62 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 63 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 64 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism of psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-09-13.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (September 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Merged in remaining instruction sets (post-increment & register-indexed load/store and immediate branching) to binutils-gdb 8 | - All planned support for CORE-V extensions is now complete in binutils-gdb 9 | * Working on integrating GCC regression testsuite with GVSoC simulator 10 | - Currently able to run GCC regression, however, ironing out issues with unresolved/failing tests 11 | * Enrico Tabanelli and I will be presenting the CORE-V toolchain (including simulator) work at the GNU Tools Track of Linux Plumbers Conference on Thursday 23 September at 08:45 Pacific Time 12 | 13 | ### Task status 14 | 15 | | Category | This Month | Last Month | Delta | 16 | | -----------:| ----------:| ----------:| --------:| 17 | | Unstarted | 13 | 13 | - | 18 | | In progress | 3 | 5 | -2 | 19 | | Complete | 20 | 18 | +2 | 20 | 21 | Details: 22 | Merge Xcorevmem into OpenHW binutils-gdb - Complete 23 | Merge Xcorevbi into OpenHW binutils-gdb - Complete 24 | 25 | ### Testing status 26 | 27 | **GNU Binutils** 28 | 29 | GAS 30 | 31 | | Category | This Month | Last Month | Delta | Baseline | Delta | 32 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 33 | | PASS | 489 | 443 | +46 | 355 | +134 | 34 | | FAIL | - | - | - | - | - | 35 | | XPASS | - | - | - | - | - | 36 | | XFAIL | 21 | 21 | - | 21 | - | 37 | | UNSUPPORTED | 5 | 5 | - | 5 | - | 38 | | UNTESTED | - | - | - | - | - | 39 | | UNRESOLVED | - | - | - | - | - | 40 | 41 | LD 42 | 43 | | Category | This Month | Last Month | Delta | Baseline | Delta | 44 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 45 | | PASS | 408 | 406 | +2 | 402 | +6 | 46 | | FAIL | - | - | - | - | - | 47 | | XPASS | - | - | - | - | - | 48 | | XFAIL | 4 | 4 | - | 4 | - | 49 | | UNSUPPORTED | 182 | 182 | - | 182 | - | 50 | | UNTESTED | 26 | 26 | - | 26 | - | 51 | | UNRESOLVED | - | - | - | - | - | 52 | 53 | Note: Numbers have been adjusted to factor in re-base 54 | 55 | **GNU GCC** 56 | 57 | * Hardware loops, multiply accumulate and general ALU operations testing in progress 58 | 59 | ### Risk register changes 60 | 61 | No changes. 62 | 63 | ### Next stages 64 | 65 | * Finalise integration of GCC regression with PULP simulator 66 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 67 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 68 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism for psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-10-11.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (October 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Continuing work on integrating GCC regression testsuite with GVSoC simulator 8 | - Currently able to run GCC regression and now ironing out issues with unresolved/failing tests 9 | 10 | ### Task status 11 | 12 | | Category | This Month | Last Month | Delta | 13 | | -----------:| ----------:| ----------:| --------:| 14 | | Unstarted | 13 | 13 | - | 15 | | In progress | 3 | 3 | - | 16 | | Complete | 20 | 20 | - | 17 | 18 | ### Testing status 19 | 20 | **GNU Binutils** 21 | 22 | GAS 23 | 24 | | Category | This Month | Last Month | Delta | Baseline | Delta | 25 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 26 | | PASS | 489 | 489 | - | 355 | +134 | 27 | | FAIL | - | - | - | - | - | 28 | | XPASS | - | - | - | - | - | 29 | | XFAIL | 21 | 21 | - | 21 | - | 30 | | UNSUPPORTED | 5 | 5 | - | 5 | - | 31 | | UNTESTED | - | - | - | - | - | 32 | | UNRESOLVED | - | - | - | - | - | 33 | 34 | LD 35 | 36 | | Category | This Month | Last Month | Delta | Baseline | Delta | 37 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 38 | | PASS | 408 | 408 | - | 402 | +6 | 39 | | FAIL | - | - | - | - | - | 40 | | XPASS | - | - | - | - | - | 41 | | XFAIL | 4 | 4 | - | 4 | - | 42 | | UNSUPPORTED | 182 | 182 | - | 182 | - | 43 | | UNTESTED | 26 | 26 | - | 26 | - | 44 | | UNRESOLVED | - | - | - | - | - | 45 | 46 | **GNU GCC** 47 | 48 | * Hardware loops, multiply accumulate and general ALU operations testing in progress 49 | 50 | ### Risk register changes 51 | 52 | No changes. 53 | 54 | ### Next stages 55 | 56 | * Finalise integration of GCC regression with PULP simulator 57 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 58 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 59 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism for psABI vendor specific linker relocations -------------------------------------------------------------------------------- /projects/gnu-tools/2021/monthly-report-2021-11-8.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V GNU Tool Chain update (November 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Continuing work on integrating GCC regression testsuite with GVSoC simulator 8 | - Currently able to run GCC regression and now ironing out issues with unresolved/failing tests 9 | 10 | ### Task status 11 | 12 | | Category | This Month | Last Month | Delta | 13 | | -----------:| ----------:| ----------:| --------:| 14 | | Unstarted | 13 | 13 | - | 15 | | In progress | 3 | 3 | - | 16 | | Complete | 20 | 20 | - | 17 | 18 | ### Testing status 19 | 20 | **GNU Binutils** 21 | 22 | GAS 23 | 24 | | Category | This Month | Last Month | Delta | Baseline | Delta | 25 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 26 | | PASS | 489 | 489 | - | 355 | +134 | 27 | | FAIL | - | - | - | - | - | 28 | | XPASS | - | - | - | - | - | 29 | | XFAIL | 21 | 21 | - | 21 | - | 30 | | UNSUPPORTED | 5 | 5 | - | 5 | - | 31 | | UNTESTED | - | - | - | - | - | 32 | | UNRESOLVED | - | - | - | - | - | 33 | 34 | LD 35 | 36 | | Category | This Month | Last Month | Delta | Baseline | Delta | 37 | | -----------:| ---------: | ---------: | ---------: | ---------: | ---------: | 38 | | PASS | 408 | 408 | - | 402 | +6 | 39 | | FAIL | - | - | - | - | - | 40 | | XPASS | - | - | - | - | - | 41 | | XFAIL | 4 | 4 | - | 4 | - | 42 | | UNSUPPORTED | 182 | 182 | - | 182 | - | 43 | | UNTESTED | 26 | 26 | - | 26 | - | 44 | | UNRESOLVED | - | - | - | - | - | 45 | 46 | **GNU GCC** 47 | 48 | * Hardware loops, multiply accumulate and general ALU operations testing in progress 49 | 50 | ### Risk register changes 51 | 52 | No changes. 53 | 54 | ### Next stages 55 | 56 | * Finalise integration of GCC regression with PULP simulator 57 | * Add post-increment & register-indexed load/store and immediate branching support to GCC 58 | * Finalise GCC testing for CORE-V hardware loops, multiply accumulate and general ALU operations 59 | * Upstream CORE-V support to binutils-gdb and GCC - awaiting mechanism for psABI vendor specific linker relocations 60 | -------------------------------------------------------------------------------- /projects/gnu-tools/2022/monthly-report-2022-02-14.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (February 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | From University of Bologna: 8 | 9 | * Upstreaming CORE-V post-increment and register-indexed load/store 10 | support and tests to gcc - First pull request is ongoing (Two steps 11 | of internal reviews from Maxim Blinov and Jeremy Bennett have 12 | already been done). Testsuite is currently composed by only 13 | compilation regression tests. Execution tests are ongoing. 14 | 15 | * Upstreaming CORE-V immediate branching support and tests to gcc - 16 | First internal review from Maxim Blinov and Jeremy Bennett is 17 | scheduled for Friday, 18 Feb 2022. Tests has not been added yet. 18 | 19 | From PLCT: 20 | 21 | * Work has been done on supporting the ZCE(code size reduction) 22 | extension on corev-gcc and corev-binutils. We had a PR and got some 23 | advise from OpenHW. Now we are updating the implement with those 24 | advise. We plan to finish this work within this month(Feb). 25 | 26 | ### Testing status 27 | 28 | **GNU Binutils** 29 | 30 | GAS 31 | 32 | | Category | Start | Now | Delta | 33 | | -----------:| ---------: | ---------: | ---------: | 34 | | PASS | - | - | - | 35 | | FAIL | - | - | - | 36 | | XPASS | - | - | - | 37 | | XFAIL | - | - | - | 38 | | UNSUPPORTED | - | - | - | 39 | | UNTESTED | - | - | - | 40 | | UNRESOLVED | - | - | - | 41 | 42 | LD 43 | 44 | | Category | Start | Now | Delta | 45 | | -----------:| ---------: | ---------: | ---------: | 46 | | PASS | - | - | - | 47 | | FAIL | - | - | - | 48 | | XPASS | - | - | - | 49 | | XFAIL | - | - | - | 50 | | UNSUPPORTED | - | - | - | 51 | | UNTESTED | - | - | - | 52 | | UNRESOLVED | - | - | - | 53 | 54 | 55 | **GCC** 56 | 57 | GCC 58 | 59 | | Category | Start | Now | Delta | 60 | | -----------:| ---------: | ---------: | ---------: | 61 | | PASS | 0 | 53 | +53 | 62 | | FAIL | 0 | 11 | +11 | 63 | | XPASS | - | - | - | 64 | | XFAIL | - | - | - | 65 | | UNSUPPORTED | - | - | - | 66 | | UNTESTED | - | - | - | 67 | | UNRESOLVED | - | - | - | 68 | 69 | 70 | ### Next stages 71 | 72 | * Adding execution tests to corev testsuite targeting GVSoC simulation platform 73 | * Finalizing the pull request for xcorevmem extensions to openhw repo 74 | * Finalizing the first review of the xcorevbi extensions -------------------------------------------------------------------------------- /projects/gnu-tools/2022/monthly-report-2022-03-14.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (February 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | From University of Bologna: 8 | 9 | Key activities 10 | 11 | * Upstreaming CORE-V post-increment and register-indexed load/store 12 | support and tests to gcc - First pull request is on going (Two 13 | steps of internal reviews from Maxim Blinov and Jeremy Bennett has 14 | already been done). Testsuite is currently composed by compilation 15 | and execution regression tests. Outcome: Issue with lb, lbu, and sb 16 | occurs. It might be due to diffeent cost functions. 17 | 18 | * Upstreaming CORE-V immediate branching support and tests to gcc - 19 | First internal review from Maxim Blinov and Jeremy Bennett has been 20 | done. Outcome: Clean up the code since it might be redundant. 21 | 22 | # Next stage: 23 | 24 | 25 | * Fixing issue with load/store byte instructions 26 | * Finalizing the pull request for xcorevmem extensions to openhw repo 27 | * Finalizing the second review of the xcorevbi extensions 28 | 29 | 30 | From PLCT: 31 | 32 | * Support for extending the ZCA, ZCF, ZCB and ZCMB extension has been 33 | completed, together with a comprehensive testsuite. 34 | 35 | * Next stage will be to develop ZCMP support. 36 | 37 | * Work will be rebased on latest compiler. 38 | 39 | ### Testing status 40 | 41 | **GNU Binutils** 42 | 43 | GAS 44 | 45 | | Category | Start | Now | Delta | 46 | | -----------:| ---------: | ---------: | ---------: | 47 | | PASS | - | - | - | 48 | | FAIL | - | - | - | 49 | | XPASS | - | - | - | 50 | | XFAIL | - | - | - | 51 | | UNSUPPORTED | - | - | - | 52 | | UNTESTED | - | - | - | 53 | | UNRESOLVED | - | - | - | 54 | 55 | LD 56 | 57 | | Category | Start | Now | Delta | 58 | | -----------:| ---------: | ---------: | ---------: | 59 | | PASS | - | - | - | 60 | | FAIL | - | - | - | 61 | | XPASS | - | - | - | 62 | | XFAIL | - | - | - | 63 | | UNSUPPORTED | - | - | - | 64 | | UNTESTED | - | - | - | 65 | | UNRESOLVED | - | - | - | 66 | 67 | 68 | **GCC** 69 | 70 | GCC 71 | 72 | | Category | Start | Now | Delta | 73 | | -----------:| ---------: | ---------: | ---------: | 74 | | PASS | 0 | 53 | +53 | 75 | | FAIL | 0 | 11 | +11 | 76 | | XPASS | - | - | - | 77 | | XFAIL | - | - | - | 78 | | UNSUPPORTED | - | - | - | 79 | | UNTESTED | - | - | - | 80 | | UNRESOLVED | - | - | - | 81 | 82 | 83 | ### Next stages 84 | 85 | * Adding execution tests to corev testsuite targeting GVSoC simulation platform 86 | * Finalizing the pull request for xcorevmem extensions to openhw repo 87 | * Finalizing the first review of the xcorevbi extensions -------------------------------------------------------------------------------- /projects/gnu-tools/2022/monthly-report-2022-04-11.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (February 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | From University of Bologna: 8 | 9 | Key activities 10 | 11 | * Upstreaming CORE-V immediate branching support and tests to gcc 12 | * Cleaning up the code from redundancies. 13 | * riscv.c has needed changes to avoid forcing register for operand 1. 14 | 15 | ### Next stage: 16 | 17 | * Fixing issue with load/store byte instructions 18 | * Finalizing the pull request for xcorevmem extensions to openhw repo 19 | * Finalizing the pull request for xcorevbi extensions to openhw repo 20 | 21 | From PLCT: 22 | 23 | * We had finished ZC extension development works in the past month, 24 | now we are working on debugging and benchmarking jobs. 25 | 26 | ### Testing status 27 | 28 | **GNU Binutils** 29 | 30 | GAS 31 | 32 | | Category | Start | Now | Delta | 33 | | -----------:| ---------: | ---------: | ---------: | 34 | | PASS | - | - | - | 35 | | FAIL | - | - | - | 36 | | XPASS | - | - | - | 37 | | XFAIL | - | - | - | 38 | | UNSUPPORTED | - | - | - | 39 | | UNTESTED | - | - | - | 40 | | UNRESOLVED | - | - | - | 41 | 42 | LD 43 | 44 | | Category | Start | Now | Delta | 45 | | -----------:| ---------: | ---------: | ---------: | 46 | | PASS | - | - | - | 47 | | FAIL | - | - | - | 48 | | XPASS | - | - | - | 49 | | XFAIL | - | - | - | 50 | | UNSUPPORTED | - | - | - | 51 | | UNTESTED | - | - | - | 52 | | UNRESOLVED | - | - | - | 53 | 54 | 55 | **GCC** 56 | 57 | GCC 58 | 59 | | Category | Start | Now | Delta | 60 | | -----------:| ---------: | ---------: | ---------: | 61 | | PASS | 53 | 63 | +10 | 62 | | FAIL | 11 | 11 | - | 63 | | XPASS | - | - | - | 64 | | XFAIL | - | - | - | 65 | | UNSUPPORTED | - | - | - | 66 | | UNTESTED | - | - | - | 67 | | UNRESOLVED | - | - | - | 68 | -------------------------------------------------------------------------------- /projects/gnu-tools/2022/monthly-report-2022-05-09.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (February 2022) 2 | 3 | ## Overview 4 | 5 | From University of Bologna: 6 | 7 | ### Key activities 8 | 9 | * Upstreaming CORE-V immediate branching support and tests to gcc - 10 | Rabasing on top of the openhw repo 11 | 12 | ### Next stages 13 | 14 | * Fixing issue with load/store byte instructions 15 | * Finalizing the pull request for xcorevmem extensions to openhw repo 16 | * Finalizing the pull request for xcorevbi extensions to openhw repo 17 | 18 | From PLCT: 19 | 20 | ### Key activities 21 | 22 | * We had finished the development work for code-size-reduction 23 | extension, and rebase it into corev-gcc/binutils branches. 24 | 25 | ### Next stages: 26 | * Meet some regression bugs on ld and trying to fix them. 27 | 28 | ### University of Bologna Testing status 29 | 30 | **GNU Binutils** 31 | 32 | GAS 33 | 34 | | Category | Start | Now | Delta | 35 | | -----------:| ---------: | ---------: | ---------: | 36 | | PASS | - | - | - | 37 | | FAIL | - | - | - | 38 | | XPASS | - | - | - | 39 | | XFAIL | - | - | - | 40 | | UNSUPPORTED | - | - | - | 41 | | UNTESTED | - | - | - | 42 | | UNRESOLVED | - | - | - | 43 | 44 | LD 45 | 46 | | Category | Start | Now | Delta | 47 | | -----------:| ---------: | ---------: | ---------: | 48 | | PASS | - | - | - | 49 | | FAIL | - | - | - | 50 | | XPASS | - | - | - | 51 | | XFAIL | - | - | - | 52 | | UNSUPPORTED | - | - | - | 53 | | UNTESTED | - | - | - | 54 | | UNRESOLVED | - | - | - | 55 | 56 | 57 | **GCC** 58 | 59 | GCC 60 | 61 | | Category | Start | Now | Delta | 62 | | -----------:| ---------: | ---------: | ---------: | 63 | | PASS | 63 | 63 | - | 64 | | FAIL | 11 | 11 | - | 65 | | XPASS | - | - | - | 66 | | XFAIL | - | - | - | 67 | | UNSUPPORTED | - | - | - | 68 | | UNTESTED | - | - | - | 69 | | UNRESOLVED | - | - | - | -------------------------------------------------------------------------------- /projects/gnu-tools/2022/monthly-report-2022-08-08.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (August 2022) 2 | 3 | ## Overview 4 | 5 | From University of Bologna: 6 | 7 | ### Key activities 8 | 9 | * Integrating and testing mem extensions 10 | * Rrebased the repo with the upstream version. 11 | * The regression summary of cv-mem-* tests is the following: 12 | 13 | ``` 14 | === gcc Summary === 15 | 16 | # of expected passes 594 17 | # of unexpected failures 218 18 | # of expected failures 62 /* with -O0 the auto-inc-dec pass is disabled */ 19 | ``` 20 | 21 | Several tests fail with the new testing framework that loops on different compile options and flags, and they may be skipped. 22 | 23 | From PLCT: 24 | 25 | ### Key activities 26 | 27 | * Written the testsuites for ZC extension 28 | * Do code size test on Embench and published the result 29 | * Sync work to RISC-V code-size-reduction TG 30 | 31 | -------------------------------------------------------------------------------- /projects/gnu-tools/2023/monthly-report-2023-01-09.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (January 2023) 2 | 3 | ## Overview 4 | 5 | From University of Bologna: 6 | 7 | ### Key activities 8 | 9 | #### GCC 10 | * Pull Request to add branching immediate instructions and testcases 11 | 12 | ``` 13 | === gcc Summary === 14 | 15 | # of expected passes 2736 16 | # of unexpected failures 53 17 | # of expected failures 6 18 | # of unresolved testcases 6 19 | # of unsupported tests 201 20 | ``` 21 | 22 | From PLCT: 23 | 24 | ### Key activities 25 | 26 | #### Binutils 27 | * Fix issues with ZCMT 28 | * Added ld testcases for ZCMT 29 | * Added --zcmt-force-table-jump option 30 | 31 | #### GCC 32 | * Fix issues with ZCMT 33 | * Extended RVC to RVC*ZCA 34 | 35 | From Embecosm: 36 | 37 | ### Key activities 38 | 39 | #### Binutils 40 | * Added Event Load Instructions and Testcases 41 | * Added SIMD Instructions and Testcases 42 | * Added Bit Manipulation Instructions and Testcases 43 | * Updated CV32E40Pv1 Encodings for CV32E40Pv2: 44 | * Multiply Accumulate 45 | * General ALU Operations 46 | * Immediate Branching 47 | 48 | ``` 49 | === gas Summary === 50 | 51 | # of expected passes 1268 52 | # of expected failures 23 53 | # of unsupported tests 9 54 | ``` 55 | 56 | #### GCC 57 | * Added Event Load Builtin and Testcase 58 | 59 | ``` 60 | === gcc Summary === 61 | 62 | # of expected passes 2589 63 | # of unexpected failures 53 64 | # of expected failures 6 65 | # of unresolved testcases 6 66 | # of unsupported tests 201 67 | ``` 68 | 69 | Planned Events: 70 | * Update CV32E40Pv1 Encodings for CV32E40Pv2: 71 | * Hardware Loops 72 | * Post-incrementing Load/Store 73 | * Add SIMD builtins and testcases 74 | * Fix issues with ZCMT in Binutils 75 | * Continue discussion on CORE-V builtin names in GCC 76 | -------------------------------------------------------------------------------- /projects/gnu-tools/2023/monthly-report-2023-02-13.md: -------------------------------------------------------------------------------- 1 | # CORE-V GNU Tool Chain Monthly Report (February 2023) 2 | 3 | ## Overview 4 | 5 | From University of Bologna: 6 | 7 | ### Key activities 8 | 9 | #### GCC 10 | * Open Pull Request: 11 | * [Implemented PULP Branching Immediate Instructions and GCC Tests](https://github.com/openhwgroup/corev-gcc/pull/9) 12 | 13 | ``` 14 | === gcc Summary === 15 | 16 | # of expected passes 2736 17 | # of unexpected failures 53 18 | # of expected failures 6 19 | # of unresolved testcases 6 20 | # of unsupported tests 201 21 | ``` 22 | 23 | From PLCT: 24 | 25 | ### Key activities 26 | 27 | #### Binutils 28 | * Working on issues with ZCMT 29 | * Cleaning up issues in Binutils with Zc* 30 | 31 | * Open Pull Request: 32 | * Reviewing [Update Zc* to Version 1.0.1](https://github.com/openhwgroup/corev-binutils-gdb/pull/65) 33 | 34 | From Embecosm: 35 | 36 | ### Key activities 37 | 38 | #### Binutils 39 | * Reviewed and Merged Pull Requests: 40 | * [Updated CV32E40Pv2 Hardware Loop Encodings](https://github.com/openhwgroup/corev-binutils-gdb/pull/60) 41 | * [Added New CV32340Pv2 Hardware Loop Instructions](https://github.com/openhwgroup/corev-binutils-gdb/pull/62) 42 | * [Updated CV32E40Pv2 Post-incrementing Load/Store](https://github.com/openhwgroup/corev-binutils-gdb/pull/61) 43 | 44 | * Fixed Issues: 45 | * [Fixed CV32E40Pv2 Bit Manipulation Immediate Order](https://github.com/openhwgroup/corev-binutils-gdb/pull/71) 46 | * [Fixed CV32E4OPv2 Immediate Branching Relocation Tests](https://github.com/openhwgroup/corev-binutils-gdb/pull/72) 47 | 48 | * Open Pull Requests: 49 | * [Fixed CV32340Pv2 SIMD Unsigned Immediate Instructions](https://github.com/openhwgroup/corev-binutils-gdb/pull/74) 50 | 51 | ``` 52 | === gas Summary === 53 | 54 | # of expected passes 1270 55 | # of expected failures 23 56 | # of unsupported tests 9 57 | ``` 58 | 59 | #### GCC 60 | * Reviewed and Merged Pull Requests: 61 | * [Implemented CV32E40Pv2 Multiply-Accumulate Builtins](https://github.com/openhwgroup/corev-gcc/pull/18) 62 | 63 | * Open Pull Requests: 64 | * [Implemented CV32E40Pv2 SIMD Builtins](https://github.com/openhwgroup/corev-gcc/pull/19) 65 | * [CORE-V GCC Builtin Specification](https://github.com/openhwgroup/core-v-sw/blob/master/specifications/corev-builtin-spec.md) 66 | 67 | ``` 68 | === gcc Summary === 69 | 70 | # of expected passes 3681 71 | # of unexpected failures 53 72 | # of expected failures 6 73 | # of unresolved testcases 6 74 | # of unsupported tests 233 75 | ``` 76 | 77 | Planned Events: 78 | * Fix issues with ZCMT in Binutils and GCC 79 | * Fix issues with CV32E40Pv2 in Binutils 80 | * Continue discussion on CORE-V builtin names in GCC 81 | * Implement CV32E40Pv2 SIMD Builtins in GCC 82 | * Implement CV32E40Pv2 General ALU Builtins in GCC 83 | * Implement CV32E40Pv2 Bit Manipulation Builtins in GCC 84 | -------------------------------------------------------------------------------- /projects/gnu-tools/README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group: GNU Tools Project 2 | 3 | A directory for materials associated with reporting progress with the CORE-V 4 | GNU Tools project 5 | -------------------------------------------------------------------------------- /projects/gnu-tools/additional-materials/supplementary-notes.md: -------------------------------------------------------------------------------- 1 | # CORE-V Tool Chain supplementary notes 2 | 3 | ## Repositories 4 | 5 | - Binutils-gdb - https://github.com/openhwgroup/corev-binutils-gdb 6 | - GCC - https://github.com/openhwgroup/corev-gcc 7 | - CORE-V docs - https://github.com/openhwgroup/core-v-sw 8 | 9 | Create your own fork until ready to create pull request into one of these repositories – all pull request must be reviewed before merging. Ensure you sign-off any pull requests to pass Eclipse foundation checks. 10 | 11 | ## -march options 12 | 13 | All instructions must be enabled for the xcorev -march option as well as their instruction set specific option: 14 | 15 | - hardware loop: `xcorevhwlp` 16 | - multiply-accumulate: `xcorevmac` 17 | - post-increment and register-indexed load/store: `xcorevpostinc` 18 | - direct branches: `xcorevbi` 19 | - general ALU operations: `xcorevalu` 20 | 21 | ## Other information 22 | 23 | - All instructions begin with a `cv` prefix e.g. `cv.starti`/`cv.endi` 24 | - Use GNU coding standards - https://www.gnu.org/prep/standards/ 25 | - Relocation numbers are not yet fixed until a mechanism for vendor specific linker relocations in the psABI is decided 26 | - FSF assignment must be in place before any pull requests can be accepted into the OpenHW repositories -------------------------------------------------------------------------------- /projects/hal/2021/.gitignore: -------------------------------------------------------------------------------- 1 | # Generated PDFs 2 | *.pdf 3 | -------------------------------------------------------------------------------- /projects/hal/2021/monthly-report-2021-04-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (April 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * On the direction of RVM-SIS, we have reached a preliminary agreement with software HC. 8 | * Complete the brief introduction slides of CSI, it's currently in the approval process. 9 | * Channel SW:HAL have be created on the Mattermost, welcome to join and recommend it to your friends.(Thanks for Jeremy's help) 10 | 11 | ### Project status 12 | 13 | * Initial stage. 14 | 15 | ### Next stages 16 | 17 | * Have talks with Software HC of RISC-V international and Software TG of OpenHW, do some CSI brief introduction to see if it meets our requirements. 18 | * Do some open discussions and decide how to move forward. 19 | * Create a Concept Project Proposal and do other initialization work. 20 | * According to the RVM-SIS, implement the Hal software stack on CV32E40P. -------------------------------------------------------------------------------- /projects/hal/2021/monthly-report-2021-05-10.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (May 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * The brief introduction of CSI was completed at the RISC-V Platform HSC meeting, and it was basically recognized as "CSI implementation would be used", and in internal discussions regarding the next steps. 8 | * Vincent made an introduction about CSI in Hardware TG and received a lot of suggestions and feedback. Thank you all. 9 | * In order to explain the definition of CSI and how to implement it, an SDK package that simply implements the CSI standard was prepared and sent to those who are interested in it. 10 | * Complete the more detailed introduction slides of CSI (include comparison with CMSIS). 11 | * Online documents describing CSI standards are being prepared. 12 | 13 | ### Project status 14 | 15 | * Initial stage. 16 | 17 | ### Next stages 18 | 19 | * Further improve the online introduction document on CSI. 20 | * Do some open discussions and decide how to move forward. 21 | * Create a Concept Project Proposal and do other initialization work. -------------------------------------------------------------------------------- /projects/hal/2021/monthly-report-2021-06-14.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (June 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * The requirements of project(draft version) written by Duncan and commented by Jeremy & Yunhai is completed. It will be reviewd on the monthly meeting. 8 | * The intial version of comparison of different popular solutions in the industry has been completed. 9 | * Pushing the progress of RVMSIS in the RISC-V international. 10 | * Project concept proposal(draft version) is ready and it will been discussed in 21 June. 11 | 12 | ### Project status 13 | 14 | * Initial stage. 15 | 16 | ### Next stages 17 | 18 | * Finalized the Project concept proposal then do discusion in the TWG Meeting. 19 | * Do other initialization work. -------------------------------------------------------------------------------- /projects/hal/2021/monthly-report-2021-07-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (July 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Finalize the Project concept propsal, thanks for help from Jeremy and Duncan. 8 | * Project concept proposal was presented in the last TWG Meeting, and project is approved. 9 | * Pushing the progress of RVMSIS in the RISC-V international. 10 | * The document of comparison between the popular solutions is fininshed, it's shared on the TWG:SW:HAL Channel. Welcome to give us more comments and inputs. 11 | 12 | ### Project status 13 | 14 | * Initial stage -> Launch stage. 15 | 16 | ### Next stages 17 | 18 | * Do more discussion and make the decision on which standard we will use, or wait for the progress of RVMSIS. 19 | * Recruit more volunteers for the project. 20 | * Make an executable plan for the project. Do other initialization work. 21 | * Port a minimal CSI-standard system to the Core-V hardware by Vincent. Strive for a demo version at the monthly meeting next month. (I think SDK project maybe need it.) -------------------------------------------------------------------------------- /projects/hal/2021/monthly-report-2021-08-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (Aug 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Port a minimal CSI-Standard system to the Core-V hardware by Vincent & Olive. 8 | * "Hello World" demo is finished and can be running on the Gensys2 board. Olive will show the demo and current progress. 9 | * Find some problems when we compiled the FreeRTOS with Core-V toolchain. Vincent had written the error logs on a document. It is preliminarily estimated that it may be caused by the version problem or configuration of Newlibc in the toolchain. 10 | * Lastest stable bitfile of Core-V MCU is required. Thanks for the document of core-v mcu from Tim. 11 | * Pushing the progress of RVM-CSI in the RISC-V international. 12 | 13 | ### Project status 14 | 15 | * Initial stage -> Launch stage. 16 | 17 | ### Next stages 18 | 19 | * Do more discussion and make the decision on which standard we will use, or wait for the progress of RVM-CSI. 20 | * Recruit more volunteers for the project. 21 | * Make an executable plan for the project. Do other initialization work. -------------------------------------------------------------------------------- /projects/hal/2022/2022-02-10-HAL-Reqiurements-minutes.md: -------------------------------------------------------------------------------- 1 | # OpenHW CORE-V HAL Requirements Discussion Meeting Minutes 2 | 3 | Thursday, Feb. 10th, 2022, 10:00 EST 4 | 5 | ## Attendees 6 | Duncan Bees, Tim Saxe, Jeremy Bennet, Yunhai Shang, Vincent Cui, Robert Balas, Olive Zhao 7 | 8 | 9 | 10 | ## Actions Items 11 | 12 | - **Yunhai and Duncan** to prepare for project lanuch. 13 | 14 | - **Yunhai and Olive** to add short description on CSI coulum in the comparison table to explain how it meets/not meet each requirement. 15 | For Requirements not being met, add what and when to do?. 16 | 17 | - **Yunhai** to discusses with Ali Baba regarding release CSI code and documents in OpenHW github to make it open source. 18 | 19 | 20 | 21 | # Meeting Notes 22 | 23 | - The comparison on existing standards and SDKs from different vendors are done. 24 | - It is proposed to go with CSI; HAL reference implementation will be based in CSI implementation. 25 | - S-3: Update from Yunhai: documents on CSI and comments in CSI code have been translated into English. 26 | - Jeremy suggested Yunhai to share the english version of the CSI documents (standards, user manual etc.) for native english spoken folks to review. 27 | - Update from Yunhai: Interactions between Alibaba and RISC-V International regarding CSI: a task group will be formed in about one month. (in March timeframe). 28 | - Jeremy suggested Duncan to get in touch with RISC-V Inernational S/W Steering committee so that OpenHW's voice can be heard when HAL standards are created. 29 | - S-4: RISC-V International might be the body to maintain the CSI HAL standards according to the interaction between Alibaba and RISC-V International 30 | - T-2: limit the supported on-chip peripherals to basic on-chip prepherals such as UART. 31 | - T-6: Not impemented in CSI. Chip information generated automatically by hardware design tools? or excel file format to provide chip information? Tim would like to search to see what example he can find. 32 | - T-7: Not implemented in CSI. this requirement is similar to the SVD in CMSIS. 33 | 34 | 35 | 36 | 37 | 38 | 39 | -------------------------------------------------------------------------------- /projects/hal/2022/monthly-report-2022-05-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (May 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Compared with many open source standards and implementations, we get the advantages and disadvantages of each implementation. We decided to follow the RVM-CSI standard from the RISC-V international. 8 | * Pushing the progress of RVM-CSI in the RISC-V international. Vincent as the acting chair had given a presentation(about project's plan) to RVI and got approval for most of the contents. RVM-CSI TG will be announced in next days. 9 | 10 | ### Project status 11 | 12 | * Initial stage -> Launch stage. 13 | 14 | ### Next stages 15 | 16 | * Wait for the progress of RVM-CSI and make an executable plan for the project. 17 | * Follow the standard of RVM-CSI and implement it on Core-V hardware. 18 | * Recruit more volunteers for the project. -------------------------------------------------------------------------------- /projects/hal/2022/monthly-report-2022-06-13.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (Jun 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Pushing the progress of RVM-CSI in the RISC-V international. Charter of RVM-CSI is prepared. Wait for a presentation on the TSC and ask for suggestions. 8 | 9 | ### Project status 10 | 11 | * Initial stage -> Launch stage. 12 | 13 | ### Next stages 14 | 15 | * Wait for the progress of RVM-CSI and make an executable plan for the project. 16 | * Follow the standard of RVM-CSI and implement it on Core-V hardware. 17 | * Recruit more volunteers for the project. -------------------------------------------------------------------------------- /projects/hal/2022/monthly-report-2022-07-11.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (July 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * RVM-CSI SIG was subjected to officially announcement and confirmation in TSC/CCM on July 4. 8 | 9 | ### Project status 10 | 11 | * Initial stage -> Launch stage. 12 | 13 | ### Next stages 14 | 15 | * Wait for the plan of RVM-CSI SIG and make an executable plan for the project. 16 | * Follow the standard of RVM-CSI and implement it on Core-V hardware. 17 | * Recruit more volunteers for the project. -------------------------------------------------------------------------------- /projects/hal/2022/monthly-report-2022-12-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (Dec 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * RVM-CSI SIG defined an initial version of YAML relatives(including Yaml Template and Yaml Parser) to describe the target. And header files(*.h) will be generated automatically by the Yaml files. 8 | * RVM-CSI will give a report of project progress on the TSC. For the next step, they will do the gap analysis between the existing solutions.(I think we can share the result of our effort on this side.) 9 | * RVM-CSI is selecting the DEV-boards(platforms) for reference implementation. It would be nice if we could add OpenHW Dev-board to the board list. 10 | 11 | ### Project status 12 | 13 | * Initial stage -> Launch stage. 14 | 15 | ### Next stages 16 | 17 | * Wait for initial version of HAL spec.(Maybe CPU core, Interrupt controller, Timer, Uart will included in first version spec) 18 | * Follow the standard of RVM-CSI and implement it on Core-V hardware. 19 | * Recruit more volunteers for the project. -------------------------------------------------------------------------------- /projects/hal/2023/monthly-report-2023-01-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V HAL update (Jan 2023) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * The group has been already migrated from SIG_RVM_CSI to TECH-RVM-CSI-SPEC-V1 officially, some new topics will be discussed in the new group. 8 | * The draft charter for RVM-CSI TG is still pending dues to holiday last month, but it will be taken consideration as highest priority in short time. 9 | * The develop board for reference implementation. haven't got the confirmation yet. Vincent will stay tuned on the decision in group. 10 | * The above update is from Vincent. 11 | 12 | ### Project status 13 | 14 | * Initial stage -> Launch stage. 15 | 16 | ### Next stages 17 | 18 | * Wait for initial version of HAL spec.(Maybe CPU core, Interrupt controller, Timer, Uart will included in first version spec) 19 | * Follow the standard of RVM-CSI and implement it on Core-V hardware. 20 | * Recruit more volunteers for the project. -------------------------------------------------------------------------------- /projects/hal/README.md: -------------------------------------------------------------------------------- 1 | # Open Hardware Group Software Task Group: Hardware Abstraction Layer (HAL) Project 2 | 3 | A directory for materials associated with reporting progress with the CORE-V 4 | Hardware Abstraction Layer project. 5 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-02-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (February 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Established secured network connection with a host provided by QuickLogic 8 | * Added basic welcome page that needs to be fulfilled further. 9 | * Minor improvements for project templates 10 | 11 | 12 | ### Planned activities for coming month 13 | 14 | * Complete the quest to run debug on a remote hardware provided by QuickLogic 15 | * Investigate how the simplistic application should look like 16 | * More hardware-neutral IDE improvements 17 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-03-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (March 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Defined "CORE-V Development" perspective to be a default for CORE-V IDE. 8 | * Added "CORE-V Projects" explorer to visualize project metadata. 9 | * Minor improvements. 10 | 11 | 12 | ### Planned activities for coming month 13 | 14 | * Complete the quest to run debug on a remote hardware provided by QuickLogic 15 | * Investigate how the simplistic application should look like 16 | * More hardware-neutral IDE improvements 17 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-04-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (April 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Found a way to work with PlatfromIO from Eclipse Workbench. 8 | * Implemented basic Eclipse IDE integration for PlatformIO. 9 | * Minor improvements. 10 | 11 | 12 | ### Planned activities for coming month 13 | 14 | * Provide basic Eclipse CDT integration with PlatformIO 15 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 16 | * Investigate how the simplistic application should look like (need input from experts) 17 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 18 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-06-11.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (June 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Upgraded target to Eclipse SimRel 2021-06. 8 | * Upgraded releng to Eclipse Tycho 2.3.0. 9 | * Minor improvements. 10 | 11 | ### Planned activities for coming month 12 | 13 | * Complete the quest to run simulation Software provided by Imperas 14 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 15 | * Provide basic Eclipse CDT integration with PlatformIO 16 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 17 | * Investigate how the simplistic application should look like (need input from experts) 18 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-07-12.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (July 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Reworked PlatformIO/Eclipse integration to be more suitable to include to CORE-V IDE 8 | * Working to harvest more metadata about boards, toolchains and other IDE "participants" 9 | * Minor improvements. 10 | 11 | ### Planned activities for coming month 12 | 13 | * Complete the quest to run simulation Software provided by Imperas 14 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 15 | * Provide basic Eclipse CDT integration with PlatformIO 16 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 17 | * Investigate how the simplistic application should look like (need input from experts) 18 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-08-09.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (August 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Did a talk with Frédéric Desbiens on RISC-V forum 8 | * Prototyping license check hook during installation of OSS/Commercial plug-ins. 9 | * Minor improvements. 10 | 11 | ### Planned activities for coming month 12 | 13 | * Complete the quest to run simulation Software provided by Imperas 14 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 15 | * Provide basic Eclipse CDT integration with PlatformIO 16 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 17 | * Investigate how the simplistic application should look like (need input from experts) 18 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-09-13.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (September 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Switched to Eclipse Platform 4.21 8 | * Switched to Eclipse CDT 10.3.3 9 | * Prototyping license check hook during installation of OSS/Commercial plug-ins. 10 | * Minor improvements. 11 | 12 | ### Planned activities for coming month 13 | 14 | * Complete the switch to 2021-09 15 | * Integrate Eclipse Passage 2.1+ 16 | * Complete the quest to run simulation Software provided by Imperas 17 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 18 | * Provide basic Eclipse CDT integration with PlatformIO 19 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 20 | * Investigate how the simplistic application should look like (need input from experts) 21 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-11-08.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (November 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Did a talk about CORE-V at EclipseCon 2021 8 | * Added Eclipse Passage 2.1.1 to CORE-V IDE 9 | * Minor improvements. 10 | 11 | ### Planned activities for coming month 12 | 13 | * Prepare CORE-V IDE 0.2.0 14 | * Prepare for SimRel 2021-12 15 | * Complete the quest to run simulation Software provided by Imperas 16 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 17 | * Provide basic Eclipse CDT integration with PlatformIO 18 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 19 | * Investigate how the simplistic application should look like (need input from experts) 20 | -------------------------------------------------------------------------------- /projects/ide/2021/monthly-report-2021-12-13.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (December 2021) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Updated to Eclipse Platform 4.22 8 | * Updated to Eclipse CDT 10.5 9 | * Updated to Eclipse Passage 2.2.1 (fixed log4j vulnerability) 10 | * Added p2 hook to intercept installation\update for license checks 11 | * Minor improvements. 12 | 13 | ### Planned activities for coming month 14 | 15 | * Prepare CORE-V IDE 0.2.0 16 | * Complete the quest to run simulation Software provided by Imperas 17 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 18 | * Provide basic Eclipse CDT integration with PlatformIO 19 | * Find a way to consume the PlatformIO Eclipse IDE by CORE-V IDE 20 | * Investigate how the simplistic application should look like (need input from experts) 21 | -------------------------------------------------------------------------------- /projects/ide/2022/monthly-report-2021-02-14.md: -------------------------------------------------------------------------------- 1 | # Software TG monthly meeting - CORE-V IDE (February 2022) 2 | 3 | ## Overview 4 | 5 | ### Key activities 6 | 7 | * Prepared releng for CORE-V IDE 0.2.0 8 | * Discussed the vision of OpenHW marketplace with Florian 9 | * Discussed the IDE participation to SDK with Hugh 10 | * Minor improvements. 11 | 12 | ### Planned activities for coming month 13 | 14 | * Complete the quest to run simulation Software provided by Imperas 15 | * Complete the quest to run debug on a remote hardware provided by QuickLogic (need help from experts) 16 | * Investigate how the simplistic application should look like (need input from experts) 17 | -------------------------------------------------------------------------------- /projects/ide/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | # Open Hardware Group Software Task Group: IDE Project 5 | 6 | 7 | 8 | A directory for materials associated with reporting progress with the CORE-V 9 | IDE project 10 | 11 | [![Eclipse License](https://img.shields.io/badge/license-EPL--2.0-brightgreen.svg)](https://github.com/openhwgroup/core-v-ide-cdt/blob/master/LICENSE) 12 | [![Build Status](https://github.com/openhwgroup/core-v-ide-cdt/workflows/CI/badge.svg)](https://github.com/openhwgroup/core-v-ide-cdt/actions) -------------------------------------------------------------------------------- /projects/qemu/2022/monthly-report-2022-08-08.md: -------------------------------------------------------------------------------- 1 | # QEMU Monthly Report for 8-August-2022 2 | 3 | ## Key activities 4 | 5 | - Reorganize the commits and fix bugs for Zc* extension[(plct-zce-upstream)](https://github.com/plctlab/plct-qemu/commits/plct-zce-upstream) 6 | 7 | ## Planned activities for coming month 8 | 9 | - Prepare project concept for CORE-V QEMU 10 | - Merge Zc* support into core-v-mcu support[(plct-corev-dev)](https://github.com/plctlab/plct-qemu/commits/plct-corev-dev) 11 | 12 | - Try to optimize the implementation for CORE-V MCU devices 13 | - Call for requirements and usages from other projects -------------------------------------------------------------------------------- /projects/qemu/2022/monthly-report-2022-09-12.md: -------------------------------------------------------------------------------- 1 | # QEMU Monthly Report for 12-September-2022 2 | 3 | ## Key activities 4 | 5 | - Update support for Zc* extension to v1.0.0.RC5-1[(plct-zce-upstream)](https://github.com/plctlab/plct-qemu/commits/plct-zce-upstream) 6 | - Reorganize and optimize support for CORE-V-MCU [(plct-corev-upstream)](https://github.com/plctlab/plct-qemu/tree/plct-corev-upstream), [(plct-corev-upstream_sync_dma)](https://github.com/plctlab/plct-qemu/tree/plct-corev-upstream-sync-dma) 7 | 8 | ## Planned activities for coming month 9 | 10 | - Merge Zc* support into core-v-mcu support if Zc* spec is stable -------------------------------------------------------------------------------- /projects/qemu/2022/monthly-report-2022-10-10.md: -------------------------------------------------------------------------------- 1 | # QEMU Monthly Report for 10-October-2022 2 | 3 | ## Key activities 4 | 5 | - Update support for Zc* extension to v1.0.0.RC5.6[(plct-zce-upstream)](https://github.com/plctlab/plct-qemu/commits/plct-zce-upstream) 6 | - Merge Zc* support into CORE-V-MCU [ [(plct-corev-upstream_sync_dma)](https://github.com/plctlab/plct-qemu/tree/plct-corev-upstream-sync-dma) 7 | 8 | ## Planned activities for coming month 9 | 10 | - Update Xpulp and Zc* support to latest version -------------------------------------------------------------------------------- /projects/qemu/2023/monthly-report-2023-01-09.md: -------------------------------------------------------------------------------- 1 | # QEMU Monthly Report for 9-January-2023 2 | 3 | ## Key activities 4 | 5 | - Support for Zc* extension have been sent to the upstream (and updated to v9)[(plct-zce-upstream-v9)](https://github.com/plctlab/plct-qemu/tree/plct-zce-upstream-v9) 6 | 7 | ## Planned activities for coming month 8 | 9 | - Update support for xcv* extensions -------------------------------------------------------------------------------- /projects/qemu/2023/monthly-report-2023-03-13.md: -------------------------------------------------------------------------------- 1 | # QEMU Monthly Report for 13-March-2023 2 | 3 | ## Key activities 4 | 5 | - Update support for Zc* extension to v1.0.3 (and updated to v12)[(plct-zce-upstream-v12)](https://github.com/plctlab/plct-qemu/tree/plct-zce-upstream-v12) 6 | - Update support for xcv* extensions to new encodings[(plct-corev-bdev)](https://github.com/plctlab/plct-qemu/tree/plct-corev-bdev) 7 | 8 | ## Planned activities for coming month 9 | 10 | - Rebase to upstream and try to update code to [corev-mcu-dev](https://github.com/openhwgroup/corev-qemu/tree/corev-mcu-dev) -------------------------------------------------------------------------------- /projects/sdk/2022/2022-02-14-report.md: -------------------------------------------------------------------------------- 1 | # SDK report 14 February 2022 2 | 3 | Draft document is work in progress which covers: 4 | 5 | - Proposed SDK Components, Main Tasks and Contributors 6 | - Proposed SDK Development Infrastructure 7 | - Additional sections to be completed including: SDK Project Plan, SDK Project Manager and SDK Life Cycle 8 | 9 | ## Next Steps 10 | 11 | Next key step is to finalise second draft of the document, share to the SDK WG and arrange an SDK meeting to finalise components, tasks and contributors. We can then proceed with project plan etc. 12 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-03-14-report.md: -------------------------------------------------------------------------------- 1 | # SDK report 14 March 2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | 7 | - Hugh O’Keeffe from Ashling is now Project Leader for SDK & IDE projects 8 | - Ashling published OpenHW SDK Overview document v002 to SDK channel 9 | - SDK channel member meeting occurred on 9th Mar to agree on main SDK Components, Development Tasks and Contributors. Details/comments as a [Google doc](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4) 10 | - Reviewed IDE progress and work done to date with Alexander of ArSysOp 11 | - Ashling contributed Opella-LD on-board debug I/F hardware design for use in DevKit (to Joseph Julicher HW : DevKit channel). Ashling Opella-LD software drivers will also be included and integrated into IDE/SDK 12 | 13 | ## Planned activities for coming month 14 | 15 | - Hugh O'Keffe is out of office until 21st March 16 | - Duncan Bees to organise committer elections for Promodkumar & Vinod from Ashling 17 | - Duncan Bees to organise bi-weekly SDK meetings on Wed after 30m MCU meeting 18 | - Hugh'Keeffe to continue work on OpenHW SDK Overview document v003 19 | - SDK Project Launch: PL Gate Preparation: 20 | 21 | - Update project plan 22 | - Identify solution for gap analysis/project resource shortfall 23 | - Finalise requirements and spec 24 | 25 | - Organise SDK meeting to review the above and (hopefully) get project approval 26 | - Start next revision IDE implementation 27 | - Start SDK implementation 28 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-05-09-report.md: -------------------------------------------------------------------------------- 1 | # SDK Report for 9-May-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0001 on 5-May-2022. More details in the above. 8 | 9 | ## Planned activities for coming month 10 | - Duncan Bees to organise committer elections for Promodkumar & Vinod from Ashling. 11 | - Ashling to plan Alpha v0002 release. 12 | - Hugh O'Keeffe to continue work on OpenHW SDK Overview document. 13 | - SDK Project Launch: PL Gate Preparation: 14 | 15 | - Update project plan 16 | - Identify solution for gap analysis/project resource shortfall 17 | - Finalise requirements and spec 18 | 19 | - Organise SDK meeting to review the above and get project approval 20 | - SDK Implementation 21 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-06-13-report.md: -------------------------------------------------------------------------------- 1 | # SDK Report for 13-June-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0002 on 11-May-2022. 8 | - Fix the issue (in some Ubuntu systems) with CORE-V-SDK.desktop 9 | - Use OpenOCD from https://sourceforge.net/projects/openocd/files/openocd/ 10 | - Promodkumar from Ashling is now a committer. 11 | - CORE-V-IDE-CDT now deprecated and visitors referred to CORE-V-SDK 12 | 13 | ## Planned activities for coming month 14 | - Visit EW 2022 in Nuremberg. Run demos on OpenHW booth and present "How to Develop a Best-in-class, Open-source, Development Kit for a RISC-V Powered Device" paper. 15 | - Ashling to plan Alpha v0003 release. 16 | - The SDK project is not yet part of the OpenHW Group Eclipse process. Duncan Bees to work with the Ashling team to bring the SDK project into the OpenHW Group Eclipse. 17 | - Hugh O'Keeffe to continue work on OpenHW SDK Overview document. 18 | - SDK Project Launch: PL Gate Preparation: 19 | 20 | - Update project plan 21 | - Identify solution for gap analysis/project resource shortfall 22 | - Finalise requirements and spec 23 | 24 | - Organise SDK meeting to review the above and get project approval 25 | - SDK Implementation 26 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-07-11-report.md: -------------------------------------------------------------------------------- 1 | # SDK Report for 11-July-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) to v004 7 | - Ashling released CORE-V-SDK Alpha v0002 on 11-May-2022. 8 | - Fix the issue (in some Ubuntu systems) with CORE-V-SDK.desktop 9 | - Use OpenOCD from https://sourceforge.net/projects/openocd/files/openocd/ 10 | - Promodkumar from Ashling is now a committer. 11 | - CORE-V-IDE-CDT now deprecated and visitors referred to CORE-V-SDK 12 | - Hugh and Rejeesh attended OpenHW booth at EW2022 and Hugh presented paper on DevKit/SDK 13 | - The SDK project is now a part of the OpenHW Group Eclipse process. 14 | 15 | ## Planned activities for coming month 16 | - Tamas Olaszi in Jade Design Automation is working on creating CSR and Peripheral files for CORE-V which we will use in the SDK Debugger to populate CSR and Peripheral views. He expects to have these by September 17 | - Alpha v0003 release planned for 29th July. See above SDK Overview document 18 | - Hugh and Promod to continue work on OpenHW SDK Overview document 19 | - SDK Project Launch: PL Gate Preparation: 20 | - Update project plan 21 | - Identify solution for gap analysis/project resource shortfall 22 | - Finalise requirements and spec 23 | 24 | - Organise SDK meeting to review the above and get project approval 25 | - SDK Implementation 26 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-08-08-report.md: -------------------------------------------------------------------------------- 1 | # SDK Report for 8-Aug-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0003 5-Aug-2022 (see above document for details) 8 | 9 | 10 | ## Planned activities for coming month 11 | - Tamas Olaszi in Jade Design Automation is working on creating CSR and Peripheral files for CORE-V which we will use in the SDK Debugger to populate CSR and Peripheral views. He expects to have these by September 12 | - Alpha v0004 release to be planned. See above SDK Overview document 13 | - Hugh and Promod to continue work on OpenHW SDK Overview document 14 | - SDK Project Launch: PL Gate Preparation: 15 | - Update project plan 16 | - Identify solution for gap analysis/project resource shortfall 17 | - Finalise requirements and spec 18 | - Organise SDK meeting to review the above and get project approval 19 | - SDK Implementation 20 | 21 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-09-12-report: -------------------------------------------------------------------------------- 1 | # SDK Report for 12-Sep-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0003 5-Aug-2022 (see above document for details) 8 | 9 | 10 | ## Planned activities for coming month 11 | - Tamas Olaszi in Jade Design Automation is working on creating CSR and Peripheral files for CORE-V which we will use in the SDK Debugger to populate CSR and Peripheral views. 12 | - Alpha v0004 release to be planned. See above SDK Overview document 13 | - Hugh and Promod to continue work on OpenHW SDK Overview document 14 | - SDK Project Launch: PL Gate Preparation: 15 | - Update project plan 16 | - Identify solution for gap analysis/project resource shortfall 17 | - Finalise requirements and spec 18 | - Organise SDK meeting to review the above and get project approval 19 | - SDK Implementation 20 | 21 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-10-10-report: -------------------------------------------------------------------------------- 1 | # SDK Report for 10-Oct-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0003 5-Aug-2022 (see above document for details) 8 | 9 | 10 | ## Planned activities for coming month 11 | - Tamas Olaszi in Jade Design Automation is working on creating CSR and Peripheral files for CORE-V which we will use in the SDK Debugger to populate CSR and Peripheral views. 12 | - Alpha v0004 release to be planned. See above SDK Overview document 13 | - Hugh and Promod to continue work on OpenHW SDK Overview document 14 | - SDK Project Launch: PL Gate Preparation: 15 | - Update project plan 16 | - Identify solution for gap analysis/project resource shortfall 17 | - Finalise requirements and spec 18 | - Organise SDK meeting to review the above and get project approval 19 | - SDK Implementation 20 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-11-14-report: -------------------------------------------------------------------------------- 1 | # SDK Report for 14-Nov-2022 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0004 29-Oct-2022 (see above document for details) 8 | 9 | 10 | ## Planned activities for coming month 11 | - Attend December RISV-V Summit in San Jose (Hugh, Rejeesh and Nadim) 12 | - Attend 15-Dec OpenHW meeting in San Jose (Rejeesh and Nadim) 13 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 14 | - Alpha v0005 release to be planned. See above SDK Overview document 15 | - Hugh and Promod to continue work on OpenHW SDK Overview document 16 | - SDK Project Launch: PL Gate Preparation: 17 | - Update project plan 18 | - Identify solution for gap analysis/project resource shortfall 19 | - Finalise requirements and spec 20 | - Organise SDK meeting to review the above and get project approval 21 | - SDK Implementation 22 | -------------------------------------------------------------------------------- /projects/sdk/2022/2022-4-11-report.md: -------------------------------------------------------------------------------- 1 | # SDK report 11-Apr-2022 2 | 3 | ## Project leader: 4 | Hugh O'Keeffe, Ashling 5 | 6 | ## Key activities 7 | Ashling updated OpenHW SDK Overview document to v003 (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) l 8 | 9 | ## Planned activities for coming month: 10 | 1. Duncan Bees to organise committer elections for Promodkumar & Vinod from Ashling. 11 | 2. ~~Duncan Bees to organise bi-weekly SDK meetings on Wed after 30m MCU meeting.~~ 12 | 3. Ashling to prepare Alpha SDK/IDE release by 29 April. Details in the above SDK Overview document. 13 | 4. Hugh'Keeffe to continue work on OpenHW SDK Overview document to include: 14 | 5. SDK Project Launch: PL Gate Preparation: 15 | * Update project plan 16 | * Identify solution for gap analysis/project resource shortfall 17 | * Finalise requirements and spec 18 | * Organise SDK meeting to review the above and (hopefully) get project approval 19 | * Start next revision IDE implementation 20 | * Start SDK implementation 21 | -------------------------------------------------------------------------------- /projects/sdk/2023/05-06-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-06-05 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 13 | - Visit RISC-V Summit Europe in Barcelona 14 | - Alpha v0005 release to be planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 16 | 17 | ### Unplanned 18 | 19 | None. 20 | 21 | # Issues and Difficulties 22 | 23 | - Latest toolchain(12 Jan 2023) has some issue with the pseudo instruction ‘csrr’ while building cli_test project in SDK 24 | 25 | # Gate status & schedule 26 | 27 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 28 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 29 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 30 | | PL | | | | | 31 | | PA | | | | | 32 | | PF | | | | | 33 | 34 | -------------------------------------------------------------------------------- /projects/sdk/2023/08-05-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-05-08 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 13 | - Alpha v0005 release to be planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 14 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | 16 | ### Unplanned 17 | 18 | None. 19 | 20 | # Issues and Difficulties 21 | 22 | - Latest toolchain(12 Jan 2023) has some issue with the pseudo instruction ‘csrr’ while building cli_test project in SDK 23 | 24 | # Gate status & schedule 25 | 26 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 27 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 28 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 29 | | PL | | | | | 30 | | PA | | | | | 31 | | PF | | | | | 32 | 33 | -------------------------------------------------------------------------------- /projects/sdk/2023/09-01-2023-report.md: -------------------------------------------------------------------------------- 1 | # SDK Report for 09-Jan-2023 2 | 3 | Project leader: Hugh O'Keeffe, Ashling 4 | 5 | ## Key activities 6 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 7 | - Ashling released CORE-V-SDK Alpha v0004 29-Oct-2022 (see above document for details) 8 | - Attended December RISV-V Summit in San Jose (Hugh, Rejeesh and Nadim) 9 | - Attended 15-Dec OpenHW meeting in San Jose (Rejeesh and Nadim) 10 | 11 | 12 | ## Planned activities for coming month 13 | 14 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 15 | - Alpha v0005 release to be planned. See above SDK Overview document 16 | - Hugh and Promod to continue work on OpenHW SDK Overview document 17 | - SDK Project Launch: PL Gate Preparation: 18 | - Update project plan 19 | - Identify solution for gap analysis/project resource shortfall 20 | - Finalise requirements and spec 21 | - Organise SDK meeting to review the above and get project approval 22 | - SDK Implementation 23 | -------------------------------------------------------------------------------- /projects/sdk/2023/10-07-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-07-10 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 13 | - Alpha v0005 release to be planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 14 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | 16 | ### Unplanned 17 | 18 | None. 19 | 20 | # Issues and Difficulties 21 | 22 | - Latest toolchain(12 Jan 2023) has some issue with the pseudo instruction ‘csrr’ while building cli_test project in SDK 23 | 24 | # Gate status & schedule 25 | 26 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 27 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 28 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 29 | | PL | | | | | 30 | | PA | | | | | 31 | | PF | | | | | 32 | -------------------------------------------------------------------------------- /projects/sdk/2023/11-09-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-09-11 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Joseph Julicher (Amazon) is working on the FreeRTOS port for DevKit. Once this is completed, we will integrate it into the SDK. 13 | - Mike, Duncan, Tamaz, etc. are working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 14 | - Alpha v0005 release is planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 16 | 17 | ### Unplanned 18 | 19 | None. 20 | 21 | # Issues and Difficulties 22 | 23 | - Latest toolchain(12 Jan 2023) has some issues with the pseudo instruction ‘csrr’ while building the cli_test project in the SDK. Raised issue in the corev-gcc repo, and Embecosm started working on this issue. 24 | 25 | # Gate status & schedule 26 | 27 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 28 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 29 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 30 | | PL | | | | | 31 | | PA | | | | | 32 | | PF | | | | | 33 | -------------------------------------------------------------------------------- /projects/sdk/2023/13-02-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-02-13 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 13 | - Alpha v0005 release to be planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 14 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | - Visit EW 2023 in Nuremberg and run demos on the OpenHW booth at the "Ashling" kiosk 16 | 17 | ### Unplanned 18 | 19 | None. 20 | 21 | # Issues and Difficulties 22 | 23 | - Latest toolchain(12 Jan 2023) has some issue with the pseudo instruction ‘csrr’ while building cli_test project in SDK 24 | 25 | # Gate status & schedule 26 | 27 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 28 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 29 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 30 | | PL | | | | | 31 | | PA | | | | | 32 | | PF | | | | | 33 | 34 | -------------------------------------------------------------------------------- /projects/sdk/2023/13-03-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-03-13 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | 12 | - Mike, Duncan, Tamaz etc working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 13 | - Alpha v0005 release to be planned. See [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 14 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 15 | - Visit EW 2023 in Nuremberg and run demos on the OpenHW booth at the "Ashling" kiosk 16 | 17 | ### Unplanned 18 | 19 | None. 20 | 21 | # Issues and Difficulties 22 | 23 | - Latest toolchain(12 Jan 2023) has some issue with the pseudo instruction ‘csrr’ while building cli_test project in SDK 24 | 25 | # Gate status & schedule 26 | 27 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 28 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 29 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 30 | | PL | | | | | 31 | | PA | | | | | 32 | | PF | | | | | 33 | -------------------------------------------------------------------------------- /projects/sdk/2023/13-11-2023-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-11-13 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 12 | - Ashling released CORE-V-SDK Alpha v0005 03-Nov-2023 (see above document for details) 13 | - Joseph Julicher (Amazon) is working on the FreeRTOS port for DevKit. Once this is completed, we will integrate it into the SDK. 14 | - Mike, Duncan, Tamaz, etc. are working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 15 | - Alpha v0006 release is planned. See [SDK Overview document (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 16 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 17 | 18 | ### Unplanned 19 | 20 | None. 21 | 22 | # Issues and Difficulties 23 | 24 | # Gate status & schedule 25 | 26 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 27 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 28 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 29 | | PL | | | | | 30 | | PA | | | | | 31 | | PF | | | | | 32 | -------------------------------------------------------------------------------- /projects/sdk/2024/08-01-2024-report.md: -------------------------------------------------------------------------------- 1 | # Summary 2 | 3 | - CORE-V-SDK report for 2023-01-08 4 | - Report by: Promodkumar CM 5 | - Project leader: Hugh O'Keeffe, Ashling 6 | 7 | 8 | # Activities and progress since last report 9 | 10 | ### Planned 11 | - Ashling OpenHW SDK Overview document updated (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit) 12 | - Ashling released CORE-V-SDK Alpha v0005 03-Nov-2023 (see above document for details) 13 | - Joseph Julicher (Amazon) is working on the FreeRTOS port for DevKit. Once this is completed, we will integrate it into the SDK. 14 | - Mike, Duncan, Tamaz, etc. are working on finalizing CORE-V CSR which we will use in the SDK Debugger to populate CSR views. 15 | - Alpha v0006 release is planned. See [SDK Overview document (https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 16 | - Hugh and Promod to continue work on OpenHW [SDK Overview document](https://docs.google.com/document/d/1pdm5ZwH6GKYAabQpQ8HwzvLy4g0O1JPzRHZVA8GHVc4/edit). 17 | 18 | ### Unplanned 19 | 20 | None. 21 | 22 | # Issues and Difficulties 23 | 24 | # Gate status & schedule 25 | 26 | | Gate | Original plan | Current plan | Achieved | Link to last gate document | 27 | | ---- | ------------- | ---------- | ---------- | ---------------------- | 28 | | PC | 2022-08-21 | 2022-08-21 | 2022-08-21 | [SDK PC](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/SDK/sdk-project-concept.md) | 29 | | PL | | | | | 30 | | PA | | | | | 31 | | PF | | | | | 32 | -------------------------------------------------------------------------------- /projects/verilator/2023/2023-09-11-verilator-modeling-report.md: -------------------------------------------------------------------------------- 1 | # Verilator modeling for Software: Monthly report 11 Sep 2023 2 | 3 | Project lead: Jeremy Bennett 4 | 5 | ## Activities and progress since last report 6 | 7 | Completed: 8 | - Generic PL gate passed; 9 | - PA gate for CV32E40Pv2 passed. 10 | - full debug model based on X-Heep for CV32E40Pv2 working. Suitable for SW development and tool chain testing; and 11 | - newlib extension to support X-Heep run-time added. 12 | 13 | To do: 14 | - provide a suitable linker script for general use; 15 | - run GCC regression; 16 | - run Embench; and 17 | - accellerate the model using DPI memory access for program loading. 18 | 19 | ## Issues and Difficulties 20 | - X-Heep model uses top level inout pins (not good for Verilator) and currently assumes JTAG is driven through DPI: 21 | - patches in preparation to fix this. 22 | 23 | ## Timeline and statistics 24 | 25 | ### Kanban chart 26 | 27 | **Note.** Task list currently under review. 28 | 29 | | Milestone | Open | In progress | Complete | 30 | | :------------------------------------ | ---: | ----------: | -------: | 31 | | CV32E40Pv2 Verilator model available | - | - | 1 | 32 | | JTAG TAP driver complete | - | - | 7 | 33 | | Initial version of Embdebug available | 1 | - | 1 | 34 | | Initial standalone model available | 2 | - | - | 35 | | Final version of Embdebug available | 2 | 1 | - | 36 | | Final standalone model available | 1 | - | - | 37 | 38 | ### GCC regression test statistics 39 | 40 | To be provided in future 41 | 42 | ## Gate status & schedule 43 | 44 | ### Verilator modeling for software generic plan 45 | 46 | | Gate | Original plan | Current plan | Achieved | Notes | 47 | | :--- | :------------ | :------------ | :------------ | :---- | 48 | | PC | | 2021-03-22 | | | 49 | | PL | | 2023-06-05 | | 1. | 50 | | PA | N/A | | | | 51 | | PF | N/A | | | | 52 | 53 | Notes: 54 | 1. Change of scope to cover purely software applications. 55 | 56 | Document links: 57 | - [Project concept](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-ppl.md) 58 | - [Project launch](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-pl.md) 59 | - Plan approved - N/A for generic software projects 60 | - Project freeze - N/A for software projects. 61 | 62 | ### Verilator modeling for software for CV32E40Pv2 63 | 64 | | Gate | Original plan | Current plan | Achieved | Notes | 65 | | :--- | :------------ | :------------ | :------------ | :---- | 66 | | PC | N/A | | | | 67 | | PL | N/A | | | | 68 | | PA | | 2023-06-05 | | | 69 | | PF | N/A | | | | 70 | 71 | - Project concept - see generic plan 72 | - Project launch - see generic plan 73 | - [Plan approved](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-pa.md) 74 | - Project freeze - N/A for software projects. 75 | -------------------------------------------------------------------------------- /projects/verilator/2023/2023-11-13-verilator-modeling-report.md: -------------------------------------------------------------------------------- 1 | # Verilator modeling for Software: Monthly report 13 Nov 2023 2 | 3 | Project lead: Jeremy Bennett 4 | 5 | ## Activities and progress since last report 6 | 7 | Completed: 8 | - JTAG pins to X-Heep Verilator model now working. 9 | 10 | To do: 11 | - get X-Heep Verilator model to run programs through GDB; 12 | - provide a suitable linker script for general use; 13 | - run GCC regression; 14 | - run Embench; and 15 | - accellerate the model using DPI memory access for program loading. 16 | 17 | ## Issues and Difficulties 18 | 19 | - The X-Heep Verilator model is not halting in response to JTAG commands. 20 | - comparing with OpenOCD to try to determine cause of differences. 21 | 22 | ## Timeline and statistics 23 | 24 | ### Kanban chart 25 | 26 | **Note.** Task list currently under review. 27 | 28 | | Milestone | Open | In progress | Complete | 29 | | :------------------------------------ | ---: | ----------: | -------: | 30 | | CV32E40Pv2 Verilator model available | - | - | 1 | 31 | | JTAG TAP driver complete | - | - | 7 | 32 | | Initial version of Embdebug available | 1 | - | 1 | 33 | | Initial standalone model available | 2 | - | - | 34 | | Final version of Embdebug available | 2 | 1 | - | 35 | | Final standalone model available | 1 | - | - | 36 | 37 | ### GCC regression test statistics 38 | 39 | To be provided in future 40 | 41 | ## Gate status & schedule 42 | 43 | ### Verilator modeling for software generic plan 44 | 45 | | Gate | Original plan | Current plan | Achieved | Notes | 46 | | :--- | :------------ | :------------ | :------------ | :---- | 47 | | PC | | 2021-03-22 | | | 48 | | PL | | 2023-06-05 | | 1. | 49 | | PA | N/A | | | | 50 | | PF | N/A | | | | 51 | 52 | Notes: 53 | 1. Change of scope to cover purely software applications. 54 | 55 | Document links: 56 | - [Project concept](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-ppl.md) 57 | - [Project launch](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-pl.md) 58 | - Plan approved - N/A for generic software projects 59 | - Project freeze - N/A for software projects. 60 | 61 | ### Verilator modeling for software for CV32E40Pv2 62 | 63 | | Gate | Original plan | Current plan | Achieved | Notes | 64 | | :--- | :------------ | :------------ | :------------ | :---- | 65 | | PC | N/A | | | | 66 | | PL | N/A | | | | 67 | | PA | | 2023-06-05 | | | 68 | | PF | N/A | | | | 69 | 70 | - Project concept - see generic plan 71 | - Project launch - see generic plan 72 | - [Plan approved](https://github.com/openhwgroup/programs/blob/master/Project-Descriptions-and-Plans/MCU-Verilator-Model/verilator-modeling-pa.md) 73 | - Project freeze - N/A for software projects. 74 | -------------------------------------------------------------------------------- /specifications/README.md: -------------------------------------------------------------------------------- 1 | # CORE-V Software Specifications 2 | 3 | This directory provides a location for CORE-V specific specifications that straddle multiple projects. 4 | -------------------------------------------------------------------------------- /specifications/corev-isa-extension-naming.md: -------------------------------------------------------------------------------- 1 | # CORE-V ISA Extension Naming 2 | 3 | ## History 4 | 5 | | Date | Version | Notes | 6 | | :---------- | :------ | :---------------------------------------------------- | 7 | | 28 Nov 2022 | 1.0 | First version as approved by TWG of 28 Nov 2022. | 8 | 9 | ## Executive summary 10 | 11 | - CORE-V ISA extension names will use the prefix `xcv`. 12 | - There are no shorthand names defined for groups of ISA extensions. 13 | - Versioning of ISA extensions will not be supported for CORE-V. 14 | 15 | ## Context 16 | 17 | Various CV32E4x cores have defined ISA extensions. The compiler tool chains need to know which ISA extensions are enabled. This is the `-march` option to GNU and LLVM tools. The format is defined by RISC-V International, and non-standard ISA extensions must begin with ‘X’ 18 | 19 | We currently have 8 ISA extensions defined. Three different implementations currently define different encodings for thes extensions. 20 | 21 | - CV32E40P version 1 (the original PULP encoding, which is not RISC-V compliant) 22 | - CV32E40P version 2 (a RISC-V compliant encoding) 23 | - CV32E41P (a different RISC-V compliant encoding) 24 | 25 | Of these only CV32E40P version 2 actually plans to implement the ISA extensions. 26 | 27 | The RISC-V standards at present embody the concept of different versions of an ISA extension, potentially providing a way to support multiple encodings. 28 | 29 | This document provides the agreed OpenHW Group position on the following questions. 30 | 31 | - How should CORE-V ISA extensions be named? 32 | - Should there be shorthands to specify groups of extensions, and if so, what should these be? 33 | - What versioning of the extensions, if any, short be supported? 34 | 35 | ## CORE-V ISA extension naming 36 | 37 | For conciseness, all CORE-V ISA extensions should use the prefix `xcv`. At the time of writing, the following are defined: 38 | 39 | - `xcvhwlp` (hardware loops) 40 | - `xcvmac` (multiply-accumulate) 41 | - `xcvbi` (immediate branch) 42 | - `xcvmem` (post-indexed and register-indexed memory access) 43 | - `xcvalu` (miscellaneous ALU operations) 44 | - `xcvsimd` (PULP 8/16-bit SIMD) 45 | - `xcvbitmanip` (PULP bit manipulation) 46 | - `xcvelw` (event load word) 47 | 48 | ## CORE-V shorthand for multiple extensions 49 | 50 | There is no concensus as to what combinations of ISA extensions would be useful, nor of how such shorthands should be named. Therefore at this time, no shorthands are defined. 51 | 52 | ## Versioning 53 | 54 | At present: 55 | 56 | - versioning of ISA extensions is missing/incomplete in the GNU and LLVM tool chains; 57 | - RISC-V international plans to remove versioning of ISA extensions from the new standard; and 58 | - only one CORE-V implementation (CV32E40P version 2) currently implements any extensions. 59 | 60 | CORE-V will therefore not support versioning of ISA extensions, and for the 8 extensions described above will use the encoding in the CV32E40P version 2. Should a future processor need an extension with different encodings, that extension will just be given a different name. 61 | --------------------------------------------------------------------------------