You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pad_cfg.hjson we list the pads, but there is no information on what is the target where they will be placed or used (pynq-z2, nexys, zcu104, ASIC...). Together with @christophmuellerorg we discussed about centralizing all of this information in this file to generate automatically the pads and make sure this information stays consistent throughout the different places where it is used. For the ASIC targets this would have the mapping of the cells (top, right, bottom...) and other information needed for their placement. This would move the extra config info added in #493 . For the FPGA targets it would have all of the pin assignments so they can be modified externally without having to apply patches. An example of the targets: that would be placed alongside the pads: is the following:
In
pad_cfg.hjson
we list the pads, but there is no information on what is the target where they will be placed or used (pynq-z2, nexys, zcu104, ASIC...). Together with @christophmuellerorg we discussed about centralizing all of this information in this file to generate automatically the pads and make sure this information stays consistent throughout the different places where it is used. For the ASIC targets this would have the mapping of the cells (top, right, bottom...) and other information needed for their placement. This would move the extra config info added in #493 . For the FPGA targets it would have all of the pin assignments so they can be modified externally without having to apply patches. An example of thetargets:
that would be placed alongside thepads:
is the following:The text was updated successfully, but these errors were encountered: