From: "R.J.Sivakumar" <rj.sivakumar@dyansys.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Reg- One wire driver in Redboot
Date: Tue, 29 May 2007 12:02:00 -0000 [thread overview]
Message-ID: <200705291528.58749.rj.sivakumar@dyansys.com> (raw)
In-Reply-To: <1180422029.5571.25.camel@sg-ubuntu>
Dear Sergei
Really thanks for your immediate response,
As this is the first attempt in ECOS, can you please give the details of how
and where to program and cross compile the bootloader for the ARM11 board,
regarding the driver ,where i have to add the register address of the one
wire protocol of ARM11 processor, we are waiting for your suggestions
Thanks once again
--
Best regards,
Sivakumar.R.J
On Tuesday 29 May 2007 12:30 pm, you wrote:
> 29/05/2007 в 10:39 +0530, R.J.Sivakumar wrote:
> > Dear all.
> > As we are working in ARM11 board which has ECOS and redboot as the
> > bootloader in the BSP, we have to monitor the battery through one wire
> > device protocol in the redboot.Can u please help me, how to program the
> > ECOS for the one wire protocol to access the battery EEPROM.Also as iam a
> > newbie for ECOS and redboot,please show me some link or documentation
> > where i can start to achieve this.
>
> If you desire to contribute the common one-wire device for eCos, I would
> refer you to
>
> http://ecos.sourceware.org/docs-latest/ref/ecos-ref.html
> http://ecos.sourceware.org/docs-latest/ref/io.html
>
> If you already did implement the same primitives, for example, as
> described here http://www.maxim-ic.com/appnotes.cfm/appnote_number/126 ,
> you can easy add new polled device (your 1-wire device) for RedBoot
> using the RedBoor_idle() register, for example
>
> RedBoot_idle (read_ow_device, RedBoot_IDLE_AFTER_NETIO);
>
> void
> read_ow_device (bool is_idle)
> {
> if (!is_idle)
> return;
>
> // call your procedure
> ...
> }
>
> I did play with that maxim source 'as is', just defined those A-J values
> for my target. It did work fine (one my eCos thread measured a
> temperature arround the board).
>
> And the last note: please, don't use interrupt driven 1-wire read in
> RedBoot.
>
>
> -- Sergei
>
> > Thanks in Advance
> >
> > --
> > Best regards,
> > Sivakumar.R.J
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-05-29 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1180414215.10739.ezmlm@ecos.sourceware.org>
2007-05-29 7:00 ` R.J.Sivakumar
2007-05-29 7:34 ` Sergei Gavrikov
2007-05-29 12:02 ` R.J.Sivakumar [this message]
2007-05-29 17:15 ` Sergei Gavrikov
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=200705291528.58749.rj.sivakumar@dyansys.com \
--to=rj.sivakumar@dyansys.com \
--cc=ecos-discuss@ecos.sourceware.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 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).