Hi Everyone. I have a Mac for a topcase replacement. I have completed the job however the Mac will boot and I get the startup chimes but not pass the Apple Logo, not even a progress bar. After a few seconds the fan spins fast. The board is 820-01598-A. I have disconnected everything except the USB ports and display and the issue persists. I am drawing 20.42v and .461A with just the screen connected so it looks like it is booting. I have looked over the board with a scope and I do not see anything that appears wrong. I can not get into diagnostics, NVRAM reset or DFU. The only issue is the topcase is used, but excellent condition however the Trackpad cable was damaged on the connector and stupidly I did not notice until I tried to connect it. I had not power or battery attached atthe time of course and the connector on the Logicboard is perfect. if anyone has any ideas that would be good and I appreciate your help.
Announcement
Collapse
No announcement yet.
A2159 will not boot past Apple Logo
Collapse
This topic has been answered.
X
X
-
Answer selected by Logix_UK at 10-17-2024, 06:16 AM.
-
Review the trackpad and trackpad cabling. Be sure the trackpad cable contact pitch is suitable for this model's connector. There are sensors in the trackpad assembly that must be visible during the OS boot using smbus communication. If absent, there will be a high fan spin.
Measure the voltage to ground of each smbus pin on the trackpad cable.
Respectively, the trackpad must be connected and working to boot.
Comment
-
Originally posted by mon2 View PostReview the trackpad and trackpad cabling. Be sure the trackpad cable contact pitch is suitable for this model's connector. There are sensors in the trackpad assembly that must be visible during the OS boot using smbus communication. If absent, there will be a high fan spin.
Measure the voltage to ground of each smbus pin on the trackpad cable.
Respectively, the trackpad must be connected and working to boot.
Comment
-
This reminds me of a very involved case with XMOS (UK) Semiconductor (multicore processors - mainly for audio when we were considering it for new designs). Long winded story but is as follows. The multicore processor would emulate the USB handshakes using 'bit banged code' to offer a USB audio device. Respectively, USB is a very time sensitive interface. If too much time is invested in one core vs. another, the USB interface will suffer and die. The other cores were handling the audio processing. A large audio OEM company invested almost 9 months I was told on attempting to fix this failed new audio design - attempting numerous new PCB layouts, etc. Then they sent in the latest design to us for a review. After a review of the firmware, the root cause was...drumroll...a missing I2C / SMBUS slave device. The code loop was repeatedly attempting to ping a SMBUS slave node that was absent on THEIR design but was on the reference board design from the factory. While stuck in this phantom device hunt loop, the USB interface would suffer and would die over time.
Same case here with the trackpad. The sensors are low cost I2C / SMBUS nodes that must be found or enumerated by the logic board else the logic board assumes the worst and believes that the CPU temp is out of range so blast the fan into hyper speed and throttle the CPU speed.
- Likes 1
Comment
-
Originally posted by Axis937 View PostOut of curisoity, what is the relation between the trackpad cable and stuck Apple logo. Whats happening behind the scene?
Comment
-
Originally posted by mon2 View PostThis reminds me of a very involved case with XMOS (UK) Semiconductor (multicore processors - mainly for audio when we were considering it for new designs). Long winded story but is as follows. The multicore processor would emulate the USB handshakes using 'bit banged code' to offer a USB audio device. Respectively, USB is a very time sensitive interface. If too much time is invested in one core vs. another, the USB interface will suffer and die. The other cores were handling the audio processing. A large audio OEM company invested almost 9 months I was told on attempting to fix this failed new audio design - attempting numerous new PCB layouts, etc. Then they sent in the latest design to us for a review. After a review of the firmware, the root cause was...drumroll...a missing I2C / SMBUS slave device. The code loop was repeatedly attempting to ping a SMBUS slave node that was absent on THEIR design but was on the reference board design from the factory. While stuck in this phantom device hunt loop, the USB interface would suffer and would die over time.
Same case here with the trackpad. The sensors are low cost I2C / SMBUS nodes that must be found or enumerated by the logic board else the logic board assumes the worst and believes that the CPU temp is out of range so blast the fan into hyper speed and throttle the CPU speed.
Comment
Comment