linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan <nathana@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Defunct Abatron / BDI2000?
Date: Fri, 1 Nov 2019 17:40:05 -0700	[thread overview]
Message-ID: <CABVqaQbcgQ2=1Se0RvVTmK7MUasRy5iB_dF2ah8Syfk_6woPUA@mail.gmail.com> (raw)

I am profusely sorry for adding noise to this list with this semi-OT
post, but I'm becoming increasingly desperate, and I suspect the odds
of running into someone with one of these units here are pretty good.

If there is anyone here who has a BDI2K with the QorIQ P-series
(P3/4/5) target firmware, and wouldn't mind reaching out to me
(off-list is fine, and probably the most polite to everyone else), I
would really, really, really appreciate it.

I'm no embedded systems engineer, but I've got one of these JTAG pods
on loan as I managed to brick a commercial board based on P3041 SoC
and I'm trying to find a way to reflash non-corrupted code to the
on-board parallel NOR.  The board has a confirmed 16-pin COP header on
it, but of course the BDI unit I have access to has MPC85xx target
firmware installed on it.

From what I can tell, not only is this a pretty old debugger model
anyway (and not the most recent one that its manufacturer produced),
but the company who manufactured it (Abatron) appears to have
shuttered their doors over a year ago...the web site is gone and
they've abandoned their domain name, so I have no way of reaching out
to any of the people involved in this product.

Short of making this unit talk to this board, from what I can tell my
only remaining options are to pay hundreds or thousands of $ for some
other JTAG interface that is still actively manufactured and supported
(which I can't justify doing in order to fix this *one* board *one*
time), or to find somebody who can desolder the flash chip so that I
can reflash it with an offline programmer (which I'd really prefer to
avoid).

Thanks so much,

-- Nathan

                 reply	other threads:[~2019-11-02  0:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CABVqaQbcgQ2=1Se0RvVTmK7MUasRy5iB_dF2ah8Syfk_6woPUA@mail.gmail.com' \
    --to=nathana@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).