• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

Trying to fix a Backlit Portable

iJol

Active member
Hey,

got a M5126 a few days ago along with the original power adapter. Checked it, and it outputs 1.5A at 7.52V, so I guess it's okay.

After cleaning and recapping the logic board, I tried powering it with a new 6v Cyclone battery but nothing happened.

I’ve played around with NMI and Reset, and suddenly the screen and the backlight turned on showing different patterns, after trying again I got a
Sad Mac with the code 00000014 0000C036, which referring to other posts mean, that some traces are not connected, I have to check this out after the holidays.

Another thing I mentioned is that all chips are cold, except for U11K, a 74AC153 for the internal modem which gets extremely hot. Could this chip be damaged and preventing the Portable from booting?

Maybe someone can help me.

Regards,
Julian
 

Attachments

  • B12BF079-4D73-4BDB-AAD8-9A0672E51648.jpeg
    B12BF079-4D73-4BDB-AAD8-9A0672E51648.jpeg
    128.2 KB · Views: 29
  • FCDDD657-4CDC-48B9-8123-AD338FE3CAD2.jpeg
    FCDDD657-4CDC-48B9-8123-AD338FE3CAD2.jpeg
    186.4 KB · Views: 18
  • 6C739363-70A8-483D-AC40-4DB295559EE4.jpeg
    6C739363-70A8-483D-AC40-4DB295559EE4.jpeg
    172.1 KB · Views: 31

iJol

Active member
Pics of your board?
I’ll take some when I‘m back in my hobby room - have to work over the holidays so I can’t go there the next days.

I think I’m trying to remove the caps again and look if there’s any cap juice or goo I haven’t seen - and try to remove the U11K-Chip.
 

iJol

Active member
Hey,

here is a pic of the board. Ignore the Cap at C16, I went out of axial caps and used a radial temporarily. Also ignore the bodge-wire, I've accidentally ripped it and have to resolder it.

I removed the 74AC153 at U11K because it had continuity between several where it shouldn't be according to the schematics. I also desoldered the SWIM to see if this makes any difference.

My guess is, that the PMGR is fried or something like that.
 

Attachments

  • portale.png
    portale.png
    16.5 MB · Views: 28

cb5890

Member
Hey,

here is a pic of the board. Ignore the Cap at C16, I went out of axial caps and used a radial temporarily. Also ignore the bodge-wire, I've accidentally ripped it and have to resolder it.

I removed the 74AC153 at U11K because it had continuity between several where it shouldn't be according to the schematics. I also desoldered the SWIM to see if this makes any difference.

My guess is, that the PMGR is fried or something like that.
Are you still getting PMGR specific error codes? It might be worth cleaning the area around the PMGR chip again - if possible even resorting to cleaning it and then baking it for a while. (As a "in between"-measure, you can also try (gently and carefully!) heating up the area around the PMGR chip. Around ~100C often did the trick for me.)

The portable PCB can become pretty "sensitive" (to be put lightly) around the PMGR area. I have had more than once the pleasure of storing a working portable PCBs in an antistatic bag - only to come back later to find it not working due to issues in the PMGR area. Re-cleaning the area fixed those - again.

The different patterns on the screen can be explain by different signals influencing each other or then even the internal runtime state of the PMGR chip itself. The 5V enable line can then get quite flaky resulting in various "interesting" noises and screen patterns.

In case the PMGR chip should be really damaged, I also have quite some good news due to a side project @androda and I have been working on for quite a while now. We have created a (basically) working replacement for the PMGR using the original PMGR code, a similar, but still largely available microchip architecture and some reverse engineering magic to transfer the original code.

So far, the prototype is designed to be a drop-in replacement for the EPMGR connector on the non-backlight portable, but we (in that case mostly androda, he's known for quite some black connector engineering magic 😂) have got some ideas on how to adapt it to a backlight board as well :)
 
Last edited:

iJol

Active member
Hey cb5890,

yeah, seems my PMGR was toast. I desoldered it, cleaned it, soldered it back in place and still nothing. Then I got a broken PB100 and changed the PMGRs, I powered my Portable on and: check! Booted right into 7.0.1 from my BlueSCSI.

The only problem now is, that the floppy is not working. I get steady 5v and 12v, but the floppy drive just spins, searches and then stops. I don't even get any message that the floppy isn't readable or something like that. Checked the traces from the SWIM, but they seem to be okay - maybe the SWIM is also toast, after the 74AC153 was.

Wow! Sounds really like Black Magic to me. :'D But that are great news for all the toasted PMGR-Portables out there and I'm interested in replacement chips. :)
 

Attachments

  • 2023-01-18 08.12.57.jpg
    2023-01-18 08.12.57.jpg
    130.2 KB · Views: 21

3lectr1cPPC

Well-known member
Maybe that explains all the dead PowerBook 100s that wouldn’t work after recapping. These power manager chips seem unreliable.
 

cb5890

Member
Hey cb5890,

yeah, seems my PMGR was toast. I desoldered it, cleaned it, soldered it back in place and still nothing. Then I got a broken PB100 and changed the PMGRs, I powered my Portable on and: check! Booted right into 7.0.1 from my BlueSCSI.

Oh, yeah, perfect. That's the other main option replace the PMGR. I'm glad that you could get ahold of a working chip, although it's kind of sad for the PB100 of course, but then a mini portable - in a manner of speaking - saved a big one :D

After resoldering the PMGR, how did the portable behave then? Were just still experiencing weird patterns on the screen or was it booting up consistently with a sad MAC? I have nine portables and PB100 and I still have yet to actually see a dead PMGR... It would be nice to figure out how these chips fail. We have a theory regarding out-of-spec hybrids for the non-backlight model that basically damage the chip through the A/D feedback line, but we're not sure how this theory translates on the (slightly) improved "hybrid area" on the backlight model.

The only problem now is, that the floppy is not working. I get steady 5v and 12v, but the floppy drive just spins, searches and then stops. I don't even get any message that the floppy isn't readable or something like that. Checked the traces from the SWIM, but they seem to be okay - maybe the SWIM is also toast, after the 74AC153 was.
Hm, interesting. I also had a lot of trouble with the floppy drives on quite some portables. One time I accidentally shorted the IWM_CNTRL and SCC_CNTRL lines when resoldering the PMGR chip... During boot, the IWM_CNTRL line is high, but the SCC_CNTRL line is low, so the result was IWM_CNTRL being pulled low as well and that in turn disabled the SWIM again. That took me a while to figure out :D

The portable can't boot without the SWIM being present and if the SWIM would be completely damaged it would likely also trash the bus, so it could be still fine.

What does happen when you're trying to boot of floppy? Does the portable recognise that the floppy is inserted and then display the floppy icon with an X?
Yep, I had also problems with a couple of 74AC153. It seems to be one of the weaker components (like the logic ICs next to the CPU) that fails quite often short when the 5V rails gets out of spec.

Wow! Sounds really like Black Magic to me. :'D But that are great news for all the toasted PMGR-Portables out there and I'm interested in replacement chips. :)
And also the PB100s :D What did happen to your PB100? Also damaged screen? It's quite hard to find one without it.

P.S.: I finally realised that I'm talking to a fellow German here, so "in that sense": Viele Gruesse aus Saarbruecken! :)
 

iJol

Active member
The portable can't boot without the SWIM being present and if the SWIM would be completely damaged it would likely also trash the bus, so it could be still fine.

What does happen when you're trying to boot of floppy? Does the portable recognise that the floppy is inserted and then display the floppy icon with an X?
Yep, I had also problems with a couple of 74AC153. It seems to be one of the weaker components (like the logic ICs next to the CPU) that fails quite often short when the 5V rails gets out of spec.


P.S.: I finally realised that I'm talking to a fellow German here, so "in that sense": Viele Gruesse aus Saarbruecken! :)
No, the floppy starts searching and that’s it - it rotates and moves for a few seconds and then nothing, no X, no ‘Disk cannot be read’ or something like this - maybe I’ll check the Lines in the next days. :)
 

cb5890

Member
No, the floppy starts searching and that’s it - it rotates and moves for a few seconds and then nothing, no X, no ‘Disk cannot be read’ or something like this - maybe I’ll check the Lines in the next days. :)
So, during boot it just sits there with a flashing disk icon if your BlueSCSI isn't plugged in? Have you already tried plugging the floppy drive into both connectors? Maybe there is something going on with INDISK signal and the portable just doesn't realise that there is a disk at all.
 

iJol

Active member
So, during boot it just sits there with a flashing disk icon if your BlueSCSI isn't plugged in? Have you already tried plugging the floppy drive into both connectors? Maybe there is something going on with INDISK signal and the portable just doesn't realise that there is a disk at all.
Yep, I‘ve tried it in both connectors. I‘ll check the INDISK-signal at home, but also an external drive doesn‘t do anything.
 

cb5890

Member
Yep, I‘ve tried it in both connectors. I‘ll check the INDISK-signal at home, but also an external drive doesn‘t do anything.
Ah, you tried an external drive. Perfect. Yeah, then INDISK is rather unlikely, since for an external drive it isn't multiplexed, but ENBL2 goes (basically) directly to the external floppy port. If that also doesn't work, then there is something else going on. Thinking about it "INDISK" likely means internal disk - somehow my head always want to interpret it as "inserted disk" 😂
In addition, you said the device spins up, so INDISK should be fine anyways, because the drive spins up, so it must get enabled :D

If I remember correctly, accessing floppy drives works somewhat like this:

At first, the firmware uses the VIA to tell the PMGR to pull the IWM_CNTRL signal high. The CPU GLU then reacts by enabling the ISM_CLK clock signal for the SWIM. The portable is special in that regard, since the clock signal is only enabled when the SWIM is actually being used - likely in an effort to further reduce power consumption. (In the beginning, I actually believed that to be a bug, since on other Macs its present all the time - until I stumbled across IWM_CNTRL 😂 )

Then, the software uses the SWIM and starts "scanning" the drives by enabling the drives one after another. In order to use the one external and two internal drives, the MISC GLUE is used to multiplex the SWIM's first enable ENABL1 signal to both internal drive ports. So from the perspective of the SWIM, the first drive gets scanned multiple times while the enable signal is redirected to the respective internal drive. (Funny side note: That also means that if you short both INDISK signals together while having a single internal drive, it will appear twice... :D)

Finally, in order to communicate with a drive, the SWIM uses the PHASE0-3 signals, the RDDATA signal to read serial data from the disk and the SENSE signal to read device status information. For machines with Sony disk drives, the RDDATA and SENSE signals are meant to be tied together according to the SWIM documentation. The portable calls this combined signal SWIM_RD.
(In context of the ISM, the ISM-specific documentation mentions that the SENSE signal is used explicitly for write protection detection. All documentations can be found here [1].)

Unfortunately, I'm not exactly sure how the SWIM handles disk detection, because the documentation doesn't expand on that, but I would bet that RDDATA and SENSE are primarily involved there. The issue with the SWIM is that it is a combination the old IWM and the new ISM chips.
If the SWIM is in IWM-mode, the PHASE signals appear to be outputs only, so the RDDATA/SENSE signals should be the corresponding inputs. In ISM mode, however, the PHASE signals can be configured as both inputs and outputs. Still, I would assume that the SWIM is going to be in IWM-mode during boot, since that's the default for all legacy hardware.

As the (a) portable is able to boot at all, (b) manages to complete POST, (c) all drives are affected and (d) the drive spins up, then I would initially assume that the SWIM is good, since it can still communicate with the rest of the machine and also the drives, but the SWIM_RD signal is somehow not received by the SWIM. There might be a broken/compromised trace on the path of that signal.
It is even possible that the 74AC244 bus driver which drives the RD signal from the floppy connectors to the SWIM_RD signal could be affected.
(It is likely not completely broken, since it is also involved in driving the EN245B signal that is also heavily involved in controlling the interface of the RAM to the address bus. I think I had a compromised 74AC244 once before, but I'm not sure anymore... The memories are quite overlapping :D)

If the all traces and the 74AC244 are good, then I'd assume that the SWIM is really bad after all. Then you are quite "lucky" blown PMGR and SWIM on the same portable :-|

Sorry, if the post is a bit lengthy, but I thought I write it down for once before I start forgetting some of details again.. :D

[1] https://archive.org/details/SWIMDesignDocs
 
Last edited:
Top