-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression with Alhambra-II 'apio time'. #422
Comments
I haven't used this I would be happy to fix the icetime function, but I am unsure how to generate the new chipdb file. |
I think that the first step is to determine what what chipdb file should be used for Alhambra-II (the canonical FPGAWars board). The candidates are the two 4k chipdb files that are currently installed (see below) or a new one that need to be added. Nextpnr seems to have a generator for these files https://github.com/YosysHQ/nextpnr/blob/master/ice40/chipdb.py @Obijuan, any thoughts?
|
I agree. I read through the files earlier and I am not sure which ICE40 the |
I also wonder if this formula for the chipdb file name is sufficient. apio/apio/resources/ice40/SConstruct Line 80 in 88672ad
@Obijuan , can you revisit the chipid generation and runtime selection? |
The `u4k' family does not exist in reality. There are only two diffent manufactured families: 1K and 8K. The 4K family in an 8K that is actually not fully used by the Lattice software (it is the propietary software that limit you from using the 8K). Let's say that 4K is a 'virtual' FPGA limited by software. When you use the Open source tools, you can see that any 4K FPGA is in fact an 8K. So, the Alhambra-II board es an 8K. Any board with 4K FPGA, is an 8K |
Thanks @Obijuan, this is very useful. A couple of follow up questions for you (referring to the ice40 fpga list below from the dev repository)
|
Does a new chipdb file need to be created still? The 8k file has the pinout of the BGA and the u4k file is not technically real. I am not sure how important it is to have the pinout be correct. I would be happy to work on generating a file for the 4k (8k technically thank you @Obijuan for the clarification) for the tq144 package but I would need to be pointed to some documentation. |
@embedded-tek, since this issue is involved, how about restoring the original configuration while you research the chipdb issue? |
That works. Let me revert and test locally. Then I can look into it a little more. |
@embedded-tek, I am preparing a commit to restore the original definition. This will make the Alhambra II test examples work again with 'apio time'. Alhambra II is the reference borad of apio and possibly the most tested, so chances are these definitions should work also with your board (with the same FPGA).
|
… again for Alhambra II. See discussion here FPGAwars#422
Fixed. |
@embedded-tek, @Obijuan
This commit seems to break the 'apio time' command with Alhmabra-II due to the change of the FPGA size from
8k
to4k
.9b528b0
Below is a log fo running the dev apio command on the
test-examples/Alhambra-II/02-jumping-LED example
. The 4k FPGA size constructsCHIPDB_PATH
with the file namechipdb-4k.txt
which does not exist (the filechipdb-u4k.txt
does exist).The text was updated successfully, but these errors were encountered: