Skip to content

occasionally an erroneously incorrect clock enable state is generated, reason unknown #32

@weatherhead99

Description

@weatherhead99

The following WDL code:
`
SLOT 1 driverx {
DRVX 1 [PCLK_fast,PCLK_slow,1] "PCLK_B3_2";
DRVX 2 [PCLK_fast,PCLK_slow,1] "PCLK_A3_2";
DRVX 3 [PCLK_fast,PCLK_slow,1] "PCLK_B2_2";
DRVX 4 [PCLK_fast,PCLK_slow,1] "PCLK_A2_2";
DRVX 5 [PCLK_fast,PCLK_slow,1] "PCLK_B1_2";
DRVX 6 [PCLK_fast,PCLK_slow,1] "PCLK_A1_2";
DRVX 7 [PCLK_fast,PCLK_slow,1] "PCLK_B1_1";
DRVX 8 [PCLK_fast,PCLK_slow,1] "PCLK_A2_1";
DRVX 9 [PCLK_fast,PCLK_slow,1] "PCLK_A2_1";
DRVX 10 [PCLK_fast,PCLK_slow,1] "PCLK_B2_1";
DRVX 11 [PCLK_fast,PCLK_slow,1] "PCLK_A3_1";
DRVX 12 [PCLK_fast,PCLK_slow,1] "PCLK_B3_1";
}

`

appears to erroneously produce an unset "enable" state on the first clock DRV1, see screenshot:

Image

(note unticked enable box, despite [,,1] statement in the "PCLK_B3_2" line definition).

I have no time right now to investigate this. The only special thing I can see about this statement is that it is the first statement in the entire file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions