--- Quote Start ---
1. Mixing vendors
--- Quote End ---
Luckily I only have to support Altera and Xilinx for now, still different vendors, but might make it easier. I can't seem to find the IP blocks of Xilinx(Altera are the asmi blocks you need to use, right?), so I can make sure they have the same in and outputs. If they have it should be simple with configurations, or is it still easier to just change the entity name to the component that needs to be used with another script I was planning to make?
--- Quote Start ---
When a user customizes the design, they can delete the GPIO component, and replace it with their component.
--- Quote End ---
Good thing is, the user may not customize the design I created. All he has to do is to tell which components he wants to use and which pins are attached to those. This way the user doesn't even need to know how an FPGA works, as long as he knows how to shoot the program in it(and if it's possible to automate that, the user doesn't have to do that either).
--- Quote Start ---
You need to think about how to arrange your code so that its easy to maintain.
--- Quote End ---
I was thinking to arrange the code with at least folders FPGA and Components, maybe I need to think better and more about that also indeed.
Those hardware blocks like SPI, I2C, SRAM, DRAM, whatever you can think of, can always be implemented the same no matter what the board looks like or what FPGA is used right? Except for the memory components, they can be bigger or smaller of course. Or did I miss more?
Honored Contributor
