Jump to content

androda

68kMLA Supporter
  • Content Count

    127
  • Joined

  • Last visited

4 Followers

About androda

Recent Profile Visitors

818 profile views
  1. So far I've used blue pill modules with real stm32 chips, and modules with obvious clones. They've all worked, passing benchmarks and booting/running just fine. So unless you get a really cheap clone that's actually a dud it sure seems like things should be fine.
  2. Your mention of a 'momentary blip' of the LED on startup sounds like the blue pill can see the SD card, read the contents properly, and there are valid images present. Makes sense, because it's an SD that works fine in a premade bluescsi. Is this a PCB which you designed? Post says it's gerbers 'based on the original bluescsi schematics'. This problem with the se/30 taking a really long time to get to the flashing ? (instead of booting) could indicate an issue with the scsi bus to blue pill pin mapping.
  3. @dalek I tried a black pill board, and it's a bit of a mess. I have the code ported and it's working but the black pill at 100MHz is *slower* than the blue pill at 72. At full 100MHz clock, the black pill gets 720k read and 700k write, where the blue pill gets 900k read and about 600k write. It's ridiculous that the newer chip with higher clock speed is slower. Black pill modules are also about 50% more than the blue pill modules and the global chip shortage just keeps driving prices up. Talked with Bill Greiman, the maintainer of SDFat (the SD library we use) and he said
  4. Look up the PowerBook 180 and Duo 280 dev notes, they have a section on the hard drive that should tell you everything you need. That's what I used as the base for my powerbook pcb for bluescsi and it's working fine.
  5. Maybe the scsi2sd PowerBook edition had some parts go out of production or something like that. It's also possible a new version is on the way but I don't see much indication of that. So maybe the bluescsi is basically "it" for now. I'm planning to keep the V2 of my powerbook design in stock until I come up with a better one.
  6. Yep. I haven't done a ton of searching (because, you know, I make the things), but bluescsi and the scsi2sd may be the only two SD style solutions that are available for internal use in a PowerBook.
  7. Have you done any benchmarking of your original drive or looked into the speed of the various scsi device emulators that could fit? Would be interesting to run the benchmark on your original drive and do the same on a bluescsi to see the difference. Seek times are practically non-existent because SD storage is solid state. This gives the bluescsi a lead on anything dealing with lots of tiny files. Larger file sizes will be where the lower speed comes into play.
  8. The BlueSCSI is not as fast as an original hard drive, with read and write speeds ranging around 900k per second. But as @Daniƫl Oosterhuis says, it's extremely easy to use. Stick a hard drive image file on your microSD card, name it properly, and it's there. No configuration utility is necessary, it's all based around the image file names. exFAT seems to provide better performance than FAT32 (speaking of SD card format). There's a listing for PowerBook style BlueSCSI drives in the trading post right now (note that this is my listing), still in stock.
  9. Tested the updated PowerBook design on a 540 and 520 w/ppc upgrade (my brother's laptops). They booted just fine on the rascsi 7.5.3 image. Will be posting the new design in my repo later today. This morning I finished assembling 8 of the updated design, and will soon be making a trading post thread to list them for sale. No sales website yet, that's another thing I need to do (and I'm pretty bad at web stuff).
  10. Thanks for the pointer. Makes me wonder how much longer the 2218 will be manufactured. How many brand new SCSI devices are being made these days, with everything being SATA and SAS?
  11. Thanks for the compliment, but my design isn't technically correct yet. The resistors can't be removed from circuit, which might cause issues in mid-bus usage even with termpower disabled. It's more suited for end of bus where termination is required. The next board revision will include some sort of bus switch for connect/disconnect of the term resistors. Termination resistors don't have to be teeny-tiny. You can use physically larger 110 ohm resistors, the normal through-hole style. I've found that these little things are actually pretty easy with a solder paste syringe and
  12. Speaking of PCB designs, here's the prototype version of my PowerBook BlueSCSI device board. This is the repo where my designs will go after they've had some basic testing done. 'USB Here' means the end of the blue pill with the USB port goes there. https://github.com/androda/PCBDesigns/tree/main/BlueSCSI/PowerBook The two jumpers are for selecting which power source you use (L = logic, M = motor) and term power. I have found that it doesn't work at all without termination enabled in my PowerBook 180. Sleep mode is not tested, unsure if it'll work. This board is definitel
  13. Yes, I've spent some time on this. While I was replacing the capacitors on a backlit portable I managed to find the time to buzz out a bunch of the backlit's hybrid replacement. The results are documented here: https://68kmla.org/forums/topic/62148-new-hybrids-for-the-macintosh-portable-m5120/?do=findComment&comment=666493 That board has gone back to its owner (working, yay) and since I don't own one myself the effort has stalled for the moment. @techknight has offered to sell me some of his old parted out backlit boards to continue the effort, so I can get back to it after
  14. That code looks to indicate a RAM test failure. FF is a reference to which RAM bits failed. I think it means all bits from 0 through 7 failed. Seems likely that you have damage to the RAM chip area, or at least a disconnect for those specific bits. So basically you would need to check bits 0 through 7 using the schematic, and verify that they have a good connection to all the places they should go.
  15. Glad you got this running at least. Have you verified the 5V always on rail is actually 5 volts? And the 12 volt rail too? Display contrast is generated by the power manager chip, from pin 57 (see page 12 of portable schematic). I'm no expert on the display contrast side of things, but here's a list of possible issues: A communication break between the system and power manager (software or hardware) Check pin connections between the power manager and VIA chip, that's how the power manager talks to the rest of the system This isn't hugely likely
×
×
  • Create New...