RE: Interrupt latency in RTEMS (Zedboard)

Well, Thank you very much for these answers ! Sébastien. -Message d'origine- De : Chris Johns [mailto:chr...@rtems.org] Envoyé : mercredi 28 mars 2018 02:12 À : j...@rtems.org; BRIARD Sebastien Cc : users@rtems.org Objet : Re: Interrupt latency in RTEMS (Zedboard) On 28/03/2018 01:28, J

Fwd: Quickstart Build instructions

-- Forwarded message -- From: Russell Haley Date: Tue, Mar 27, 2018 at 10:45 PM Subject: Re: Quickstart Build instructions To: Sebastian Huber On Tue, Mar 27, 2018 at 10:36 PM, Sebastian Huber wrote: > Please send e-mails to the mailing list. Sorry, my mistake. > > > On 28/

Re: Quickstart Build instructions

Thanks! Russ On Tue, Mar 27, 2018 at 10:23 PM, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 28/03/18 07:14, Russell Haley wrote: > >> Hi, the quick start indicates using ./bootstrap -p, but using said >> parameter only results in the error/hep output. Using ./bootstrap withou

Re: Quickstart Build instructions

On 28/03/18 07:14, Russell Haley wrote: Hi, the quick start indicates using ./bootstrap -p, but using said parameter only results in the error/hep output. Using ./bootstrap without any parameters started the the process for me? https://docs.rtems.org/branches/master/user/start/index.html Sor

Re: Quickstart Build instructions

On Tue, Mar 27, 2018 at 10:14 PM, Russell Haley wrote: > Hi, the quick start indicates using ./bootstrap -p, but using said > parameter only results in the error/hep output. Using ./bootstrap without > any parameters started the the process for me? > > https://docs.rtems.org/branches/master/user/

Quickstart Build instructions

Hi, the quick start indicates using ./bootstrap -p, but using said parameter only results in the error/hep output. Using ./bootstrap without any parameters started the the process for me? https://docs.rtems.org/branches/master/user/start/index.html Thanks, Russ ___

Re: Interrupt latency in RTEMS (Zedboard)

On 28/03/2018 01:28, Joel Sherrill wrote: > On Tue, Mar 27, 2018 at 8:05 AM, BRIARD Sebastien > > wrote: > > Okay, I realized how I was confusing clock tick (for timekeeping) and > interrupt latency and why the result were not the ones I expe

Re: Interrupt latency in RTEMS (Zedboard)

On Tue, Mar 27, 2018 at 8:05 AM, BRIARD Sebastien < sebastien.bri...@thalesaleniaspace.com> wrote: > Okay, I realized how I was confusing clock tick (for timekeeping) and > interrupt latency and why the result were not the ones I expected. > I still have one question, is there a macro to choose/im

RE: Interrupt latency in RTEMS (Zedboard)

Okay, I realized how I was confusing clock tick (for timekeeping) and interrupt latency and why the result were not the ones I expected. I still have one question, is there a macro to choose/impose the processor frequency ? -Message d'origine- De : BRIARD Sebastien Envoyé : mardi 27 mar

RE: Interrupt latency in RTEMS (Zedboard)

I am using the expiration of a timer. And basically I am doing two things: - I keep measuring time in my main loop - when I am in the handler I take a new measure of the time. It was a quick, not so rigorous test, with global variables. Here is the code : // Global variable for tests // volati

Re: Interrupt latency in RTEMS (Zedboard)

He said in the first email he was using the classic_signal example which sets a timer to fire after fifty clock tick ticks. https://devel.rtems.org/browser/examples-v2/classic_api/classic_signal/test.c?rev=b241c6c58c59176c372980435b2620276568f72a Depending on where you start and stop the start an

Re: Interrupt latency in RTEMS (Zedboard)

Hello Sebastien, could you give a code example how you measure the interrupt latency? Which interrupt do you use? The time keeping is independent of the clock tick configuration. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189

RE: Interrupt latency in RTEMS (Zedboard)

Well, I didn't mention that because I can't guess why. However, I had what could be a similar thing before, but with Leon3 implemented on the logic of the Zedboard. When I traced down the BSP code (which wasn't RTEMS, I used the bcc there as far as I remember) it really didn't contain anything that

RE: Interrupt latency in RTEMS (Zedboard)

Good point. Thanks. Would you have any idea concerning my other question ? (why I get the same result for interrupt latency with different values of Tick per microsecond ) De : Rehab Massoud [mailto:rehab.mass...@gmail.com] Envoyé : mardi 27 mars 2018 13:57 À : BRIARD Sebastien Cc : rtems-us...@

RE: Interrupt latency in RTEMS (Zedboard)

Needless to say also you can't measure software execution time that accurately with software. It's not only that it's intrusive but also would never be cycle accurate. If you really need such cycle accuracy you might think about hardware-based tracing techniques. On Mar 27, 2018 13:52, "BRIARD Seba

RE: Interrupt latency in RTEMS (Zedboard)

Yeah, hardware limits to 1.5ns if we take in account the max frequency of the cortex. (That was the more or less 1ns =) ) De : Rehab Massoud [mailto:rehab.mass...@gmail.com] Envoyé : mardi 27 mars 2018 13:49 À : BRIARD Sebastien; rtems-us...@rtems.org Objet : Re: Interrupt latency in RTEMS (Zedbo

Re: Interrupt latency in RTEMS (Zedboard)

Hi, the smaller theoretical delay accuracy you can measure (without adding to an ASIC cascaded FF) is one clock cycle. I think the maximum frequency that could be achieved on zedboard is not more than 800 MHz, and the maximum Zync's Cortex freq per Zedboard's datasheet is 667 MHz, which means you c

Interrupt latency in RTEMS (Zedboard)

De : BRIARD Sebastien Envoyé : mardi 27 mars 2018 11:42 À : 'users@rtems.org' Objet : Interrupt latency in RTEMS (Zedboard) Hi, I was trying to measure the interrupt latency in RTEMS with a Xilinx Zynq Zedboard (cortex A9). I modified the c file in classic_signal example to measure time in the