Search results

I have now worked through the scenarios and these are my discoveries on the M5120 Portable: * Upgrade card set to 4MB or less: No perf degradation (no degradation after sleep) * Upgrade card set to 5MB or more: Perf degradation (worse after sleep) So it looks like for some reason or another...

It also depends on whether people want an update. Based on all my investigation, there's nothing wrong with the RAM card. It's performing exactly as it should. All these side effects of increased overhead due to memory management and the bug in CPU wait states are from things that are not...

I don't know if there's an easy way for you to flash the update. This is something I'd have to look into, because it's not friendly or convenient like an STM32 or Raspberry Pi Pico. This CPLD uses JTAG for flashing, which is a lot less common.

Overall it appears that any slowdown after a cold boot is probably due to system overhead with the memory manager. The strange behavior after sleep is because of a bug with the glue chip's wait states. My next step is to tweak the firmware again to increase available memory and see where the...

I created a "quick and dirty" test firmware for the CPLD. It reports as 3 megs of expansion (but provides 3.5mb because chip select logic is complicated). The Portable doesn't know what to do with half-meg increments and generally leaves it alone. The results? 2.08 CPU performance rating...

Ah, so it's the cpu glue which controls that. Is there a register or address reference available?

This is... odd. RAM access on the 68000 is controlled by the /AS pin (noted "AS" in the pictures because my analyzer didn't want to let me add a "/"). It means "The address on the bus is valid and the CPU is selecting whatever is there". Normal /AS cycles look like the above images, about 4...

Started investigating, was curious whether something was up with the RAM timing. The original spec is 100 nanosecond RAM, Techknight's 8 meg card used 55ns and mine uses 70ns. This doesn't appear to be related at all. Below are screen captures from my logic analyzer, with my 8 meg card on top...

Well, I'll be taking a look at this to hopefully duplicate and try to fix.

The hybrid module is probably not at fault here. The hybrid sends a signal to the power manager chip which indicates battery level. And the power manager chip sends a signal to the hybrid to tell it whether -5 volts should be generated or not. If that battery level signal droops too low your...

I think it's pretty unlikely that the hybrid could be a cause of this issue. Assuming the power LED comes on to the BlueSCSI after exiting sleep, it's not a power issue.

I use a Hakko desoldering tool from under the main portable PCB. The pins are pretty skinny, there's a lot of solder around them. Correct, replacement hybrids include new pin headers.

Two thoughts on the LiFePO4. First, it might need time to charge up to full voltage. Second, your hybrid's battery level reporting opamps might be showing the wrong charge level. This happens with hybrids that have seen just about any level of capacitor fluid ingress, it gets into the...

For the curious, the attached picture shows the damage to the transceiver chips (likely caused by 12v from the floppy port). I swapped out all the chips excluding the activity LED driver (this is more isolated, running from 3.3 via pico) and now it's working again. The pico itself is making a...

Pretty sure that eBay listing is from @SuperSVGA

There's almost always a way, if you're willing to do the work and build it out yourself. :)

This issue was discussed in Discord. Turns out that the BlueSCSI unit was accidentally partially plugged into the Floppy Drive port. Floppy drive ports provide a variety of voltages which are hazardous to BlueSCSI, such as 12v. It was probably damaged by the over-voltage. I'm going to take a...

Doesn't look different to me. As I said, I also recreated *this specific* screen cable.

Yes, I'll put together some more of those. What you have is the official backlit screen upgrade for the original portable. And lucky for you, I also recreated this screen flex cable. It's just not listed on my site because these are so rare. Pretty sure I have at least one more of these cables.

I do think most or all of the 1x0 series powerbooks will have that 50 pin internal connector. It's for SCSI target disk mode, so the Mac can dynamically assign the SCSI ID of the internal hard drive for use with an external system. These drives use jumpers there at the back to set the SCSI ID...