-
Notifications
You must be signed in to change notification settings - Fork 58
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
No way to define platform connectors #77
Comments
I don't have particular comments except that the ARTIQ use cases (e.g. Kasli/Metlino+EEMs) should be covered, perhaps with different code. |
Here's an older example of a snag w/ the existing system:
Migen does not gracefully handle connector conflicts w/ overlapped resources, and I think perhaps it should error ASAP rather than relying on the backend to error out. Overlapping resources should still be supported:
|
That's a general issue with the current system and not specific to connectors - it never checks if a physical pin is used multiple times (the synthesis toolchain normally produces a clear error message in that case, so I didn't consider this important). |
There are many other somewhat similar errors that we don't check, and they can be vendor-specific, e.g. conflicting voltages in the same I/O bank... |
I was under assumption that the existing system does not allow using dictionaries for connectors. But of course I am wrong. So, I think no major changes are needed to the connector system specifically. |
I notice that the platform code has been stubbed; removing quite a lot of complexity. I have been testing and I have just managed to get a uart going on nmigen using a port of @whitequark 's original blog post. https://github.com/zignig/tinybx_stuff/tree/master/platform_test . Max speed is 57600 before it stops responding as echo from a 16MHz clock. Observations:
where extend is an empty function that runs straight after Anyway, I'm going to try and hook up a Boneless to the uart tonight. |
We need some way to define platform connectors, like in oMigen. But in oMigen this feature was somewhat inconvenient. I would like to collect feedback from everyone who used it so that the nMigen one would be better.
cc @sbourdeauducq @jordens @cr1901 @key2
The text was updated successfully, but these errors were encountered: