home.social

#vivado — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vivado, aggregated by home.social.

  1. `Generate Bitstream` ⌛

    :coffee_mug: 🚶 :coffee_mug: ⌛ …

    #FPGA #Vivado

  2. As of today, I am claiming credit as the first Shure associate in the 101 year history of Shure Incorporated to officially contribute to an open source project by completing our new Open Source Contribution process!

    Thank you Gwenhael Goavec-Merou for maintaining the excellent openFPGALoader project!

    github.com/trabucayre/openFPGA

    #Shure #openFPGALoader #FPGA #Xilinx #Vivado #AMD #JTAG #FOSS

  3. As of today, I am claiming credit as the first Shure associate in the 101 year history of Shure Incorporated to officially contribute to an open source project by completing our new Open Source Contribution process!

    Thank you Gwenhael Goavec-Merou for maintaining the excellent openFPGALoader project!

    github.com/trabucayre/openFPGA

    #Shure #openFPGALoader #FPGA #Xilinx #Vivado #AMD #JTAG #FOSS

  4. As of today, I am claiming credit as the first Shure associate in the 101 year history of Shure Incorporated to officially contribute to an open source project by completing our new Open Source Contribution process!

    Thank you Gwenhael Goavec-Merou for maintaining the excellent openFPGALoader project!

    github.com/trabucayre/openFPGA

    #Shure #openFPGALoader #FPGA #Xilinx #Vivado #AMD #JTAG #FOSS

  5. As of today, I am claiming credit as the first Shure associate in the 101 year history of Shure Incorporated to officially contribute to an open source project by completing our new Open Source Contribution process!

    Thank you Gwenhael Goavec-Merou for maintaining the excellent openFPGALoader project!

    github.com/trabucayre/openFPGA

    #Shure #openFPGALoader #FPGA #Xilinx #Vivado #AMD #JTAG #FOSS

  6. As of today, I am claiming credit as the first Shure associate in the 101 year history of Shure Incorporated to officially contribute to an open source project by completing our new Open Source Contribution process!

    Thank you Gwenhael Goavec-Merou for maintaining the excellent openFPGALoader project!

    github.com/trabucayre/openFPGA

    #Shure #openFPGALoader #FPGA #Xilinx #Vivado #AMD #JTAG #FOSS

  7. Posted to: #openFPGALoader #irc channel:

    Hello. I'm new here. I was in need of support for indirect flashing of a flash part that is not supported by #vivado. I am working on adding support for the #Winbond W25Q256PW and #Xilinx XCAU7P-1SBVC484E, and have a working prototype. I will push it to my fork. Would this be a contribution others are interested in?

    I also produced a PR:
    github.com/trabucayre/openFPGA

    #FOSS tools are great. I couldn't have added this support to #vivado without a binary patch.

  8. Posted to: #openFPGALoader #irc channel:

    Hello. I'm new here. I was in need of support for indirect flashing of a flash part that is not supported by #vivado. I am working on adding support for the #Winbond W25Q256PW and #Xilinx XCAU7P-1SBVC484E, and have a working prototype. I will push it to my fork. Would this be a contribution others are interested in?

    I also produced a PR:
    github.com/trabucayre/openFPGA

    #FOSS tools are great. I couldn't have added this support to #vivado without a binary patch.

  9. Posted to: #openFPGALoader #irc channel:

    Hello. I'm new here. I was in need of support for indirect flashing of a flash part that is not supported by #vivado. I am working on adding support for the #Winbond W25Q256PW and #Xilinx XCAU7P-1SBVC484E, and have a working prototype. I will push it to my fork. Would this be a contribution others are interested in?

    I also produced a PR:
    github.com/trabucayre/openFPGA

    #FOSS tools are great. I couldn't have added this support to #vivado without a binary patch.

  10. Posted to: #openFPGALoader #irc channel:

    Hello. I'm new here. I was in need of support for indirect flashing of a flash part that is not supported by #vivado. I am working on adding support for the #Winbond W25Q256PW and #Xilinx XCAU7P-1SBVC484E, and have a working prototype. I will push it to my fork. Would this be a contribution others are interested in?

    I also produced a PR:
    github.com/trabucayre/openFPGA

    #FOSS tools are great. I couldn't have added this support to #vivado without a binary patch.

  11. Posted to: #openFPGALoader #irc channel:

    Hello. I'm new here. I was in need of support for indirect flashing of a flash part that is not supported by #vivado. I am working on adding support for the #Winbond W25Q256PW and #Xilinx XCAU7P-1SBVC484E, and have a working prototype. I will push it to my fork. Would this be a contribution others are interested in?

    I also produced a PR:
    github.com/trabucayre/openFPGA

    #FOSS tools are great. I couldn't have added this support to #vivado without a binary patch.

  12. Создаем I2C Master Controller на Verilog. Перенос на Zynq 7000 (bare-metal)

    После успешной отладки на плате с Cyclone IV пришла пора перенести наработки на плату Zynq Mini c XC7Z020. В этой статье я опишу, каким образом можно организовать вывод нужной нам информации из PS-части Zynq на дисплей который подключен к EMIO на выводах PL. Сделаем обновленный модуль i2c_master_axi который добавляет сверху к уже разработанному ядру поддержку AXI4-Lite Slave, сделаем сборку проекта, подключим их к PS и проверим в bare-metal сценарии. После того как это будет все работать - переходить к Linux уже будет гораздо проще. Всем заинтересованным добро пожаловать под кат!

    habr.com/ru/companies/beget/ar

    #zynq7000 #zynqmini #oled #ssd1306 #verilog #baremetal #tutorial #vivado #vitis

  13. Создаем I2C Master Controller на Verilog. Перенос на Zynq 7000 (bare-metal)

    После успешной отладки на плате с Cyclone IV пришла пора перенести наработки на плату Zynq Mini c XC7Z020. В этой статье я опишу, каким образом можно организовать вывод нужной нам информации из PS-части Zynq на дисплей который подключен к EMIO на выводах PL. Сделаем обновленный модуль i2c_master_axi который добавляет сверху к уже разработанному ядру поддержку AXI4-Lite Slave, сделаем сборку проекта, подключим их к PS и проверим в bare-metal сценарии. После того как это будет все работать - переходить к Linux уже будет гораздо проще. Всем заинтересованным добро пожаловать под кат!

    habr.com/ru/companies/beget/ar

    #zynq7000 #zynqmini #oled #ssd1306 #verilog #baremetal #tutorial #vivado #vitis

  14. “We appreciate the community’s candid feedback” 😆

    Good news! AMD listened. Linux will be supported by the basic ($0) version of #Vivado: adaptivesupport.amd.com/s/ques

  15. “We appreciate the community’s candid feedback” 😆

    Good news! AMD listened. Linux will be supported by the basic ($0) version of #Vivado: adaptivesupport.amd.com/s/ques

  16. Good news everyone... well, every FPGA nerd: #AMD though it over and added #Linux support back in the basic (aka free of charge) license tier of #Vivado.

    It's really good to see when companies roll back stupid ideas. #Kudos!

  17. AMD's latest Vivado 2026.1 release has sparked outrage among Linux users, who now face an annual cost of $1,200-$1,800 for a tool that was previously free. This abrupt licensing change, which AMD calls 'more flexible,' is seen by the community as a bait-and-switch, eroding years of trust and impacting students, hobbyists, and professional developers alike. The move forces a choice: pay the 'AMD tax' or…

    tpp.blog/2naxuyp

    #opensource #amd #vivado

    🤖 This post was AI-generated.

  18. AMD's latest Vivado 2026.1 release has sparked outrage among Linux users, who now face an annual cost of $1,200-$1,800 for a tool that was previously free. This abrupt licensing change, which AMD calls 'more flexible,' is seen by the community as a bait-and-switch, eroding years of trust and impacting students, hobbyists, and professional developers alike. The move forces a choice: pay the 'AMD tax' or…

    tpp.blog/2naxuyp

    #opensource #amd #vivado

    🤖 This post was AI-generated.

  19. Oh, look! #AMD decided to #troll #Linux users with #Vivado licensing changes, proving once again that open-source enthusiasts are merely pawns in their corporate chess game. 🎯🤦‍♂️ Meanwhile, AMD's PR department must be working overtime crafting excuses that no one will read. 📉
    itsfoss.com/news/amd-vivado-ba #OpenSource #CorporateChess #HackerNews #ngated

  20. Oh, look! #AMD decided to #troll #Linux users with #Vivado licensing changes, proving once again that open-source enthusiasts are merely pawns in their corporate chess game. 🎯🤦‍♂️ Meanwhile, AMD's PR department must be working overtime crafting excuses that no one will read. 📉
    itsfoss.com/news/amd-vivado-ba #OpenSource #CorporateChess #HackerNews #ngated

  21. ⚙️ AMD cambia Vivado: le licenze gratuite restano senza supporto Linux. Una scelta che pesa su maker, studenti e team FPGA. #AMD #Vivado

    🔗 tomshw.it/hardware/amd-vivado-

  22. While not as ubiquitous as the two big ones, there *are* #FPGA vendors that embrace #FOSS toolchains. So, given #AMD's license blunder with #vivado free version not available for #Linux anymore, I'll push for companies like #CologneChip wherever I can (which is also #digitalsoveignty for those who care): colognechip.com/

  23. While not as ubiquitous as the two big ones, there *are* #FPGA vendors that embrace #FOSS toolchains. So, given #AMD's license blunder with #vivado free version not available for #Linux anymore, I'll push for companies like #CologneChip wherever I can (which is also #digitalsoveignty for those who care): colognechip.com/

  24. All recent dev teams I've worked with in hardware and software have been Linux/Mac. AMD should be releasing a free version of #Vivado for Linux and macOS.

    Imagine if AMD charged $1000+ to compile software on Linux.

    The only people hurt are hobbyists and the future of #FPGA outside big enterprises.

  25. All recent dev teams I've worked with in hardware and software have been Linux/Mac. AMD should be releasing a free version of #Vivado for Linux and macOS.

    Imagine if AMD charged $1000+ to compile software on Linux.

    The only people hurt are hobbyists and the future of #FPGA outside big enterprises.

  26. AMD (Xilinx) are no longer supporting Linux in the free version of #Vivado. You need to pay at least $1200/year! amd.com/en/products/software/a

    This makes no sense to me. This will make it harder for people to learn and get into #FPGA. 🤔

  27. AMD (Xilinx) are no longer supporting Linux in the free version of #Vivado. You need to pay at least $1200/year! amd.com/en/products/software/a

    This makes no sense to me. This will make it harder for people to learn and get into #FPGA. 🤔

  28. Запуск Vivado 2019.1 на Orange Pi 3 LTS через QEMU

    Если вам интересно как выглядит работа Vivado на одноядерном ARM процессоре с частотой 1.8 ГГц, и 2 Гб ОЗУ, то я вам это покажу, и расскажу, как я запустил и успешно прошил плату (ДА! Собрал проект и прошил).

    habr.com/ru/articles/1033766/

    #Vivado #Xilinx #FPGA #OrangePi #Orange_Pi_3 #QEMU

  29. #Vivado so: „Nene, vor Deinem Befehl musst Du erst noch `reset_run` ausführen.“

    Ich so: `reset_run`

    Vivado so: „Nene, `reset_run` gibt es gar nicht.“

    🙄

  30. @sci_photos Also erstmal ½ Stunde was anderes arbeiten, während #Vivado rumrödelt …

  31. @sci_photos Also erstmal ½ Stunde was anderes arbeiten, während #Vivado rumrödelt …

  32. * klickt "Generate Bitstream" …

    … dann jetzt also ½ Stunde was anderes arbeiten, während #Vivado rumrödelt …

  33. Huh, I haven't had Vivado reduce LUT usage after synthesis like this before—at least not drastically like this.

    This must be the opt_design stage after synthesis? Or does the placement stage really optimize LUT packing like that?

    It's my first timing using “Flow_AreaOptimized_high" and “ExploreArea”.

  34. Huh, I haven't had Vivado reduce LUT usage after synthesis like this before—at least not drastically like this.

    This must be the opt_design stage after synthesis? Or does the placement stage really optimize LUT packing like that?

    It's my first timing using “Flow_AreaOptimized_high" and “ExploreArea”. #FPGA #vivado

  35. Xilinx AXI DMA v7.1 (Simple Mode)

    Я заметил, что в сообществе FPGA многие задают вопросы, которые можно решить с помощью DMA. Сделал поиск по Хабру в поисках чистых статей о том, как запустить DMA и не нашел таких. Поэтому решил в этой статье собрать свои знания в кучу и показать, как пользуюсь DMA . Это будут чистые примеры, без лишней информации, также будут сравнительные тесты разного характера.

    habr.com/ru/articles/974008/

    #FPGA #MicroBlaze #Vivado #DMA

  36. Новое поколение ПЛИС это не только про повышение частоты…

    Прослеживается тенденция, что сложность CLB повышается, сами примитивы становятся хитрее. От сюда вытекает вопрос, а на сколько эффективными становятся ячейки, и сколько ресурсов ПЛИС они экономят в сравнении с предыдущими поколениями?

    habr.com/ru/articles/971560/

    #ise #vivado #xilinx #fpga #ПЛИС

  37. Процессорный модуль Corgi SoM v1 на базе Xilinx Zynq-7000

    Коллеги, приветствую, обзорная статья работы с Corgi SoM v1 на базе AMD (Xilinx) Zynq-7000. Статья охватывает работу модуля с Vivado IDE, Vitis IDE, подготовку базового образа, работу с Embedded Linux (u-boot, device tree, linux kernel, rootfs). Подготовку образа для SPI NOR памяти, SPI NAND памяти и сопутствующие моменты необходимые для старта работы с данным модулем. Дополнительно статья будет полезно для linux embedded разработчиков, которые делать будут bring-up плат на базе AMD(Xilinx) zynq платформ.

    habr.com/ru/articles/948280/

    #xilinx_zynq #embedded_linux #vivado #uboot #device_tree #fpga #linux_kernel

  38. Potentially daft question on #FPGA and #VIVADO
    I'm trying to see the address that I'm writing to on the LEDs, but I don't.. I *do* see the data though, regardless of what address I write to (provided it is in the range assigned to the BRAM controller).
    Do I need some kind of latch to be able to latch the address?
    Maybe with the bram_we_a lines?

  39. Potentially daft question on #FPGA and #VIVADO
    I'm trying to see the address that I'm writing to on the LEDs, but I don't.. I *do* see the data though, regardless of what address I write to (provided it is in the range assigned to the BRAM controller).
    Do I need some kind of latch to be able to latch the address?
    Maybe with the bram_we_a lines?

  40. There are few more horrid things in my job than flashing Firmware on QSPI memory with #Vivado. #fpga

  41. #FPGA dorks. I'm running into an issue where #vivado says: multiple drivers on MMCM pins when I use a known good block (LVDS deserializer from appnote xapp523) in the vivado block diagram for a 7 series #xilinx #zynq part (snickerdoodle black). I get the error even if I pin out directly to top level pins. I hate using the gui because it hides too much magic. Has anyone hit this madness before?

    I'm trying to deserialize a 1.024 Mbps 8b10b lvds to get it on the linux side for storage on disk.