OmpSs@FPGA

This module introduces the audience to the BSC tools for heterogenous programming on FPGA devices. It describes the FPGA architecture and OmpSs@FPGA, as a productive programming environment for compute systems with FPGAs.

More specifically, the module provides insights into:

  • the high-level blocks that build up FPGAs, and how they can be used for computation.

  • the OmpSs@FPGA programming model, how to write, compile and execute applications on FPGAs

  • how to analyze applications to determine which portions can be executed on FPGAs, and use OmpSs@FPGA to parallelize/optimize them.

Prerequisites

  • Good knowledge of C/C++

  • Basic knowledge of acceleration architectures and offloading models

  • Basic knowledge of Paraver/Extrae

Episodes

Learning outcomes

The material in this EVITA module is for all researchers and engineers who work with FPGAs to accelerate applications using BSC’s OmpSs@FPGA programming model.

By the end of this module, learners should be able to:

  • describe the architecture of FPGA devices and how their components can be used

  • describe the characteristics of the OmpSs@FPGA programming model

  • annotate applications with OmpSs@FPGA directives to accelerate applications on FPGAs

  • describe how to annotate the matrix multiplication algorithm for tasks exploitation on FPGAs

Suggested dedication

This module is thought to be taught on around 3 hours. Episode “Introduction to FPGA Hardware” can take around 1 hour and episode “Introduction to OmpSs@FPGA” around 2 hours of teaching / online learning.

License

CC BY-SA for media and pedagogical material

Copyright © 2025 XXX. This material is released by XXX under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0).

Canonical URL: https://creativecommons.org/licenses/by-sa/4.0/

See the legal code

You are free to

  1. Share — copy and redistribute the material in any medium or format for any purpose, even commercially.

  2. Adapt — remix, transform, and build upon the material for any purpose, even commercially.

  3. The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms

  1. Attribution — You must give appropriate credit , provide a link to the license, and indicate if changes were made . You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.

  2. ShareAlike — If you remix, transform, or build upon the material, you mus t distribute your contributions under the same license as the original.

  3. No additional restrictions — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.

Notices

You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation .

No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

MIT for source code and code snippets

MIT License

Copyright (c) 2025, EVITA project, Daniel Jimenez-Gonzalez, Antonio Filgueras, Miquel Vidal, Carlos Alvarez, and Xavier Martorell

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Note

To module authors: For code you may use any OSI-approved license as mentioned in https://spdx.org/licenses/, such as Apache License 2.0, GNU GPLv3, MIT. Please make sure to update the deed above and LICENSE.code file accordingly.