From: joeri_melis@agilent.com
To: joeri_melis@agilent.com, ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Problem configuring integrator board with ecos
Date: Thu, 13 Jun 2002 02:31:00 -0000 [thread overview]
Message-ID: <F117750B5476D311B4D40090275413D907ED2703@portia> (raw)
Ok, we solved the problem by locating the code in the hardware init region of eCos itself.
-----Original Message-----
From: joeri_melis@agilent.com [mailto:joeri_melis@agilent.com]
Sent: donderdag 13 juni 2002 10:50
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Problem configuring integrator board with ecos
Hi,
We are using an ARM7 integrator board to run our software and use the following code to change the clock speed to 60 MHz instead of the default 20 MHz.
*(int *)(INTEGRATOR_HDR_LOCK) = INTEGRATOR_HDR_OSC_MEM_UNLOCK;
set_osc = *(int *)INTEGRATOR_HDR_OSC & 0x00000FFF;
set_osc += INTEGRATOR_HDR_OSC_MEM_60MHz;
*(int *)INTEGRATOR_HDR_OSC = set_osc;
*(int *)(INTEGRATOR_HDR_LOCK) = INTEGRATOR_HDR_OSC_MEM_UNLOCK + 1;
This works fine without eCos but when we combine it with an application using eCos it won't work. We tried locating the code at different spots (cyg_prestart, cyg_user_start, in a thread function) but no changes are made to the register and clock speed.
Does anyone have a clue what might go wrong here?
Thanks, Joeri.
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2002-06-13 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 2:31 joeri_melis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-13 1:50 joeri_melis
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=F117750B5476D311B4D40090275413D907ED2703@portia \
--to=joeri_melis@agilent.com \
--cc=ecos-discuss@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).