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
>
>
>