Re: Sandpoint 8240 or 7400

    Dan> Got all of those switches set correctly :-)?

Not sure... VxWorks boots fine, does anything need to change for Linux?

    Dan> Let me clean mine up a little (I'm actually doing 405 at the
    Dan> moment) and put it on a server someplace.  No promises, but
    Dan> it should be better than anything else right now.  The
    Dan> Sandpoint seems to always be one of those "background"
    Dan> projects that can't gain momentum.

That would be great.  Let me know when you get a chance to do that.

    >> ......  And (forgive the naive question) how do I build a
    >> kernel image that I can send to the Sandpoint via the serial
    >> port and start from DINK32?

    Dan> What version of DINK do you have?  I'll send you my little
    Dan> downloader as well if you wish.  The easiest way is I just
    Dan> blow the bits over the JTAG with my Abatron....

Actually I figured this out myself a little bit later and managed to
build my own kernel that hung in the same place.

    Dan> It's getting closer, but this Sandpoint stuff still isn't
    Dan> there.

Out of curiousity, what is different about the Sandpoint that requires
changes in the kernel?

Thanks,
Roland

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

Roland Dreier wrote:

That would be great.  Let me know when you get a chance to do that.

I worked on it about 40 hours this past weekend, still no go.  The
problem for me still continues to be interrupt routing on this board.
The 8240 or 107 have the EPIC, which is like OpenPIC but not really.
This is further complicated by the 8259 cascade, which the OpenPIC
code assumes is configured a particular way, but doesn't work on
Sandpoint.  It is just a problem of using standard functions and
making the interrupts line up correctly.  Pain in the ass.  The whole
Linux interrupt management is just plain stupid (there is more to
the world than PCs with hardcoded 8259s).

Out of curiousity, what is different about the Sandpoint that requires
changes in the kernel?

Ummm, like it is a different board than anything else supported?  We
can use lots of the same code, you just may have to call functions
with slightly different parameters for set up.

I discovered the newer versions of DINK (I'm using 12.0) don't need
any special download program.  I just use 'cu', set the baud rate
to 38400, and just 'cat file_to_download > /dev/cua0'.  The processors
and code are fast enough to just suck it up and write it to memory (I
would hope so, too :-).


	-- Dan

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