review RTIO clock frequency #21

Closed
opened 2020-06-28 17:44:39 +08:00 by sb10q · 3 comments

Once #5 is sorted out, we should check that the RTIO frequency is correct. There is typical ZynqⓇ-behavior with that clock depending on how the chip was booted (SZL/FSBL, JTAG/SD card, ps7_init applied or not).

Once #5 is sorted out, we should check that the RTIO frequency is correct. There is typical ZynqⓇ-behavior with that clock depending on how the chip was booted (SZL/FSBL, JTAG/SD card, ps7_init applied or not).
Poster
Owner

Yes, there is a problem, this outputs 333Hz instead of 1kHz (loading via SZL and JTAG which should be consistent now):

from artiq.experiment import *


class BlinkForever(EnvExperiment):
    def build(self):
        self.setattr_device("core")
        self.setattr_device("led0")

    @kernel
    def run(self):
        self.core.reset()
        while True:
            self.led0.pulse(0.5*ms)
            delay(0.5*ms)
Yes, there is a problem, this outputs 333Hz instead of 1kHz (loading via SZL and JTAG which should be consistent now): ``` from artiq.experiment import * class BlinkForever(EnvExperiment): def build(self): self.setattr_device("core") self.setattr_device("led0") @kernel def run(self): self.core.reset() while True: self.led0.pulse(0.5*ms) delay(0.5*ms) ```
Poster
Owner

With ps7_init.apply() it goes to 400Hz.

With ``ps7_init.apply()`` it goes to 400Hz.
Poster
Owner

Fixed by a8de572014

Fixed by https://git.m-labs.hk/M-Labs/artiq-zynq/commit/a8de572014437660e7d00b6f355d971c9e6152ef
sb10q closed this issue 2020-07-07 19:47:42 +08:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/artiq-zynq#21
There is no content yet.