-
Notifications
You must be signed in to change notification settings - Fork 177
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
Gowin vendor definitions don't support the GW1NR-LV9QN88PC6/I5 (tang nano 9k) but apicula does #953
Comments
Also same issue with |
cc @bl0x who contributed Gowin support--I do not understand how the part numbering works to be honest |
@jeremyherbert The family given in the Apicula Makefile ( The correct family name is Nextpnr generates chipdb files only for family GW1N, but the same file seems to work also with the GW1NR family. This is what is also mentioned in YosysHQ/apicula#206. When using Amaranth, the correct family name needs to be specified. This is automatically the case when using the platform definitions from the amaranth-boards repository, so e.g. for the tang nano 9k: part = "GW1NR-LV9QN88PC6/I5"
family = "GW1NR-9C" (Taken from tang_nano_9k.py#L14) When using amaranth_boards, the error mentioned above does not appear and the build succeeds with both the The requirement from the apicula readme is automatically satisfied by the I hope this is a bit clearer now, but if any questions remain, please ask! |
Thanks @bl0x for the clear explanation! Gowin part names are something else... |
Thank you for following up on this. |
According to this line in apicula, the Tang Nano 9k has the device
GW1NR-LV9QN88PC6/I5
and familyGW1N-9C
. However, when using these values with the Gowin vendor support in Amaranth, the following error is emitted fromparse_part
:The apicula readme also has this note at the bottom:
"C devices require passing the --family flag as well as --device to Nextpnr, and stating the family in place of device when passing -d to gowin_pack because the C isn't part of the device ID but only present in the date code."
The text was updated successfully, but these errors were encountered: