Jump to content


  • Content Count

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Shouldn't it be possible to get an NXP MC7448THX1267N to work in there? Note it's a lower power part bin specifically for that use... the 1400-1700mhz parts are higher power even at idle/sleep than this chip. Looking at the datasheet if using 2.5V IO, the IO pins can tolerate 3.3v maximum, it is specified to run across 33-200Mhz MPX bus speeds. I think it may be nessicary to make an straight through BGA adapter board to disconnect some pins or reconnect some to the ground and power but other than that it seems possible. Or is there something i have missed on my first perusal of the
  2. There is an open source implementation of Ethernet over SCSI http://ipoverscsi.sourceforge.net/ it's for Linux 2.4 but that is probably a good thing as it will be simpler... It should at least give ideas about how to encapsulate the data over scsi... it isn't like TCP/IP encapsulaiton is a new thing, even a brain dead shoehoring of slip onto scsi might be quite usable... SLIP being lower overhead on the host anyway as well as being simplistic. If you are motivated enough to make the hardware the drivers should not be the issue... it would go something like set up RX/TX buffers on t
  3. Obviously a SCSI based Ethernet card caters to a different problem than built in Ethernet or add-on boards.... and doesn't have the advantage of being able to use a DeclROM driver.. That said it is a solution that doesn't require opening your Mac or interfering with other modifications... so there is a case for both (the built in or add-on on board is going to be better/faster most likely... but less flexible in what other mods you add).
  4. Just bear in mind that using an ESP8266 is separate from direct Ethernet or WiFi support... since they are WiFi to Serial converters.... so basically you only have access to a socket that is handled on the ESP instead of actually having control of the TCP stack.. it just means the code for handing that would be more different than not than the existing code to connect to an SPI Ethernet controller most likely. I think he used the PHY IC as a shortcut to getting something working initially he can always enhance the code to add support for other methods of interfacing with the bus later.
  5. Also more on topic.. the TinySCSI is not a Disk Emulator only... it is a SCSI peripheral emulator, SCSI cabletron Ethernet emulation is in the works among other things... and the author even put Scuzzygraph emulation on the wishlist. Currently the Ethernet drivers crash with it.. but nobody will be playing $100+ on ebay for SCSI Ethernet anymore once this thing is out. And I imagine it may be able to combine multiple devices into one... perhaps with some speed degradation. Also I forgot to mention one thing... the SCSI2SD is fully open source so I'm not sure why anyone is complaining..
  6. SCSI2SD already supports SDXC AFAIK... I should test with my 128Gb uSD (44 Bucks on amazon) card I use for my action cam... lol I have the powerbook version in my SparcBook 3GX it works great and Micheal McMaster is a nice guy.... even on the older firmwares I'm sure he would fix bugs if people reported them and they were fixable. I mentioned the TinySCSI in another thread a few days ago... where people decried it using the NCR5380 as it is a piece of crap... I mentioned this to him and he seems inclined to add support for multiple PHYs at some point... probably something FPGA centric as t
  7. That makes sense about the DDR QSPI....I saw DDR and immediately thought SDRAM. The proprietary Apollo core does much better than 1 IPC ... IIRC it does more like 4 instructions per cycle max and averaging around 2.5. .... It throws alot of FPGA resources at the problem http://www.apollo-core.com/index.htm?page=features. You could probably do some of those optimizations on a 68k core... but not all (they dropped some less used features I think). Tantalum caps can go bad as well... best to use ceramic where you can.
  8. This guy has a goal of emulating cabletron SCSI ethernet + maybe others. Plus the device can probably also act as a disk drive at the same time. I also mentioned Scuzzygraph emulation and he seemed interested in that as well.... Also basing something on something that already exists is a valid response in many cases... especially if the software/drivers for it already exists. https://hackaday.io/project/18974-tiny-scsi-emulator I'm a big fan of the the SCSI2SD but this one might have it's own niche as well... note that this uses a vintage NCR 5380 controller so isn't so much of
  9. The Problem with the ice40... is DDR probably wouldn't even fit in a 1k part, and would use up nearly 50% of a 4k part...that's and edducated guess based on the LUT figures for other lattice parts. SDR SDRAM fits in under 150LUTS for ice40 and they give you the code for that ... I'm not sure ice40 can meet the timing requirements for DDR. I agree, if you are going to bother with an FPGA at all... you may as well go full bore. For instance. 15k LUT Artix-7 is 25$ and is very fast... especially for a 68000. http://dcd.pl/ipcore/101/d68000/<- that runs a 107Mhz on a kintex-7 and th
  10. such things become an issue above about 20Mhz, 50Mhz was refered to as black magic stuff back in the days of SparcStations... (thats the max speed mbus will run at it maxes out at 40Mhz on the SS20 for instance as it isn't designed well enough to be reliable above that but the Hyperstation 30 could beat that by 10Mhz). Another good example is PCI, which maxes out at 33Mhz at 5v PCI 2.0 doubled that rate to 66Mhz by cutting the bus voltage to 3.3V. Serial links tend to run faster these days because you can do things like run differental pairs etc.. and you have less concern about cross talk
  11. http://experiment-s.de/en/<- this guy has 68030 emulation code working for Atari for his Suska series of boards... he seems to not be updating much lately but he does cool stuff like most people around here. Personally I think emulating the cpu on an ARM is self defeating, and probably not practical.... if you are going to do that you may as well run an emulator on a PC. Other options might be a Zilinx Zynq ... those are around $60 but smash a speedy FPGA + decent ARM chip together. So you could do something like use a VHDL 68k core while using the ARM for accelerating other things
  12. So... can you use this as a direct replacement for the SE/30 tube? Or is there something I missed there.. looks like you are only using it connected to a separate mac with VGA out at the moment?
  13. I agree you should logically understand the code you write.... however..... he asked for a compiler not an assembler and chances are if you are used to new compilers features you take for granted may be completely broken in the old compilers or non existant. so better to have it on hand from the get go so you can test incrementally as you go along rather than developing the whole program essentially on paper to find out it won't work without a rewrite. Also I said retro64 earlier when it is acutally Retro68 and apparently its being used to build the Browsy App for system 6. https:/
  14. My library had Dynix terminals I thought they were awesome .... not Dynix as in unix but Dynix as in the catalog system there are acutally still a few online you can access via telnet. This was in the early 90's
  15. No they are not in bussiness... you can't even find a card on ebay these days (I haven't seen one in months).... of course a few turn up once in a blue moon sometimes they go cheap sometimes people go crazy and spend way too much on them....
  • Create New...