is still alive and kicking and I think that's awesome! Anyone care to share any other groups you're part of that's 68k related?
-Mux
Yep, pretty cool that m68k is alive and well.
I've come into a supply of 68000 and 68008 chips, and plan a couple of >projects around them. Just subscribed to this group tonight :-)
On Wednesday, February 24, 2016 at 6:42:07 PM UTC+11, Zach Metzinger wrote:
Yep, pretty cool that m68k is alive and well.
As long as you don't mind a post/response time in this group that would have been considered slow back in the 17th century for mail between Australia and the UK...
I'm also reminded of the "I'm not dead" line in:
https://en.wikiquote.org/wiki/Monty_Python_and_the_Holy_Grail
If you have questions about your 68k chips, you might be better off here:
https://community.freescale.com/community/coldfire/content
ColdFire's "not quite dead yet" either...
I've come into a supply of 68000 and 68008 chips, and plan a couple of
projects around them. Just subscribed to this group tonight :-)
Very awesome!
Do you have some firmware and cross compiler for it?
I used a 68008 board not so long ago.
My web page includes the monitor source:
http://ferretronix.com/tech/sbc/index.html#68k
This may help:
Application Note AN897 "MC68008 minimum configuration"
http://ferretronix.com/tech/68k/an897.fsl.d.rev0.pdf
I used a 68008 board not so long ago.
My web page includes the monitor source:
http://ferretronix.com/tech/sbc/index.html#68k
He even lists that same app note. Do you, by chance, know where I might
find the AR226 article he mentions?
--- Zach
Le 25/02/2016 07:53, Zach Metzinger a écrit :
He even lists that same app note. Do you, by chance, know where I mightHello,
find the AR226 article he mentions?
--- Zach
Maybe AR226 is a reprint of this article:
Designing with the 68008 Microprocessor (WirelessWorld 1984)?
Available here: www.retronik.fr/motorola
On 10/27/15 15:11, Mux wrote:
is still alive and kicking and I think that's awesome! Anyone care to
share any other groups you're part of that's 68k related?
-Mux
Yep, pretty cool that m68k is alive and well.
I've come into a supply of 68000 and 68008 chips, and plan a couple of projects around them. Just subscribed to this group tonight :-)
--- Zach
Hi,
I recently got a 68008 working (i.e. loading scode) with 3 ttl chips, rom, ram (512+128K) and 68681. But I have to admit - I used a pcb (10*10cm). Amazing how many errors you can do in a project - even after you are sure it MUST be correct.
But very rewarding to succeed!
Hi, Zach. Welcome to the group!
Since you're a fan of *ix, you might like http://www.bigmessowires.com/68-katy/
Linux on a breadboard!
PS: My 68010 homebrew currently has ~DTACK permanently grounded. Memories are faster than they were when the CPU came out!
Did you keep the ROM at 0x00000000 and use jumps in the interrupt vector table, or did you do the cycle-count-and-swap-ROM-for-RAM trick?
It's pretty easy to do the latter in my address decoder PAL, and I understand that most existing code expects that behavior.
--- Zach
Hi,
I recently got a 68008 working (i.e. loading scode) with 3 ttl chips, rom, ram (512+128K) and 68681. But I have to admit - I used a pcb (10*10cm). Amazing how many errors you can do in a project - even after you are sure it MUST be correct.
But very rewarding to succeed!
On 02/25/16 15:15, Ola wrote:
Hi,
I recently got a 68008 working (i.e. loading scode) with 3 ttl chips, rom, ram (512+128K) and 68681. But I have to admit - I used a pcb (10*10cm). Amazing how many errors you can do in a project - even after you are sure it
MUST be correct.
But very rewarding to succeed!
Did you keep the ROM at 0x00000000 and use jumps in the interrupt vector table, or did you do the cycle-count-and-swap-ROM-for-RAM trick?
It's pretty easy to do the latter in my address decoder PAL, and I
understand that most existing code expects that behavior.
--- Zach
On 02/25/16 15:15, Ola wrote:
Hi,
I recently got a 68008 working (i.e. loading scode) with 3 ttl chips, rom, ram (512+128K) and 68681. But I have to admit - I used a pcb (10*10cm). Amazing how many errors you can do in a project - even after you are sure it
MUST be correct.
But very rewarding to succeed!
Did you keep the ROM at 0x00000000 and use jumps in the interrupt vector table, or did you do the cycle-count-and-swap-ROM-for-RAM trick?
It's pretty easy to do the latter in my address decoder PAL, and I
understand that most existing code expects that behavior.
--- Zach
On Thursday, 25 February 2016 21:15:39 UTC, Ola wrote:
Hi,
I recently got a 68008 working (i.e. loading scode) with 3 ttl chips, rom, ram (512+128K) and 68681. But I have to admit - I used a pcb (10*10cm). Amazing how many errors you can do in a project - even after you are sure it
MUST be correct.
But very rewarding to succeed!
Indeed!
I've been designing a board with a XR82C684 UART for, erm, longer than I care to think about! It claims to be 68000-compatible, though it still expects ME to turn its ~INT signal into ~IPL2/1/0 and generate an interrupt acknowledge [scowl].
I see from a Google search that Freescale (née Motorola Semiconductor) issues an End Of Life notice on the 68681 in 2009... but the NXP version seems readily available.
Amazing how many errors you can do in a project - even after you are sure it MUST be correct.
But very rewarding to succeed!
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 42:16:53 |
| Calls: | 6,648 |
| Files: | 12,193 |
| Messages: | 5,329,573 |
