Home » RBC Forums » General Discussion » Plasmo's 68k pathfinder projects (68K, 68000, 68020, 68030, 68040, 100mm x 100mm pc board)
|
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2802 is a reply to message #2801] |
Tue, 16 May 2017 12:51   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
Using a $25 7128s seems like it'll be hard to get to a $10 board. The MAX-10 is only $17.50! The 29 decoupling caps for the MAX-10 are a definite negative for it. 
If I tried using the MAX-10's user flash for the boot ROM image, then I'd either have to add the high 8 bits of the data bus to the MAX-10 using valuable pins or I'd have to copy the ROM contents to RAM like you're doing. Both approaches have risk involved since I haven't done anything significant with a FPGA before! With the external flash for the ROMs, I just need standard chip select functionality from the FPGA before I'd have a minimally working system. The plan is then to add SDRAM support, then a periodic timer, SDIO, and Ethernet. The ETHclick is based upon the ENC28J60 but on a little board with the RJ-45. Someplace along the way I hope to be running ucLinux.
I looked into adding DVI but I was 4 pins short! But if I add video out, then I'd need USB in for keyboard and mouse. So I'd need even more pins! So I decided to put off video for either a daughter board, hence the two 40 pin headers, or for my "real" system.
Speaking of my "real" system, I discovered Coldfire v4/v4e processors last night. 200+ MHz 68000, MMU, FPU, SDRAM controller, PCI controller, UARTs, Ethernet, expansion bus, ... all in one little 388 pin BGA. And NXP is still making them! Add KVM and that would make a nice system. Not very "retro" though.
Too many choices. Not enough money in the toy fund.
Mike
[Updated on: Tue, 16 May 2017 12:53] Report message to a moderator
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2810 is a reply to message #2805] |
Wed, 17 May 2017 13:44   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
I guess I'm too much of an old fuddy duddy worrying about a deal "that's too good to be true" with the random Chinese or Russian suppliers on the net. So I've stuck to Digikey whenever possible. I know that if I ever build my 040 dream machine, that I'll have to bite the bullet and deal with the unknown sources.
As for the Coldfire, since I don't have any 68K binaries, being 100% 68K complete isn't that big of a deal for me. As long as GCC supports the processor and there's a reasonable chance of running Linux, I'm happy. I ran into the Coldfire on the http://firebee.org. It's a Atari ST/Falcon compatible so they're more interested in binary compatibility. Sounds like the Coldfire is good enough for them.
The bigger problem with the Coldfires is that they're essentially complete SoCs. They have just about everything already built in. So where's the fun in that? At that point, I just as well go with a modern ARM SoC running at GHz rates instead of 266 MHz old stuff.
Are you planning on writing your own SDRAM controller or are you going to use/modify one of the "open" implementations that are out there? I sketched out what I thought the VHDL should look like before I went looking. The ones I found pretty much matched what I was expecting. They all have different feature sets but the basics of talking to a SDRAM are the same.
Mike
|
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2943 is a reply to message #2942] |
Wed, 31 May 2017 20:54   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
The 68SEC000 would save you a lot of board space! 
If you have to have a DIP, you can get a 64 pin QFP to DIP adapter from Digikey. And it is 0.6" row spacing. I used a pair of standard 40 pin DIP sockets on my first board.
The local FPGA guru warned me about how fast the MAX CPLDs fill up. He has ulterior motives though, trying to get me to become a passable FPGA developer. Sounds like you're on your way to that goal! Congratulations!
BTW, is that a resistor I see holding pin 7 up?
Mike
[Updated on: Wed, 31 May 2017 20:56] Report message to a moderator
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2968 is a reply to message #2945] |
Mon, 05 June 2017 17:35   |
plasmo
Messages: 916 Registered: March 2017 Location: New Mexico, USA
|
Senior Member |
|
|
Its alive!

All 68000's 16 megabyte memory space is taken up with a 16meg SIMM module except the top 32K bytes which are allocated to 68681 (DUART), IDE, and the expansion edge connector. The DRAM should be fast enough to run at zero wait for the fastest 68000 (20MHz). I have a 68HC000P10 running at 8Mhz right now. The refresh logic is CAS-before-RAS running automatically invisible to the the 68000 by inserting wait state to DRAM access during a refresh cycle. The monitor is about 11K bytes. The serial EEPROM loader loads half (16K bytes) of the AT24C256 into low memory of DRAM at powerup or reset. The serial clock is 500KHz so it takes about 300mS to load the monitor, barely noticeable.
The monitor uses EASy68k trap #15 services for I/O so Lee Davison's EhBasic runs with very little modifications-- two changes: org to 0x4000 & disable DUART interrupts. I got the ASCII art program from tobster's hackaday page and I use it as a performance benchmark. The program takes 102 seconds to run on the 8MHz Tiny68k. It takes 29 seconds on Tiny030, 22MHz 68030.

I built up the board mostly with my existing inventory of parts, but since low cost is the main goal of this project, I look around eBay for 10pcs lot (shipping excluded) to find out how close it comes the $10 goal:
68HC000P10, $3
68681, $2
16meg SIMM72, $4
SIMM72 socket, $1.5
24C256, $0.4
Oscillator, $1
Altera EPM7128SQC100-15, $3
pc board, $0.5
So that's $15.4 for major parts and probably $2 for miscellaneous parts. Definitely over $10, but it is about $10 if you already have spare 68000, 16 mega SIMM, and miscellaneous parts,
|
|
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2992 is a reply to message #2986] |
Tue, 06 June 2017 14:58   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
Are you only using half of the SIMM? Looking at the schematic, you have the high word (16b) and the low word (16b) of the SIMM connected to the 16b data bus of the 68K. Seems like you're either using half of the available memory or you're interleaving the 68K's word accesses. Since you're only using 2 of the 4 RAS signals, I'm leaning towards using half of the capacity. Your SIMM is probably bigger than the 16MB address range of the 68K so it doesn't matter if you are only using a fraction.
Mike
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #2998 is a reply to message #2992] |
Tue, 06 June 2017 18:13   |
plasmo
Messages: 916 Registered: March 2017 Location: New Mexico, USA
|
Senior Member |
|
|
mikemac wrote on Tue, 06 June 2017 14:58Are you only using half of the SIMM? Looking at the schematic, you have the high word (16b) and the low word (16b) of the SIMM connected to the 16b data bus of the 68K. Seems like you're either using half of the available memory or you're interleaving the 68K's word accesses. Since you're only using 2 of the 4 RAS signals, I'm leaning towards using half of the capacity. Your SIMM is probably bigger than the 16MB address range of the 68K so it doesn't matter if you are only using a fraction.
The 72-pin SIMMs I have are populated on one side only with eight 4megx4 (e.g. HY5117404) DRAM, so that's 16 megabytes. My understanding of one-sided 72-pin SIMM is that RAS0 goes with CAS0 (low byte) and CAS1 (high byte) and RAS2 goes with CAS2(low byte) and CAS3 (high byte). RAS1 & RAS3 are for the other side which is unpopulated. The way I map the memory is 0x0-0x7FFFFF to RAS0/CAS0/CAS1 while 0x800000-0xFF7FFF to RAS2/CAS2/CAS3. When refreshing all CAS0-3 and RAS0/RAS2 are activated which does created quite a current spike and need to be managed with bypass & filter caps plus multiple ground traces
[Updated on: Tue, 06 June 2017 18:18] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3052 is a reply to message #3051] |
Sat, 10 June 2017 11:27   |
plasmo
Messages: 916 Registered: March 2017 Location: New Mexico, USA
|
Senior Member |
|
|
lynchaj wrote on Sat, 10 June 2017 10:04Interested in NS32K projects?
Yes and I've followed the discussion closely. BUT...I don't meant to be critical, but I thought it is too ambitious, at least for me. Since we are just dipping our toes in the NS32K processors, I thought we should start simple, small & cheap and experiencing the architecture of 32xxx at ground level. NS32008 with NS32202, DUART, RAM, Flash, CPLD, & IDE44 should fit in a cheap 100mm x 100mm 2-layer board. That's sufficient to learn NS32K assembly language, write a monitor/debugger in assembly and graduate to some sort of disk operating system. In fact, I already have a small hoard of NS32008 and I've contacted John Coffman to see if I can buy some NS32202 so I can pursue a simple, small, cheap solution. I know I'm not being a team player going off by myself like this, but NetBSD & high level language seem such a big leap and so disconnected from the heart & soul of 32xxx architecture, IMHO
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3053 is a reply to message #3052] |
Sun, 11 June 2017 00:19   |
pbirkel
Messages: 61 Registered: October 2015
|
Member |
|
|
plasmo wrote on Sat, 10 June 2017 11:27I thought it is too ambitious, at least for me. Since we are just dipping our toes in the NS32K processors, I thought we should start simple, small & cheap and experiencing the architecture of 32xxx at ground level. NS32008 with NS32202, DUART, RAM, Flash, CPLD, & IDE44 should fit in a cheap 100mm x 100mm 2-layer board. That's sufficient to learn NS32K assembly language, write a monitor/debugger in assembly and graduate to some sort of disk operating system. In fact, I already have a small hoard of NS32008 and I've contacted John Coffman to see if I can buy some NS32202 so I can pursue a simple, small, cheap solution.
FWIW, this is the entry-level that I'd like to eventually pursue, as well.
"experiencing the architecture of 32xxx at ground level" is a great summary statement :->!
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3054 is a reply to message #3052] |
Sun, 11 June 2017 07:10   |
lynchaj
Messages: 1080 Registered: June 2016
|
Senior Member |
|
|
plasmo wrote on Sat, 10 June 2017 14:27lynchaj wrote on Sat, 10 June 2017 10:04Interested in NS32K projects?
Yes and I've followed the discussion closely. BUT...I don't meant to be critical, but I thought it is too ambitious, at least for me. Since we are just dipping our toes in the NS32K processors, I thought we should start simple, small & cheap and experiencing the architecture of 32xxx at ground level. NS32008 with NS32202, DUART, RAM, Flash, CPLD, & IDE44 should fit in a cheap 100mm x 100mm 2-layer board. That's sufficient to learn NS32K assembly language, write a monitor/debugger in assembly and graduate to some sort of disk operating system. In fact, I already have a small hoard of NS32008 and I've contacted John Coffman to see if I can buy some NS32202 so I can pursue a simple, small, cheap solution. I know I'm not being a team player going off by myself like this, but NetBSD & high level language seem such a big leap and so disconnected from the heart & soul of 32xxx architecture, IMHO
Without an MMU there is no VM and no hope of NetBSD or any other sophisticated operating system. Its essentially just another 8 bit microcontroller with a neat 32 bit ISA. Interfacing to the outside world though is still just 8 bits. If you want to do that its OK but its not where my interests are.
I think NS's original goal was sophisticated operating systems which seems pretty obvious from their ISA, datasheets, and application notes. I think they settled for embedded controllers when Intel and Motorola beat them to market. I think the PC532 or something like it (Symmetric 375) is the way to go.
Good luck with your project though. Andrew Lynch
|
|
|
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3138 is a reply to message #3137] |
Sun, 02 July 2017 16:52   |
plasmo
Messages: 916 Registered: March 2017 Location: New Mexico, USA
|
Senior Member |
|
|
Some performance specs:
- The 68000 is running at 8MHz, serial port is 38.4k baud.
- Power consumption is 350mA at 5V.
- Memory access to the 16meg DRAM is zero wait state.
- Compactflash IDE is bus connected with 1 wait state access.
- CF (SanDisk as pictured) read access is 250K bytes/sec, write access is 45K bytes/sec.
- All 9 floppy disks from the CP/M v1.3 are copied into drive A which is 8 megabyte, block size of 2048 bytes and 512 directory entries.
- I allocated most of the 16meg memory for TPA which is from 0x20000 (just above CP/M) to 0xE20000, about 14 megabytes.
- Since this is my first CP/M machine, I have no speed reference. "DIR" command responds immediately, the bottleneck is the 38.4kbaud serial port. Is there a benchmark I can run against?
- I have not figured out how to block/deblock 128 byte/sector of CP/M into 512 byte/sector of the CF, so each 128-byte CP/M sector takes a full 512-byte CF sector--very wasteful, something to work on in the near term.
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3140 is a reply to message #3138] |
Sun, 02 July 2017 21:18   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
Congratulations! At this point, I can only imagine the joy of seeing your creation come to life, opening up a new world to explore and play in.
I've never actually used CPM either. Somehow just missed that whole thing. Almost got to 25-30 years ago with a Big Board but the 74138 was bad and the 8" floppies wouldn't work. So I wussed out and went back to Suns and Lisp Machines.
Mike
[Updated on: Sun, 02 July 2017 21:28] Report message to a moderator
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3141 is a reply to message #3140] |
Sun, 02 July 2017 21:27   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
I just read your updated Design page. I thought you were originally going to program the serial PROM through the USB Blaster. But I see you're now using an external programmer and that the serial PROM is socketed. Other than being easier to use the external programmer, was there a problem using the USB Blaster?
Mike
|
|
|
|
Re: Plasmo's 68k pathfinder projects [message #3144 is a reply to message #3143] |
Mon, 03 July 2017 13:03   |
mikemac
Messages: 250 Registered: March 2017
|
Senior Member |
|
|
Nope. I had thought you had figured out a way to program the AT24C256 in place through the MAX7000 using the USB Blaster. Similar to how you can flash some of the external configuration PROMs through some of Altera's FPGAs. I thought that would be a nifty trick to know if you had. I guess for the time being we're still stuck with socketed boot ROMs.
Mike
|
|
|
|
|
Current Time: Mon Mar 17 05:03:37 PDT 2025
Total time taken to generate the page: 0.00862 seconds
|