We usually work on very complex FPGA-based projects built around Vaaman and its upcoming series. However, Shrike-lite is a passion project at Vicharak, driven by our love for engineering across both embedded microcontrollers and FPGAs.
Our goal is to make FPGAs accessible to everyone by offering robust toolchains, high-quality hardware, and strong ecosystem support. We’re committed to keeping the hardware prices extremely low, and every piece of software for Shrike will be completely open-source.
We invite contributors from all over the world to join us in this mission. Together, let’s make FPGA technology truly accessible to all.
Shrike-lite is lighter version of world's first fully open source FPGA Dev board crowdsupply releasing on CrowdSupply Renesas Forge FPGA SLG47910 and RP2350.
We at vicharak have kept in mind need of a learner, maker and a hobbyist while designing this art. This dev board will be your stepping stone in the field of FPGA, reconfigurable and heterogenous computing.
- FPGA with 1120 5 Input LUT's
- RP2040 - ARM Cortex M0
- PMOD Compatible Connector
- Bread Board compatible
- IO interface Between FPGA and MCU
- QSPI Flash
- 2x User LED's
- Type C Port for Power and Programming
-
FPGA Datasheet - Renesas Forge FPGA
-
EDA Tool - Go Configure Software Hub
-
RP2040 Related Resources- Getting Started
We are building a ecosystem for learners , makers and hobbyist around shrike and the projects that will follow in future, thus we request you contribution in the same. Join our communities across all the platforms, pitch and showcase your ideas with Shrike.
Thank You
| FPGA PIN | RP 2040 PIN | RP2040 | FPGA |
|---|---|---|---|
| EN | 13 | GPIO | EN (Enable) |
| PWR | 12 | GPIO | PWR |
| 3 | 2 | GPIO | SPI_SCLK |
| 4 | 1 | UART RX / GPIO | SPI_SS |
| 5 | 3 | GPIO | SPI_SI (MOSI) |
| 6 | 0 | UART TX / GPIO | SPI_SO (MISO) / CONFIG |
| 18 | 14 | GPIO / I2C 1 SDA | GPIO |
| 17 | 15 | GPIO / I2C 1 SDA | GPIO |
Your contribution to the Shrike project are always welcome. To contribute fork the project test your changes and create a PR. Few things in to keep in mind for better contribution.
- Try to document as much as possible.
- Keep your design clean and readable.
- Do not push unnecessary directories and .env.
- Make sure your changes can be recreated.
We really appreciate everyone’s enthusiasm in improving the project!
However, please avoid opening PRs for very small changes such as:
- Minor rewording of documentation (that doesn’t improve clarity)
- Typo fixes in comments or README
- Indentation or formatting-only edits
These types of changes create noise in the PR queue and make it harder to review substantial contributions.
If you spot something small, feel free to open an issue instead so we can batch those improvements together.