开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Xpander ROM disassembly


 

Has anyone here attempted to disassemble the XPander or Matrix 12 ROMS?
If so, where is the dissembled source code at?

If not, what would you recommend using getting the ROM bin files that are separated
into even & odd addresses, into 1 contiguous file? I don't want to goof that up and make the job more difficult.


Thanks

Tony


 

I've not done this for the Xpander, but I have for the Prophet VS. I combined the roms into one file using Python - relatively simple script to load a byte from each file and interleave them. I then used IDA Pro to turn into code (68k for the VS). It's quite an interesting task to do, though I didn't get around to fully decompiling/commenting.

The xpander should be interesting as it uses a 6809 chip (68b09) as used in Robotron. Should be relatively easy to understand the code, though it will be very verbose and reliant on the other chips around it (so have a schematic handy to figure out the memory map)

Good luck!

On Tue, Jun 12, 2018 at 9:41 PM, Tony Cappellini cappy2112@... [xpantastic] <xpantastic@...> wrote:
?

Has anyone here attempted to disassemble the XPander or Matrix 12 ROMS?
If so, where is the dissembled source code at?

If not, what would you recommend using getting the ROM bin files that are separated
into even & odd addresses, into 1 contiguous file? I don't want to goof that up and make the job more difficult.


Thanks

Tony



 

I had tried to do this to the VS but came up short... I've interleaved the ROMs and the single file works in a VS emulator, but I cant seem to figure out getting it into assembly in IDA. Any tips? You can email so we don't spam the Xpander thread. Thanks!


 

Hi Tony, if you're willing to share, I'm curious to know what your plans are for the code??


 

If I can get it disassembled- correctly I will. I don't have any serious plans other than looking through it to see what might jump out.

I don't know if I'll get around to adding any comments, since I've never done any real disassembly before.


On Wed, Jun 13, 2018 at 1:45 PM mattvrazo@... [xpantastic] <xpantastic@...> wrote:
?

Hi Tony, if you're willing to share, I'm curious to know what your plans are for the code??


 

Hi Tony,
I have written tons of assembly code for a Motorolla 68HC11 which has a similar instruction set. I would be willing to help with this project any way I can.
I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
BTW? there are two sets of firmware for the Xpander / M12.?One set of?for the system CPU and one set for the voice boards. ?I imagine you are talking about the code for the system cpu ?

Best Regards

Karl


On Wednesday, June 13, 2018 3:48 PM, "Tony Cappellini cappy2112@... [xpantastic]" wrote:


?
If I can get it disassembled- correctly I will. I don't have any serious plans other than looking through it to see what might jump out.

I don't know if I'll get around to adding any comments, since I've never done any real disassembly before.


On Wed, Jun 13, 2018 at 1:45 PM mattvrazo@... [xpantastic] <xpantastic@...> wrote:
?
Hi Tony, if you're willing to share, I'm curious to know what your plans are for the code??



 

开云体育

Hi Karl !

A bit O.T. but ...

Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page.

The limitation are the modulation busses,- pedals #1 & #2 and levers #1 & #2,- which isnt enough, especially vs. the count of modulation destinations in the mod-matrix.
So, when there were a chance maxing out modulation busses in the sense of mod-sources, that would be most excellent.

Theres a bug in Multipatch-Mode when changing multi-patches via MIDI PrgCh. while MIDI CC#07 is assigned to "pedal #2" as a source and a value is being received.
The volume drops to zero then and it needs another MIDI CC#07=127 command to get some noise back from the synth.

Im pretty sure its a bug because "lever #2 and "pedal #2" are "universal" (global) controllers while lever and pedal #1 work individual for each voice.
So, in Multipatch Mode, MIDI CC#07 should be the master volume controller which should work when sending a program change and volume offset command,- but it doesnt because theres no guarantee, the volume command arrives after the program change in exact sequential order when being transmitted from p.ex. a MIDI processor/matrix switcher or masterkeyboard.
A sequencer might handle that different compared to the devices mentioned above though.

In addition to the "master volume" functionality in "Multipatch-Mode", individual / relative volume control (not overriding MIDI CC#07 value !) for each voice should work using MIDI CC#11 together w/ MIDI CC#07 and w/o dropping overall volume to zero.
But even when we can get rid of the bug mentioned above, in Multipatch-Mode using MIDI CC#07 and MIDI CC#11 simultaneously eats up both pedals as modulation sources and makes it impossible using MIDI CC#04 for filter cutoff, may it be per voice or global,- WHEN the mod wheel is in use for vibrato p.ex..

So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
I dunno if thats doable via software at all, but it would be great if it were.

Anyway,- now some private stuff and because its the occasion to send some lines ...

I received and still do receive all your emails, but when I reply, ALL the emails I send to shire03@... come back to me as a mailer demon after exactly 4 (FOUR !!!) days.
I regret and have no idea what causes that behaviour, but we should try to find another way for private communication I think.
Maybe PMs @ Keybd Corner ... (???) ... what do you think ?
Please reply to my private email addy 1st.
When you agree, you might post something over there,- Ill recognize and will jump in via PM.
Let me know please.

thx for reading

:-)

PeWe


Am 14.06.2018 um 00:02 schrieb Karl Schmeer shire03@... [xpantastic]:


I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
Best Regards


Karl





 

FYI- thanks everyone for replying.

I think some of you may have gotten the wrong idea about my post.
I’m not planning on adding any features, nor extensively document the hopefully-forthcoming disassembly.
I don’t think I have the experience that deserves. My intent was simply to see how’ve the cassette dump works, just for my own education.

I am mor than happy to share what I find (if anything), as well as the disassembly (which will be very ra and crude), and of course talk all of this over on the list.

Regarding adding features- there’s is very littke code space left, I’m not sure how much could be added, even if we had documented sources.


I am off for vacation for 2 weeks, so no work on this will take place until closer to the end of the month.
Until then- keep on patching!


On Wed, Jun 13, 2018 at 1:45 PM mattvrazo@... [xpantastic] <xpantastic@...> wrote:
?

Hi Tony, if you're willing to share, I'm curious to know what your plans are for the code??


 


PeWe Wrote:

>>"So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
>> I dunno if that?s doable via software at all, but it would be great if it were."

Hi PeWe,
This is what I am talking about.?? Permanently assigning some parameters to midi CC's??like many current synths are capable of doing. Yes it would take
a considerable amount of understanding of the firmware, but it should be possible if enough room could be found in the ROMS. If not just have to use the slower
sysex method.
Another possibility:
I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment. Using this technique it may be possible to allow more room?
for added features.?But I have not fully investigated this yet.

Sent you a PM

Best Karl



On Wednesday, June 13, 2018 10:12 PM, "PeWe ha-pewe@... [xpantastic]" wrote:


?
Hi Karl !

A bit O.T. but ...

Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page.

The limitation are the modulation busses,- pedals #1 & #2 and levers #1 & #2,- which isn?t enough, especially vs. the count of modulation destinations in the mod-matrix.
So, when there were a chance maxing out modulation busses in the sense of mod-sources, that would be most excellent.

There?s a bug in Multipatch-Mode when changing multi-patches via MIDI PrgCh. while MIDI CC#07 is assigned to "pedal #2" as a source and a value is being received.
The volume drops to zero then and it needs another MIDI CC#07=127 command to get some noise back from the synth.

I?m pretty sure it?s a bug because "lever #2 and "pedal #2" are "universal" (global) controllers while lever and pedal #1 work individual for each voice.
So, in Multipatch Mode, MIDI CC#07 should be the master volume controller which should work when sending a program change and volume offset command,- but it doesn?t because there?s no guarantee, the volume command arrives after the program change in exact sequential order when being transmitted from p.ex. a MIDI processor/matrix switcher or masterkeyboard.
A sequencer might handle that different compared to the devices mentioned above though.

In addition to the "master volume" functionality in "Multipatch-Mode", individual / relative volume control (not overriding MIDI CC#07 value !) for each voice should work using MIDI CC#11 together w/ MIDI CC#07 and w/o dropping overall volume to zero.
But even when we can get rid of the bug mentioned above, in Multipatch-Mode using MIDI CC#07 and MIDI CC#11 simultaneously eats up both pedals as modulation sources and makes it impossible using MIDI CC#04 for filter cutoff, may it be per voice or global,- WHEN the mod wheel is in use for vibrato p.ex..

So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
I dunno if that?s doable via software at all, but it would be great if it were.

Anyway,- now some private stuff and because it?s the occasion to send some lines ...

I received and still do receive all your emails, but when I reply, ALL the emails I send to shire03@... come back to me as a mailer demon after exactly 4 (FOUR !!!) days.
I regret and have no idea what causes that behaviour, but we should try to find another way for private communication I think.
Maybe PMs @ Keybd Corner ... (???) ... what do you think ?
Please reply to my private email addy 1st.
When you agree, you might post something over there,- I?ll recognize and will jump in via PM.
Let me know please.

thx for reading

:-)

PeWe
?

Am 14.06.2018 um 00:02 schrieb Karl Schmeer shire03@... [xpantastic]:

?

I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
Best Regards


Karl







 

Karl,

>>I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment.
there are 4 8K ROMS, and 3 8K RAMS?on the processor board, two ROMS and two RAMS on the voice board.

The 6809 only has a 64K address space. 56K of address space is already used on the processor board.
Unless you put in a?whole new circuit board to do bank switching (and rewrite the FW to go with it), you won't be able to use larger EEPROMS.


On Thu, Jun 14, 2018 at 9:03 AM, Karl Schmeer shire03@... [xpantastic] <xpantastic@...> wrote:
?


PeWe Wrote:

>>"So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
>> I dunno if that?s doable via software at all, but it would be great if it were."

Hi PeWe,
This is what I am talking about.?? Permanently assigning some parameters to midi CC's??like many current synths are capable of doing. Yes it would take
a considerable amount of understanding of the firmware, but it should be possible if enough room could be found in the ROMS. If not just have to use the slower
sysex method.
Another possibility:
I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment. Using this technique it may be possible to allow more room?
for added features.?But I have not fully investigated this yet.

Sent you a PM

Best Karl



On Wednesday, June 13, 2018 10:12 PM, "PeWe ha-pewe@... [xpantastic]" <xpantastic@...> wrote:


?
Hi Karl !

A bit O.T. but ...

Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page.

The limitation are the modulation busses,- pedals #1 & #2 and levers #1 & #2,- which isn?t enough, especially vs. the count of modulation destinations in the mod-matrix.
So, when there were a chance maxing out modulation busses in the sense of mod-sources, that would be most excellent.

There?s a bug in Multipatch-Mode when changing multi-patches via MIDI PrgCh. while MIDI CC#07 is assigned to "pedal #2" as a source and a value is being received.
The volume drops to zero then and it needs another MIDI CC#07=127 command to get some noise back from the synth.

I?m pretty sure it?s a bug because "lever #2 and "pedal #2" are "universal" (global) controllers while lever and pedal #1 work individual for each voice.
So, in Multipatch Mode, MIDI CC#07 should be the master volume controller which should work when sending a program change and volume offset command,- but it doesn?t because there?s no guarantee, the volume command arrives after the program change in exact sequential order when being transmitted from p.ex. a MIDI processor/matrix switcher or masterkeyboard.
A sequencer might handle that different compared to the devices mentioned above though.

In addition to the "master volume" functionality in "Multipatch-Mode", individual / relative volume control (not overriding MIDI CC#07 value !) for each voice should work using MIDI CC#11 together w/ MIDI CC#07 and w/o dropping overall volume to zero.
But even when we can get rid of the bug mentioned above, in Multipatch-Mode using MIDI CC#07 and MIDI CC#11 simultaneously eats up both pedals as modulation sources and makes it impossible using MIDI CC#04 for filter cutoff, may it be per voice or global,- WHEN the mod wheel is in use for vibrato p.ex..

So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
I dunno if that?s doable via software at all, but it would be great if it were.

Anyway,- now some private stuff and because it?s the occasion to send some lines ...

I received and still do receive all your emails, but when I reply, ALL the emails I send to shire03@... come back to me as a mailer demon after exactly 4 (FOUR !!!) days.
I regret and have no idea what causes that behaviour, but we should try to find another way for private communication I think.
Maybe PMs @ Keybd Corner ... (???) ... what do you think ?
Please reply to my private email addy 1st.
When you agree, you might post something over there,- I?ll recognize and will jump in via PM.
Let me know please.

thx for reading

:-)

PeWe
?

Am 14.06.2018 um 00:02 schrieb Karl Schmeer shire03@... [xpantastic]:
?

I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
Best Regards


Karl








 



On Thursday, June 14, 2018 11:14 AM, "Tony Cappellini cappy2112@... [xpantastic]" wrote:


?
>Karl,

>>>>I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment.
>there are 4 8K ROMS, and 3 8K RAMS?on the processor board, two ROMS and two RAMS on the voice board.

>The 6809 only has a 64K address space. 56K of address space is already used on the processor board.
>Unless you put in a?whole new circuit board to do bank switching (and rewrite the FW to go with it), you won't be able to use larger EEPROMS.

That's too bad. Like I said I had not fully investigated it.?
?????????????????








 

Exactly. Of course, if people are happy for board mods, there's a chunk of address space which is just being mirrored for the dealing with output (ie, the last 4k iirc which actually just has something like 12 output addresses). But to get into there, you'll need to add some wires and some logic gates -- far beyond a simple hack.

The best chance to add in new behaviour is if the code in the ROMs isn't particularly optimized for space. It's a long shot though. You might be able to claw back a few bytes here and there, but then you have the challenge of making a big enough hole to then do something worthwhile without breaking the existing code. It could be an interesting project for someone to look into this, and the sheer challenge of understanding code from the disassembly is kinda fun.

//deano

On Thu, Jun 14, 2018 at 5:14 PM, Tony Cappellini cappy2112@... [xpantastic] <xpantastic@...> wrote:
?

Karl,

>>I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment.
there are 4 8K ROMS, and 3 8K RAMS?on the processor board, two ROMS and two RAMS on the voice board.

The 6809 only has a 64K address space. 56K of address space is already used on the processor board.
Unless you put in a?whole new circuit board to do bank switching (and rewrite the FW to go with it), you won't be able to use larger EEPROMS.


On Thu, Jun 14, 2018 at 9:03 AM, Karl Schmeer shire03@... [xpantastic] <xpantastic@...> wrote:
?


PeWe Wrote:

>>"So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
>> I dunno if that?s doable via software at all, but it would be great if it were."

Hi PeWe,
This is what I am talking about.?? Permanently assigning some parameters to midi CC's??like many current synths are capable of doing. Yes it would take
a considerable amount of understanding of the firmware, but it should be possible if enough room could be found in the ROMS. If not just have to use the slower
sysex method.
Another possibility:
I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment. Using this technique it may be possible to allow more room?
for added features.?But I have not fully investigated this yet.

Sent you a PM

Best Karl



On Wednesday, June 13, 2018 10:12 PM, "PeWe ha-pewe@... [xpantastic]" <xpantastic@...> wrote:


?
Hi Karl !

A bit O.T. but ...

Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page.

The limitation are the modulation busses,- pedals #1 & #2 and levers #1 & #2,- which isn?t enough, especially vs. the count of modulation destinations in the mod-matrix.
So, when there were a chance maxing out modulation busses in the sense of mod-sources, that would be most excellent.

There?s a bug in Multipatch-Mode when changing multi-patches via MIDI PrgCh. while MIDI CC#07 is assigned to "pedal #2" as a source and a value is being received.
The volume drops to zero then and it needs another MIDI CC#07=127 command to get some noise back from the synth.

I?m pretty sure it?s a bug because "lever #2 and "pedal #2" are "universal" (global) controllers while lever and pedal #1 work individual for each voice.
So, in Multipatch Mode, MIDI CC#07 should be the master volume controller which should work when sending a program change and volume offset command,- but it doesn?t because there?s no guarantee, the volume command arrives after the program change in exact sequential order when being transmitted from p.ex. a MIDI processor/matrix switcher or masterkeyboard.
A sequencer might handle that different compared to the devices mentioned above though.

In addition to the "master volume" functionality in "Multipatch-Mode", individual / relative volume control (not overriding MIDI CC#07 value !) for each voice should work using MIDI CC#11 together w/ MIDI CC#07 and w/o dropping overall volume to zero.
But even when we can get rid of the bug mentioned above, in Multipatch-Mode using MIDI CC#07 and MIDI CC#11 simultaneously eats up both pedals as modulation sources and makes it impossible using MIDI CC#04 for filter cutoff, may it be per voice or global,- WHEN the mod wheel is in use for vibrato p.ex..

So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
I dunno if that?s doable via software at all, but it would be great if it were.

Anyway,- now some private stuff and because it?s the occasion to send some lines ...

I received and still do receive all your emails, but when I reply, ALL the emails I send to shire03@... come back to me as a mailer demon after exactly 4 (FOUR !!!) days.
I regret and have no idea what causes that behaviour, but we should try to find another way for private communication I think.
Maybe PMs @ Keybd Corner ... (???) ... what do you think ?
Please reply to my private email addy 1st.
When you agree, you might post something over there,- I?ll recognize and will jump in via PM.
Let me know please.

thx for reading

:-)

PeWe
?

Am 14.06.2018 um 00:02 schrieb Karl Schmeer shire03@... [xpantastic]:
?

I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
Best Regards


Karl









min struct
 

Hello,
Would this work bring any chance to be able to replace the 6809 CPU with an upgraded reference ?
What would happen if the CPU frequency would be 4 times the original one ? Would it be possible to speed up the software envelopes ? or some software modulation sources ?
Or would it be a mess for the other controls ?
(Prophet600 Z80's Teensy upgrade by Gligli in mind)
thanks

2018-06-14 18:14 GMT+02:00 Tony Cappellini cappy2112@... [xpantastic] <xpantastic@...>:

?

Karl,

>>I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment.
there are 4 8K ROMS, and 3 8K RAMS?on the processor board, two ROMS and two RAMS on the voice board.

The 6809 only has a 64K address space. 56K of address space is already used on the processor board.
Unless you put in a?whole new circuit board to do bank switching (and rewrite the FW to go with it), you won't be able to use larger EEPROMS.


On Thu, Jun 14, 2018 at 9:03 AM, Karl Schmeer shire03@... [xpantastic] <xpantastic@...> wrote:
?


PeWe Wrote:

>>"So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
>> I dunno if that?s doable via software at all, but it would be great if it were."

Hi PeWe,
This is what I am talking about.?? Permanently assigning some parameters to midi CC's??like many current synths are capable of doing. Yes it would take
a considerable amount of understanding of the firmware, but it should be possible if enough room could be found in the ROMS. If not just have to use the slower
sysex method.
Another possibility:
I have seen guys use larger EEPROMs to condense the size of memory in some HP test equipment. Using this technique it may be possible to allow more room?
for added features.?But I have not fully investigated this yet.

Sent you a PM

Best Karl



On Wednesday, June 13, 2018 10:12 PM, "PeWe ha-pewe@... [xpantastic]" <xpantastic@...> wrote:


?
Hi Karl !

A bit O.T. but ...

Assigning MIDI CCs to Xpander-parameters like VCF cutoff and MIDI volume works on my Xpander uising the MIDI Controls page.

The limitation are the modulation busses,- pedals #1 & #2 and levers #1 & #2,- which isn?t enough, especially vs. the count of modulation destinations in the mod-matrix.
So, when there were a chance maxing out modulation busses in the sense of mod-sources, that would be most excellent.

There?s a bug in Multipatch-Mode when changing multi-patches via MIDI PrgCh. while MIDI CC#07 is assigned to "pedal #2" as a source and a value is being received.
The volume drops to zero then and it needs another MIDI CC#07=127 command to get some noise back from the synth.

I?m pretty sure it?s a bug because "lever #2 and "pedal #2" are "universal" (global) controllers while lever and pedal #1 work individual for each voice.
So, in Multipatch Mode, MIDI CC#07 should be the master volume controller which should work when sending a program change and volume offset command,- but it doesn?t because there?s no guarantee, the volume command arrives after the program change in exact sequential order when being transmitted from p.ex. a MIDI processor/matrix switcher or masterkeyboard.
A sequencer might handle that different compared to the devices mentioned above though.

In addition to the "master volume" functionality in "Multipatch-Mode", individual / relative volume control (not overriding MIDI CC#07 value !) for each voice should work using MIDI CC#11 together w/ MIDI CC#07 and w/o dropping overall volume to zero.
But even when we can get rid of the bug mentioned above, in Multipatch-Mode using MIDI CC#07 and MIDI CC#11 simultaneously eats up both pedals as modulation sources and makes it impossible using MIDI CC#04 for filter cutoff, may it be per voice or global,- WHEN the mod wheel is in use for vibrato p.ex..

So, the Xpander/ Matrix-12 needs more modulation busses/channels on the modulation-input side.
I dunno if that?s doable via software at all, but it would be great if it were.

Anyway,- now some private stuff and because it?s the occasion to send some lines ...

I received and still do receive all your emails, but when I reply, ALL the emails I send to shire03@... come back to me as a mailer demon after exactly 4 (FOUR !!!) days.
I regret and have no idea what causes that behaviour, but we should try to find another way for private communication I think.
Maybe PMs @ Keybd Corner ... (???) ... what do you think ?
Please reply to my private email addy 1st.
When you agree, you might post something over there,- I?ll recognize and will jump in via PM.
Let me know please.

thx for reading

:-)

PeWe
?

Am 14.06.2018 um 00:02 schrieb Karl Schmeer shire03@... [xpantastic]:
?

I would love to "enhance" the original code to allow some midi cc of parameters like filter, envelope times etc.. As well as allow midi volume control (cc #7).
Best Regards


Karl









 

开云体育

>>>

Am 15.06.2018 um 00:20 schrieb min struct min.struct@... [xpantastic]:
Hello,
Would this work bring any chance to be able to replace the 6809 CPU with an upgraded reference ?
What would happen if the CPU frequency would be 4 times the original one ?

When speeding up CPU frequency by the facor of 4,- in a synthwhere lots of modulators are realized in software, almost everything speeds up in relation,- LFO rate p.ex. and even the actually slowest possible rate.
Same w/ ENV segment times (Delay, A, D & R), Ramp times, Portamento times and so on.
No sound formerly being programmed and stored into memory would sound the same like it does today.

I know well because they got that issue w/ the "Musitronics" SpeedKit for the D50/550 w/ the target making the synth tighter when playing chords.
They got it, but after they had speed up the processor by a factor of 4 (theres a daughterboard which fits the original socket, which also offers 3 more memory banks and a 2nd/separate battery in addition as also they replaced the original quartz making the clock more accurate) they had to slow down those rates mentioned above to make the synth sounding the same as it did w/ the original processor, quartz and firmware.

Would it be possible to speed up the software envelopes ? or some software modulation sources ?

In case of the ENVs, you want to make em snappier, not faster ... thats the Attack/Decay times and probably also slope ...
For LFOs, you might want em to go faster (audio rate), but want em as slow as tthey originally go,- or slower in addition.
Same for Ramps.
And those things are all realized in software in Xpander/ M12


Or would it be a mess for the other controls ?

not urgently when done right.

:-)

P.


 

开云体育

>>>

Am 14.06.2018 um 18:03 schrieb Karl Schmeer shire03@... [xpantastic]:

Sent you a PM

Best Karl

I got it,- thx !

I doubt theres a "o" / "0" problem when using your original email or when replying on your mails, just because replying means clicking the button [reply].

You announced providing a gmail-addy in that 2017 email ... but it never happened.
Anyway,- Ill reply on your email now and hope it works again.

When you wont receive it within 4 days, we have the same issue than before.

:-)

PeWe




 

Hitachi makes a pin and instruction compatible CPU (6309), I don’t know if they make the B variant though.

This CPU can run up to 4 MHZ, where’s the 6809 maxes out at 1.89 or so.
There are additional registers an instructions in the 6309 when running in enhanced mode, that offer additional features, notably performance enhancements.

However the ROMS would need to be rewritten to take advantage of the new speed, and it is highly likely a lot of peripheral hardware
Would be affected. With the higher performance, it may be possible to add new features in the same 64K addressing space, because of the extra instructions and registers. It would be a monumental effort though, and a lot of time.

No silver bullet there.



On Thu, Jun 14, 2018 at 5:20 PM PeWe ha-pewe@... [xpantastic] <xpantastic@...> wrote:

>>>

Am 15.06.2018 um 00:20 schrieb min struct min.struct@... [xpantastic]:
?
Hello,
Would this work bring any chance to be able to replace the 6809 CPU with an upgraded reference ?
What would happen if the CPU frequency would be 4 times the original one ?

When speeding up CPU frequency by the facor of 4,- in a synthwhere lots of modulators are realized in software, almost everything speeds up in relation,- LFO rate p.ex. and even the actually slowest possible rate.
Same w/ ENV segment times (Delay, A, D & R), Ramp times, Portamento times and so on.
No sound formerly being programmed and stored into memory would sound the same like it does today.

I know well because they got that issue w/ the "Musitronics" SpeedKit for the D50/550 w/ the target making the synth tighter when playing chords.
They got it, but after they had speed up the processor by a factor of 4? (there?s a daughterboard which fit?s the original socket, which also offers 3 more memory banks and a 2nd/separate battery in addition as also they replaced the original quartz making the clock more accurate) they had to slow down those rates mentioned above to make the synth sounding the same as it did w/ the original processor, quartz and firmware.



Would it be possible to speed up the software envelopes ? or some software modulation sources ?

In case of the ENVs, you want to make ?em snappier, not faster ... that?s the Attack/Decay times and probably also slope ...
For LFOs, you might want ?em to go faster (audio rate), but want ?em as slow as tthey originally go,- or slower in addition.
Same for Ramps.
And those things are all realized in software in Xpander/ M12




Or would it be a mess for the other controls ?

not urgently when done right.

:-)

P.


 


Hi,
FYI, 6 years ago a guy called Christophe Janot posted some messages in the Xpantastic forum about this.
I did had some exchanges with him outside Xpantastic. He was building a kind of clone of Matrix 12 with extra functionalities.
Here is what he said at the time about the CPU (translated):

"Otherwise, from what I understood from the architecture, the two CPUs operate completely asynchronously and can therefore work at different frequencies. It is also quite possible to boost the CPU of the analog card up to 3.5Mhz (instead of 2Mhz) by replacing it with a 63C09P. I use this CPU on my main board (but 2Mhz). Now, there is a timer on the analog board, and I wondered if it was not used to clock the generation of different modulations. If this were the case, it would be necessary to modify the firmware to program it differently. I also wondered if the main DAC would be able to support the additional data rate caused by the increase in CPU frequency."

He was prototyping his clone on a xmos/xcore evaluation card, and wanted to put everything open source à la Mutable Instruments.

I did get no news from him on the internet since this time.
The last status I had at the time (sept. 2012)? is that he was able to boot the native rom images and load the presets.
I have no news since.

Regards,



?


 

Sorry for a little bit of offtop.
But I did not find the right particular topic for my question.
So to my view this topic looks like a proper place to ask.

Will?
?
[url]http://dbwbp.com/synthbin/Oberheim%20Matrix%2012%20(Japanese%20Edition)%20CPU%20&%20Voice%20EPROMs.zip[/url]
?
or?
?
[url]http://dbwbp.com/synthbin/Oberheim%20Matrix%2012%20(Japan%20version).zip[/url]
?
or?
?
[url]https://www.vintagesynthshop.com/Oberheim-Matrix-12-OS-1-6-Rom-Firmware-bbaaaaqba.asp[/url]
?
work on USA matrix 12 ???
?
I suspect dead EPROM chips in one that I'm servicing now
and need to know can I flash my own or buy.
Probably nowhere on the net I can see a set for a US version.
Vintagesynthshop telling that those won't work on US version.
But how can it be ???
The logic components are totally the same ?
?
Thanks.


 

开云体育


Hi,

It was me who dumped h thee ?Jap .Matrix 12 EPROMs and gave em to the web?

No, the CPU board was redisgned for the Jap version . They are similar but not identical?

You can still try to put the jap EPROMs files in your US one , but you’ll end up with a ? voice processor malfunction ? message?
Cheers,

Manfred?

Le 27 janv. 2020 à 15:30, leo-666 via Groups.Io <leo-666@...> a écrit?:

?Sorry for a little bit of offtop.
But I did not find the right particular topic for my question.
So to my view this topic looks like a proper place to ask.

Will?
?
[url]http://dbwbp.com/synthbin/Oberheim%20Matrix%2012%20(Japanese%20Edition)%20CPU%20&%20Voice%20EPROMs.zip[/url]
?
or?
?
[url]http://dbwbp.com/synthbin/Oberheim%20Matrix%2012%20(Japan%20version).zip[/url]
?
or?
?
[url]https://www.vintagesynthshop.com/Oberheim-Matrix-12-OS-1-6-Rom-Firmware-bbaaaaqba.asp[/url]
?
work on USA matrix 12 ???
?
I suspect dead EPROM chips in one that I'm servicing now
and need to know can I flash my own or buy.
Probably nowhere on the net I can see a set for a US version.
Vintagesynthshop telling that those won't work on US version.
But how can it be ???
The logic components are totally the same ?
?
Thanks.


Xpantastic!