All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BCCMD Test Command "memory"
Date: Mon, 22 Aug 2005 16:45:45 +0200	[thread overview]
Message-ID: <1124721945.23599.58.camel@pegasus> (raw)
In-Reply-To: <4309DF55.3010106@hasborg.com>

Hi Josh,

> While reading through the BlueCore BCCMD Commands documentation, I came
> across the "memory" test command.  This command allows us to read or
> write from/to a block of RAM within the chip.
> 
> The documentation is rather sparse for this test command.  The Varid and
> Type are documented, indicating that it's possible to specify a base
> memory address and a length of bytes, but it does not indicate how to
> differentiate a read or write operation.

the BCCMD itself differs between writing or reading a value and this
should be the same for direct memory access.

> Does anyone have more documentation on this test command, or know how to
> use this command to read memory from RAM on the chip for a given offset?

I think that I do, but without permission from CSR I will not share them
or make them public.

Regards

Marcel




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-08-22 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22 14:21 [Bluez-devel] BCCMD Test Command "memory" Joshua Wright
2005-08-22 14:45 ` Marcel Holtmann [this message]

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=1124721945.23599.58.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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.