-
Notifications
You must be signed in to change notification settings - Fork 201
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
artiq_ddb_template.py does not add leds to most variants #2245
Comments
That's because those LEDs are used to indicate presence of a DRTIO link on the SFP port next to each LED when DRTIO is enabled, and are not user-controllable then. |
Small note, on Kasli 2.0 LED RTIO devices are generated only for standalone; it's not just |
The current implementation reflects this shared use of the LEDs on Kasli v1. It's not (yet) noted on the Kasli wiki. Kasli v2 and kasli-soc now have dedicated user LEDs (led0, led1, led2). Since the .JSON includes a hardware version field the behavior of the build scripts as well as
|
In kasli v2, As @Spaqin mentioned, an update to the |
Glad you're working on this @SimonRenblad! The User LEDs are helpful whether or not they are visible from the front panel. ![]() (above) kasli v2 has three user LEDs. ![]() ![]() (above) kasli-soc has three user LEDs. They are on two different pages of the schematic. |
Thank you for the catch! From what I could gather,
I will amend the draft PR to reflect this and also add support for the user leds that are available in kasli v1.1. |
AFAICT this is fixed? |
Should be fixed. With the exception of the Kasli-SoC L2 LED, which we omitted due to it being controlled by the ps7, all other LEDs should be added in #2262. |
ps7 is the processing system, i.e. the ARM cores. Some pins can only be accessed through the CPU. |
artiq/frontend/artiq_ddb_template.py
does not automatically add led0 and led1 for all kasli variants. Currently they are only added forstandalone
. This makes getting started harder for new users and debugging of existing systems harder.The text was updated successfully, but these errors were encountered: