IMac G3 computers still refusing to power up? Here is a solution.

This post is the sequel to the discussion "iMac G3 computers still refusing to power up? Here is what I've found out!", accessible under this link http://discussions.apple.com/thread.jspa?threadID=2326420&tstart=0 .
I made it! I have fixed the issue of the iMac DV refusing to power up.
For this, I had to design and build a prototype of a cost-effective nonresident hardware patch, which I am about to describe in this article. I will also give the instructions of use. Subsequently, I will expose the rationale, which led to the background of the design. Finally, I will report the observations after the experiment with the patch and sketch the theory of its actual operation with the PMU firmware.
*TABLE OF CONTENTS*
1. Applicability condition and restriction
2. Description of the PMU hardware patch
3. Interconnections of the PMU microcontroller with the PMU Hardware Patch
4. Instructions to read before mounting and unmounting the PMU Hardware Patch on the iMac
5. Background to the design of the PMU Hardware Patch
5.1. The genesis
5.2. What the PMU Hardware Patch actually does
6. Recommended updates before using the PMU Hardware Patch
7. User's Manual of the PMU microcontroller
8. Datasheets of the 74HC4049 Hex inverting high-to-low level shifter
9. Datasheets of the 74HC193 Presettable synchronous 4-bit binary up/down counter
10. Errata to the discussion start of February 6th, 2010
h1. 1. Applicability condition and restriction
The hardware patch addresses the issue of a slot-loading iMac, which can be powered up only within two seconds after resetting the PMU microcontroller. It is not required otherwise.
Moreover, it does not need to reside in the iMac, but suffices once to permanently cure the power-management firmware.
h1. 2. Description of the PMU hardware patch
As seen on figures 1 and 2, the PMU hardware patch relies on a low part count: two logic ICs (74HC193 and 74HC4049), two 0805-packaged resistors and two 1206-packaged capacitors, which all fit on a 31mm x 45mm single-sided SMD prototyping board. The circuit consumes a current intensity of about 7.5 milliamps for a supply voltage of 3.3 volts.
The PMU hardware patch functions as a frequency divider of the PMU sub-clock generator output, XCOUT. It applies an active low pulse to the PMU NMI_bar non-maskable input, once every sixteen XCOUT rising edge for half a period. It is disabled when the PMU main clock generator output, XOUT, returns to 0 by oscillations, or when the system is being reset with the PMU RESET_bar input asserted to 0. The peak-to-peak 1.5-Volt oscillations of XCOUT are fed through the 1-nanofarad DC-blocking capacitor to the inverter biased in the linear region by a feedback resistor of twice 270 kilo-ohms, for translation to 3.3V-compatible logic levels.
The power-supply bypass capacitor amounts to 100 nanofarads.
*Figure 1: Schematics of the PMU Hardware Patch*
[Figure 1|http://www.flickr.com/photos/aegidius_2/4923600713/in/photostream/|Click to view in a new tab.]
Note the 0.5mm-diameter insulated copper wires in ochre color on the prototype board (figure 2).
*Figure 2: Picture of the PMU Hardware Patch prototype - component side*
[Figure 2|http://www.flickr.com/photos/aegidius_2/4924196064/in/photostream/|Click to view in a new tab.]
The 10cm-long interface wires can be clamped to the board with cylinder blocks made of epoxy glue (Araldite), as seen on figure 3.
*Figure 3: Picture of the PMU Hardware Patch prototype - interface side*
[Figure 3|http://www.flickr.com/photos/aegidius_2/4924196296/in/photostream/|Click to view in a new tab.]
h1. 3. Interconnections of the PMU microcontroller with the PMU Hardware Patch
The PMU Hardware Patch uses the signals RESET_bar, NMI_bar and the clocks XOUT and XCOUT of the PMU microcontroller, U34 on the Logic Board underside. Both are supplied by the voltage available across the tantalum capacitor C131.
Pin 73 of U34 performs the function INT3_bar because it turns out to be permanently configured as an edge-sensitive interrupt input, once the PMU Hardware Patch has been used. This will be justified in section 5.2. When the computer is plugged to the mains, a pressure on any power button can induce a falling edge on pin 73. U34 responds by asserting pin 75 to logic 0, as long as the computer has to remain powered on from the PAV board.
Pin 10 of U34 is the active low reset input, RESET_bar. It toggles from logic 0 to 1, a few hundred milliseconds after U35 has detected the supply voltage across the capacitor C131 has settled above 2.2 volts, either because a good battery has been inserted in the holder, or else because the computer has been plugged to the mains and the trickle power from the PAV board, T5V, is available. It is also asserted to logic 0, as long as the PMU reset button is depressed.
Pin 9 of U34 is the sub-clock output, XCOUT. The PMU microcontroller selects it for its operation in low-power dissipation mode to carry on the timekeeping, normally as soon as the computer is being shut down. The microcontroller shall then draw no more than 40 microamps typically from the battery.
Pin 11 of U34 is the main clock output, XOUT. It is the default clock of the PMU microcontroller after the reset phase. The microcontroler selects it for its operation in high-speed mode, when the computer is powered on.
Pin 15 of U34 is the active low edge-sensitive non-maskable interrupt, NMI_bar. It is normally unused and its voltage remains pulled up to the microcontroller supply through resistor R124. However, it happens to help resolve the power-up issue when it is controlled by the PMU Hardware Patch. The justifications are exposed in section 5.2.
Figure 4 shows an easier access to the clock and control signal pins of U34, to be connected to the PMU Hardware Patch, from the top of the Logic Board. You will have to solder the PMU Hardware Patch interface wires at the locations pointed to.
*Figure 4: View of the access to the PMU U34 chip signals for the PMU Hardware Patch*
[Figure 4|http://www.flickr.com/photos/aegidius_2/4929783304/in/photostream/|Click to view in a new tab.]
h1. 4. Instructions to read before mounting and unmounting the PMU Hardware Patch on the iMac
All possible updates accessible from the links in section 6 shall be installed. Then remove the battery. All this ensures your iMac will be prepared to interact with the PMU Hardware Patch under the same initial conditions as in the experiment I have carried out.
Afterwards, remove the bottom housing, the metal shield, the SDRAM, the IDE cable and disconnect the hard-drive power cable. Take off the Logic Board together with the Down Converter board and the modem and place it on your workbench. Now carefully solder the PMU Hardware Patch interface wires at the locations pointed to in figure 4. Figure 5 illustrates the result.
Install the boards back in the iMac, reconnect the hard-drive power cable and the IDE cable, and re-insert the SDRAM in its original slot. Put the computer on a large flat and safe area near a power socket. Stand up the PMU Hardware Patch on a plastic pouch, to insulate it for the parts of the Logic Board, as seen in figure 6. Connect the keyboard and the mouse.
Once you have plugged the computer back to the mains, don't take the risk to touch the computer except the keyboard and the mouse, because quite a few visible metal parts are live and lethal by body contact!
Wait for twenty seconds and then unplug the computer from the mains. Wait for a minute. Again, supply the mains to the computer and wait for twenty seconds, before you press the power button on the keyboard. Then let the operating system load until you can see the menu bar. Maybe a window will pop up to warn you that the system date is too ancient, but you can skip it. Now shut down the computer by selecting the command in the Special menu. I know it is awkward to move the mouse pointer when the picture is upside down. But take it easy!
Unplug the computer from the mains and unmount the PMU Hardware Patch. Once you have re-assembled your iMac, you can power it up and use it without the constraint to reset the PMU each time before and then to press on a power button in a hurry within two seconds.
A good tip: get all this task cleanly done by a professional, like a repairman or an electronics technician, if you feel you don't have enough skill in soldering!
*Figure 5: View of the Patch-PMU interconnections*
[Figure 5|http://www.flickr.com/photos/aegidius_2/4929190683/in/photostream/|Click to view in a new tab.]
*Figure 6: View of the mounted PMU Hardware Patch*
[Figure 6|http://www.flickr.com/photos/aegidius_2/4929190963/in/photostream/|Click to view in a new tab.]
h1. 5. Background to the design of the PMU Hardware Patch
h2. 5.1. The genesis
My idea to the design of the PMU Hardware Patch started with the study of the user's manual of the PMU microcontroller and with my observations on the clocks XOUT and XCOUT.
The symptom of the power-up default was accompanied by the disappearance of the clocks XOUT and XCOUT, if no power button was depressed within two seconds after pushing on the PMU reset button. I concluded, it was the reason why the PMU microcontroller could no longer react to a power button signal on pin 73 (P15/D13/INT3) and perform any timekeeping until the next PMU reset.
By looking at the block diagram Figure 1.10.3 (Clock generating circuit) of the microcontroller user's manual, I noticed that any clock oscillator, XOUT and XOUT, can be re-enabled after the CM10 bit has pulsed to logic 1, provided that the SR latch is reset by the NMI_bar non-maskable interrupt line or by the RESET_bar input. If bit CM04 was set to logic 1, then XCOUT resumes the clock oscillations, and likewise for XOUT if bit CM05 was set to logic 1.
I assumed the situation CM04 = 1 and CM05 = 0, as the PMU microcontroller enters the STOP mode. My idea was then to let it avoid the STOP mode and continue operating in the low-power dissipation mode, by periodically refreshing the SR latch reset through a low pulse on the NMI_bar input. Since the 32.768-kHz oscillations on XCOUT fade within a few hundred microseconds, repeating the pulse on NMI_bar at a quicker rate, once every 488 microseconds (i.e. once every sixteen XCOUT clock period) is acceptable.
However, I could not foresee how the non-maskable interrupt routine would interfere with the PMU firmware, whenever the NMI_bar pulse would be acknowledged to let the microcontroller program counter branch to it. I know that events on edge-sensitive interrupt lines are normally latched, which allows the microcontroller state machine to detect them even if they are too short compared to the clock period. And yet, I assumed it differently, after reading this excerpt in the microcontroller user's manual in the section "Precautions for Interrupts": "Signals input to the NMI pin require an “L” level of 1 clock or more, from the operation clock of the CPU". I decided to design and build a PMU Hardware Patch, that would generate a pulse on NMI_bar for a duration of less one XCOUT clock period, actually for half of it. If it is synchronised with the appropriate edge of XCOUT, then maybe the pulse would not cause the branch to the NMI routine. Moreover, when both XOUT and XCOUT are running, the duration of the pulse from the PMU Hardware Patch would exceed the period of the XOUT clock. To avoid the risk that the pulse occurs for more than one period of XOUT, as the operation clock of the microcontroller, I designed the PMU Hardware Patch, so that it remains inactive as long as XOUT is not steadily asserted to logic 1. The PMU Hardware Patch will not either generate any low pulse during the reset phase, as long as RESET_bar is asserted to 0, and as required in the microcontroller user's manual.
Once the PMU Hardware Patch assembled, I took the risk to use it in the iMac DV. What a relief it was, whenever I turned on the computer again, without the need to press the PMU reset button each time. The PMU Hardware Patch works!
After a power cycling of one minute, without unplugging the iMac from the mains, I looked at the time and date I had initially set. The time had not advanced correctly, while the computer was turned off. Instead it was lagging: it recovered with the value I had initially entered, plus about one minute that the operating system takes to load. That means that no clock was running again, while the computer was turned off. Nonetheless I unmounted the PMU Hardware Patch and tried power cycling the computer at any time interval. Powering it on always succeeded without the need anymore to reset the PMU microcontroller before each attempt.
h2. 5.2. What the PMU Hardware Patch actually does
This means the PMU Hardware Patch had definitely interfered with the PMU firmware and cured it with respect to the power-up issue once and for all. I have figured out it interrupts the firmware through the NMI routine, which restores a few data in the non-volatile FLASH memory. These data are used to program the interrupt control register INT3IC, so that pin 73 behaves as the edge sensitive interrupt INT3_bar. This eliminates the need to have any clock running to register a request on pin 73 to power up the computer. Furthermore, when INT3_bar senses a low pulse because a power button is being pushed on, it urges the internal signal "Interrupt request level judgment" to reset the SR latch register, which re-enables any clock oscillator, as seen in figures 1.11.9 (Maskable interrupts priorities (peripheral I/O interrupts)) and 1.10.3 (Clock generating circuit). The PMU microcontroller can resume its operations and look for the source of the interruption. It finds out it has to power up the iMac, because INT3_bar had been latched in as active.
h1. 6. Recommended updates before using the PMU Hardware Patch
+Mac OS 9: Available Updates+
http://support.apple.com/kb/HT1387
+Power PC-based iMac: When to install available updates+
http://support.apple.com/kb/HT2560?viewlocale=enUS&locale=enUS
+iMac: How to Install an iMac Firmware Update+
http://support.apple.com/kb/HT2561
h1. 7. User's Manual of the PMU microcontroller
http://documentation.renesas.com/eng/products/mpumcu/62aeum.pdf
h1. 8. Datasheets of the 74HC4049 Hex inverting high-to-low level shifter
http://www.nxp.com/documents/datasheet/74HC4049CNV.pdf
http://www.st.com/stonline/products/literature/ds/1965/m74hc4049.pdf
http://www.ti.com/lit/gpn/cd74hc4049
http://www.fairchildsemi.com/ds/MM/MM74HC4049.pdf
h1. 9. Datasheets of the 74HC193 Presettable synchronous 4-bit binary up/down counter
http://www.nxp.com/documents/datasheet/74HCHCT193.pdf
http://www.ti.com/lit/gpn/cd74hc193
h1. 10. Errata to the discussion start of February 6th, 2010
1. "PRAM battery": Wrong naming! The Logic-Board battery only serves to support the timekeeping operation when the mains is removed from the computer, whereas the PRAM data are stored in the non-volatile FLASH memory of the PMU microcontroller (in slot-loading iMacs).
2. "(...) sets bit 1 of the CM1 register (system clock control register 1) to 1 (...)". This fragment shall rather read: "(...) sets bit 0 of the CM1 register (system clock control register 1) to 1 (...)".
Aegidius_2
Keep perseverance and reach your goal!

This post is the sequel to the discussion "iMac G3 computers still refusing to power up? Here is what I've found out!", accessible under this link http://discussions.apple.com/thread.jspa?threadID=2326420&tstart=0 .
I made it! I have fixed the issue of the iMac DV refusing to power up.
For this, I had to design and build a prototype of a cost-effective nonresident hardware patch, which I am about to describe in this article. I will also give the instructions of use. Subsequently, I will expose the rationale, which led to the background of the design. Finally, I will report the observations after the experiment with the patch and sketch the theory of its actual operation with the PMU firmware.
*TABLE OF CONTENTS*
1. Applicability condition and restriction
2. Description of the PMU hardware patch
3. Interconnections of the PMU microcontroller with the PMU Hardware Patch
4. Instructions to read before mounting and unmounting the PMU Hardware Patch on the iMac
5. Background to the design of the PMU Hardware Patch
5.1. The genesis
5.2. What the PMU Hardware Patch actually does
6. Recommended updates before using the PMU Hardware Patch
7. User's Manual of the PMU microcontroller
8. Datasheets of the 74HC4049 Hex inverting high-to-low level shifter
9. Datasheets of the 74HC193 Presettable synchronous 4-bit binary up/down counter
10. Errata to the discussion start of February 6th, 2010
h1. 1. Applicability condition and restriction
The hardware patch addresses the issue of a slot-loading iMac, which can be powered up only within two seconds after resetting the PMU microcontroller. It is not required otherwise.
Moreover, it does not need to reside in the iMac, but suffices once to permanently cure the power-management firmware.
h1. 2. Description of the PMU hardware patch
As seen on figures 1 and 2, the PMU hardware patch relies on a low part count: two logic ICs (74HC193 and 74HC4049), two 0805-packaged resistors and two 1206-packaged capacitors, which all fit on a 31mm x 45mm single-sided SMD prototyping board. The circuit consumes a current intensity of about 7.5 milliamps for a supply voltage of 3.3 volts.
The PMU hardware patch functions as a frequency divider of the PMU sub-clock generator output, XCOUT. It applies an active low pulse to the PMU NMI_bar non-maskable input, once every sixteen XCOUT rising edge for half a period. It is disabled when the PMU main clock generator output, XOUT, returns to 0 by oscillations, or when the system is being reset with the PMU RESET_bar input asserted to 0. The peak-to-peak 1.5-Volt oscillations of XCOUT are fed through the 1-nanofarad DC-blocking capacitor to the inverter biased in the linear region by a feedback resistor of twice 270 kilo-ohms, for translation to 3.3V-compatible logic levels.
The power-supply bypass capacitor amounts to 100 nanofarads.
*Figure 1: Schematics of the PMU Hardware Patch*
[Figure 1|http://www.flickr.com/photos/aegidius_2/4923600713/in/photostream/|Click to view in a new tab.]
Note the 0.5mm-diameter insulated copper wires in ochre color on the prototype board (figure 2).
*Figure 2: Picture of the PMU Hardware Patch prototype - component side*
[Figure 2|http://www.flickr.com/photos/aegidius_2/4924196064/in/photostream/|Click to view in a new tab.]
The 10cm-long interface wires can be clamped to the board with cylinder blocks made of epoxy glue (Araldite), as seen on figure 3.
*Figure 3: Picture of the PMU Hardware Patch prototype - interface side*
[Figure 3|http://www.flickr.com/photos/aegidius_2/4924196296/in/photostream/|Click to view in a new tab.]
h1. 3. Interconnections of the PMU microcontroller with the PMU Hardware Patch
The PMU Hardware Patch uses the signals RESET_bar, NMI_bar and the clocks XOUT and XCOUT of the PMU microcontroller, U34 on the Logic Board underside. Both are supplied by the voltage available across the tantalum capacitor C131.
Pin 73 of U34 performs the function INT3_bar because it turns out to be permanently configured as an edge-sensitive interrupt input, once the PMU Hardware Patch has been used. This will be justified in section 5.2. When the computer is plugged to the mains, a pressure on any power button can induce a falling edge on pin 73. U34 responds by asserting pin 75 to logic 0, as long as the computer has to remain powered on from the PAV board.
Pin 10 of U34 is the active low reset input, RESET_bar. It toggles from logic 0 to 1, a few hundred milliseconds after U35 has detected the supply voltage across the capacitor C131 has settled above 2.2 volts, either because a good battery has been inserted in the holder, or else because the computer has been plugged to the mains and the trickle power from the PAV board, T5V, is available. It is also asserted to logic 0, as long as the PMU reset button is depressed.
Pin 9 of U34 is the sub-clock output, XCOUT. The PMU microcontroller selects it for its operation in low-power dissipation mode to carry on the timekeeping, normally as soon as the computer is being shut down. The microcontroller shall then draw no more than 40 microamps typically from the battery.
Pin 11 of U34 is the main clock output, XOUT. It is the default clock of the PMU microcontroller after the reset phase. The microcontroler selects it for its operation in high-speed mode, when the computer is powered on.
Pin 15 of U34 is the active low edge-sensitive non-maskable interrupt, NMI_bar. It is normally unused and its voltage remains pulled up to the microcontroller supply through resistor R124. However, it happens to help resolve the power-up issue when it is controlled by the PMU Hardware Patch. The justifications are exposed in section 5.2.
Figure 4 shows an easier access to the clock and control signal pins of U34, to be connected to the PMU Hardware Patch, from the top of the Logic Board. You will have to solder the PMU Hardware Patch interface wires at the locations pointed to.
*Figure 4: View of the access to the PMU U34 chip signals for the PMU Hardware Patch*
[Figure 4|http://www.flickr.com/photos/aegidius_2/4929783304/in/photostream/|Click to view in a new tab.]
h1. 4. Instructions to read before mounting and unmounting the PMU Hardware Patch on the iMac
All possible updates accessible from the links in section 6 shall be installed. Then remove the battery. All this ensures your iMac will be prepared to interact with the PMU Hardware Patch under the same initial conditions as in the experiment I have carried out.
Afterwards, remove the bottom housing, the metal shield, the SDRAM, the IDE cable and disconnect the hard-drive power cable. Take off the Logic Board together with the Down Converter board and the modem and place it on your workbench. Now carefully solder the PMU Hardware Patch interface wires at the locations pointed to in figure 4. Figure 5 illustrates the result.
Install the boards back in the iMac, reconnect the hard-drive power cable and the IDE cable, and re-insert the SDRAM in its original slot. Put the computer on a large flat and safe area near a power socket. Stand up the PMU Hardware Patch on a plastic pouch, to insulate it for the parts of the Logic Board, as seen in figure 6. Connect the keyboard and the mouse.
Once you have plugged the computer back to the mains, don't take the risk to touch the computer except the keyboard and the mouse, because quite a few visible metal parts are live and lethal by body contact!
Wait for twenty seconds and then unplug the computer from the mains. Wait for a minute. Again, supply the mains to the computer and wait for twenty seconds, before you press the power button on the keyboard. Then let the operating system load until you can see the menu bar. Maybe a window will pop up to warn you that the system date is too ancient, but you can skip it. Now shut down the computer by selecting the command in the Special menu. I know it is awkward to move the mouse pointer when the picture is upside down. But take it easy!
Unplug the computer from the mains and unmount the PMU Hardware Patch. Once you have re-assembled your iMac, you can power it up and use it without the constraint to reset the PMU each time before and then to press on a power button in a hurry within two seconds.
A good tip: get all this task cleanly done by a professional, like a repairman or an electronics technician, if you feel you don't have enough skill in soldering!
*Figure 5: View of the Patch-PMU interconnections*
[Figure 5|http://www.flickr.com/photos/aegidius_2/4929190683/in/photostream/|Click to view in a new tab.]
*Figure 6: View of the mounted PMU Hardware Patch*
[Figure 6|http://www.flickr.com/photos/aegidius_2/4929190963/in/photostream/|Click to view in a new tab.]
h1. 5. Background to the design of the PMU Hardware Patch
h2. 5.1. The genesis
My idea to the design of the PMU Hardware Patch started with the study of the user's manual of the PMU microcontroller and with my observations on the clocks XOUT and XCOUT.
The symptom of the power-up default was accompanied by the disappearance of the clocks XOUT and XCOUT, if no power button was depressed within two seconds after pushing on the PMU reset button. I concluded, it was the reason why the PMU microcontroller could no longer react to a power button signal on pin 73 (P15/D13/INT3) and perform any timekeeping until the next PMU reset.
By looking at the block diagram Figure 1.10.3 (Clock generating circuit) of the microcontroller user's manual, I noticed that any clock oscillator, XOUT and XOUT, can be re-enabled after the CM10 bit has pulsed to logic 1, provided that the SR latch is reset by the NMI_bar non-maskable interrupt line or by the RESET_bar input. If bit CM04 was set to logic 1, then XCOUT resumes the clock oscillations, and likewise for XOUT if bit CM05 was set to logic 1.
I assumed the situation CM04 = 1 and CM05 = 0, as the PMU microcontroller enters the STOP mode. My idea was then to let it avoid the STOP mode and continue operating in the low-power dissipation mode, by periodically refreshing the SR latch reset through a low pulse on the NMI_bar input. Since the 32.768-kHz oscillations on XCOUT fade within a few hundred microseconds, repeating the pulse on NMI_bar at a quicker rate, once every 488 microseconds (i.e. once every sixteen XCOUT clock period) is acceptable.
However, I could not foresee how the non-maskable interrupt routine would interfere with the PMU firmware, whenever the NMI_bar pulse would be acknowledged to let the microcontroller program counter branch to it. I know that events on edge-sensitive interrupt lines are normally latched, which allows the microcontroller state machine to detect them even if they are too short compared to the clock period. And yet, I assumed it differently, after reading this excerpt in the microcontroller user's manual in the section "Precautions for Interrupts": "Signals input to the NMI pin require an “L” level of 1 clock or more, from the operation clock of the CPU". I decided to design and build a PMU Hardware Patch, that would generate a pulse on NMI_bar for a duration of less one XCOUT clock period, actually for half of it. If it is synchronised with the appropriate edge of XCOUT, then maybe the pulse would not cause the branch to the NMI routine. Moreover, when both XOUT and XCOUT are running, the duration of the pulse from the PMU Hardware Patch would exceed the period of the XOUT clock. To avoid the risk that the pulse occurs for more than one period of XOUT, as the operation clock of the microcontroller, I designed the PMU Hardware Patch, so that it remains inactive as long as XOUT is not steadily asserted to logic 1. The PMU Hardware Patch will not either generate any low pulse during the reset phase, as long as RESET_bar is asserted to 0, and as required in the microcontroller user's manual.
Once the PMU Hardware Patch assembled, I took the risk to use it in the iMac DV. What a relief it was, whenever I turned on the computer again, without the need to press the PMU reset button each time. The PMU Hardware Patch works!
After a power cycling of one minute, without unplugging the iMac from the mains, I looked at the time and date I had initially set. The time had not advanced correctly, while the computer was turned off. Instead it was lagging: it recovered with the value I had initially entered, plus about one minute that the operating system takes to load. That means that no clock was running again, while the computer was turned off. Nonetheless I unmounted the PMU Hardware Patch and tried power cycling the computer at any time interval. Powering it on always succeeded without the need anymore to reset the PMU microcontroller before each attempt.
h2. 5.2. What the PMU Hardware Patch actually does
This means the PMU Hardware Patch had definitely interfered with the PMU firmware and cured it with respect to the power-up issue once and for all. I have figured out it interrupts the firmware through the NMI routine, which restores a few data in the non-volatile FLASH memory. These data are used to program the interrupt control register INT3IC, so that pin 73 behaves as the edge sensitive interrupt INT3_bar. This eliminates the need to have any clock running to register a request on pin 73 to power up the computer. Furthermore, when INT3_bar senses a low pulse because a power button is being pushed on, it urges the internal signal "Interrupt request level judgment" to reset the SR latch register, which re-enables any clock oscillator, as seen in figures 1.11.9 (Maskable interrupts priorities (peripheral I/O interrupts)) and 1.10.3 (Clock generating circuit). The PMU microcontroller can resume its operations and look for the source of the interruption. It finds out it has to power up the iMac, because INT3_bar had been latched in as active.
h1. 6. Recommended updates before using the PMU Hardware Patch
+Mac OS 9: Available Updates+
http://support.apple.com/kb/HT1387
+Power PC-based iMac: When to install available updates+
http://support.apple.com/kb/HT2560?viewlocale=enUS&locale=enUS
+iMac: How to Install an iMac Firmware Update+
http://support.apple.com/kb/HT2561
h1. 7. User's Manual of the PMU microcontroller
http://documentation.renesas.com/eng/products/mpumcu/62aeum.pdf
h1. 8. Datasheets of the 74HC4049 Hex inverting high-to-low level shifter
http://www.nxp.com/documents/datasheet/74HC4049CNV.pdf
http://www.st.com/stonline/products/literature/ds/1965/m74hc4049.pdf
http://www.ti.com/lit/gpn/cd74hc4049
http://www.fairchildsemi.com/ds/MM/MM74HC4049.pdf
h1. 9. Datasheets of the 74HC193 Presettable synchronous 4-bit binary up/down counter
http://www.nxp.com/documents/datasheet/74HCHCT193.pdf
http://www.ti.com/lit/gpn/cd74hc193
h1. 10. Errata to the discussion start of February 6th, 2010
1. "PRAM battery": Wrong naming! The Logic-Board battery only serves to support the timekeeping operation when the mains is removed from the computer, whereas the PRAM data are stored in the non-volatile FLASH memory of the PMU microcontroller (in slot-loading iMacs).
2. "(...) sets bit 1 of the CM1 register (system clock control register 1) to 1 (...)". This fragment shall rather read: "(...) sets bit 0 of the CM1 register (system clock control register 1) to 1 (...)".
Aegidius_2
Keep perseverance and reach your goal!

Similar Messages

  • 2008 iMac 8,1 still won't power up after replacing power supply

    A few days ago my iMac powered-ON as usual at 8AM and was working normally, I checked email and left for a meeting. When I returned 30 minutes later my office had a slight odor of hot bakelite and the screen was dark, instead of displaying the screen saver. Thinking the power may have blinked, I pushed the start button on the back and nothing happened, tried several more times, then depressing and holding, still nothing - absolutely lifeless.
    Presumed it was probably the power supply, so took it into the Genius Bar and my suspicion was confirmed; they checked the LEDs and advised that the power supply was mostly bad. Despite the hassle, the solution seemed simple enough: replace the power supply and I'd be back in business. That proved to be wrong!
    Bought a new (NIB) power supply from a reputable dealer and carefully disassembled/reassembled the iMac feeling ever so confident that I'd hear the chime and fan whir when I depressed the ON/OFF Button. To my total disbelief nothing has changed! Its still dark and lifeless as before. Not discounting a theoretical chance that both power supplies could be bad I'm puzzled what to do next and where to look. Obviously, there isn't much in line ahead of the power supply, but given the fact there is no fan noise and no glimmer on the display, I can't fathom it could be anything other than something between the power cord and the power supply.
    What could have caused the hot bakelite smell? The original power supply had NO bakelite odor and no burned chips, traces, scorched transformer windings or cooked capacitors. That had surprised me, so sniffed around the motherboard/backplane and detected a slight bakelite odor at or near the hard drive; I haven't cracked the case yet to examine the HDD - but, even if it were dead, I'd still hear the chime and fan, and maybe see at least a slight glow on the display, right?
    And so, I'm calling on all you "pros from Dover" for some insights, wisdom and pointers to help me diagnose the problem and get the thing fixed. Your thoughts?
    Thanks, much, compadres. AK

    My assumption is the same as KT’s, the logic board fried. If the logic board is functional, even if the hard drive is dead, it should power on and perform the POST. Since it isn’t my advice is the same as KT’s - hope you don’t need Snow Leopard to run some older program(s).

  • TS3274 My ipad still refuses to power off will not let me slide

    The screen says not enough storage
    This ipad cannot be backed up because
    there is not enogh icloud storage available
    you can manage storage in settings
    CLOSE SETTINGS   
    it will not let me press either and also can not poere off

    can anyone help??????

  • Zombie iMac 21.5": refuses to power on for hours

    This has happened twice to my 21.5" iMac (mid-range): After writing to disk for hours, I power down the iMac in the evening via Apple menu, disconnect the cables, carry it to another room, connect the power cable, but the iMac refuses to power on.
    Measures: verified cable connections, electrical power outlet, reset SMC. Result: iMac refuses to power on.
    Solution: disconnect all cables, wait till morning, connect power cable, press power button. Result: No issues, works fine.
    Any idea why this happens? Have you experienced this?

    Hi, just to share I experience the same thing.
    One month ago this happen to me when I power off the socket power (the power to the plug of my iMac 27"). When I power on the socket power and press the power button behind the screen, no respond at all. Tried various method suggested at support site but no improvement. Finally I gave up go to bed and next morning it power up perfectly fine.
    After this I use iMac for a month without power down the main socket it work perfectly fine whenever I power up or power down using the push button behind the screen. Just 15 mins before this post, I came back home, the iMac still cool as it not been turn on. I power off the main socket, remove the power plug, put back the power plug again, turn on the main socket power, press the power button behind the screen, no respond at all. Sign......do I need to wait till next morning then can power up again? Sign............
    What shall I do?
    Do I have to restrict myself do not power down the main socket power so that I can use the iMac as and when I like.
    Shall I send for Servicing?
    Somebody please help.

  • I have an old (first generation) iMac that I still use sometimes for the applications that are on it. I was using it yesterday and unfortunately had a power cut. I went to turn it on today, and nothing at all happens. It's as though no power is getting to

    I have an old (first generation) iMac that I still use sometimes for the applications that are on it. I was using it yesterday and unfortunately had a power cut. I went to turn it on today, and nothing at all happens. It's as though no power is getting to it. I've checked the obvious things, changed the fuse, tried different cables, poked paperclips in reset holes, but nothing doing. I wonder if there is anyone who knows what might be wrong. I was hoping to get some of its content transferred soon, but I'm guessing that can't be done if it can't be started up. Many thanks, if you can help

    Hello,
    >It's as though no power is getting to it.
    Would it be correct to assume that no sounds at all can be heard? Also, no lights, not even green or amber at the power button?
    >unfortunately had a power cut.
    Was it possibly a power cut in connection with a thunderstorm? Any other evidence of higher than normal voltages (light bulbs, et cetera)? Has the line voltage been checked (measured with an appropriate voltmeter/multimeter)?
    If necessary, it would be possible to remove the hard drive, and then connect it to an external IDE/ATA to USB adapter (example below). That way you could gain access to files on the hard disk from another computer.
    http://www.newertech.com/products/usb3_universaldriveadap.php
    Jan

  • My 2002 iMac G4 went down during a power out. won't restart. tried PMU button. still won't start. fan tries for 2 sec, but nothing

    my 2002 iMac G4 went down during a power out. won't restart. tried PMU button. still won't start. fan tries for 2 sec, but nothing

    Sometimes, a replacement 1/2AA 3.6v Lithium PRAM battery is needed
    to get these back into running form again, because these are one-way
    and without a good battery, settings are lost or easily corrupted. And this
    can contribute to a failure on startup. But that is a troubleshooting measure.
    There could be another issue, although these batteries are only good for a
    few years at best. A power outage can revoke any remainder of life out of it.
    The take-apart is tedious and detail oriented; to include new thermal paste
    and some special tools, good instructions, and some skills also help. An
    ifixit.com repair guide may help; as would an original Apple Service guide.
    Not sure if other good online guides or youtube video are available.
    If the power supply is bad, the test ports near the PMU button are where
    to check; with multi-meter. Also power supplies may develop issues with
    bad capacitors. They have been said to be repairable.
    Here's an older site with a take-apart from some time ago.
    http://www.xlr8yourmac.com/systems/imac_g4/imacg4_takeapart.html
    This also would be a good time to consider, if battery is all that's failed, to
    upgrade the internal RAM chip, or upgrade the hard disk drive, etc.
    Good luck & happy computing!
    edited

  • I would like to leave my iMac on Snow Leapord to use Power PC software, and run Mountain Lion on my Macbook pro. I am getting an iPhone 5. Is there a way to use mail on all of them?

    I would like to leave my iMac on Snow Leapord to use Power PC software, and run Mountain Lion on my Macbook pro. I am getting an iPhone 5. Is there a way to use mail on all of them with the same accounts?

    Any IMAP e-mail account can be accessed from all devices just fine. You don't need to upgrade from Snow Leopard to be able to access an IMAP e-mail account. However, Snow Leopard won't have built-in support for iCloud. As mende1 points out, you can still read your iCloud e-mail from Snow Leopard, but you have to set it up manually. You won't be able to do things like sync your iCloud calendar or addresses with iCal or Address Book on the iMac, though.

  • HT4060 My ipad has been charging most of the morning but its still saying low power...what does that mean?

    I've been charging my ipad most of the morning but its still saying low power...what does that mean?

    iPad Charging
    "The fastest way to charge your iPad is with the included USB Power Adapter.
    iPad will also charge, although more slowly, when attached to a computer with a high-power USB port (many recent Mac computers) or with an iPhone Power Adapter.
    When attached to a computer via a standard USB port (most PCs or older Mac computers) iPad will charge, but only when it's in sleep mode.
    Make sure your computer is on while charging iPad via USB. If iPad is connected to a computer that’s turned off or is in sleep or standby mode, the iPad battery will continue to drain."

  • My late 2009 iMac is starting to refuse to play DVD's.

    My late 2009 iMac is starting to refuse to play DVD's. Any ideas? It is still in warranty till Nov 2012. it will accept all DVD's, but some it will not play, justs searches for a bit, then spits out. others it plays ok. There appeasrs to be nothing (Quality of DVD, age of DVD etc), that i can pick on. I expect that a trip into the nearest apple store is needed, but iMacs are a bit large to cart around!
    bw
    Andrew

    If you are under Warranty, which you appear to be,  and you live in the US within 50 miles of an Apple Store, you can request free onsite Service at your home for desktop Macs through Apple Express.
    Hope this helps

  • My Hp notebook laptop refuse to power-on

    I travelled for 4 months and left my hp notebook laptop for dat period witout using it with d battery intact but on arrival i decided to use it and it refuse to power-on.I tot mayb d ba3 is down so i charged for more long hours but still it didnt on den someone told me dat bcos i left d ba3 in it for dat long period dat it has damaged d motherboard.Is it true? Wot can i do? Cos d person advice me to get anoda laptop but d laptop is new i avnt used it for long

    remove the battery
    remove the AC adapter
    hold down the power button 30 seconds
    wait 30 seconds
    plug in AC adapter, not battery
    try to turn it on

  • My first generation iPhone just refuses to power up.  What can I do?

    This morning my iphone was fully charged and working fine.  I may have mistakenly connected a power cable to it that went nowhere.  When I got where I was going a bit later, it refused to power up at all.  I have reconnected to the charger, and after an hour, still no signs of life.  Any fixes or ideas.  It was not dropped, immersed or abused in any way.
    thanks.

    Bring it into an Apple Store for a free diagnosis and quote for cost of repair/replacement of parts.
    If the costs are $500 or over, consider using the money toward a new or "newer" (used) Mac.

  • Thanks so much for the offer of help. I'm using 10.9.2 OSX. I have Numbers 2.3 (554). I tried the new version but it was "dumbed down" so much (to make it usable on multiple platforms) that it was of no use on iMac.   I still can't get my contacts to open

    Thanks so much for the offer of help. I'm using 10.9.2 OSX. I have Numbers 2.3 (554). I tried the new version but it was "dumbed down" so much (to make it usable on multiple platforms) that it was of no use on iMac.
    I still can't get my contacts to open in Numbers like they used to do. I have a group of five addresses in a test folder in Mail called "untitled group." But no amount of pasting, dragging, etc can get them to open up in Numbers. My "real" folder has almost 100 addresses so I can't do it one by one.
    Thoughts?
    Thanks again.
    Bob

    Bob,
    You can place contacts in a table In Numbers by the following methods:
    Numbers 2.3:
    drag from contacts
    Numbers 3.2
    copy from contacts, then paste into Numbers
    In both cases you need to open System preferences, then select the "Security & Privacy panel and allow Numbers aaccess your contacts information.

  • Since upgrading to Yosemite on my iMac, My Mail app refuses to open, Safari won't load, and I can't upload pictures from my iPad... Please help, any ideas very welcome. I've had my iMac since 2011, and have never had any issues to deal with before..

    Since upgrading to Yosemite on my iMac: My Mail app refuses to open, Safari won't load, and I can't upload pictures from my iPad...
    Please help, any ideas very welcome. I've had my iMac since 2011, and have never had any issues to deal with before..
    Thanks

    29/11/2014 20:17:01.315 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 11 seconds. Pushing respawn out by 49 seconds.
    29/11/2014 20:17:37.013 com.apple.backupd[616]: Finished scan
    29/11/2014 20:17:43.108 com.apple.backupd[616]: Saved event cache at
    /Volumes/Time Machine Backups/Backups.backupdb/Geoff Lambrechts’s iMac
    (2)/2014-11-29-200648.inProgress/9B453663-603F-40B8-AC21-24F05C724E15/.6162AD34- 38F8-30AB-98E0-4A22FB9D311F.eventdb
    29/11/2014 20:17:43.207 com.apple.backupd[616]: Not using file event
    preflight for Macintosh HD
    29/11/2014 20:18:01.561 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 11 seconds. Pushing respawn out by 49 seconds.
    29/11/2014 20:18:16.288 com.apple.xpc.launchd[1]:
    (com.apple.quicklook[715]) Endpoint has been activated through legacy
    launch(3) APIs. Please switch to XPC or bootstrap_check_in():
    com.apple.quicklook
    29/11/2014 20:18:23.705 com.apple.SecurityServer[56]: Session 100013 created
    29/11/2014 20:18:32.046 mdworker[718]: code validation failed in the
    process of getting signing information: Error Domain=NSOSStatusErrorDomain
    Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
    29/11/2014 20:19:01.662 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 11 seconds. Pushing respawn out by 49 seconds.
    29/11/2014 20:19:45.458 com.apple.xpc.launchd[1]:
    (com.apple.imfoundation.IMRemoteURLConnectionAgent) The
    _DirtyJetsamMemoryLimit key is not available on this platform.
    29/11/2014 20:19:59.123 com.apple.xpc.launchd[1]:
    (com.apple.PubSub.Agent[725]) Endpoint has been activated through legacy
    launch(3) APIs. Please switch to XPC or bootstrap_check_in():
    com.apple.pubsub.ipc
    29/11/2014 20:19:59.123 com.apple.xpc.launchd[1]:
    (com.apple.PubSub.Agent[725]) Endpoint has been activated through legacy
    launch(3) APIs. Please switch to XPC or bootstrap_check_in():
    com.apple.pubsub.notification
    29/11/2014 20:20:01.138 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:21:01.484 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:21:13.430 com.apple.backupd[616]: Found 4529 files (1.1 GB)
    needing backup
    29/11/2014 20:21:18.786 com.apple.backupd[616]: 2.82 GB required (including
    padding), 1.24 TB available
    29/11/2014 20:21:31.775 Console[734]: Failed to connect (_consoleX) outlet
    from (NSApplication) to (ConsoleX): missing setter or instance variable
    29/11/2014 20:21:34.230 WindowServer[162]: disable_update_timeout: UI
    updates were forcibly disabled by application "Console" for over 1.00
    seconds. Server has re-enabled them.
    29/11/2014 20:21:36.898 WindowServer[162]: common_reenable_update: UI
    updates were finally reenabled by application "Console" after 3.67 seconds
    (server forcibly re-enabled them after 1.00 seconds)
    29/11/2014 20:21:36.971 coreservicesd[83]: SFLEntryBase::ListHasChanged
    mach_msg returned 10000004d
    29/11/2014 20:22:01.817 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:23:02.170 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:24:02.547 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:25:02.168 CalendarAgent[218]:
    [Refusing to parse response
    to PROPPATCH because of content-type: .]
    29/11/2014 20:25:02.233 CalendarAgent[218]:
    [Refusing to parse response
    to PROPPATCH because of content-type: .]
    29/11/2014 20:25:02.236 CalendarAgent[218]:
    [Refusing to parse response
    to PROPPATCH because of content-type: .]
    29/11/2014 20:25:02.284 CalendarAgent[218]:
    [Refusing to parse response
    to PROPPATCH because of content-type: .]
    29/11/2014 20:25:03.059 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:25:12.674 com.apple.xpc.launchd[1]:
    (com.apple.imfoundation.IMRemoteURLConnectionAgent) The
    _DirtyJetsamMemoryLimit key is not available on this platform.
    29/11/2014 20:26:03.464 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    29/11/2014 20:27:03.841 com.apple.xpc.launchd[1]: (jp.buffalo.NASPower)
    Service only ran for 10 seconds. Pushing respawn out by 50 seconds.
    On 29 November 2014 at 19:29, Apple Support Communities Updates <

  • Macbook Pro (Mid 2012 Version) refuses to power on

    Hello Everybody
    I have some problem here and I was hoping for some help!
    Problem:  Macbook Pro refuses to power on. ( no fan sound, no hard disk spinning sound)
    Event leading up to problem: I was using the laptop when it suddenly it just blanked out( Power went off ). I pressed the power button and the computer started; however, after loading the operating system ( I managed to log in to the OS and was navigating my desktop), the computer blanked out again. Ever since then, the Macbook Pro refused to power on.
    Solutions I have tried:
         Plug in a new Magsafe Charger : I plugged in a new macbook pro charger which is working ( i verified that its working by plugging it into another macbook). The charging indicator refused to light up even when the working charger is plugged into the macbook pro.
    Tried a SMC reset : I tried a SMC reset by pressing left control, left option, left shift and power button and releasing it all together. Nothing changed.
    Final Note:
    My macbook is out of warranty already so I am prepared to open up the laptop to disconnect and reconnect the battery, or do anything you guys might suggest;
    that said, please do not advise me to bring this into a service centre. That will obviously be my final resort. We wouldn't be talking here if we could just bring it to the service centre right?
    Thanks for all the help that i might receive guys !

    When did it happen? After updating/upgrading? or just randomly?
    You can try to perform a SMC reset and resetting the PRAM:
    SMC Reset -> http://support.apple.com/kb/HT3964
    PRAM/NVRAM -> http://support.apple.com/kb/ht1379

  • My 24" iMac just died and will not power-up.  What can I do?

    My 24" iMac just died and will not power-up.  What can I do?

    Bring it into an Apple Store for a free diagnosis and quote for cost of repair/replacement of parts.
    If the costs are $500 or over, consider using the money toward a new or "newer" (used) Mac.

Maybe you are looking for

  • How can I display de last items of a region from other page in Portal?

    I want to display de last five items (f.e.) included in a region (with attributes created) from other page. I've tried using custom search, but it also shows the attribute names, and I want show the attribute values (I don´t know how can I format the

  • Can't connect to wireless network with "conflicting" essid

    Hello, My wireless card works perfectly (actually I am using ndiswrapper, but anyway) on Arch and I can connect to my home wireless network. I use iwconfig to connect. In my office we have a wireless network. It's essid is "default" and it uses WEP.

  • Pricing procedure for Credit Memo request WITHOUT reference

    Dear friends, I have come across a requirement where credit memo request has to be created without reference to preceding document. i.e. for just giving some credit to customer may be for over pricing or giving some credit to customer (as to maintain

  • Problem with Scenario tRFC - XI - File

    Hello, Can you tell me if it is possible to implement the scenario tRFC -> XI -> File Adapter without using a sync-async bridge. I am having a hard time implementing this scenario. My problem is that I am not able to see the messages in transaction S

  • Srcpac. Making packages with dash in the name.

    Last time I've rebuild program with dash in the name (gtk-smooth-engine). After modify my srcpac.conf: conf_gtk-smooth-engine=('#./configure --prefix=/usr#./configure --prefix=/usr --enable-gtk-1 --enable-gtk-2#' "#depends=('gtk2'#depends=('gtk2' 'gt