linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pohland <pohland@snom.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MPC8BUG crashes on Windows 95/98/NT
Date: Wed, 27 Oct 1999 16:06:15 +0200	[thread overview]
Message-ID: <381706D7.FF1D8477@snom.de> (raw)



Hi,

I am a PPC newbie, but after checking the FAQ and mailing lists I have 
found a lot of helpful hints but nothing quite addresses my problem.

I am one of the poor sods trying to get a FADS 860T board to work. I
have 
used the cross compiler tools to generate an image of the embedded-2.2.5 
kernel version. 

I had to guess a lot of flags - does someone have a FADS 860T config
file ? 
There seems to be one for everything else ...

I then thought I would just use the MPC8BUG program to program the flash
with
the generated image. 

Is this the correct way of doing this ? Or do I need a Linux tool chain
and
a soldering iron ?

I received my ADI board, read and followed the readme procedure and 
hooked it up to the FADS. But when I try to start the MPC8BUG or
MPC8BUG95 program,
it just crashes under all 3 Windows versions. I have also tried
different IO addresses 
(0x100, 0x200 and 0x300) and used 2 different PCs (133 and 450 Mhz). 

The BIOS of the boards does NOT allow me to set the ISA bus frequency.

The MPC8bug version is 1.6.

Did someone experience also have this problem ?

Or have a viable alternative ?

Any help would be greatly appreciated.

Nicolas Pohland

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-10-27 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 14:06 Nicolas Pohland [this message]
1999-10-27 15:46 ` MPC8BUG crashes on Windows 95/98/NT Dan Malek
1999-10-28 17:15   ` Nicolas Pohland
1999-10-28 17:39     ` Dan Malek

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=381706D7.FF1D8477@snom.de \
    --to=pohland@snom.de \
    --cc=linuxppc-embedded@lists.linuxppc.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).