Feature request: much longer "variant" #352

New Issue

Dimitris · 2025-01-16T07:55:51+08:00

Dimitris commented

2025-01-16 07:55:51 +08:00

Feature request

The system description file contains the compulsory key "variant", whose value gets logged on Kasli SoC start-up and can be read out by artiq_coremgmt log. We like to make it rather long, for example:

"variant" : "kasli_soc_v1.1_artiq_master_commit_63157588bb8ed214bc9f24ade2d09b4ddefada03_drtio_master_wrpll_True_sed_lanes_32_peripherals_dio_sma_12",

Unfortunately, our long variant name gets cut off somewhere in the middle of the commit hash. Would it be possible to allow longer variant names to be returned by artiq_coremgmt log?

Or is there some other way you can recommend to determine exactly what binary is currently loaded to a Kasli SoC? For example, is there a way to read out the contents of a .json file that is located on the Kasli SoC's SD card via Ethernet?

# Feature request The [system description file](https://github.com/m-labs/artiq/blob/master/artiq/coredevice/coredevice_generic.schema.json) contains the compulsory key `"variant"`, whose value gets logged on Kasli SoC start-up and can be read out by `artiq_coremgmt log`. We like to make it rather long, for example: ``` "variant" : "kasli_soc_v1.1_artiq_master_commit_63157588bb8ed214bc9f24ade2d09b4ddefada03_drtio_master_wrpll_True_sed_lanes_32_peripherals_dio_sma_12", ``` Unfortunately, our long variant name gets cut off somewhere in the middle of the commit hash. Would it be possible to allow longer variant names to be returned by `artiq_coremgmt log`? Or is there some other way you can recommend to determine exactly what binary is currently loaded to a Kasli SoC? For example, is there a way to read out the contents of a `.json` file that is located on the Kasli SoC's SD card via Ethernet?

Sign in to join this conversation.