Skip to content

External interrupts take 6 us to responds #200

Closed
@joverbee

Description

@joverbee

Even though we can expect the interrupt handling through arduino interface to be slower than doing low level coding with the dataheet at hand, 6 us is really ridicoulously long for a processor with 20ns clock cycle (300 clock cycles).
I havent figured out yet to find the cause of this (played with genclck of the EIC but no improvement) but to me it is clear that this can not be an optimal way to use the EIC controller. This makes interrupting for anything dynamic impossible. It seems even longer than it was on arduino uno boards, but dont recall the exact time.
( btw I managed through hw event system to start stop the TCC on external interrupt in 180ns=9 cycles- but of course we need to do more checking and jumping to ISR in this case, but still: does it really take 291 clock cycles to do this?)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions