Getting Started with FPGA-based Hardware Design (Philip Salmony, EOC 2023)

For instance, we need to worry about the finesses of controlled impedance traces, delay tuning, stack-up choice, DDR memory layout, power distribution and decoupling network design, power delivery for multiple voltage rails with high currents - and that's just naming a few examples!

This talk will show you - in a very condensed form - the basics and what you need to pay attention to when attempting your first FPGA-based hardware and PCB design, including real-world, practical examples.

According to Philip Salmony's talk, what is the main reason to choose an FPGA or SoC instead of a microcontroller for a hardware project?

What power-delivery approach does the speaker recommend for FPGAs and why?

Why does Philip emphasize placing a ground plane adjacent to every signal and power plane in the PCB stack-up?

Which routing practice for DDR memory does the speaker identify as important for a successful FPGA/SoC design?

You answered 0 out of 4 questions correctly.

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block (multi-line) wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Up-to-date Upvotes Newest Oldest MadMan Score: 0 | 3 years ago | no reply This post has been deleted by the author Submit Reply M↓ MARKDOWN HELP italics surround text with *asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > MadMan Score: 0 | 3 years ago | no reply Awesome info

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > dcomer Score: 1 | 4 years ago | 1 reply Philip, have you experimented with the Xilinx RFSoC? I've been waiting for the price of development boards to go down (certainly less than $10k) and watching to see if anyone creates an open-source design. I've programmed with the Zynq 7000 but would LOVE to delve into direct conversion radio with the RFSOC. Great presentation... Dave

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Phil Salmony Speaker Score: 0 | 4 years ago | no reply Hey Dave, Thanks for your comment. I'm afraid I haven't used the RFSoC yet.. The only more advanced AMD/Xilinx chip I'm currently creating a design for is the Zynq UltraScale+ MPSoC. Best, Phil

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Matthew.Zaleski Score: 1 | 4 years ago | 1 reply This was a nice overview for those of us that have not delved into the topic. Lots of good keywords in the presentation for going down the Google rabbit hole!

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Phil Salmony Speaker Score: 0 | 4 years ago | no reply Thank you, Matthew! Yes, I hope it serves as a starting point for further research into various topics :)

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Thomas.Schaertel Score: 0 | 4 years ago | 1 reply Phil, this was a very engaging and fast paced talk! I've enjoyed it very much. How do you prototype the ZettBrett? Is it all done within the Xilinx ecosystem? There is actually no way to build something (on a breadboard) with all those BGA type ICs. I struggle a lot with all the tools I need to get the job done, years later, I can't even remember what I thought at that time nor stay the tools the same. To even make smaller changes is an endeavour! Thank you for your great talk!

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Phil Salmony Speaker Score: 0 | 4 years ago | no reply Thank you, Thomas!Unless you're utilising sensor with fairly 'simple' interfaces (SPI, I2C, ..) and have a devboard with your FPGA/SoC of choice, then prototyping physically will be quite hard.As suggested in the talk, I'd usually start with reference designs and system-on-modules.Build a carrier board with my required peripherals and then hone in to a final product, which puts everything onto a single board (for example).The ZettBrett however was done without any 'pre-prototype' or SoM.

The only tools I used were datasheets, app notes, reference designs, and the Xilinx tools.

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > amrith Score: 0 | 4 years ago | 1 reply Really informative and concise overview of the whole design process. Thank you for all these videos and educational content.

Thank You Amrith Harijayanthan Namboodiri

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > Phil Salmony Speaker Score: 0 | 4 years ago | no reply Thank you, Amrith!

*asterisks* bold surround text with **two asterisks** hyperlink [hyperlink](https://example.com) or just a bare URL inline code surround text with single `backticks` code block wrap on its own lines with three backticks: ``` your code here ``` strikethrough surround text with ~~two tilde characters~~ quote prefix with > You Might Also Like Talk Hacking FPGAs & SoC FPGAs security threats to consider once your FPGA hardware is designed

Hardware Security Analysis on Soft-Core RISC-V Processors

running soft cores on FPGAs and analyzing their security

Beat the Supply Chain by Making your Own Chips!

alternative approach when off-the-shelf silicon is unavailable

Get Your Conference Pass

Every EOC 2026 session and workshop, on demand. Add the archives for every session since 2020. Passes bought now also include the upcoming EOC 2027, with access to both editions until December 31, 2027.

Partners & Sponsors