From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] BDI2000 and MPC8260
Date: Tue, 06 Sep 2005 15:48:57 -0400 [thread overview]
Message-ID: <431DF2A9.6020301@smiths-aerospace.com> (raw)
In-Reply-To: <20050906193648.9B859352B3A@atlas.denx.de>
Wolfgang Denk wrote:
> In message <431DB954.9030803@smiths-aerospace.com> you wrote:
>
>>* Freescale seems to have stopped providing unfettered access to the
>>BSDL (Boundary Scan Description Language) interface to their processors.
>> For instance, the MPC8260 is not in the list:
>><http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=0162468rH3bTdGZj9NtRjM>
>
> We were never able to pass their NDA roadblocks when we asked for the
> necessary information to extend the BDM4GDB adapter for 82xx... :-(
Slightly different question, different answer ;-). The BSDL is
describing the processor I/O ring shift register, allowing the JTAG to
wiggle pins. What you are referring to is the COP (?) debugger
interface which is also accessed via JTAG but is proprietary. The BSDL
_is_ available as Rune pointed out. This allows you to program memory
(very slowly) by shifting an {address, data, chip select}, toggle the
write line, repeat ad nausium.
Note that you have to be careful with wiggling pins via JTAG: if you
inadvertantly set two pins that are connected together to be "output"
and set them to fighting, one of them will lose (generally the
processor). I would never do that, but know someone who did ;-).
[snip]
> Best regards,
> Wolfgang Denk
Thanks,
gvb
next prev parent reply other threads:[~2005-09-06 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 16:44 [U-Boot-Users] BDI2000 and MPC8260 Rune Torgersen
2005-09-06 15:44 ` Jerry Van Baren
2005-09-06 18:05 ` Dan Malek
2005-09-06 19:36 ` Wolfgang Denk
2005-09-06 19:48 ` Jerry Van Baren [this message]
2005-09-06 19:52 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-09-01 19:18 Rune Torgersen
2005-09-01 10:43 Alex Zeffertt
2005-09-01 17:42 ` Dan Malek
2005-09-01 18:43 ` Pantelis Antoniou
2005-09-01 10:12 Alex Zeffertt
2005-09-01 15:50 ` Wolfgang Denk
2005-09-01 15:56 ` Alex Zeffertt
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=431DF2A9.6020301@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=u-boot@lists.denx.de \
/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.