Jump to content


  1. Important Information

    1. The 68kMLA Forum Rules   (10381 visits to this link)

      To quote vintage Apple manuals: "Read Me First!"

  2. Community Connections

    1. General 68kMLA News & Stuff

      What's going down in the barracks.

    2. Conquests

      Discuss your latest vintage Mac finds!

    3. Trading Post

      Feel free to trade all of your Mac goodies here with all honest intentions. The website provider assumes NO liability, so buyer beware! Please see this topic for more information.

  3. Projects & Hosted Forums

    1. RetroChallenge

      What can you do given only one month and strictly "retro" hardware? Find out with RetroChallenge!

    2. 68kMLA Wiki

      The creation and maintenance of the 68kMLA's information repository.

  4. 68k Model Forums

    1. Compact Mac

      Macintosh, 512k, SE, etc.

    2. Mac II, Quadra & Centris

      Just think, having a Quadra 950 in 1992 would be like having a Mac Pro today… except with more slots, more expandability, and on-board SCSI!

    3. 68k LC & Performa

      Ah, the consumer computers!

    4. 68k PowerBook

      From the Portable to the 190cs.

  5. PowerPC Model Forums

    1. NuBus Power Mac, LC & Performa

      The NuBus architecture gets a new brain!

    2. PCI Power Mac & Performa

      The PPC comes of age and adopts the industry standard expansion slot.

    3. G3/G4/G5 Power Mac, iMac & eMac

      From the Beige G3 to the quad-core G5, via various iMacs!

    4. PPC PowerBook & iBook

      All that power in a laptop? Never…

  6. Everything Else…

    1. Apple I, ][, /// & Lisa

      Not really 68k Macs, but certainly Vintage!

    2. Newton

      The best PDA ever finally gets its own forum!

    3. Software

      Includes system stuff, productivity, emulation, design, and games for pre-OS X Macs!

    4. Hacks & Development

      Yes, it's back! Hardware hacks/modifications and software development for Mac OS.

    5. Peripherals

      Anything you can hook up to your Mac or stuff into it as an interface!

  • Posts

    • I have a Classic AB which, while otherwise fine, suffers from "screen shimmers" every time it reads from the disk. I figured that recapping the AB would fix that, and I've managed to recap everything but the beefiest capacitors – CP1 and CP13, both 220uF/250V capacitors. Unfortunately, it still has the shimmers, and so I figure it's time to get those recapped. They have really large traces. Would anyone have any tips on desoldering those with a minimum of effort/dwell time on each pad? I'm thinking of using my large hoof tip, using as much tacky flux as possible, going over it multiple times by alloying the existing metal trace with leaded solder, going over with solder braid, and repeating... anyone else have any other tips?   Thanks for helping someone who's just learning the ropes out!
    • Maybe, just maybe, since both the +5V and +12V rails are lower than expected, there might be a voltage pot you can adjust on the AB? I don't know what it is off the top off my head.   Strange, but I've also had an uncapped Classic II LB (rev B) that had no sound – don't know what it was, and I guess I won't know for a while since I lifted a few pads while trying to recap it.
    • @rplacd the VIA is the main interface chip, at least in the original 68000 based macs - it's a Rockwell (typically) 6522, or these days, the 65C22N from WDC.
    • Here's what i lifted from the inside macintosh hardware reference books - vol III, it's referencing the Mac 512k/Plus RTC which is only 20 bytes of PRAM, but other than that, the rest of the chip is identical. The 1-sec output doesn't drive a clock, it drives the 65C22's interrupts every second, so not having an exact 1sec output is a no-go. Running the MCU off the external 32.768Khz clock should still be doable, though, it doesn't have to do much 'heavy lifting'. I'm also trying to have a look to see if there's any I2C chips that would work in this config - most seem to have an almost identical pinout, just not more than 64 bytes of EEPROM for PRAM for almsot all of them.   The Macintosh real-time clock is a custom chip whose interface lines are available through the VIA. The clock contains a four-byte counter that's incremented once each second, as well as a line that can be used by the VIA to generate an interrupt once each second. It also contains 20 bytes of RAM that are powered by a battery when the Macintosh is turned off. These RAM bytes, called parameter RAM, contain important data that needs to be preserved even when the system power is not available. The Operating System maintains a copy of parameter RAM that you can access in low memory. To find out how to use the values in parameter RAM, see chapter 13 of Volume Il. Accessing the Clock Chip The clock is accessed through the following bits of VIA data register B (vBase+vBufB): rTCData .EQU 0 ;real-time clock serial data line rTCClk .EQU 1 ;real-ti.me clock data-clock line rTCEnb .EQU 2 ;real-time clock serial enable These three bits constitute a simple serial interface. The rTCData bit is a bidirectional serial data line used to send command and data bytes back and forth. The rTCClk bit is a data-clock line, always driven by the processor (you set it high or low yourself) that regulates the transmission of the data and command bits. The rTCEnb bit is the serial enable line, which signals the real-time clock that the processor is about to send it serial commands and data. To access the clock chip, you must first enable its serial function. To do this, set the serial enable line (rTCEnb) to 0. Keep the serial enable line ~ow during the entire transaction; if you set it to 1, you'll abort the transfer. Warning: Be sure you don't alter any of bits 3-7 of VIA data register B during clock serial access. A command can be either a write request or a read request. After the eight bits of a write request, the clock will expect the next eight bits across the serial data line to be your data for storage into one of the internal registers of the clock. After receiving the eight bits of a read request, the clock will respond by putting eight bits of its data on the serial data line. Commands and data are transferred serially in eight-bit groups over the serial data line, with the high-order bit first and the low-order bit last. To send a command to the clock, first set the rTCData bit of VIA data direction register B (vBase+vDirB) so that the real-time clock's serial data line will be used for output to the clock. Next, set the rTCClk bit of vBase+vBufB to 0, then set the rTCData bit to the value of the first (high-order) bit of your data byte. Then raise (set to 1) the data-clock bit (rTCClk). Then lower the data-clock, set the serial data line to the next bit, and raise the data-clock line again. After the last bit of your command has been sent in this way, you can either continue by sending your data byte in the same way (if your command was a write request) or switch to receiving a data byte from the clock (if your command was a read request). To receive a byte of data from the clock, you must first send a command that's a read request. After you've clocked out the last bit of the command, clear the rTCData bit of the data direction register so that the real-time clock's serial data line can be used for input from the clock; then lower the data-clock bit (rTCClk) and read the first (high-order) bit of the clock's data byte on the serial data line. Then raise the data-clock, lower it again, and read the next bit of data. Continue this until all eight bits are read, then raise the serial enable line (rTCEnb }, disabling the data transfer. The following table lists the commands you can send to the clock. A 1 in the high-order bit makes your command a read request; a 0 in the high-order bit makes your command a write request. (In this table, "z" is the bit that determines read or write status, and bits marked "a" are bits whose values depend on what parameter RAM byte you want to address.) Command byte Register addressed by the command z000000l Seconds register 0 (lowest-order byte) z0000101 Seconds register 1 z0001001 Seconds register 2 z000l101 Seconds register 3 (highest-order byte) 00110001 Test register (write only) 00110101 Write-protect register (write only) z010aa01 RAM address 100aa ($10-$13) zlaaaaOl RAM address Oaaaa ($00-$0F) Note that the last two bits of a command byte must always be 01. If the high-order bit (bit 7) of the write-protect register is set, this prevents writing into any other register on the clock chip (including parameter RAM). Clearing the bit allows you to change any values in any registers on the chip. Don't try to read from this register; it's a write-only register. The two highest-order bits (bits 7 and 6) of the test register are used as device control bits during testing, and should always be set to 0 during normal operation. Setting them to anything else will interfere with normal clock counting. Like the write-protect register, this is a write-only register; don't try to read from it. All clock data must be sent as full eight-bit bytes, even if only one or two bits are of interest. The rest of the bits may not matter, but you must send them to the clock or the write will be aborted when you raise the serial enable line. It's important to use the proper sequence if you're writing to the clock's seconds registers. If you write to a given seconds register, there's a chance that the clock may increment the data in the next higher-order register during the write, causing unpredictable results. To avoid this possibility, always write to the registers in low-to-high order. Similarly, the clock data may increment during a read of all four time bytes, which could cause invalid data to be read. To avoid this, always read the time twice (or until you get the same value twice). Warning: When you've finished reading from the clock registers, always end by doing a final write such as setting the write-protect bit. Failure to do this may leave the clock in a state that will run down the battery more quickly than necessary. The One-Second Interrupt The clock also generates a VIA interrupt once each second (if this interrupt is enabled). The enable status for this interrupt can be read from or written to bit 0 of the VlA's interrupt enable register (vBase+vIER). When reading the enable register, a 1 bit indicates the interrupt is enabled, and 0 means it's disabled. Writing $01 to the enable register disables the clock's onesecond interrupt (without affecting any other interrupts), while writing $81 enables it again. See chapter 6 of Volume Il for more information about writing your own interrupt handlers. Warning: Be sure when you write to bit 0 of the VIA's interrupt enable register that you don't change any of the other bits.  
    • Seems like I hear a lot about people having a dead Egret chip?