Is should compile the core in isim and run the simulation (of course ISE must be installed and in the path ). Doing the same with the full Bonfire SoC will not be much more effort, I decided to make it in two steps, because my understanding of FuseSOC is that a project is composed of cores, so I want to try this approach and hope that the SoC can reuse the CPU as IP core.įusesoc -cores-root=. The example is limited to simulation because it is my CPU core test bench. I succeed to simulate the Bonfire CPU with FuseSOC. This is a good first step to test out automated builds, up next is using the library management features and then getting it under CI. The second line creates a bin file that can be loaded using zpuinoprogrammer. The first one allows us to use a ucf file that has all the papilio pins defined without throwing up errors. Project set "Create Binary Configuration File" true Project set "Allow unmatched LOC Constraints" true I added the following two lines to the tcl script that creates the project: I was unable to figure out how to make changes to the xise project file for things that we use with the Papilio so I had to fork the project and hard code the necessary changes for now. ![]() The result is a fully automated build process that creates a WebPack_QuickStart.bit file in the build/quickstart_0/bld-ise/ directory. Then on a linux machine on AWS I did the following commands: I'm attempting to first setup a simple project to autobuild with it. I've been looking over the documentation (which is extremely sparse) and think it might be a good fit. In another discussion about getting back to basics FuseSOC was mentioned as a possible tool to manage HDL libraries.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |