[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New firmware for PseudoDisk / some problems



Alex Freed <alexf@mirrow.com> wrote:

> "David Empson" <dempson@actrix.gen.nz> wrote in message
> 1hpa9lw.1cq1hqgxzilwN%dempson@actrix.gen.nz">news:1hpa9lw.1cq1hqgxzilwN%dempson@actrix.gen.nz...
> >
> > Do you mean auto starting with your card as the "disk controller" in the
> > highest slot (Ctrl-Apple-Reset on a //e or later)?
> yes
> >
> > Perhaps you are trying to call something which is not initialized after
> > a cold boot.
> 
> For the record it appears that the "cout" at $FDED is not initialized,
> but the pure Apple 40 col screen routines work fine. Including "cout1" at
> $FDF0

Right. That means that something needs to call one of the I/O vector
init routines (there is one for input and one for output) - basically
calling the PR#0 and IN#0 handlers directly. The addresses $FE89 and
$FE93 ring a bell. (Confirmed - that memory of mine frightens me again:
SETKBD and SETVID, respectively.)

Text output window etc. is probably OK if COUT1 is working.

> > I might at least be able to contribute to the project on the
> > software/firmware side of things - I've developed firmware for Apple II
> 
> If you develop improved firmware, I'll give you a free card.
> The only thing is that the bulk of the code is written for the AVR uC rather
> than 6502.

Shouldn't be a problem. I've done assembly programming for at least five
processor families: 6502, Z80, 6301 (6800 superset), ST9, M32C/80, plus
I've had a passing acquaintance with the 6809, 68000, 8080, 8086, 8051,
AVR and MSP430 (and maybe others that I've forgotten about). Mostly
doing C these days, but some assembly is still required.

Haven't done much with the AVR but we have some development tools at
work as we have used it in a few products (2313, 4414, 8515, but not the
AtMEGA). We didn't like it, and started using the TI MSP430 family more
recently, with a side trip back to the 8051 for simple products.

I also have access to EPROM programmers and similar tools. I even have
my IIgs set up at work, and can dig out a IIe if necessary. Nothing
older available (and I don't want more old computers).

> > [IOSTROBE, $CFFF]
> 
> The CPLD has enough logic to handle all that but not all the signals needed
> are wired on the current board. In particular only 9 address lines are
> connected to the PROM. A few wires will be needed.

I'm sure I can hack it in, but that complicates things a bit if I wanted
to develop SmartPort and other people also wanted to use it.

The main benefit of a SmartPort driver would be supporting more than two
volumes per slot in ProDOS-8 (four in slot 5 with ProDOS-8 1.2 or
later). With a Smartport driver in the firmware, ProDOS-8 2.0.1 or later
can access up to about 12 volumes if there are no other disk controller
cards.

GS/OS can also use it to access even more volumes, and volumes larger
than 32 MB (using HFS rather than ProDOS).

-- 
David Empson
dempson@actrix.gen.nz