Korg Poly800/EX800 Users group photo

Yahoo Groups archive

Korg Poly800/EX800 Users

Index last updated: 2026-04-28 23:27 UTC

Thread

HAWK-800 - 100+ units shipped...

HAWK-800 - 100+ units shipped...

2012-07-02 by korgpolyex800

Hi Poly fans,

Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

I've been trying to think of a way to wind down the project but I just can't let it go just yet.

The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

How is everyone else doing with their HAWK's? It's been mighty quiet around here.

Mike

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by Nate King

Hi Mike,

I know I'm definitely interested in the hawk hardware and software. I emailed (though only once) and when I didn't get a response, I dropped it. I still have two poly 800s and would like to mod them both.

For what it's worth, the feeling around the web is that the project is mostly dead. Otherwise, I'm certain others would be interested in your product.

Thanks a lot for posting and for sharing with the community, it's much appreciated.

I love my poly 800 :)

Nate
Show quoted textHide quoted text
On Mon, Jul 2, 2012 at 10:46 AM, korgpolyex800 <korgpolyex800@...> wrote:

Hi Poly fans,

Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

I've been trying to think of a way to wind down the project but I just can't let it go just yet.

The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

How is everyone else doing with their HAWK's? It's been mighty quiet around here.

Mike




--
n a t e

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by Alex Drinkwater

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x
Show quoted textHide quoted text
> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by Michael Hawkins

I can understand people thinking that the project is dead because in a sense it is because, other than the arpeggiator, there isn't much more to do. The HAWK does what it it is supposed to do. I did update the website today to show that the HAWK kits are still available and to generally show "signs of recent activity".

Cheers,

Mike



________________________________
Show quoted textHide quoted text
 From: Nate King <nate@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 10:59 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
Hi Mike,

I know I'm definitely interested in the hawk hardware and software. I emailed (though only once) and when I didn't get a response, I dropped it. I still have two poly 800s and would like to mod them both. 

For what it's worth, the feeling around the web is that the project is mostly dead. Otherwise, I'm certain others would be interested in your product. 

Thanks a lot for posting and for sharing with the community, it's much appreciated. 

I love my poly 800 :)

Nate


On Mon, Jul 2, 2012 at 10:46 AM, korgpolyex800 <korgpolyex800@...> wrote:

 
>  
>Hi Poly fans,
>
>Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>
>I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>
>The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>
>How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
>Mike
>
>


-- 
   n   a   t   e

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by Michael Hawkins

As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x
Show quoted textHide quoted text
> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: HAWK-800 - 100+ units shipped...

2012-07-02 by bimmerfan222

If support is going to be cut off later on/no more production,  will there be any release of the coding/assy. language?


I have ideas I'd like to tinker with.  One is to convert keyboard key switch pairs into encoders .. 
basically make a Poly into a rack unit.. or somehow make the KB go from keys to an edit mode with up to 24 encoders that do direct edits, instead of jamming up the MPU with too many midi signals..
I figure the KB's are not much use when you have velocity sens. avail and use an external KB controller.


-Blaine




--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
>
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
>

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by LARRY HAWKE

As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

Show quoted textHide quoted text

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>






-----Original Message-----
From: Michael Hawkins
Sent: 7/2/2012 3:53:53 PM
To: korgpolyex@yahoogroups.com
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>



Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by LARRY HAWKE

As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

Show quoted textHide quoted text

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>






-----Original Message-----
From: Michael Hawkins
Sent: 7/2/2012 3:53:53 PM
To: korgpolyex@yahoogroups.com
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>



Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by LARRY HAWKE

I can understand people thinking that the project is dead because in a sense it is because, other than the arpeggiator, there isn't much more to do. The HAWK does what it it is supposed to do. I did update the website today to show that the HAWK kits are still available and to generally show "signs of recent activity".

Cheers,

Mike

Show quoted textHide quoted text

From: Nate King
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 10:59 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike,

I know I'm definitely interested in the hawk hardware and software. I emailed (though only once) and when I didn't get a response, I dropped it. I still have two poly 800s and would like to mod them both.

For what it's worth, the feeling around the web is that the project is mostly dead. Otherwise, I'm certain others would be interested in your product.

Thanks a lot for posting and for sharing with the community, it's much appreciated.

I love my poly 800 :)

Nate

On Mon, Jul 2, 2012 at 10:46 AM, korgpolyex800 <korgpolyex800@...> wrote:
Hi Poly fans,

Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

I've been trying to think of a way to wind down the project but I just can't let it go just yet.

The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

How is everyone else doing with their HAWK's? It's been mighty quiet around here.

Mike




--
n a t e





-----Original Message-----
From: Michael Hawkins
Sent: 7/2/2012 3:53:24 PM
To: korgpolyex@yahoogroups.com
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

I can understand people thinking that the project is dead because in a sense it is because, other than the arpeggiator, there isn't much more to do. The HAWK does what it it is supposed to do. I did update the website today to show that the HAWK kits are still available and to generally show "signs of recent activity".

Cheers,

Mike

From: Nate King
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 10:59 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike,

I know I'm definitely interested in the hawk hardware and software. I emailed (though only once) and when I didn't get a response, I dropped it. I still have two poly 800s and would like to mod them both.

For what it's worth, the feeling around the web is that the project is mostly dead. Otherwise, I'm certain others would be interested in your product.

Thanks a lot for posting and for sharing with the community, it's much appreciated.

I love my poly 800 :)

Nate

On Mon, Jul 2, 2012 at 10:46 AM, korgpolyex800 <korgpolyex800@yahoo.com> wrote:
Hi Poly fans,

Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

I've been trying to think of a way to wind down the project but I just can't let it go just yet.

The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

How is everyone else doing with their HAWK's? It's been mighty quiet around here.

Mike




--
; n a t e


Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by rib109@aol.com

I love my Poly 800 ! Still having some issues with the sequencer. I'm 
always interested in keeping it maintained and up  and running, so patches, 
upgrades etc. are much appreciated.

Re: [korgpolyex] Re: HAWK-800 - 100+ units shipped...

2012-07-02 by Michael Hawkins

Yes, I will be making the code available on sourceforge very soon.

But the idea is that support would INCREASE through a community of HAWKer's

The latest board now has three extra TTL output lines available so I think your encoder project is technically feasible. 


Mike



________________________________
 From: bimmerfan222 <bperkins211@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 12:55 PM
Subject: [korgpolyex] Re: HAWK-800 - 100+ units shipped...
 

  


If support is going to be cut off later on/no more production,  will there be any release of the coding/assy. language?

I have ideas I'd like to tinker with.  One is to convert keyboard key switch pairs into encoders .. 
basically make a Poly into a rack unit.. or somehow make the KB go from keys to an edit mode with up to 24 encoders that do direct edits, instead of jamming up the MPU with too many midi signals..
I figure the KB's are not much use when you have velocity sens. avail and use an external KB controller.

-Blaine

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
>
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
>

Re: HAWK-800 - 100+ units shipped...

2012-07-02 by bimmerfan222

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
>
  > Yes, I will be making the code available on sourceforge very soon.

That would be very helpful and greatly appreciated.  Do you have any recommendations of good books to learn about the 80C51 and programming it?

 

  > But the idea is that support would INCREASE through a community of HAWKer's

That would be very nice.. sure hate to see all this work you've done end up fizzling away in continued support.


 
  > The latest board now has three extra TTL output lines available so I think your encoder project is technically feasible. 


The boards you just shipped out have them?  By output lines, what are you referring to?  I'm just barely getting a grasp on TTL/CMOS.  I got ahold of Lancaster's books  TTL & CMOS Cookbooks and slowly digesting on the families and their applications/logic.

I finally think I figured out how the Poly KB's scan for input using the 3 to 8 decoder/selector chip with the octal buffer..  it's kinda neat to see how there are 8 groups of 8 switches.. and how that 3-8 selector goes from each output, to each group of switches and then routed back to the buffer for the MPU to read/poll.
Thats probably all elementary for you, but for me it was a moment of "aha!.. THATS how it works"
So that's what gave me the idea to use keyboard key switches and reprogram their inputs as encoder controlled bilateral switches for in depth editing of all the new toys coded in.

If you might have a moment to share how those TTL outputs are built into the new architecture, I'd greatly appreciated it in order to read up more about using them.

-Blaine



______________________
Show quoted textHide quoted text
>  From: bimmerfan222 <bperkins211@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 12:55 PM
> Subject: [korgpolyex] Re: HAWK-800 - 100+ units shipped...
>  
> 
> Â  
> 
> 
> If support is going to be cut off later on/no more production,  will there be any release of the coding/assy. language?
> 
> I have ideas I'd like to tinker with.  One is to convert keyboard key switch pairs into encoders .. 
> basically make a Poly into a rack unit.. or somehow make the KB go from keys to an edit mode with up to 24 encoders that do direct edits, instead of jamming up the MPU with too many midi signals..
> I figure the KB's are not much use when you have velocity sens. avail and use an external KB controller.
> 
> -Blaine
> 
> --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote:
> >
> > As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> > 
> > Mike
> > 
> >
>

Re: [korgpolyex] Re: HAWK-800 - 100+ units shipped...

2012-07-02 by Michael Hawkins

The three outputs are just a latched output register. The chip used is a 74HC174 which is a six bit latch. I originally used three out of the six latches. The new boards have the remaining three made available. Basically, the code can write values to the six bits and the latches keep them in that state after the CPU moves on to other tasks. I know someone wanted a signal that indicated a note hit. So that's one bit latch taken for that already. Then, your encoder project was probably going to use one or two latches. Adding a scanning latch to HAWK would not be too difficult so it would seem unnecessary to steal keyboard inputs.


The CPU in the Poly is an 80C85 which is darn close to the 8080 which was the precursor to the Z80.

I would suggest reading the datasheet for the 80C85 for a start and also read the instruction set. I use TASM for the assembly language and Eclipse as the IDE. There is actually a 80C85 plug in for eclipse. I had it working with eclipse version 3.2 and am now just trying to see if I can get it to work with the latest version of Eclipse.

Mike



________________________________
 From: bimmerfan222 <bperkins211@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 4:17 PM
Subject: [korgpolyex] Re: HAWK-800 - 100+ units shipped...
 

  


--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
>
> Yes, I will be making the code available on sourceforge very soon.

That would be very helpful and greatly appreciated.  Do you have any recommendations of good books to learn about the 80C51 and programming it?

> But the idea is that support would INCREASE through a community of HAWKer's

That would be very nice.. sure hate to see all this work you've done end up fizzling away in continued support.

> The latest board now has three extra TTL output lines available so I think your encoder project is technically feasible. 

The boards you just shipped out have them?  By output lines, what are you referring to?  I'm just barely getting a grasp on TTL/CMOS.  I got ahold of Lancaster's books  TTL & CMOS Cookbooks and slowly digesting on the families and their applications/logic.

I finally think I figured out how the Poly KB's scan for input using the 3 to 8 decoder/selector chip with the octal buffer..  it's kinda neat to see how there are 8 groups of 8 switches.. and how that 3-8 selector goes from each output, to each group of switches and then routed back to the buffer for the MPU to read/poll.
Thats probably all elementary for you, but for me it was a moment of "aha!.. THATS how it works"
So that's what gave me the idea to use keyboard key switches and reprogram their inputs as encoder controlled bilateral switches for in depth editing of all the new toys coded in.

If you might have a moment to share how those TTL outputs are built into the new architecture, I'd greatly appreciated it in order to read up more about using them.

-Blaine

______________________
Show quoted textHide quoted text
>  From: bimmerfan222 <bperkins211@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 12:55 PM
> Subject: [korgpolyex] Re: HAWK-800 - 100+ units shipped...
> 
> 
> Â  
> 
> 
> If support is going to be cut off later on/no more production,  will there be any release of the coding/assy. language?
> 
> I have ideas I'd like to tinker with.  One is to convert keyboard key switch pairs into encoders .. 
> basically make a Poly into a rack unit.. or somehow make the KB go from keys to an edit mode with up to 24 encoders that do direct edits, instead of jamming up the MPU with too many midi signals..
> I figure the KB's are not much use when you have velocity sens. avail and use an external KB controller.
> 
> -Blaine
> 
> --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote:
> >
> > As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> > 
> > Mike
> > 
> >
>

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-02 by Alex Drinkwater

OK, here's where I am at the moment.

Firmware v.1.94
Software v.2.53
Atomahawk installed
At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:

Issue 1:
I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.

Issue 2:
I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).

Issue 3:
I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.

Issue 4:
Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.

We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.

I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.

Is there anything else I can try?

a|x




Show quoted textHide quoted text
From: LARRY HAWKE
To: "korgpolyex@yahoogroups.com "
Sent: Monday, 2 July 2012, 18:18
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...



As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>






-----Original Message-----
From: Michael Hawkins
Sent: 7/2/2012 3:53:53 PM
To: korgpolyex@yahoogroups.com
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>







Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-03 by Michael Hawkins

V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.

I would say that is probably the biggest problem.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Monday, July 2, 2012 6:35 PM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
OK, here's where I am at the moment.

Firmware v.1.94
Software v.2.53
Atomahawk installed
At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:

Issue 1:
I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.

Issue 2:
I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).

Issue 3:
I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.

Issue 4:
Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.  

We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.


I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.

Is there anything else I can try?

a|x





________________________________
 From: LARRY HAWKE <gorgarh@...>
To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
Sent: Monday, 2 July 2012, 18:18
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 




  
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike



________________________________
 From: Alex Drinkwater 
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
> 







-----Original Message----- 
From: Michael Hawkins 
Sent: 7/2/2012 3:53:53 PM 
To: korgpolyex@yahoogroups.com 
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
  
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...


  
Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
 gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
 I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
 either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
 everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
 Groups Links
Show quoted textHide quoted text
> 
> 
>

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-03 by Michael Hawkins

V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.

I would say that is probably the biggest problem.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Monday, July 2, 2012 6:35 PM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
OK, here's where I am at the moment.

Firmware v.1.94
Software v.2.53
Atomahawk installed
At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:

Issue 1:
I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.

Issue 2:
I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).

Issue 3:
I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.

Issue 4:
Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.  

We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.


I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.

Is there anything else I can try?

a|x





________________________________
 From: LARRY HAWKE <gorgarh@...>
To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
Sent: Monday, 2 July 2012, 18:18
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 




  
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike



________________________________
 From: Alex Drinkwater 
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
 

  
Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
> 







-----Original Message----- 
From: Michael Hawkins 
Sent: 7/2/2012 3:53:53 PM 
To: korgpolyex@yahoogroups.com 
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
  
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...


  
Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
> 
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
 gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
 I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
 either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

> 
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> 
> Mike
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
 everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
 Groups Links
Show quoted textHide quoted text
> 
> 
>

Re: [korgpolyex] HAWK-800 - 100+ units shipped...

2012-07-03 by Alex Drinkwater

Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.

a|x



Show quoted textHide quoted text
From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 2:23
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...



V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.

I would say that is probably the biggest problem.

Mike

From: Alex Drinkwater
To: "korgpolyex@yahoogroups.com"
Sent: Monday, July 2, 2012 6:35 PM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

OK, here's where I am at the moment.

Firmware v.1.94
Software v.2.53
Atomahawk installed
At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:

Issue 1:
I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.

Issue 2:
I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).

Issue 3:
I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.

Issue 4:
Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.

We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.

I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.

Is there anything else I can try?

a|x




From: LARRY HAWKE
To: "korgpolyex@yahoogroups.com "
Sent: Monday, 2 July 2012, 18:18
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...



As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>






-----Original Message-----
From: Michael Hawkins
Sent: 7/2/2012 3:53:53 PM
To: korgpolyex@yahoogroups.com
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Monday, July 2, 2012 11:11 AM
Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...

Hi Mike.

On 2 Jul 2012, at 15:46, korgpolyex800 wrote:

> Hi Poly fans,
>
> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.

Congratulations!

> I've been trying to think of a way to wind down the project but I just can't let it go just yet.

That's a shame. I understand it's taken a lot of your time, over several years, though.

> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.

Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.

a|x

>
> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>
> Mike
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>













Alex's HAWK

2012-07-03 by korgpolyex800

I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are. This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.

In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Thanks,

Mike



--- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
Show quoted textHide quoted text
>
> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
> 
> a|x
> 
> 
> 
> 
> ________________________________
>  From: Michael Hawkins <korgpolyex800@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, 3 July 2012, 2:23
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>  
> 
> 
> 
> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
> 
> I would say that is probably the biggest problem.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Monday, July 2, 2012 6:35 PM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>   
> OK, here's where I am at the moment.
> 
> Firmware v.1.94
> Software v.2.53
> Atomahawk installed
> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
> 
> Issue 1:
> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
> 
> Issue 2:
> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
> 
> Issue 3:
> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
> 
> Issue 4:
> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.  
> 
> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
> 
> 
> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
> 
> Is there anything else I can try?
> 
> a|x
> 
> 
> 
> 
> 
> ________________________________
>  From: LARRY HAWKE <gorgarh@...>
> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
> Sent: Monday, 2 July 2012, 18:18
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
> 
> 
> 
>   
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater 
> To: korgpolyex@...m 
> Sent: Monday, July 2, 2012 11:11 AM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>   
> Hi Mike.
> 
> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> 
> > Hi Poly fans,
> > 
> > Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> 
> Congratulations!
> 
> > I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> 
> That's a shame. I understand it's taken a lot of your time, over several years, though.
> 
> > The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> 
> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> 
> a|x
> 
> > 
> > How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> > 
> > Mike
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> > 
> > 
> > 
> 
> 
> 
> 
> 
> 
> 
> -----Original Message----- 
> From: Michael Hawkins 
> Sent: 7/2/2012 3:53:53 PM 
> To: korgpolyex@yahoogroups.com 
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>   
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater <the_voder@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 11:11 AM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> 
> 
>   
> Hi Mike.
> 
> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> 
> > Hi Poly fans,
> > 
> > Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> 
> Congratulations!
> 
> > I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> 
> That's a shame. I understand it's taken a lot of your time, over several years, though.
> 
> > The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> 
> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>  gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>  I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>  either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> 
> a|x
> 
> > 
> > How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> > 
> > Mike
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>  everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>  Groups Links
> > 
> > 
> >
>

Re: HAWK-800 - 100+ units shipped...

2012-07-03 by bimmerfan222

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
 
     >Basically, the code can write values to the six bits and the latches keep them in that state after the CPU moves on to other tasks. I know someone wanted a signal that indicated a note hit. So that's one bit latch taken for that already. Then, your encoder project was probably going to use one or two latches. Adding a scanning latch to HAWK would not be too difficult so it would seem unnecessary to steal keyboard inputs.<


So can the code be altered to release that note hit latch?
I'm guessing the first three used up are required to pick between memories or something...

Am I following that it's possible to add in another 3 to 8 demux to create another scanning routine to a new set of matrix's?

Re: [korgpolyex] Re: HAWK-800 - 100+ units shipped...

2012-07-03 by Michael Hawkins

You're right, the first two bits are used as the bank select for patch memory. The last one was used in previous versions of hardware to provide a RAM bank select. But, it cannot be used for anything due to incompatibilities with the older version boards.

The three new latches are available for anything right now. I haven't written any code around them. But, I would imagine two could be used for LFO flashing LED's. And one was intended for note hit trigger.

But, there are lots of spare chip select lines available for your multiplexer needs. If I recall correctly there are six spare chip select lines. The latest version boards also use a buffered write signal. So, it is very likely that we can add up to 6 additional input buffers or output latches to accommodate additional hardware mod's.


Mike



________________________________
Show quoted textHide quoted text
 From: bimmerfan222 <bperkins211@...>
To: korgpolyex@yahoogroups.com 
Sent: Tuesday, July 3, 2012 1:04 PM
Subject: [korgpolyex] Re: HAWK-800 - 100+ units shipped...
 

  


--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:

>Basically, the code can write values to the six bits and the latches keep them in that state after the CPU moves on to other tasks. I know someone wanted a signal that indicated a note hit. So that's one bit latch taken for that already. Then, your encoder project was probably going to use one or two latches. Adding a scanning latch to HAWK would not be too difficult so it would seem unnecessary to steal keyboard inputs.<

So can the code be altered to release that note hit latch?
I'm guessing the first three used up are required to pick between memories or something...

Am I following that it's possible to add in another 3 to 8 demux to create another scanning routine to a new set of matrix's?

Re: [korgpolyex] Alex's HAWK

2012-07-03 by Alex Drinkwater

On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> 
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x
Show quoted textHide quoted text
> 
> Thanks,
> 
> Mike
> 
> 
> 
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
>> 
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>> 
>> a|x
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Michael Hawkins <korgpolyex800@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>> 
>> I would say that is probably the biggest problem.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>>   
>> OK, here's where I am at the moment.
>> 
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>> 
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>> 
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>> 
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>> 
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.  
>> 
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>> 
>> 
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>> 
>> Is there anything else I can try?
>> 
>> a|x
>> 
>> 
>> 
>> 
>> 
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>>   
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater 
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>>   
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message----- 
>> From: Michael Hawkins 
>> Sent: 7/2/2012 3:53:53 PM 
>> To: korgpolyex@yahoogroups.com 
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>>   
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>>   
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] Alex's HAWK

2012-07-03 by Michael Hawkins

Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  

On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> 
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x
Show quoted textHide quoted text
> 
> Thanks,
> 
> Mike
> 
> 
> 
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
>> 
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>> 
>> a|x
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Michael Hawkins <korgpolyex800@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>> 
>> I would say that is probably the biggest problem.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> OK, here's where I am at the moment.
>> 
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>> 
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>> 
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>> 
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>> 
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered. 
>> 
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>> 
>> 
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>> 
>> Is there anything else I can try?
>> 
>> a|x
>> 
>> 
>> 
>> 
>> 
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater 
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message----- 
>> From: Michael Hawkins 
>> Sent: 7/2/2012 3:53:53 PM 
>> To: korgpolyex@yahoogroups.com 
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] Alex's HAWK

2012-07-03 by Alex Drinkwater

Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x



Show quoted textHide quoted text
From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK



Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK


On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
>
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x

>
> Thanks,
>
> Mike
>
>
>
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater wrote:
>>
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>>
>> a|x
>>
>>
>>
>>
>> ________________________________
>> From: Michael Hawkins
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>>
>> I would say that is probably the biggest problem.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> OK, here's where I am at the moment.
>;>
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>>
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>>
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>>
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>>
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.
>>
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>>
>>
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>;>
>> Is there anything else I can try?
>>
>;> a|x
>>
>>
>>
>>
>>
>> ________________________________
>> From: LARRY HAWKE
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com>
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Michael Hawkins
>> Sent: 7/2/2012 3:53:53 PM
>> To: korgpolyex@yahoogroups.com
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>>
>>>
>>>
>>
>
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>







Re: HAWK-800 - 100+ units shipped...

2012-07-03 by k9k9dog

Hi Mike, 
embarassed to say i haven't installed it yet: no time/headpace, 
and i was put off by rumours of problems with one of the chip 
batches you sent out...i don't know if i was part of that batch. 
i need to look at this again, bcs i want to get it fitted and 
running.

nb: i was also confused by the number of dils vs dil slots on the 
board. bought extra ones in case, but am still at  that stage.

#2: what about latency introduced by the additional cpu operations? 
is this fact?

other than that, i'd personally welcome continuation of project, 
conceptually, practically etc.

--- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
Show quoted textHide quoted text
>
> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
> 
> a|x
> 
> 
> 
> 
> ________________________________
>  From: Michael Hawkins <korgpolyex800@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, 3 July 2012, 2:23
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>  
> 
> 
> 
> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
> 
> I would say that is probably the biggest problem.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@...m> 
> Sent: Monday, July 2, 2012 6:35 PM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>   
> OK, here's where I am at the moment.
> 
> Firmware v.1.94
> Software v.2.53
> Atomahawk installed
> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
> 
> Issue 1:
> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
> 
> Issue 2:
> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
> 
> Issue 3:
> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
> 
> Issue 4:
> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.  
> 
> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
> 
> 
> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
> 
> Is there anything else I can try?
> 
> a|x
> 
> 
> 
> 
> 
> ________________________________
>  From: LARRY HAWKE <gorgarh@...>
> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
> Sent: Monday, 2 July 2012, 18:18
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
> 
> 
> 
>   
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater 
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 11:11 AM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
>   
> Hi Mike.
> 
> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> 
> > Hi Poly fans,
> > 
> > Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> 
> Congratulations!
> 
> > I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> 
> That's a shame. I understand it's taken a lot of your time, over several years, though.
> 
> > The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> 
> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> 
> a|x
> 
> > 
> > How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> > 
> > Mike
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> > 
> > 
> > 
> 
> 
> 
> 
> 
> 
> 
> -----Original Message----- 
> From: Michael Hawkins 
> Sent: 7/2/2012 3:53:53 PM 
> To: korgpolyex@yahoogroups.com 
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>   
> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Alex Drinkwater <the_voder@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 11:11 AM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> 
> 
>   
> Hi Mike.
> 
> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> 
> > Hi Poly fans,
> > 
> > Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> 
> Congratulations!
> 
> > I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> 
> That's a shame. I understand it's taken a lot of your time, over several years, though.
> 
> > The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> 
> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>  gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>  I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>  either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> 
> a|x
> 
> > 
> > How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> > 
> > Mike
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>  everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>  Groups Links
> > 
> > 
> >
>

80c85 programming & P800 modding

2012-07-04 by bimmerfan222

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:

 
   > The CPU in the Poly is an 80C85 which is darn close to the 8080 which was the precursor to the Z80.<
   > I would suggest reading the datasheet for the 80C85 for a start and also read the instruction set. I use TASM for the assembly language and Eclipse as the IDE. There is actually a 80C85 plug in for eclipse. I had it working with eclipse version 3.2 and am now just trying to see if I can get it to work with the latest version of Eclipse.
> 


I went ahead and purchased a book for 8085 assy. language:

http://www.amazon.com/8080A-8085-Assembly-Language-Programming-Leventhal/dp/0931988101/ref=sr_1_3?ie=UTF8&qid=1341413191&sr=8-3&keywords=8085+assembly

it was dirt cheap, so I went ahead and got it.  Is this worth a darn to study/use as reference?  I realize it's not actual 80c85.. but from what I understand, the "C" just stands for CMOS vs. the 8085 NMOS technology... and the real difference between 8080/8085 is that the 8085 is 5v supplied.


also curious if it would be worthwhile to get ahold of a 8085 based microprocessor trainer/kit..  like the SDK-85 (hard to find/expensive if found) 

or this little guy I found cheap on ebay right now.. the Graymark G-809 microprocessor trainer:

http://www.graymarkint.com/catalogv2/graym18.htm

That one has a bus edge card on the side that could be used to interface components in.. Graymark use to sell an actual breadboard that would plug right into it to break out the 8085.
It looks like it could be a decent unit for around $50.  An actual SDK-85 is on ebay right now.. but it's like $250!

I've seen several emulators for free online for 8085 training, but the actual unit seems more appealing to me since they usually allow you to interface actual TTL/CMOS components directly to the MPU.
I'd be learning from ground zero on assy. language and just how MPU's work in general..  my desire to mod the P800 is twofold, I'd like to do something cool with the synth, but I also really want to dig in and learn digital electronics and MPU programming for either hobby purposes or even to add to my resume for future job seeking reasons.




    > there are lots of spare chip select lines available for your multiplexer needs. If I recall correctly there are six spare chip select lines. The latest version boards also use a buffered write signal. So, it is very likely that we can add up to 6 additional input buffers or output latches to accommodate additional hardware mod's.<


are these spare select lines from the original Korg architecture or from your Hawk board?


-Blaine

Re: [korgpolyex] 80c85 programming & P800 modding

2012-07-05 by Michael Hawkins

Although you can do any of the things you mention, I would suggest that you don't spend money on any emulator or development kit. I would use the free software emulators and your HAWK'ed Poly-800 itself.

With the HAWK in place, you can do all of your 8085 assembly learning you want. And when you're done, just upload and flash the latest working software to get your Poly back into operation.

The spare chip select lines are coming from the HAWK board.

Mike



________________________________
Show quoted textHide quoted text
 From: bimmerfan222 <bperkins211@...>
To: korgpolyex@yahoogroups.com 
Sent: Wednesday, July 4, 2012 11:37 AM
Subject: [korgpolyex] 80c85 programming & P800 modding
 

  


--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:

> The CPU in the Poly is an 80C85 which is darn close to the 8080 which was the precursor to the Z80.<
> I would suggest reading the datasheet for the 80C85 for a start and also read the instruction set. I use TASM for the assembly language and Eclipse as the IDE. There is actually a 80C85 plug in for eclipse. I had it working with eclipse version 3.2 and am now just trying to see if I can get it to work with the latest version of Eclipse.
> 

I went ahead and purchased a book for 8085 assy. language:

http://www.amazon.com/8080A-8085-Assembly-Language-Programming-Leventhal/dp/0931988101/ref=sr_1_3?ie=UTF8&qid=1341413191&sr=8-3&keywords=8085+assembly

it was dirt cheap, so I went ahead and got it.  Is this worth a darn to study/use as reference?  I realize it's not actual 80c85.. but from what I understand, the "C" just stands for CMOS vs. the 8085 NMOS technology... and the real difference between 8080/8085 is that the 8085 is 5v supplied.

also curious if it would be worthwhile to get ahold of a 8085 based microprocessor trainer/kit..  like the SDK-85 (hard to find/expensive if found) 

or this little guy I found cheap on ebay right now.. the Graymark G-809 microprocessor trainer:

http://www.graymarkint.com/catalogv2/graym18.htm

That one has a bus edge card on the side that could be used to interface components in.. Graymark use to sell an actual breadboard that would plug right into it to break out the 8085.
It looks like it could be a decent unit for around $50.  An actual SDK-85 is on ebay right now.. but it's like $250!

I've seen several emulators for free online for 8085 training, but the actual unit seems more appealing to me since they usually allow you to interface actual TTL/CMOS components directly to the MPU.
I'd be learning from ground zero on assy. language and just how MPU's work in general..  my desire to mod the P800 is twofold, I'd like to do something cool with the synth, but I also really want to dig in and learn digital electronics and MPU programming for either hobby purposes or even to add to my resume for future job seeking reasons.

> there are lots of spare chip select lines available for your multiplexer needs. If I recall correctly there are six spare chip select lines. The latest version boards also use a buffered write signal. So, it is very likely that we can add up to 6 additional input buffers or output latches to accommodate additional hardware mod's.<

are these spare select lines from the original Korg architecture or from your Hawk board?

-Blaine

Re: HAWK-800 - 100+ units shipped...

2012-07-10 by jcmayer3000

Nate,

Michael clearly has no time for you.  And the Hawk 800 are a major waste of time.

Johnny

--- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@...> wrote:
Show quoted textHide quoted text
>
> I can understand people thinking that the project is dead because in a sense it is because, other than the arpeggiator, there isn't much more to do. The HAWK does what it it is supposed to do. I did update the website today to show that the HAWK kits are still available and to generally show "signs of recent activity".
> 
> Cheers,
> 
> Mike
> 
> 
> 
> ________________________________
>  From: Nate King <nate@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Monday, July 2, 2012 10:59 AM
> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>  
> 
> Â  
> Hi Mike,
> 
> I know I'm definitely interested in the hawk hardware and software. I emailed (though only once) and when I didn't get a response, I dropped it. I still have two poly 800s and would like to mod them both. 
> 
> For what it's worth, the feeling around the web is that the project is mostly dead. Otherwise, I'm certain others would be interested in your product. 
> 
> Thanks a lot for posting and for sharing with the community, it's much appreciated. 
> 
> I love my poly 800 :)
> 
> Nate
> 
> 
> On Mon, Jul 2, 2012 at 10:46 AM, korgpolyex800 <korgpolyex800@...> wrote:
> 
>  
> >Â  
> >Hi Poly fans,
> >
> >Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> >
> >I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> >
> >The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> >
> >How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> >
> >Mike
> >
> >
> 
> 
> -- 
>    n   a   t   e
>

Re: [korgpolyex] Alex's HAWK

2012-07-10 by Alex Drinkwater

OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x


Show quoted textHide quoted text
From: Alex Drinkwater
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK



Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x



From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK



Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike

From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK


On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
>
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x

>
> Thanks,
>
> Mike
>
>
>
> --- In korgpolyex@...m, Alex Drinkwater wrote:
>>
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>>
>> a|x
>>
>>
>>
>>
>> ________________________________
>> From: Michael Hawkins
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@...m>
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>;>
>>
>>
>>
>>
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>>
>> I would say that is probably the biggest problem.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater <;the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> OK, here's where I am at the moment.
>>
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>>
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>>
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>>
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>>
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.
>>
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>>
>>
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>>
>> Is there anything else I can try?
>>
>> a|x
>>
>>
>>
>>
>>
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com>
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>;>
>>
>>
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Michael Hawkins
>> Sent: 7/2/2012 3:53:53 PM
>> To: korgpolyex@yahoogroups.com
>>; Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>;> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>;>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>>
>>>
>>;>
>>
>
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>











Re: [korgpolyex] Alex's HAWK

2012-07-10 by Michael Hawkins

"Synth booted to just before preset number would be displayed, but at 
this point just an 'A' is visible in the second character of the first 
LED display and nothing further happens. It seems to hang completely at 
this point."

It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.

So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.

Let's see what we get from that.

Mike




________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, July 10, 2012 5:15 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  
OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK
 




Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x




________________________________
 From: Michael Hawkins <korgpolyex800@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK
 




Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  

On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> 
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x
Show quoted textHide quoted text
> 
> Thanks,
> 
> Mike
> 
> 
> 
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
>> 
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>> 
>> a|x
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Michael Hawkins <korgpolyex800@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>> 
>> I would say that is probably the biggest problem.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> OK, here's where I am at the moment.
>> 
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>> 
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>> 
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>> 
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>> 
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered. 
>> 
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>> 
>> 
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>> 
>> Is there anything else I can try?
>> 
>> a|x
>> 
>> 
>> 
>> 
>> 
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater 
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message----- 
>> From: Michael Hawkins 
>> Sent: 7/2/2012 3:53:53 PM 
>> To: korgpolyex@yahoogroups.com 
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] Alex's HAWK

2012-07-11 by Alex Drinkwater

Is this what's supposed to happen, then? It doesn't say so in the walkthrough.
How do I flash each chip? Do I remove them one-by-one and place then in the 2nd socket?

a|x



Show quoted textHide quoted text
From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 10 July 2012, 22:39
Subject: Re: [korgpolyex] Alex's HAWK



"Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point."

It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.

So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.

Let's see what we get from that.

Mike


From: Alex Drinkwater To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, July 10, 2012 5:15 PM
Subject: Re: [korgpolyex] Alex's HAWK

OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x


From: Alex Drinkwater
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK



Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x



From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK



Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK


On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
>
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x

>
> Thanks,
>
> Mike
>
>
>
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater wrote:
>>
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>>
>> a|x
>>
>>
>>
>>
>> ________________________________
>> From: Michael Hawkins
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>>
>> I would say that is probably the biggest problem.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> OK, here's where I am at the moment.
>;>
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>>
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>>
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>>
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>>
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.
>>
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>>
>>
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>;>
>> Is there anything else I can try?
>>
>;> a|x
>>
>>
>>
>>
>>
>> ________________________________
>> From: LARRY HAWKE
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com>
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Michael Hawkins
>> Sent: 7/2/2012 3:53:53 PM
>> To: korgpolyex@yahoogroups.com
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>>
>>>
>>>
>>
>
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>

















Re: [korgpolyex] Alex's HAWK

2012-07-11 by Michael Hawkins

I am not sure what walk through you're referring to but after you do the boot ROM software upgrade you need to reflash the software into the three ROM's. Follow the procedure on page 8 of the owners manual.

Mike




________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Wednesday, July 11, 2012 3:47 AM
Subject: Re: [korgpolyex] Alex's HAWK
 

  
Is this what's supposed to happen, then? It doesn't say so in the walkthrough.
How do I flash each chip? Do I remove them one-by-one and place then in the 2nd socket?

a|x




________________________________
 From: Michael Hawkins <korgpolyex800@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 10 July 2012, 22:39
Subject: Re: [korgpolyex] Alex's HAWK
 




"Synth booted to just before preset number would be displayed, but at 
this point just an 'A' is visible in the second character of the first 
LED display and nothing further happens. It seems to hang completely at 
this point."

It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.

So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.

Let's see what we get from that.

Mike




________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, July 10, 2012 5:15 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  
OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK
 




Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x




________________________________
 From: Michael Hawkins <korgpolyex800@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK
 




Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  

On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> 
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x
Show quoted textHide quoted text
> 
> Thanks,
> 
> Mike
> 
> 
> 
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
>> 
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>> 
>> a|x
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Michael Hawkins <korgpolyex800@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>> 
>> I would say that is probably the biggest problem.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> OK, here's where I am at the moment.
>> 
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>> 
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>> 
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>> 
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>> 
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered. 
>> 
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>> 
>> 
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>> 
>> Is there anything else I can try?
>> 
>> a|x
>> 
>> 
>> 
>> 
>> 
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater 
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message----- 
>> From: Michael Hawkins 
>> Sent: 7/2/2012 3:53:53 PM 
>> To: korgpolyex@yahoogroups.com 
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] Alex's HAWK

2012-07-11 by Alex Drinkwater

OK, I think I've got it working again now. I've upgraded the boot ROM, installed the latest Hawk software, and re-uploaded some of the patch banks. It all seems OK now. That annoying unwanted modulation has gone. I hope it doesn't come back now....

Thanks for your patience, Mike. I have my EX-800 back!!

a|x




Show quoted textHide quoted text
From: Alex Drinkwater
To: "korgpolyex@yahoogroups.com"
Sent: Wednesday, 11 July 2012, 8:47
Subject: Re: [korgpolyex] Alex's HAWK



Is this what's supposed to happen, then? It doesn't say so in the walkthrough.
How do I flash each chip? Do I remove them one-by-one and place then in the 2nd socket?

a|x



From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 10 July 2012, 22:39
Subject: Re: [korgpolyex] Alex's HAWK



"Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point."

It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.

So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.

Let's see what we get from that.

Mike


From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, July 10, 2012 5:15 PM
Subject: Re: [korgpolyex] Alex's HAWK

OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x


From: Alex Drinkwater
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK



Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x



From: Michael Hawkins
To: "korgpolyex@yahoogroups.com"
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK



Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike

From: Alex Drinkwater
To: korgpolyex@yahoogroups.com
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK


On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
>
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x

>
> Thanks,
>
> Mike
>
>
>
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater wrote:
>>
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>>
>> a|x
>>
>>
>>
>>
>> ________________________________
>> From: Michael Hawkins
>;> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>>
>> I would say that is probably the biggest problem.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com>
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> OK, here's where I am at the moment.
>>
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>>
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>>
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>>
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>>
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered.
>>
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>>
>>
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>>
>> Is there anything else I can try?
>>
>> a|x
>>
>>
>>;
>>
>>
>> ________________________________
>> From: LARRY HAWKE
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com>
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>>
>>
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>;>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>;
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>>
>>>
>>>;
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Michael Hawkins
>> Sent: 7/2/2012 3:53:53 PM
>;> To: korgpolyex@yahoogroups.com
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>>
>> Mike
>>
>>
>>
>> ________________________________
>> From: Alex Drinkwater
>> To: korgpolyex@yahoogroups.com
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>>
>>
>;>
>> Hi Mike.
>>
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>>
>>> Hi Poly fans,
>>>
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>>
>> Congratulations!
>>
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>>
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>>
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>>
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>>
>> a|x
>>
>>>
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>>
>>> Mike
>>>
>>>
>>>
>>> ------------------------------------
>>>
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>>
>>>
>>>
>>
>
>
>
>
> ------------------------------------
>
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>
>
>





















Re: [korgpolyex] Alex's HAWK

2012-07-12 by Michael Hawkins

Yes, those were the correct instructions for your version of the kit.

And I am extremely happy that you got it working again! BRAVO!

But the mystery is what you did different this time around.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Wednesday, July 11, 2012 4:49 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  
OK, I think I've got it working again now. I've upgraded the boot ROM, installed the latest Hawk software, and re-uploaded some of the patch banks. It all seems OK now. That annoying unwanted modulation has gone. I hope it doesn't come back now....

Thanks for your patience, Mike. I have my EX-800 back!!

a|x






________________________________
 From: Alex Drinkwater <the_voder@yahoo.co.uk>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Wednesday, 11 July 2012, 8:47
Subject: Re: [korgpolyex] Alex's HAWK
 




Is this what's supposed to happen, then? It doesn't say so in the walkthrough.
How do I flash each chip? Do I remove them one-by-one and place then in the 2nd socket?

a|x




________________________________
 From: Michael Hawkins <korgpolyex800@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 10 July 2012, 22:39
Subject: Re: [korgpolyex] Alex's HAWK
 




"Synth booted to just before preset number would be displayed, but at 
this point just an 'A' is visible in the second character of the first 
LED display and nothing further happens. It seems to hang completely at 
this point."

It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.

So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.

Let's see what we get from that.

Mike




________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, July 10, 2012 5:15 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  
OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
Here's what happened:

I put the synth into Flash mode and sent the latest boot ROM sysex to it
The display said 'Go od 3'
I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
The synth then did not boot. No sign of life from the display at all
Replaced the chips in their original location and tried sending the boot sysex again
Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.

What else can I try?

a|x



________________________________
 From: Alex Drinkwater <the_voder@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 22:01
Subject: Re: [korgpolyex] Alex's HAWK
 




Cool. What do I have to do?
When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..

a|x




________________________________
 From: Michael Hawkins <korgpolyex800@...>
To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
Sent: Tuesday, 3 July 2012, 21:57
Subject: Re: [korgpolyex] Alex's HAWK
 




Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.

The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.

v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.

Mike



________________________________
 From: Alex Drinkwater <the_voder@...>
To: korgpolyex@yahoogroups.com 
Sent: Tuesday, July 3, 2012 3:57 PM
Subject: Re: [korgpolyex] Alex's HAWK
 

  

On 3 Jul 2012, at 15:56, korgpolyex800 wrote:

> I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.

I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.

> This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.

That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
It's obviously much easier if you don't have to do this this time.

> I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> 
> In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?

Yes it does.

Cheers,

a|x
Show quoted textHide quoted text
> 
> Thanks,
> 
> Mike
> 
> 
> 
> --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
>> 
>> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
>> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
>> 
>> a|x
>> 
>> 
>> 
>> 
>> ________________________________
>> From: Michael Hawkins <korgpolyex800@...>
>> To: "korgpolyex@...m" <korgpolyex@yahoogroups.com> 
>> Sent: Tuesday, 3 July 2012, 2:23
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
>> 
>> I would say that is probably the biggest problem.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
>> Sent: Monday, July 2, 2012 6:35 PM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> OK, here's where I am at the moment.
>> 
>> Firmware v.1.94
>> Software v.2.53
>> Atomahawk installed
>> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
>> 
>> Issue 1:
>> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
>> 
>> Issue 2:
>> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
>> 
>> Issue 3:
>> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
>> 
>> Issue 4:
>> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered. 
>> 
>> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
>> 
>> 
>> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
>> 
>> Is there anything else I can try?
>> 
>> a|x
>> 
>> 
>> 
>> 
>> 
>> ________________________________
>> From: LARRY HAWKE <gorgarh@...>
>> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
>> Sent: Monday, 2 July 2012, 18:18
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> 
>> 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater 
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -----Original Message----- 
>> From: Michael Hawkins 
>> Sent: 7/2/2012 3:53:53 PM 
>> To: korgpolyex@yahoogroups.com 
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
>> 
>> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
>> 
>> Mike
>> 
>> 
>> 
>> ________________________________
>> From: Alex Drinkwater <the_voder@...>
>> To: korgpolyex@yahoogroups.com 
>> Sent: Monday, July 2, 2012 11:11 AM
>> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
>> 
>> 
>> 
>> Hi Mike.
>> 
>> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
>> 
>>> Hi Poly fans,
>>> 
>>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
>> 
>> Congratulations!
>> 
>>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
>> 
>> That's a shame. I understand it's taken a lot of your time, over several years, though.
>> 
>>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
>> 
>> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
>> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
>> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
>> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
>> 
>> a|x
>> 
>>> 
>>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
>>> 
>>> Mike
>>> 
>>> 
>>> 
>>> ------------------------------------
>>> 
>>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
>> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
>> Groups Links
>>> 
>>> 
>>> 
>> 
> 
> 
> 
> 
> ------------------------------------
> 
> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> 
> 
>

Re: [korgpolyex] Alex's HAWK

2012-07-12 by Alex Drinkwater

Hiya.

On 12 Jul 2012, at 14:31, Michael Hawkins wrote:

> Yes, those were the correct instructions for your version of the kit.

Good stuff.

> And I am extremely happy that you got it working again! BRAVO!

I'm happy too!

> But the mystery is what you did different this time around.

Yes, true. It's a mystery to me, too, actually. I think I was just essentially doing things in the wrong order, so (as you suggested) I was ending up with incomplete software. I'm still not 100% sure why I was initially getting nothing at bootup after reflashing the boot ROM though. I'm not going to go through the whole process again, now, though (unless for some reason I have to).

Thanks for your patience (and entertaining impatience).

a\x
Show quoted textHide quoted text
> 
> Mike
> 
> From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Wednesday, July 11, 2012 4:49 PM
> Subject: Re: [korgpolyex] Alex's HAWK
> 
> OK, I think I've got it working again now. I've upgraded the boot ROM, installed the latest Hawk software, and re-uploaded some of the patch banks. It all seems OK now. That annoying unwanted modulation has gone. I hope it doesn't come back now....
> 
> Thanks for your patience, Mike. I have my EX-800 back!!
> 
> a|x
> 
> 
> 
> 
> From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Wednesday, 11 July 2012, 8:47
> Subject: Re: [korgpolyex] Alex's HAWK
> 
> 
> 
> Is this what's supposed to happen, then? It doesn't say so in the walkthrough.
> How do I flash each chip? Do I remove them one-by-one and place then in the 2nd socket?
> 
> a|x
> 
> 
> 
> From: Michael Hawkins <korgpolyex800@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, 10 July 2012, 22:39
> Subject: Re: [korgpolyex] Alex's HAWK
> 
> 
> 
> "Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point."
> 
> It halted at "A" because the actual software that resides in ROM's 1,2 and 3 is now missing the right code in ROM 1. Because ROM 1 has boot code in it.
> 
> So, reflash ROM 1 with EEPROM0.syx. And for good measure, do ROM 2 and 3 with EEPROM1.syx and EEPROM2.syx.
> 
> Let's see what we get from that.
> 
> Mike
> 
> 
> From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, July 10, 2012 5:15 PM
> Subject: Re: [korgpolyex] Alex's HAWK
> 
>  
> OK, I've tried upgrading the boot ROM, following the instruction on Sourceforge, but that seems to have failed.
> Here's what happened:
> 
> I put the synth into Flash mode and sent the latest boot ROM sysex to it
> The display said 'Go od 3'
> I then tried removing original boot ROM chip and replacing the Flash ROM and replaced it in boot ROM location
> The synth then did not boot. No sign of life from the display at all
> Replaced the chips in their original location and tried sending the boot sysex again
> Synth booted to just before preset number would be displayed, but at this point just an 'A' is visible in the second character of the first LED display and nothing further happens. It seems to hang completely at this point.
> I tried resending the boot and software syx files, but no change. It appears to be bricked at this point.
> 
> What else can I try?
> 
> a|x
> 
> 
> From: Alex Drinkwater <the_voder@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, 3 July 2012, 22:01
> Subject: Re: [korgpolyex] Alex's HAWK
> 
> 
> 
> Cool. What do I have to do?
> When did you release 1.95 of the boot code? I didn't find a 1.95 chip last night, but it's possible you may already have sent me one..
> 
> a|x
> 
> 
> 
> From: Michael Hawkins <korgpolyex800@...>
> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> Sent: Tuesday, 3 July 2012, 21:57
> Subject: Re: [korgpolyex] Alex's HAWK
> 
> 
> 
> Yes, at the time that you had problems, I was also in the middle of a hideous series of bugs in the HAWK code. Those bugs went out in boot code 1.93 and 1.94.
> 
> The code ended up so badly broken that I had to basically drop support for all versions of code prior to 2.53 and boot code 1.95. I learned a lot about code versioning from that nasty experience.
> 
> v1.95 is very stable and very ongoing supportable. So let's get you onto that code and then version 2.53 software might actually do the trick for you. Fingers crossed.
> 
> Mike
> 
> From: Alex Drinkwater <the_voder@...>
> To: korgpolyex@yahoogroups.com 
> Sent: Tuesday, July 3, 2012 3:57 PM
> Subject: Re: [korgpolyex] Alex's HAWK
> 
>  
> 
> On 3 Jul 2012, at 15:56, korgpolyex800 wrote:
> 
> > I just needed to see which PCB version you have and if the ROM's are all in sockets, which they are.
> 
> I'm not 100% sure they were always socketed. At some point, I bought an upgrade kit from you, but I forget the details, I'm afraid.
> 
> > This means you can upgrade the 1.94 to 1.95 boot code without obtaining a new ROM from me.
> 
> That's odd. You obviously decided this wasn't the case with previous upgrades, which you sent out to me on pre-burned chips.
> It's obviously much easier if you don't have to do this this time.
> 
> > I will post instructions for doing the boot ROM upgrade on sourceforge over the next couple of days.
> > 
> > In the meantime, can you check that holding the "Write" button down during power up puts the Poly into "Flash" mode?
> 
> Yes it does.
> 
> Cheers,
> 
> a|x
> 
> > 
> > Thanks,
> > 
> > Mike
> > 
> > 
> > 
> > --- In korgpolyex@yahoogroups.com, Alex Drinkwater <the_voder@...> wrote:
> >> 
> >> Here's a photo of the board. It's a bit rubbish I'm afraid. Was the best I could do with my iPhone this morning.
> >> It may be that you already sent me a 1.95 chip. I couldn't find any chips newer than 1.94 when I looked last night, thought. I also seem to have lost some of the emails we exchanged last year, so I'm not sure exactly how far we got.
> >> 
> >> a|x
> >> 
> >> 
> >> 
> >> 
> >> ________________________________
> >> From: Michael Hawkins <korgpolyex800@...>
> >> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> >> Sent: Tuesday, 3 July 2012, 2:23
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> V1.94 has bugs - serious bugs. You need 1.95. Send me a photo of your board so I can determine if you can do your own boot upgrade or not.
> >> 
> >> I would say that is probably the biggest problem.
> >> 
> >> Mike
> >> 
> >> 
> >> 
> >> ________________________________
> >> From: Alex Drinkwater <the_voder@...>
> >> To: "korgpolyex@yahoogroups.com" <korgpolyex@yahoogroups.com> 
> >> Sent: Monday, July 2, 2012 6:35 PM
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> >> 
> >> 
> >> 
> >> OK, here's where I am at the moment.
> >> 
> >> Firmware v.1.94
> >> Software v.2.53
> >> Atomahawk installed
> >> At some point, I went for the cheaper of two upgrade options for my original Hawk board (think I chose to upgrade the firmware without upgrading the memory, but I can't remember the details now, and the option is no longer listed on your site). You seemed to think this might be the cause of some of the software issues I've been experiencing. The outstanding issues are:
> >> 
> >> Issue 1:
> >> I can't enter Global mode. If I press the Step button in Prog mode, the synth drops straight into Flash-update mode, or sometimes, the display just flashes, and goes straight back to Prog. mode.
> >> 
> >> Issue 2:
> >> I can't enter diagnostics mode by holding down Write and Prog/Para at startup. It just drops straight into Flash upgrade mode if I try and do this. I can't get into Diagnostic mode via the Global command, because I can't execute Global commands (see above).
> >> 
> >> Issue 3:
> >> I can't send Sysex banks to the synth. If I attempt to do so, it says 'CR AS H on the display, and reboots itself after a few seconds.
> >> 
> >> Issue 4:
> >> Every single patch has heavy LFO modulation applied to VCF cutoff, irrespective of the parameters set. This modulation can't be turned off. The rate of this modulation appears to be controlled by extended parameter 11 (LFO 1 Frequency). Extended Para.12 however, has no effect on the delay before the modulation start- it starts as soon as a note is triggered. 
> >> 
> >> We exchanged quite a few emails about this towards the end of last year, and you sent me several new firmware chips to try, but none quite worked as they should, unfortunately.The modulation issue has been constant across several different chip versions though, and makes the synth basically unusable.
> >> 
> >> 
> >> I'd love to get this working. At the moment, it's for all practical purposes a brick, sadly.
> >> 
> >> Is there anything else I can try?
> >> 
> >> a|x
> >> 
> >> 
> >> 
> >> 
> >> 
> >> ________________________________
> >> From: LARRY HAWKE <gorgarh@...>
> >> To: "korgpolyex@yahoogroups.com " <korgpolyex@yahoogroups.com> 
> >> Sent: Monday, 2 July 2012, 18:18
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> >> 
> >> Mike
> >> 
> >> 
> >> 
> >> ________________________________
> >> From: Alex Drinkwater 
> >> To: korgpolyex@yahoogroups.com 
> >> Sent: Monday, July 2, 2012 11:11 AM
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> >> 
> >> 
> >> 
> >> Hi Mike.
> >> 
> >> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> >> 
> >>> Hi Poly fans,
> >>> 
> >>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> >> 
> >> Congratulations!
> >> 
> >>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> >> 
> >> That's a shame. I understand it's taken a lot of your time, over several years, though.
> >> 
> >>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> >> 
> >> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level. I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> >> 
> >> a|x
> >> 
> >>> 
> >>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> >>> 
> >>> Mike
> >>> 
> >>> 
> >>> 
> >>> ------------------------------------
> >>> 
> >>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> >>> 
> >>> 
> >>> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> -----Original Message----- 
> >> From: Michael Hawkins 
> >> Sent: 7/2/2012 3:53:53 PM 
> >> To: korgpolyex@yahoogroups.com 
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped... 
> >> 
> >> As you well know, I do my best to make sure every HAWK works for every customer. I am always available to help.
> >> 
> >> Mike
> >> 
> >> 
> >> 
> >> ________________________________
> >> From: Alex Drinkwater <the_voder@...>
> >> To: korgpolyex@yahoogroups.com 
> >> Sent: Monday, July 2, 2012 11:11 AM
> >> Subject: Re: [korgpolyex] HAWK-800 - 100+ units shipped...
> >> 
> >> 
> >> 
> >> Hi Mike.
> >> 
> >> On 2 Jul 2012, at 15:46, korgpolyex800 wrote:
> >> 
> >>> Hi Poly fans,
> >>> 
> >>> Yes, I am still producing HAWK-800's and have now just gone past 100 units sold.
> >> 
> >> Congratulations!
> >> 
> >>> I've been trying to think of a way to wind down the project but I just can't let it go just yet.
> >> 
> >> That's a shame. I understand it's taken a lot of your time, over several years, though.
> >> 
> >>> The one thing not done yet is the arpeggiator. I still remain committed to putting an arp into the HAWK. I just don't know how long it is going to take to get it done.
> >> 
> >> Personally, I'm having an arpeggiator isn't a massive priority. Unfortunately, I never got my EX-800 working properly after the mod. We exchanged emails for some time (as I'm sure you remember), then I got sidetracked into other projects, and sadly, it's been
> >> gathering dust in a box for a while now. I keep meaning to have another look at it and see if I can work out what's going wrong. When it was working, it really did sound great, and the myriad extra Hawk-800 functions really took the synth to another level.
> >> I'll dig it out of the cupboard again soon, if I get a chance. There's a good chance I'll be dropping you emails about it again though, I'm afraid. I think I'd managed to eliminate soldering errors and other more obvious causes before I let it slip, so it's
> >> either some odd hardware/software interaction 'edge-case', or maybe an underlying problem with the original hardware.
> >> 
> >> a|x
> >> 
> >>> 
> >>> How is everyone else doing with their HAWK's? It's been mighty quiet around here.
> >>> 
> >>> Mike
> >>> 
> >>> 
> >>> 
> >>> ------------------------------------
> >>> 
> >>> Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up
> >> everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo!
> >> Groups Links
> >>> 
> >>> 
> >>> 
> >> 
> > 
> > 
> > 
> > 
> > ------------------------------------
> > 
> > Feel free to upload into the files section any sysex dumps and tape dumps of patches that you may have but please discuss (with the entire group) the posting of other files *before* posting them. This helps us to keep redundant information from showing up everywhere and also allows us to constantly improve the format and structure of the documentation. We talk about the HAWK-800 quite a bit but we also discuss and help owners of the original Poly-800 models. So don't be shy if you haven't got the HAWK-800.Yahoo! Groups Links
> > 
> > 
> > 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.