This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: RedBoot as an application command shell
- From: Gary Thomas <gary at mlbassoc dot com>
- To: Nicolas Brouard <nicolas dot brouard at silicomp dot ca>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Wed, 08 Sep 2004 07:47:51 -0600
- Subject: Re: [ECOS] RedBoot as an application command shell
- Organization: MLB Associates
- References: <MFENKKFPNAKOOKBAEHLHGEAKCDAA.nicolas.brouard@silicomp.ca>
On Wed, 2004-09-08 at 07:35, Nicolas Brouard wrote:
> Hi all,
> I would like to do an application with a command shell. So I planned to use
> RedBoot in RAM and add some commands for my application. One of the commands
> uses an I2C driver. My I2C driver uses interrupts and cyg_flag
> synchronization functions. To compile RedBoot with this driver, I have to
> add the kernel package. And when I execute RedBoot and start my command, it
> hangs on cyg_flag_timed_wait function (with a timeout = cyg_current_time() +
> 10).
> This driver works very well in a test application.
> Why can I use synchronization functions in RedBoot and how can I do?
> Do I have to rewrite a command shell application?
RedBoot [purposefully] runs without interrupts.
If you want an interrupt environment, you'll need to set up some threads
and call cyg_scheduler_start()
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss