From: "Wiebe Baron" <Wiebe.Baron@Wirelessvalue.nl>
To: "BlueZ Mailing List" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Embedded bluetooth recommendations
Date: Thu, 28 Oct 2004 12:27:04 +0200 [thread overview]
Message-ID: <006501c4bcd8$ab2e1ba0$af00a8c0@wivd10> (raw)
In-Reply-To: 1098693859.24932.18.camel@pegasus
Hi Marcel,
> > I have a question about embedded Bluetooth. I'm working on a feedback
> > control project which involves 8 devices. Up till now a module has
> > been used with integrated stack but this is unable to support an
> > RFCOMM link with seven slaves and the response time of a scatternet is
> > unacceptable so I'm now looking for a multiprocessor solution with a
> > separate stack.
>
> are you talking about seven RFCOMM links on the same ACL link or about
> seven different ACL links. If you really wanna work with piconet where
> the master controls 7 slaves you should use a CSR chip, because all
> other Bluetooth chips are acting somekind weird. However even with the
> CSR stuff you must make sure that at least a HCI 18.2 firmware is used.
Yes the idea is to use seven ACL links. Luckily the current design uses a
sharp process in combination with a CSR chip.
>
> > I'm currently experimenting with a sharp LH79520 with embedded Linux
> > from metrowerks and Bluez but this seems to be overkill because the
> > application requirements themselves are minimal (7 way cable
> > replacement).
>
> The Sharp uses an ARM7TDMI. Actually this is really overkill and then
> you should better buy a Bluetooth chip that itself uses this ARM chip
> like Zeevo etc. However then the above point comes in ...
I took a look at the Zeevo but it only seems to support 4 simultaneous ACK
links which is a bit worrying given that it's based on the same ARM chip.
>
> > Does anyone have a suggestion of a combination of stack, operating
> > system and microprocessor that is known to work together and has
> > minimum requirements in terms of RAM, ROM and processor speed (cost)?
>
> I am not a microprocessor expert, but actually every processor with
> Linux support should be useable and BlueZ is of course the best choice
> for a Bluetooth stack.
Thanks for the advice. This is the route I'm going to be taking.
Cheers,
Wiebe.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out
more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-28 10:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 8:22 [Bluez-users] Embedded bluetooth recommendations Wiebe Baron
2004-10-25 8:44 ` Marcel Holtmann
2004-10-28 10:27 ` Wiebe Baron [this message]
2004-10-28 10:47 ` Marcel Holtmann
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='006501c4bcd8$ab2e1ba0$af00a8c0@wivd10' \
--to=wiebe.baron@wirelessvalue.nl \
--cc=bluez-users@lists.sourceforge.net \
/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.