ROM interface
The Macintosh PowerBook 100 uses the same ROM as the Macintosh
Portable. The Macintosh PowerBook 100 is shipped with 256 KB of
ROM permanently soldered to the main logic board. The Macintosh
PowerBook 100 will accommodate a maximum of 4 MB of ROM on
the main logic board, but it does not include a provision for internal
or external ROM expansion. The ROM is arranged as a 128K x 16-bit
array consisting physically of two 28-pin 128K x 8-bit devices with an
access and cycle time of 150 ns.
THX, I'm having a blast! [] I've got that beat up PartsBook 100 with the bullet riddled (two rounds) screen that I'd swap for some Portable resurrection work if you wanna play along in this insane thread. []I love this thread.But....
1. I am more of a portable guy.
2. I wish I had a PB100, but finding one in decent condition with a decent LCD is way out of my budget so...
I will follow and help where I can, but thats limited.
Chapter 1 Macintosh PowerBook 100 Hardware
Note:
If you design your RAM expansion card correctly, it will also work in future Macintosh-family, 68030-based portable computers. A 68030-based machine has a 32-bit data bus, whereas the 68HC000 in the Macintosh PowerBook 100 has only a 16-bit data bus. You should design the expansion card as a 32-bit device, but if you correctly partition the data lines and chip select lines on the card, you can use the same card in either type of machine without loss of performance. The card should have 32 data lines coming out to its connector, and the chip select lines for the upper 16 data bits and the lower 16 data bits should be separated to allow for individual selection of either the upper 16 bits or the lower 16 bits of data. The separated chip select lines are necessary for the Macintosh PowerBook 100 because it can get access to only 16 bits at a time. A 68030-based machine does not require separated chip select lines because it has a 32-bit data bus; therefore, the lines are tied back together on the computer’s main logic board.
Elaborating on that decoding method would be most helpful. Avoiding memory controller portion of the CPU Glu ASIC's complications and doing all memory ops directly off the 68030's internal bus would almost be too good to be true.Good thing is, the RAM could be connected to the 030, and used in 030 style decoding. Dont need the UDS/LDS 16-bit switching as needed on the standard bus, so it would be wired behind that logic.
I'm VERY curious about how the Compact Mac accelerators address SIMMs on board? Can anyone clue me in on that?
Yep, that's why I was wondering early on if the Luggable and PB100 would be compatible with Compact Virtual, given the extra memory to play with. []The accelerators usually used the on-board ram as a virtual memory/disk routed via the MMU.
That's exactly why I was elated to see you interested in this project. Thanks, I'd skimmed the docs on the two ASICS. I misinterpreted the verbiage and missed the thin lines connecting the entire memory subsystem to Misc.GLU:Trash: I know the portable inside and out. Not the backlit, but the non-backlit. the MISC GLU does the bank switching/decoding for the on-board RAM.
Studying the saga of your MemCard's development is definitely on my reading list. []My portable, I removed the buffer ICs and changed the CPLD code on my RAM card and actually "took over" the 1MB of onboard RAM. That knocked me down to 8MB, but it ran faster as the on board-RAM is slower than what I used in my RAM card.