home.social

#fpga — Public Fediverse posts

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

fetched live
  1. The AMD Versal RF devices are getting there time on stage at Hot Chips 2026 with hardend IP blocks to flexible FPGA fabric#amd #FPGA #Versal
    AMD Versal RF Series at Hot Chips 2026
  2. At Hot Chips 2026 the first talk of day 2 is AMD Versal Premium Gen2 which is being shown for edge and physical AI use cases and more#amd #FPGA #Versal
    AMD Versal Premium Gen2 at Hot Chips 2026
  3. Une excellente série de Vidéos par Denis Bodor (rédac-chef de GNU Linux Mag et Hackable) pour découvrir le développement de FPGA sur Linux avec l'environnement open-source LiteX #Hardware #FPGA #Video youtube.com/playlist?list=PL_r

  4. Zeitlos #FPGA SOC/OS v0.0.1 is released. Now with real screenshots, DHCP, many bug fixes, and an easier installation process. github.com/machdyne/zeitlos/

  5. youtu.be/0F3pyxdG0kU?is=HVwFPT

    #OutRunners su mister #fpga una cosa fantastica e gira molto bene . Split screen configurabile. Magari 🤔 uscirà una versione #twin ?
    @giochi
    Link per scaricare il core e i relativi file : patreon.com/Meathax/posts/outr

  6. Decided to put up a public repository of my WIP new fantasy console, the "GameJimmy" - except it's not just a software emulator, it's a low level FPGA implementation that runs as a MiSTer core! :)

    codeberg.org/GlaireDaggers/Gam

    #fpga #retro #misterfpga #retrogaming #fantasyconsole

  7. I haven't had an FPGA build time blow up to times like this since the early 2000's.

    I'm going to let it run to see how long it goes.

    #FPGA #buildinpublic #electronics

  8. With scroll hardware registers fixed, here’s a demo of draw and display scrolling hardware. #ULX3S #FPGA

  9. Does anyone happen to know anything about the ECP5's undocumented SPI commands?

    I've scanned through all possible bytes and found a few commands the system apparently (based on the Invalid Command bit in the device status register) recognizes, but that are not documented in the sysCONFIG User Guide.

    • 02, no interesting direct output, probably LSC_WRITE_COMP_DIC?
    • 0a, no interesting direct output
    • 11, outputs 0a00d0dd on my device
    • 16, outputs 41111043 on my device (which is the IDCODE of my device lul, this is also returned by the documented e0 command)
    • 19, outputs 00044c61 on my device
    • 24, no interesting direct output
    • 3a, no interesting direct output
    • 42, no interesting direct output
    • 47, no interesting direct output
    • 67, no interesting direct output
    • 70, no interesting direct output
    • 72, no interesting direct output
    • 72, no interesting direct output
    • 73, outputs 00000000 on my device
    • 7d, no interesting direct output
    • 80, outputs 00000000 on my device
    • 9c, no interesting direct output
    • 9d, no interesting direct output
    • 9e, outputs 00ffffff on my device
    • 9e, outputs 20ffffff on my device
    • b0, outputs 00000000 on my device
    • b2, no interesting direct output, maybe LSC_EBR_WRITE???
    • c9, no interesting direct output
    • ca, no interesting direct output
    • cb, no interesting direct output
    • cf, no interesting direct output
    • e2, no interesting direct output, but sets the ID Error bit in the device status register, so it is just undocumented for SPI, but is actually the VERIFY_ID command
    • e8, outputs 00000000 on my device
    • f6, no interesting direct output, maybe LSC_EBR_ADDRESS???
    • f7, outputs 00ffffff on my device
    • f8, no interesting direct output

    If anyone knows what any of these commands do or might do, please please please let me know :3



    RE: https://wafrn.jcm.re/fediverse/post/450ff258-774f-4a05-93c4-720beb7cc7dd
    #FPGA #ECP5 #Lattice
  10. Alrighty, soooooo:

    It's actually possible to "talk" directly to the configuration engine using Slave SPI Mode (set MASTER_SPI_PORT=DISABLE SLAVE_SPI_PORT=ENABLE in your constraints) and simply using D0/MOSI/IO0 as MOSI, D1/MISO/IO1 as MISO, and SN/CSN as CS. The clock is a bit more difficult, since you cannot directly use it as an I/O port. However, it is possible to instantiate the USRMCLK primitive, feed your clock into USRMCLKI and set USRMCLKTS to 0.

    This basically allows communicating with the config engine using the SPI commands specified in section 6.2.3 of ECP5 and ECP5-5G sysCONFIG User Guide.

    Sadly, when the device is in user mode (i.e. actually running your logic), the config engine only allows read commands (except for LSC_PROG_CTRL0 for some odd reason) and you cannot use this to partially reconfigure the device :(

    The configuration bitstream contains optional Slave SPI persistence bits. When the device completes configuration and wakes up, it checks the persistent bits to determine if the Slave SPI port is to remain operational once in user mode. This selection is independent of the CFGMDN pin setting. A port enabled by persistence is capable of reading commands only. Thus, the port is a Background Mode port and is not a configuration port, and can only be used for read back operations.

    This is really, really sad.

    My next idea is to try the Slave Serial Configuration Mode or Slave Parallel Mode, which does not have a restriction depending on the FPGA mode documented, but might still have one.



    RE: https://wafrn.jcm.re/fediverse/post/4f89c699-be4c-4800-a0fa-19dc91e9a3bb
    #FPGA
  11. SPI-контроллер на FPGA: переносим на Zynq 7000. Часть 2

    Продолжаем разработку SPI IP Core на Verilog. В первой части мы перенесли SPI-контроллер с Altera Cyclone IV на Zynq-7020, сохранили исходный регистровый интерфейс и добавили AXI4-Lite. Теперь задача меняется: нужно превратить работающий RTL в полноценное устройство под Linux. Во второй части соберем Block Design с PS, настроим карту адресов и прерывания, подготовим загрузочную цепочку и Device Tree, а затем подключим контроллер к стандартной SPI subsystem Linux. Здесь уже недостаточно рабочего bitstream: ошибка в ps7_init , адресах или Device Tree может сделать исправное ядро недоступным для ОС. После обычного PIO-доступа добавим потоковый тракт для больших объемов данных. Для этого появятся AXI-Stream адаптер, глубокий FIFO, backpressure и режим TX-only. По ходу разберем ошибки, которые проявляются только под нагрузкой: потерю байтов на границе FIFO, проблемы запуска DMA и устаревший результат синтеза. Финал этой части - плата самостоятельно загружает Linux, SPI работает через драйвер, а большие буферы передаются из DDR в PL через AXI DMA без побайтового участия Cortex-A9. Всем, кому интересно продолжение - добро пожаловать под кат! =)

    habr.com/ru/companies/beget/ar

    #fpga #spi_controller #linux #buildroot #driver #dts #lcd #dma #verilog #axi

  12. @lethalbit protocompiler for haps 80 is no longer available or even maintained for paid support so you'll have issues finding it.

    #electronics #fpga

  13. New Zeitlos #FPGA SOC/OS features:

    - Window manager
    - Object-based interprocess messaging/streaming
    - Networking (IP/ICMP/ARP/UDP/TFTP)

    github.com/machdyne/zeitlos