All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Seeger <steve@domain.hid>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] no-brainer issue found, but not solved
Date: Tue, 21 Feb 2006 10:15:37 -0800	[thread overview]
Message-ID: <C02098C9.24B1%steve@domain.hid> (raw)
In-Reply-To: <43FB546E.5090802@domain.hid>

Here are the routines in question:

low priority:

for(;;) {
    /* regular rf watchdogs */
    outb(0x45, 0x????);
    outb(0x6a, 0x????);
    outb(0x7e, 0x????);
               
    outb(0, 0x????); //patient watchdog
    outb(0, 0x????); //fault led

    flip_reg_bits(WRFPC, 0x????); //flash yellow led
                
    ????_flip_spi_bits(HV_STATUS_CONTROL, HV_WDOG_STROBE_MONITOR);
                
    rt_task_wait_period();
}

high priority:

    for(;;) {
        if(motor_move) {
            syslog(LOG_INFO, "about to lock up");
            for(int i=0; i<100000000; i++);
            motor_move=0;
        }

        rt_task_wait_period();
    }

All function calls contain only inb or outb, no system calls. If I comment
out the syslog call in the high priority thread, the yellow LED stops
flashing completely. Otherwise, it flashes every second, with the
periodicity of the higher priority thread.

I have another problem, too:

Using the same yellow LED flashing thread, if I start up a LOWER priority
task like this, I can see jitter on my LED strobe line on the scope once a
second. Why would the lower priority thread making a system call affect the
higher priority one?

for(;;) {
    syslog(LOG_INFO, "sleeping 1");
    sleep(1);
}

Steven



  reply	other threads:[~2006-02-21 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 17:38 [Xenomai-help] no-brainer issue found, but not solved Steven Seeger
2006-02-21 17:57 ` Jan Kiszka
2006-02-21 18:15   ` Steven Seeger [this message]
2006-02-21 18:36     ` Jan Kiszka
2006-02-21 21:20       ` Jeroen Van den Keybus
2006-02-22 14:21         ` Steven Seeger
2006-02-22 15:00           ` Jan Kiszka
2006-02-24  9:01       ` Philippe Gerum
2006-02-24 14:00         ` Steven Seeger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C02098C9.24B1%steve@domain.hid \
    --to=steve@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.