This is the mail archive of the
mailing list for the eCos project.
[ECOS] Bluetooth Stack
- From: Gonçalo Antunes .::. [gmma at gmma dot NeT] .::. <gmma at gmma dot net>
- Cc: "eCos development" <ecos-devel at ecos dot sourceware dot org>,"eCos Discussion" <ecos-discuss at ecos dot sourceware dot org>
- Date: Tue, 26 Oct 2004 01:01:21 +0100
- Subject: [ECOS] Bluetooth Stack
- References: <firstname.lastname@example.org> <1098715987.12371.142.camel@hermes>
- Reply-to: Gonçalo Antunes .::. [gmma at gmma dot NeT] .::. <gmma at gmma dot net>
Anyone using a bluetooth stack on eCos?
I'm working on my Engineering final degree project and I need to use it to
implement wireless access to a generic embedded system.
Thank you very much.
Regards from Portugal.
----- Original Message -----
From: "Gary Thomas" <email@example.com>
To: "Manfred Gruber" <firstname.lastname@example.org>
Cc: "eCos development" <email@example.com>; "eCos Discussion"
Sent: Monday, October 25, 2004 3:53 PM
Subject: [ECOS] Re: Redboot console on ep93xx
On Mon, 2004-10-25 at 08:37, Manfred Gruber wrote:
I use a ep9315 board
I want to change in in the redboot bootloader the console. Now it is
configured on the first serial port. How do i change this to the second
I found out that this is done in
I changed what i thought would be correct, but i does not work:
int cur =
// Init channels
// TODO shouldn't this be default value, not 0?
// Setup procs in the vector table
// Set channel 0
// Set channel 1
comm = CYGACC_CALL_IF_CONSOLE_PROCS();
//Contec hypercontrol micro9 change to 1
--> //CYGACC_COMM_IF_CH_DATA_SET(*comm, &ep9312_ser_channels);
--> CYGACC_COMM_IF_CH_DATA_SET(*comm, &ep9312_ser_channels);
// Restore original console
Maybe someone has done this already, or there is a config option missing.
Thanks for help
You should not have to make these changes at all. Simply set
CYGPKG_REDBOOT_ANY_CONSOLE to 0/false
so RedBoot will only use a single console device. Then set
CYGNUM_HAL_VIRTUAL_VECTOR_CONSOLE_CHANNEL to 1
for your desired channel.
That's the whole idea behind the configuration system - source code
changes should not be required to make simple choices like this.
BTW - where did you get this port? It's not part of the public CVS.
Finally, this question really belongs on the eCos discussion list which
is for discussing questions and issues about using eCos. The eCos
development list is really for discussing changes to the eCos sources.
Gary Thomas <firstname.lastname@example.org>
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss