get_module_info

Script to automatically prepare the ‘modules.json’ file (or whichever name is given in dirigent.toml).

This script can automatically determine e-Fuse codes from chips, retrieve chip settings from the database, and modify ‘modules.json’ accordingly.

Each step in this script can also be enabled/disabled.

Usage: dirigent get_module_info [OPTIONS]

    Some text

Options:
    --help                          Show this message and exit.

Functions

edit_value_in_JSON(jsonFile, key, values)

This is performed using regex, since json does not retain file formatting

edit_value_in_XML(xmlFile, hybrid_ids, ...)

extract_eFuseCode_from_log(log_file)

get_values_from_JSON(jsonFile, key, croc_ver)

run_calibration_detect_abort(context, N)

Temporary abort check while logic in run_calibration() is being developed

edit_value_in_JSON

module_testing.tools.get_module_info.edit_value_in_JSON(jsonFile, key, values)

This is performed using regex, since json does not retain file formatting

edit_value_in_XML

module_testing.tools.get_module_info.edit_value_in_XML(xmlFile, hybrid_ids, chip_ids, eFuseCodes, key='eFuseCode', croc_ver='RD53Bv2')

extract_eFuseCode_from_log

module_testing.tools.get_module_info.extract_eFuseCode_from_log(log_file)

get_values_from_JSON

module_testing.tools.get_module_info.get_values_from_JSON(jsonFile, key, croc_ver)

run_calibration_detect_abort

module_testing.tools.get_module_info.run_calibration_detect_abort(context, N)

Temporary abort check while logic in run_calibration() is being developed