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.
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
-
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
-
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.Comment
-
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.Comment
Related Topics
Collapse
-
by throwaway327ASUS ROG Ally X - (Handheld Gaming PC)
Model No: RC72LA
Serial No: SBNVKD001014459
Hi all, I've spent the past week digging through the forums and guides to try correct my foolish mistake of changing hidden settings while tinkering around, and to be honest my heads overloaded so I'm hoping you'll be able to help.
I used a tool called 'Smokeless-UMAF' to access usually hidden settings in the bios. I tweaked one or two 'safe' things but made the mistake of tweaking a lot of settings under 'USB/Thunderbolt Configurations' when I didn't know what they did. For...-
Channel: BIOS Requests ONLY!
-
-
by irepair559hello guys , ok i tried everyhting and all that was left was to check bios, ch341 says bios is good? not sure here is the dump.. TIA!...
-
Channel: BIOS Requests ONLY!
-
-
by JaquesPrattI have a Vizio D32f-E1 LCD TV that does NOT have a TCON board.
This TV recently went through some 'death throes' and now won't boot. The first problem that began to manifest was while watching tv, the screen would 'freeze', and the image would dim over a few seconds until it was very dark. HOWEVER, the audio of the show would continue as normal. I could power off the TV for 5-20 seconds, power back on, and the video would be normal. This would occur 1-3 times when the TV was first started, and would not happen again after the TV was 'warmed up'. Not ideal, but this glitch was manageable.... -
by taslanHello everyone,
as stated in the title, my surface 7 pro wont boot anymore.
When i press the power button it shows the square windows logo for a second and immediately turtns off again.
I dont even have a chance to get into bios or boot from usb.
While trying to find help online it was suggested to look for help/repair here on badcaps and it might be a ME Region corruption in bios.
I dont know what that is exactly, but i never tinkered with the bios or windows in terms of hacking/patching etc.
Bought it directly from microsoft and used it now and then and only... -
by a_p3rsonHi there,
I'm looking for anyone who might have information on Apple's embedded Apple Watch charging daughterboard, ID 820-02601. This is currently used by Anker in their Apple Watch charging products, but likely by other Apple partner brands as well.
You can see the board referenced in ChargerLab's teardown of the Anker Y1811 3-in-1 MagSafe cube - they discuss the "Apple Watch wireless charging circuit" about 2/3rds down the page. It's not pictured, but the board ID reads 820-02601-A, which sure sounds like Apple.
This daughterboard uses an interesting...-
Channel: Schematic Requests ONLY!
04-21-2025, 11:41 PM -
- Loading...
- No more items.
Comment