Woolly would be a device that services memory in the low address range and
responds to new I/O addresses, and would have an onboard 8MB flash chip. As
such, serving OptROM images is one of the planned services. If I can make the
protocol look like REX, then no new 8085 software would be needed.
The FPGA / CPLD is used to decode the 8085 bus signals to determine write
operations to the OptROM socket. This is needed to perform SRAM replacement in
that address region and be able to write to that SRAM. Also it decodes new I/O
port numbers to provide WiFi, disk and REX operations.
With a large enough FPGA, you could do other things, such as add a floating
point coprocessor, etc. However larger = more expensive and shorter battery
It is hard to guess price right now ... it depends on too many factors.
Developing a PCB has both one time setup charges as well as per board charges.
The one time charges have to be amortized over the number of boards expected to
sell. A $5k setup fee spread over 200 units would add $25 to the raw board
Sent from my iPhone
> On Aug 5, 2017, at 2:30 PM, Jim Williams <hira...@hotmail.com> wrote:
> Pardon my ignorance, but I'm *very* interested in the Woolly... internal
> wifi, on-board storage, this is something I've really wanted for my
> M100. A faster screen refresh is the only other thing (cause my focus is
> always on games & graphics... never grew up I guess).
> Will the Woolly also have the capability of storing ROMs like the Rex
> does? I was anxiously waiting for the Rex 5 (4?) for the addition of
> on-board storage, and I'd hate to have to give up being able to load,
> say, the Ultimate ROM II.
> I also don't understand the benefits of the FPGA. I'm not criticizing
> it; I know it's a Field Programmable Gate Array, and I know it's been
> used to make "virtual" C64s and Amiga 500s, but could someone tell me
> the implications of having the FPGA? What could be done with it in the
> context of the Model T? Again, this is ignorance, not criticism.
> Could someone use it to create a sort-of memory management unit? Or is
> that what it's already for?
> Semi-off topic, but the memory management thing made me remember: could
> a program implement a jump table storing the offsets from the
> start-of-program to the various routines and data, and then calculate
> the jumps/branches based on the start-of-program, wherever the program
> was loaded? Would this allow for relocatable code? (I think I've asked
> this before, but I can't remember...)
> One last question... how much is the Woolly likely to cost, roughly? I'm
> only asking so I know how much to tighten my belt to start saving up for
> one. If I have to choose between a Nadsbox and a Rex 5, or the Woolly...
> I vote Woolly...