Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Adam Nielsen <a.nielsen@optushome.com.au>
To: linux-mips@linux-mips.org
Subject: Re: Running Linux on an NCD HMX X-Terminal
Date: Sun, 11 Jan 2004 12:04:23 +1000	[thread overview]
Message-ID: <200401111204.23752@korath> (raw)
In-Reply-To: <200401101240.i0ACePX01584@mwave.heeltoe.com>

> I brought up linux on the PPC403 version of an NCD x-terminal.  As I recall
> I had to write program to hack the elf header to get kernels to load.
> The project is at http://sourceforge.net/projects/explora-linux/

Hmm...this looks interesting!

> You may get lucky and find they used the same format for MIPS...

Well I am hopeful, given that they use the same manual for the HMX and the 
Explora, but running ncdhack on the kernel didn't seem to have any effect :-(

I did try some fiddling with the ELF files, just to see what would happen (but 
not having any experience with this, I was just guessing ;-))  The load 
address for the proper boot image is 0x40020000 but the kernel is 0x88002000 
which I think is partly why it doesn't work.  If I shrink the ELF file a 
little by removing a couple of the sections (by telling objcopy to ignore 
them) *and* I change the load address to 0x40020000 then the xterm actually 
downloads the image but then gives a "File corrupted CRC error" just as it 
goes to boot it.

I'm not sure why that happens, because manipulating the file properly with 
objcopy should adjust any CRC checksums accordingly.  I wonder whether the 
xterm is checking that the image is 'official'?

Cheers,
Adam.

      reply	other threads:[~2004-01-11  2:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  5:05 Running Linux on an NCD HMX X-Terminal Adam Nielsen
2004-01-10 12:40 ` Brad Parker
2004-01-11  2:04   ` Adam Nielsen [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=200401111204.23752@korath \
    --to=a.nielsen@optushome.com.au \
    --cc=linux-mips@linux-mips.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