10 ms·
Motorola M68000 Family Programmer’s Reference Manual (1992) [pdf]
- alxlaz 9y agoI think one of the greatest things about the M68K today is that it's a relatively powerful processor that's relatively straightforward to program and it's pretty easy to design hardware that uses it. A single board computer with the m68k is still small enough that you can comprehend the schematics and build it at home (e.g. http://www.kswichit.com/68k/68k.html http://www.kswichit.com/68k/68k.html ), and it's a very valuable learning experience.
- juliangoldsmith 9y agoAre new M68K chips still produced? I looked a while ago, but couldn't find any.
- duskwuff 9y agoBarely. The 68SEC000 is still in production, but is NRND.
- 0xcde4c3db 9y agoWhat about the second-source vendors? Historically I know there were Hitachi ("HD" prefix), Toshiba ("TMP" prefix), and Signetics ("SN" prefix) parts. At one point I saw a modern-looking Atmel data sheet for a TS68C000 (Thomson/STMicro license?), but I don't know how recent that actually was. The Hitachi line, at least, seems to be explicitly EOL by Renesas. I'm not familiar enough with the other vendors to know who might have picked up their licenses.
- duskwuff 9y agoI suspect those are all gone too. TS68C000 went EOL in 2010 -- it was produced by Thomson-CSF, which was acquired by e2v. One interesting avenue to explore might be the Sega Genesis. It's still being produced in Brazil, believe it or not -- and there must be some sort of 68000-compatible processor at the core of those.
- yuhong 9y agoI think many was EOLed when the Freescale Sendai fab shut down.
- saagarjha 9y agoI'd assume so, since there are still many devices that use them!
- bryanlarsen 9y agoYes. They're known as ColdFire processors now, and they're sold by NXP.
- duskwuff 9y agoColdfire is a rather different product, though. The instruction set is similar but not identical, and there's no exposed memory bus. (Most of the parts have internal flash and SRAM, like a modern microcontroller.)
- MisterTea 9y ago> The instruction set is similar but not identical, and there's no exposed memory bus. Actually, there are a number of offerings in the coldfire v2/v3/v4family with decent performance and external buses including PCI, 10/100 ethernet, USB, ATA, and CAN with DDR memory and parallel bus interface. https://www.nxp.com/docs/en/data-sheet/MCF5307BUM.pdf https://www.nxp.com/docs/en/data-sheet/MCF5307BUM.pdf https://www.nxp.com/docs/en/data-sheet/MCF54418.pdf https://www.nxp.com/docs/en/data-sheet/MCF54418.pdf https://www.nxp.com/docs/en/data-sheet/MCF54455.pdf https://www.nxp.com/docs/en/data-sheet/MCF54455.pdf
- duskwuff 9y agoOh, the modern ones absolutely have other external busses -- but not a standard 68000 memory bus. There's no way to hook up an EEPROM with your program on it, for instance.
- MisterTea 9y agoI see what you are talking about. While the external bus interface on these cold fire parts is not a pin compatible m68k cpu bus, it certainly can access memory devices and uses DMA. From the 5307 manual: 1.3.7.1 External Bus Interface The bus interface controller transfers information between the ColdFire core or DMA and memory, peripherals, or other devices on the external bus.
- 9y ago
- mrpippy 9y agoNXP still makes a range of ColdFire-based chips, which is based on M68k
- joezydeco 9y agoThe 68K evolved into two lines: the Dragonball and, more recently, the ColdFire line. NXP is continuing production of the ColdFire parts. Dragonball evolved into the iMX line by swapping the 68K core for ARM. https://en.wikipedia.org/wiki/Freescale_DragonBall https://en.wikipedia.org/wiki/Freescale_DragonBall https://en.wikipedia.org/wiki/NXP_ColdFire https://en.wikipedia.org/wiki/NXP_ColdFire
- deleted 9y ago[deleted]
- bwldrbst 9y agoI've got one of these: http://apollo-core.com/index.htm http://apollo-core.com/index.htm in an Amiga. It's an insane amount of fun. "Apollo Core 68080 is the natural and modern evolution of latest 68000 processors. It's 100% code compatible, corrects bugs of 680x0 designs and adds on top most of the cool features which were invented the years after."
- jacobush 9y agoCheck this out. Apolle core should have a neon sign above it.
- alxlaz 9y agoAFAIK, no, at least not for the general market, but they're pretty easy to get on Ebay, AliExpress & friends.
- hermitdev 9y agoI used the 68K back in college for a couple of hardware/software codesign classes. It was a lot of fun and easy to work with. The boards we used were all wire-wrapped. No where near as clean as the kit you linked to. Still, was pretty easy to work with and fairly forgiving (I don't remember any of them burning up despite all of the crazy lab circuits we connected). Still have my Programmer's Reference Manual sitting on my shelf, sadly just collecting dust.
- ashleyn 9y agoAlso the processor the Sega Genesis uses, so you can learn to make your own Genesis game!
- zoenolan 9y agoGamehut has a series on doing that https://youtu.be/PSYhSmXBgIw https://youtu.be/PSYhSmXBgIw
- eludwig 9y agoThe 68K was such a glorious processor to program, especially after coming from the 6502. Hardware multiply and divide? Sign me up! :D The assembly code looked like poetry.
- Lionsion 9y agoI wish the m68k architecture had beat out Intel.
- sofaofthedamned 9y agoI actually connected on LinkedIn last year with Darek Mihocka, a guy who I last knew of 30-odd years ago. He'd made a Atari ST extension called (I think) Quick ST. The ST had awfully slow text output due to many things such as the interleaved bitmaps and lack of hardware assist. His made it much faster. I wrote a competitor that was faster than his. A couple of month later he wrote a new version that obliterated mine. I literally spent weeks trying to work out how he'd done it, went through the 68k reference manual, nothing. Then one day it came to me in an actual dream - 12 year old me actually woke up and started typing. It was the 'move.p' instruction. From memory this instruction split a 16 bit word into 2 bytes but aligned on a word (16 bit) boundary. I added this and my code then beat his. Bear in mind this was before the internet, so no to-and-fro with conversation, all I saw was what he did. It absolutely stood me in good stead for the rest of my career, each time now I see a programmer who writes something completely sloppy I ask them how it will scale. I really miss those days and wish somebody could bring this back for newer people to learn the basics.
- puzzle 9y agoI'm still proud of my shell sort implementation in 10 or 12 68K instructions. I was young, so it felt like a huge achievement. :-) That and helping a couple of demo coders shave an instruction or two from core loops. These days I yell at people because they build Docker images that take up several Gigabytes...
- sofaofthedamned 9y ago
- paulcole 9y agoDid anyone else get into ASM coding through the TI-89 (M68K) and TI-83 (Z80)? I had so much fun drawing sprites on graph paper and working on random projects and games I was thinking about. Sharing them with my friends through the cable that went into the headphone jacks. The fun of seeing somebody at my school I didn't really know getting a kick out of something I made.
- hermitdev 9y agoI did ASM on the TI-83 when I was in high school. Self-taught from the reference manual. Didn't know how to properly use the stack or write functions in ASM at the time...my code was a mess! Still, was quite a lot of fun with the only danger of having to yank the batteries if you messed up. By the time I got a TI-89 around 1999, I was in college and just didn't have the time to do anything substantive with programming it. I'd dust it off, but mine is old enough to just have the I/O port, and don't know that I have any functioning computers with a parallel or serial port for the old TI Link.
- duskwuff 9y agoThere are USB versions of the TI-Link. Alternatively, a while ago I used Emscripten to build an emulator for the TI Voyage 200 (a late revision of the TI-92). There's some minor glitches, but it's mostly functional: https://woofle.net/v200/ https://woofle.net/v200/
- freedomben 9y agoTI-89 was my gateway drug to 68k. I still have it on my desk actually, tho it's been in a box for the last 15 years.
- andreiw 9y agoAnyone else use the hex “assembler” on the TI-83+? After a while you just memorize the hex opcodes for z80 insns... TI-GCC for my TI-89 was nice...a few years back I tried to dust-off my IMSA-issued 89, and...it didn’t turn on. Sad. Replaced all batteries. Nothing... Then the flex connector on my 83+ started flaking out (the LCD corruption issue plaguing these...).
- protomyth 9y agoBack in the 80's, I wrote a letter to their documentation department asking how much certain manuals were (I was a fan). I got a box of manuals in the mail instead of a price list. They sent the references for both the 68000 and 6809. It was funny when I got to college and one of the EE courses involved programming of a 6809. Its a true shame their isn't a 64-bit 68000 as it is such a nicer processor than the x86.
- puzzle 9y agoThey never charged for manuals, as far as I know. I have a whole bookshelf of 68K and PPC books, datasheets and references.
- brlewis 9y agoI had the same experience with 6809E as a teenager. I have warm feelings toward Motorola to this day.
- ddingus 9y agoAs a high school kid, I got a ride to a local office to get docs. Picked up 68k, 6809 and various databooks. Not only were docs free, but the engineers there started up a good conversation. That I was a kid didn't matter much.
- slededit 9y agoZilog refused to send me Z80 manuals when I was a teenager. I was pretty sad. I did print out the datasheet but it wasn't the same.
- jonsen 9y agoNotice the high quality of documentation. Motorolas were some of the best as I remember it.
- puzzle 9y agoIt was definitely among the very best, but more than 15 years ago I found an error in the E500/Book E reference manual that repeated itself for more than 200 pages. It only was relevant to you if you cared about the actual bit encoding of SPE instructions. Plus there was a random reference to someone named Gary that, obviously, wasn't meant to be there. Motorola's PowerPC support hotline acknowledged the problem on the same day and published a new version of the manual by the end of the week or the next one. Of course they did, because that's how great they were.
- SmellyGeekBoy 9y agoBut what became of Gary?
- puzzle 9y agoThey never acknowledged Gary, but removed him anyway. The original said "Scalar floating-point instructions operate on single 32-bit operands that reside in the lower 32-bits of the GPRs. These instructions are considered a proper subset of the SPE APU; this subset is referred to as the SPFPU now called the EFPU Gary cares only that it have embedded in it somewhere." (more recent e500 chips considered the scalar instructions to be in a separate APU)
- jimjimjim 9y agoAn elegant weapon for a more civilized age.
- sofaofthedamned 9y ago68k was the easiest 'language' I ever learned. You had the reference manual, the instruction timings, no middleware, it was awesome and I made my future career from the age of 12 by writing Amiga / ST stuff. Best thing is - it was me against the machine. If anybody did something that moved more sprites than I did, or did better parallax, it was because they were better than I. No driver incompatibility to blame. I loved programming in 1984, it made me tolerate less shit and produce better code than people who were less fortunate to be born later. I miss those days :(
- segmondy 9y agoThere are still jobs for asm, C/C++ programmers where dependency on external libraries are not needed. I do understand tho, I miss those days too. My first 68k system was a sun 380.
- freedomben 9y agoI feel ya. The 68k days were glorious indeed. I'm sure things weren't really as good as I remember them, but man the nostalgia pull is real. I agree with the Raspberry Pi people, it's a lot harder to hack on stuff than it used to be.
- mrguyorama 9y agoI completely missed the heyday of microprocessor programming, but I wholeheartedly disagree that hacking on things is harder than it used to be. TI-84 calculators are $100 and let you write Z80 assembly, 68k microprocessors are available for less than $10 from any number of sources, easily available documentation and 30+ years of experience to draw on, freely available plans for whole systems so that you don't actually have to figure anything out yourself, or you can bypass all that and build your own processor in a circuit simulator, like I did, or learn HDL and buy a cheap FPGA and run it for real, or use something like python to control your parallel port with single lines of code connected to a webserver if you don't mind being silly. Heck, if I want to, I can even massively hack things, write kernel drivers for linux OR windows, do basically whatever I want. Some of them are harder than others, and some are more intended than others, and some require more time than others, but the world of hacking is still one of possibility. Pretty much the only locked down systems are smartphones, which sucks, but I just bought a raspberry Pi zero W for 10 dollars, which is incredible compared to the Basic Stamp 2 micro controller that cost $120 just a decade ago. Literally the only difficult (at least IMO) thing for hacking whatever you want is analog circuits. I still massively struggle with that.
- mistrial9 9y agoGood times ... EXCEPT ' you cannot move “word” or “long-word” sized data in and out of memory, if the address is an odd number' .. in other words, a hard fault.. This mis-feature can come up a lot, and was fixed in later CPUs. http://mrjester.hapisan.com/04_MC68/Sect01Part06/Index.html http://mrjester.hapisan.com/04_MC68/Sect01Part06/Index.html
- puzzle 9y agoWell, purists would have told you that you had to align your data. Yes, later chips did support misaligned accesses, but that came at a cost: extra bus cycles.
- phkahler 9y agoAnd now compilers will make sure your data structures are aligned. Adding circuitry and compromising performance for lazy programmers is a bad idea. This is one thing RISC-V has carried over and I'm not sure they have justified the decision to do so.
- userbinator 9y agoIn some cases, packing data structures with no alignment is more important because it means more data fits in the cache, and cache misses are extremely slow in comparison. Modern x86 is mostly insensitive to data alignment, since it fetches internally in cacheline-sized blocks (I believe it's 64 bytes) and a very wide barrel shifter is used to access the desired bytes. There's a tiny (single-digit cycles) extra time when the element straddles two cachelines (assuming both lines are in cache)
- baobrien 9y agoThe justification in the RISC-V spec is that it might make porting some software easier. They also say that unaligned loads/stores may be non-atomic and take much longer than aligned accesses -- allowing firmware emulation on simple implementations. The current atomic extension doesn't allow unaligned at all -- though I think there's an extension to allow atomic unaligned accesses in the works.
- jeffbarr 9y agoBack in the 1980's, I took one of these chips and ran four copies of the same OS on it, using some virtual memory and driver magic. The full story can be found at http://jeff-barr.com/2008/01/08/inmsx-running-4-copies-of-an-operating-system-at-once/ http://jeff-barr.com/2008/01/08/inmsx-running-4-copies-of-an... .
- Teknoman117 9y agothat was a fun read, thank you!
- gameshot911 9y agoWow dude, you're amazing! How are you able to dig so far into (extremely technical, difficult!) uncharted territory without getting diverted one way or another - frustration, "too hard", give up, etc.? ESPECIALLY since you did it all without the galaxies of information and well-tred paths available today!
- spc476 9y agoThere was no Internet to distract him.
- skissane 9y agoI'm always fascinated by old operating systems, especially ones which are different from Unix/Windows/etc. Do binaries still exist? Documentation? Source code?
- BackwardSpy 9y agoBrilliant read, thank you for sharing!
- rjsw 9y ago[turns to bookshelf] My copy is dated 1984.
- gtufano 9y agoI have an MC68000 User's Manual edited by Prentice-Hall with the HP logo (and an HP 9800 Computer Systems sub-title) that says December 1981.
- aoki 9y agomine as well (albeit 4th edition, 1984). which is sort of weird because i never saw or touched an M68k HP; i only ever referred to it when debugging stripped binaries on Sun 3s.
- bobpappas 9y agoI wrote this game in the 80's for the Mac in assembler. Loved the 68000! https://www.macintoshrepository.org/3331-macgolf-classic https://www.macintoshrepository.org/3331-macgolf-classic Wrote some others too: https://www.macintoshrepository.org/3732-macracquetball https://www.macintoshrepository.org/3732-macracquetball https://www.macintoshrepository.org/3384-road-racer https://www.macintoshrepository.org/3384-road-racer
- eludwig 9y agoOh my god!! I loved MacGolf!! I think that back in the day I used TMON to break the copy protection scheme (for personal use only, of course!) so many good memories. Thanks so much.
- danaliv 9y agoHey, I played that game on our Mac Plus! Or was it our LC II? Hard to remember the details now. :)
- indescions_2018 9y agoThanks for posting. Well before my time. But powered some legendary video game consoles such as SNK Neo-Geo and Sega 16. http://www.sega-16.com/ http://www.sega-16.com/
- deleted 9y ago[deleted]
- keithnz 9y agoI started with the 6502, but my second computer was an Atari STE and did a lot of 68k programming. It was great. Then I discovered the book "The Art of Electronics" as a late teen. It had a whole bunch on the 68008 ( which is gone from the current edition ) which was nice for little embedded projects as it interfacedd with the 8 bit world. https://en.wikipedia.org/wiki/Motorola_68008 https://en.wikipedia.org/wiki/Motorola_68008 later on I got to do some work on a 68030 series micro. That was pretty nice also. All assembly based.
- starchild_3001 9y agoBrings me back in memory lane, where I was a 13-14 yrs old middle-schooler trying to read this extremely thick manual with no or little background in logic design, CPUs etc. Well I could still program, or at the very least hack it to show some graphics, implement sinus scroll from scratch etc :)
- Fjolsvith 9y agoIn the Air Force, I went to school to learn how to repair and maintain an 18 bit Hewitt-Rand mainframe computer in 1988. It was a four month course taught at Tyndall AFB near Panama City Beach, Florida. At the time, I was an Amiga fan, and I had this manual. I was totally blown away at how nearly identical the architecture of the M68000 was compared to that mainframe. Imagine my thinking that my Amiga 500 had the equivalent of a room-sized mainframe in that chip!
- TheMagicHorsey 9y agoWhat is the modern equivalent that kids can use today? Arduino?
- watersb 9y agoI am not qualified to answer, so here I go: If in the USA: Hack a TI-89 calculator. They are still 68K-based, are unfortunately inescapable bricks tied to mandated Maths curriculum, and have an active hacking community. I re-learned M68K programming via the Palm Pilot, which has a fun SDK clearly inspired by the Classic Macintosh. I would say that ARM programming can be as fun as 68K, so perhaps a Raspberry Pi to start. You can get closer to the glory days with ARM-M Arduino-like toys such as the Teensy. I haven’t done any assembly-level Arduino programming, so I don’t know what that feels like versus 68K. Lots of microcontrollers grew upwards out of the then-popular 8051, which does not feel the same to me. I got started on the Motorola 6809 CPU and the TRS-80 Color Computer. You could almost call it an 8-bit precursor to the M68K, it is limited but very nice design.
- pjmlp 9y agoYep, here is a possible starting point with ARM Assembly on the PI. https://www.cl.cam.ac.uk/projects/raspberrypi/tutorials/os/introduction.html https://www.cl.cam.ac.uk/projects/raspberrypi/tutorials/os/i...
- HeyLaughingBoy 9y agoPOKE 65495, 0 :-)
- pskisf 9y agoI still program the 68K today in K&R C. I recently released a Dropbox client for Tandy XENIX. http://pski.net/trs-box-xenix/ http://pski.net/trs-box-xenix/
- phendrenad2 9y agoI read old processor manuals for fun as a kid. 68k, x86, the rare ARM or SPARC book...
- TomMasz 9y agoOh, the memories. Being able to predict the exact instructions the compiler would generate. Patching in memory using NOP instructions. Actually being able to write assembler code. Unsegmented memory. It has always disappointed me that Motorola didn't do better in microprocessors but that's water under the bridge.