--- Quote Start ---
Flaming responses aren't necessary.......Yes, we're all over the "why bother with 6809", but they have their place in certain scenarios that can't be bypassed.
--- Quote End ---
The response was not intended to be a flame. It was merely to check/confirm that you understood that sometimes you need to take a step further back and look at the big picture.
--- Quote Start ---
The picture is a lot bigger than perhaps i explained (trying to keep things simple).
Each board has a license code in its rom, and the controller software always checks the board during polling etc.
I would have initially built something with a pic to do the driving etc, but then the whole software/license is another can of worms worth avoiding.
--- Quote End ---
Can you clarify this a bit more ... Do you control the software, i.e., is it possible to modify the code? I suspect not, which is why its a can of worms :)
You still have the problem of matching the original code timing, so having the source code is critical, just so that you can see if there is a cycle-accuracy requirement.
--- Quote Start ---
Besides the above requirement, i would like to emulate 6809 or even Z80's in numerous legacy projects, believe it or not some people still use and enjoy that stuff, dont bag it !!!!
--- Quote End ---
I'm Ok with hobbies keeping ancient technology alive. However, your task involves heavy machinery, so does involve a level of risk, and hence a certain level of caution is required, i.e., you will need to prove that the new CPU board is functionally equivalent.
--- Quote Start ---
Thanx for the opencores link, it's something in the right direction.
--- Quote End ---
A few of the other 6809 links seemed to indicate this was the main source people were using. I am sure there is a forum with 6809 "archeologists" that could help :)
Cheers,
Dave
Honored Contributor
