Jump to content

Bolle

68020
  • Content Count

    2278
  • Joined

  • Last visited

Everything posted by Bolle

  1. I will be done with reworking the quirks of the first revision. Once that's it done I'll create a second fork of the board with through hole sockets for the two large PLCC ICs. (68882 and GLUE) Sockets are going to be problematic, because most of the time the old parts you pull off a board will have corrosion and make very bad contact in a spring loaded socket. Having two board versions you can choose if you want it to be easier to solder (because through hole sockets) but with the tradeoff of possibly having to go through extensively reconditioning the ICs. Going for through ho
  2. No. You will always need a donor SE/30 board to pull off a few of the Apple custom ICs.
  3. Well done. The break around that via is very common. I already had a few boards with the exact same trace broken. If the pullup resistor is still connected the Mac will turn on but won’t turn off on its own from software. If it’s disconnected like in your case you’ll get just the behavior you observed.
  4. I suspect the Presto040 (or whatever it was called under the Donoho brand) is the successor to the Tokamac SX made for the IIci. Btw: I contacted the person with the IIfx card from the thread linked above asking if they would send me the GAL from their logicboard and the accelerator to recreate everything. Didn't hear back from them though. Won't blame them though, having one of the few working Tokamac IIfx setups.
  5. Mind sharing how you did that exactly? I have a set of Nubus TDM hardware as well that I have yet to get to do anything useful without a TDM mix activation.
  6. Did run them without noticing any further issues, so I guess it's fine to have them here... Remember, those aren't dumps of the actual chips but code I rewrote to match the behavior of the originals, so use at your own risk. If something goes horribly wrong harm to the analog board is possible. Jedec files are for standard 16V8 devices - either real GAL16V8, PALCE16V8 or ATF16V8. I used ATF16V8B-15 for the 5 DIP chips and an ATF16V8C-7 for the single PLCC chip. Be aware that ATF16V8C behave differently because they don't have internal pullups. I ha
  7. I'd love to take one I think I even have enough spare parts here to populate one.
  8. My BluePills all had the Blink firmware on it as well from the factory.
  9. On my spinoff of the board there‘s separate jumpers to select power sources for the BluePill and for termination. If you‘d implement the same on your board that would solve the problem of having to run an extra jumper on the Plus. It would boil down to moving a single jumper if you want to power everything externally (USB or another 5V source) On another sidenote: just confirmed the passive termination does even play well with the IIfx, which is otherwise very picky with termination.
  10. The Sonnet adapter is easily doable without desoldering anything (except the PAL to dump/reverse engineer it) I am pretty sure though that it needs a specific Sonnet accelerator to go with it. You won't be able to use two normal LC PDS cards with it.
  11. It is on for me as well, but the actual voltage that's getting to the BluePill is rather low on some of the machines I tried (mainly a lot of different SE/30 logicboards, IIcx, IIci, 475, LC) The SCSI2SD must somehow be more tolerant to lower voltages. This is how I connected the SD card: On the original ArdSCSino github repo there's schematics as well: https://github.com/ztto/ArdSCSino-stm32
  12. The 630 DOS board is actually a LC580, that’s why it had two RAM sockets.
  13. ExFat did not work for me, neither did the factory FAT32 formatting the SD card I used came with. After reformating the card everything was fine. I do need external power though on nearly all machines I tried so far - which is not a big deal as I made a few boards with a Molex connector, so things will plug right in. The SCSI2SD will work just fine when powered from the term power supply on all those machines, so there definitely are a few differences in power requirements here. What I noticed is that despite the Quantum drive identification thingy it won’t show up in App
  14. Just count the pins VRAM -> 68 ROM -> 64 RAM -> 72
  15. I think I have some spares with really bad corrosion somewhere... they would be perfect for this. I’ll see if I can find them.
  16. Just test points I guess. There's everything that's needed on the other pages. Also the Apple schematics are 100% correct - I just copied everything exactly like it's on there. On a side note: I had the modernized schematics open next to them and encountered quite a few errors and mislabeled signals but unfortunately stopped taking notes at some point because there were quite a lot of them and I started to get confused with what to put down in Eagle.
  17. If you do it like that you’re going to kill the PowerCache. There‘s an adapter needed to run the PowerCache in the SE/30. The Daystar accelerators only work directly in the IIci, Performa 600 and IIvx(i?) Everything else needs an adapter. The pinouts are vastly different, 12V will get sent into places, combustional computing is going to happen.
  18. Why are these things popping up everywhere suddenly? @joshc just got one of them as well but without the video section populated. I figured from the missing components that it must have been made to have video ouptut at some point but never saw an adapter yet that actually has it populated. Just what I expected though... some VRAM, a few GALs and three MACHx10. Very interesting indeed...
  19. I am running an old Cisco 1840 with an older IOS that still has AppleTalk implemented. It will take care of the IP encapsulation so you can use any of the dumb ethernet to localtalk bridges.
  20. Yoke connector plugged in the wrong way around?
  21. Yes. The peeper application in live mode to toggle individual pins and observe the behavior is really useful. The automated analysis was only useful to give a few hints. It didn't even finish on the two 16L8s because it got confused with the latches and aborts when outputs don't match what it expected them to be. On the registered devices it was a good way to record truth tables of the statemachines. With that the only thing that was left was to see how the known inputs (because we have the schematics and know what's going to be an input) change the behavior of the statemachin
  22. I just noticed I didn't even try that yet - fitment check: Fits Now on to the missing bits in the serial section and to add the remaining 4 RAM sockets.
  23. Of course the whole thing, network, accelerator, graphics card all at once.
×
×
  • Create New...