Korg Poly800/EX800 Users

Well, now it's really toast... I tried to re-upgrade the Boot ROM and I get errors. Awesome!

Here's a compilation of what I'm seeing. I only got one "Good 0" out of about 10 trys with 2.4.2 and 2.4.3. I am getting to Flash5 step though, then the error occurs.

2.4.2 - EEPROM0.syx
0C680
0E880

2.4.2 - EEPROM1.syx
19050
16E50 (or 1bE50, it didn't have a horizontal top line)
1GF50 (or 16F50, it did have a horizontal top line)

2.4.3 - EEPROM0.syx
0d140
01F40
0E940

At least there's kind of a pattern here. Mike, please let me know if you have any insight into this problem. I have gone around a hit all the chips solder points and even pulled the EPROM to make an image of it in case that was bonky. I only saw one difference from the file online and I assume that's because you have changed something since the file was uploaded. Address 0x10 I have CC instead of C4. If you don't have any other tips I guess my next step is to de-solder the EEPROMs (ugh) and blank them out with my burner.

Thanks,
Everett

--- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@.. .> wrote:
>
> Should have just waited to post... that didn't take long. Sequencer works fine now that I enabled that global parameter 24. I can't find any problems with this thing other than the SYSEX dumps. This time it failed with a 4 showing. Is there a way to access the memory at the moment of failure? I really don't see how I am able to do all this other stuff and it be a hardware problem. It takes a very long time to fail, like it just runs out of room or something. Is that possible?
>
> --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@> wrote:
> >
> > I have not tried the sequencer, but the midi control works... actually everything I've tried works which seems weird. I have also copied the standard patches over from ROM with no problem (diag 6). I have seen two more failure modes now that I have tried a few times. The one time I did it, there was a 4, then a C, but mostly an H. Yes it is in the position where the word PATCH would be. I always have to "reboot" at that point. There is never a PATCH5, so I'll go back and touch up my soldering. Hopfully I find something there or I get lucky and it will just start working after I re-touch all the contacts.
> >
> > Thanks!
> > Everett
> >
> > --- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ > wrote:
> > >
> > > Hi Everett,
> > >
> > > If you send a HAWK patch dump to your EX-800 while using "Flash" mode then you will write patch data over one of the flash ROM's that contains software. So you were right to reflash all of the ROM's again.
> > >
> > > Now, while sending a HAWK flash patch dump you say that the display changed to PATCH4. But did you also see it change to PATCH5 even for just for a moment? Normally, the PATCH5 message will only show for less than a second but it is quite obvious if it does show up.
> > >
> > > Or did it just go from PATCH4 to "H" without ever showing PATCH5? I assume that the "H" is quite bright and it is in the position of the "H" in "PATCH" - right?
> > >
> > > If that is all true then I would say that you need to check your soldering of the 28C256 ROM on the HAWK board. Because when the display is showing PATCH4, the HAWK software is copying the uploaded software from RAM memory into the patch EEROM. And if it is able to successfully copy over all of the patch data then the display changes to PATCH5. And PATCH5 is the message that is displayed while the HAWK does a data integrity check. The integrity check only happens after all of the data is copied into the patch data EEROM.
> > >
> > > So I would check the soldering of the 28C256.
> > >
> > > Does all of the functions of the HAWK work? Have you tested the sequencer? The patch editing? Used some of the MIDI controllers?
> > >
> > > Mike
> > >
> > >
> > >
> > >
> > > ____________ _________ _________ __
> > > From: Everett <evy_newt@>
> > > To: korgpolyex@yahoogro ups.com
> > > Sent: Thu, November 12, 2009 8:10:18 PM
> > > Subject: [korgpolyex] Freshly upgraded EX-800
> > >
> > >
> > > Just received my second Hawk-800 kit... this time with the Atomahawk portion too! I have a few questions about this new sample dump feature. I had previously been running a Poly-800 with the original kit (1.2 BOOT ROM, who knows what software) so this is all new to me.
> > >
> > > Here's what's happening:
> > >
> > > I enter diag mode 8, send the bulk file from the 2.4.3 zip file... everything looks like the manual says (Flash4 etc.), but then I get a big fat H instead of a "Good". I'm pretty sure it locks up at this point because it won't respond to anything.
> > >
> > > I should say I accidentally loaded this bulk file once during the ROM flash routine (not realizing the difference). I did go back and re-load the three EEPROM files after that and everything seems to be working except these sysex dumps.
> > >
> > > Is it possible that there are still something hanging out in the EEPROMs from that instance? Also, how do I load the sysex patches posted in the files section. They show "Error 2" in this "Diag 8" mode and I can't seem to find any other reference to a different mode. As you can see I'm a little confused... don't use SYSEX much.
> > >
> > > Thanks,
> > > Everett
> > >
> >
>

Jeez, I'm beginning to feel like this is a blog. All is well now! It was a stupid timing issue with the SYSEX buffers. I realized that the same behavior was occurring on my Poly as the EX no matter what I did. Swapping things back and forth, burning new EPROMs, etc. I forgot that the first time I did the ROM flash I was using the 4096/8 buffer timing as the manual states. Later on I moved to the 128/256/20ms timing as the OS manual states. Then while doing the Bulk Dumps I was using the 1024/32/2000 timing as in the MIDI hints and tips section. Eventually what worked for me (M-Audio 1010LT card) was the original option of 4096/8. Not sure why, but after all this, I don't really care. Just in case anyone was following this I didn't want to waste their time.

--- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@.. .> wrote:
>
> Well, now it's really toast... I tried to re-upgrade the Boot ROM and I get errors. Awesome!
>
> Here's a compilation of what I'm seeing. I only got one "Good 0" out of about 10 trys with 2.4.2 and 2.4.3. I am getting to Flash5 step though, then the error occurs.
>
> 2.4.2 - EEPROM0.syx
> 0C680
> 0E880
>
> 2.4.2 - EEPROM1.syx
> 19050
> 16E50 (or 1bE50, it didn't have a horizontal top line)
> 1GF50 (or 16F50, it did have a horizontal top line)
>
> 2.4.3 - EEPROM0.syx
> 0d140
> 01F40
> 0E940
>
> At least there's kind of a pattern here. Mike, please let me know if you have any insight into this problem. I have gone around a hit all the chips solder points and even pulled the EPROM to make an image of it in case that was bonky. I only saw one difference from the file online and I assume that's because you have changed something since the file was uploaded. Address 0x10 I have CC instead of C4. If you don't have any other tips I guess my next step is to de-solder the EEPROMs (ugh) and blank them out with my burner.
>
> Thanks,
> Everett
>
>
>
>
>
> --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@> wrote:
> >
> > Should have just waited to post... that didn't take long. Sequencer works fine now that I enabled that global parameter 24. I can't find any problems with this thing other than the SYSEX dumps. This time it failed with a 4 showing. Is there a way to access the memory at the moment of failure? I really don't see how I am able to do all this other stuff and it be a hardware problem. It takes a very long time to fail, like it just runs out of room or something. Is that possible?
> >
> > --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@> wrote:
> > >
> > > I have not tried the sequencer, but the midi control works... actually everything I've tried works which seems weird. I have also copied the standard patches over from ROM with no problem (diag 6). I have seen two more failure modes now that I have tried a few times. The one time I did it, there was a 4, then a C, but mostly an H. Yes it is in the position where the word PATCH would be. I always have to "reboot" at that point. There is never a PATCH5, so I'll go back and touch up my soldering. Hopfully I find something there or I get lucky and it will just start working after I re-touch all the contacts.
> > >
> > > Thanks!
> > > Everett
> > >
> > > --- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ > wrote:
> > > >
> > > > Hi Everett,
> > > >
> > > > If you send a HAWK patch dump to your EX-800 while using "Flash" mode then you will write patch data over one of the flash ROM's that contains software. So you were right to reflash all of the ROM's again.
> > > >
> > > > Now, while sending a HAWK flash patch dump you say that the display changed to PATCH4. But did you also see it change to PATCH5 even for just for a moment? Normally, the PATCH5 message will only show for less than a second but it is quite obvious if it does show up.
> > > >
> > > > Or did it just go from PATCH4 to "H" without ever showing PATCH5? I assume that the "H" is quite bright and it is in the position of the "H" in "PATCH" - right?
> > > >
> > > > If that is all true then I would say that you need to check your soldering of the 28C256 ROM on the HAWK board. Because when the display is showing PATCH4, the HAWK software is copying the uploaded software from RAM memory into the patch EEROM. And if it is able to successfully copy over all of the patch data then the display changes to PATCH5. And PATCH5 is the message that is displayed while the HAWK does a data integrity check. The integrity check only happens after all of the data is copied into the patch data EEROM.
> > > >
> > > > So I would check the soldering of the 28C256.
> > > >
> > > > Does all of the functions of the HAWK work? Have you tested the sequencer? The patch editing? Used some of the MIDI controllers?
> > > >
> > > > Mike
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: Everett <evy_newt@>
> > > > To: korgpolyex@yahoogro ups.com
> > > > Sent: Thu, November 12, 2009 8:10:18 PM
> > > > Subject: [korgpolyex] Freshly upgraded EX-800
> > > >
> > > >
> > > > Just received my second Hawk-800 kit... this time with the Atomahawk portion too! I have a few questions about this new sample dump feature. I had previously been running a Poly-800 with the original kit (1.2 BOOT ROM, who knows what software) so this is all new to me.
> > > >
> > > > Here's what's happening:
> > > >
> > > > I enter diag mode 8, send the bulk file from the 2.4.3 zip file... everything looks like the manual says (Flash4 etc.), but then I get a big fat H instead of a "Good". I'm pretty sure it locks up at this point because it won't respond to anything.
> > > >
> > > > I should say I accidentally loaded this bulk file once during the ROM flash routine (not realizing the difference). I did go back and re-load the three EEPROM files after that and everything seems to be working except these sysex dumps.
> > > >
> > > > Is it possible that there are still something hanging out in the EEPROMs from that instance? Also, how do I load the sysex patches posted in the files section. They show "Error 2" in this "Diag 8" mode and I can't seem to find any other reference to a different mode. As you can see I'm a little confused... don't use SYSEX much.
> > > >
> > > > Thanks,
> > > > Everett
> > > >
> > >
> >
>

Hehe, looking back I guess it looks like I was frantic? I was methodically going through what I knew about. I have been at this for two days now ;) I still cannot load the "Global Defaults" dump or anything besides the Bulk dump. I am going to assume it's a compatibility problem and move on to creating patches.

Thanks for the tips! If you need any pictures to improve the manual let me know. I still have everything loose.

--- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ ...> wrote:
>
> Those error codes could mean a couple of different things.
>
> 1) check the +5 volt rail is bang on 5 volts. Adjust it if necessary. Measure the rail with the HAWK board plugged in.
> 2) check that the "write" jumper is correctly installed.
> 3) double check all of the address and data lines on the HAWK board.
>
> I still think that point 3 is most likely. Just don't start removing chips or anything like that. Please just slow down and be patient. We can get this going but you need to take your time.
>
> Check the three things above, then try again using v2.43 files. Don't use 2.42. The differences between them are very small and are not going to change the outcome of your current situation.
>
> Mike
>
>
>
>
> ____________ _________ _________ __
> From: Everett <evy_newt@.. .>
> To: korgpolyex@yahoogro ups.com
> Sent: Fri, November 13, 2009 12:56:05 PM
> Subject: [korgpolyex] Re: Freshly upgraded EX-800
>
>
> Well, now it's really toast... I tried to re-upgrade the Boot ROM and I get errors. Awesome!
>
> Here's a compilation of what I'm seeing. I only got one "Good 0" out of about 10 trys with 2.4.2 and 2.4.3. I am getting to Flash5 step though, then the error occurs.
>
> 2.4.2 - EEPROM0.syx
> 0C680
> 0E880
>
> 2.4.2 - EEPROM1.syx
> 19050
> 16E50 (or 1bE50, it didn't have a horizontal top line)
> 1GF50 (or 16F50, it did have a horizontal top line)
>
> 2.4.3 - EEPROM0.syx
> 0d140
> 01F40
> 0E940
>
> At least there's kind of a pattern here. Mike, please let me know if you have any insight into this problem. I have gone around a hit all the chips solder points and even pulled the EPROM to make an image of it in case that was bonky. I only saw one difference from the file online and I assume that's because you have changed something since the file was uploaded. Address 0x10 I have CC instead of C4. If you don't have any other tips I guess my next step is to de-solder the EEPROMs (ugh) and blank them out with my burner.
>
> Thanks,
> Everett
>
>
> --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@ .> wrote:
> >
> > Should have just waited to post... that didn't take long. Sequencer works fine now that I enabled that global parameter 24. I can't find any problems with this thing other than the SYSEX dumps. This time it failed with a 4 showing. Is there a way to access the memory at the moment of failure? I really don't see how I am able to do all this other stuff and it be a hardware problem. It takes a very long time to fail, like it just runs out of room or something. Is that possible?
> >
> > --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@> wrote:
> > >
> > > I have not tried the sequencer, but the midi control works... actually everything I've tried works which seems weird. I have also copied the standard patches over from ROM with no problem (diag 6). I have seen two more failure modes now that I have tried a few times. The one time I did it, there was a 4, then a C, but mostly an H. Yes it is in the position where the word PATCH would be. I always have to "reboot" at that point. There is never a PATCH5, so I'll go back and touch up my soldering. Hopfully I find something there or I get lucky and it will just start working after I re-touch all the contacts.
> > >
> > > Thanks!
> > > Everett
> > >
> > > --- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ > wrote:
> > > >
> > > > Hi Everett,
> > > >
> > > > If you send a HAWK patch dump to your EX-800 while using "Flash" mode then you will write patch data over one of the flash ROM's that contains software. So you were right to reflash all of the ROM's again.
> > > >
> > > > Now, while sending a HAWK flash patch dump you say that the display changed to PATCH4. But did you also see it change to PATCH5 even for just for a moment? Normally, the PATCH5 message will only show for less than a second but it is quite obvious if it does show up.
> > > >
> > > > Or did it just go from PATCH4 to "H" without ever showing PATCH5? I assume that the "H" is quite bright and it is in the position of the "H" in "PATCH" - right?
> > > >
> > > > If that is all true then I would say that you need to check your soldering of the 28C256 ROM on the HAWK board. Because when the display is showing PATCH4, the HAWK software is copying the uploaded software from RAM memory into the patch EEROM. And if it is able to successfully copy over all of the patch data then the display changes to PATCH5. And PATCH5 is the message that is displayed while the HAWK does a data integrity check. The integrity check only happens after all of the data is copied into the patch data EEROM.
> > > >
> > > > So I would check the soldering of the 28C256.
> > > >
> > > > Does all of the functions of the HAWK work? Have you tested the sequencer? The patch editing? Used some of the MIDI controllers?
> > > >
> > > > Mike
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: Everett <evy_newt@>
> > > > To: korgpolyex@yahoogro ups.com
> > > > Sent: Thu, November 12, 2009 8:10:18 PM
> > > > Subject: [korgpolyex] Freshly upgraded EX-800
> > > >
> > > >
> > > > Just received my second Hawk-800 kit... this time with the Atomahawk portion too! I have a few questions about this new sample dump feature. I had previously been running a Poly-800 with the original kit (1.2 BOOT ROM, who knows what software) so this is all new to me.
> > > >
> > > > Here's what's happening:
> > > >
> > > > I enter diag mode 8, send the bulk file from the 2.4.3 zip file... everything looks like the manual says (Flash4 etc.), but then I get a big fat H instead of a "Good". I'm pretty sure it locks up at this point because it won't respond to anything.
> > > >
> > > > I should say I accidentally loaded this bulk file once during the ROM flash routine (not realizing the difference). I did go back and re-load the three EEPROM files after that and everything seems to be working except these sysex dumps.
> > > >
> > > > Is it possible that there are still something hanging out in the EEPROMs from that instance? Also, how do I load the sysex patches posted in the files section. They show "Error 2" in this "Diag 8" mode and I can't seem to find any other reference to a different mode. As you can see I'm a little confused... don't use SYSEX much.
> > > >
> > > > Thanks,
> > > > Everett
> > > >
> > >
> >
>

Hehe, looking back I guess it looks like I was frantic? I was methodically going through what I knew about. I have been at this for two days now ;) I still cannot load the "Global Defaults" dump or anything besides the Bulk dump. I am going to assume it's a compatibility problem and move on to creating patches.

Thanks for the tips! If you need any pictures to improve the manual let me know. I still have everything loose.

--- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ ...> wrote:
>
> Those error codes could mean a couple of different things.
>
> 1) check the +5 volt rail is bang on 5 volts. Adjust it if necessary. Measure the rail with the HAWK board plugged in.
> 2) check that the "write" jumper is correctly installed.
> 3) double check all of the address and data lines on the HAWK board.
>
> I still think that point 3 is most likely. Just don't start removing chips or anything like that. Please just slow down and be patient. We can get this going but you need to take your time.
>
> Check the three things above, then try again using v2.43 files. Don't use 2.42. The differences between them are very small and are not going to change the outcome of your current situation.
>
> Mike
>
>
>
>
> ____________ _________ _________ __
> From: Everett <evy_newt@.. .>
> To: korgpolyex@yahoogro ups.com
> Sent: Fri, November 13, 2009 12:56:05 PM
> Subject: [korgpolyex] Re: Freshly upgraded EX-800
>
>
> Well, now it's really toast... I tried to re-upgrade the Boot ROM and I get errors. Awesome!
>
> Here's a compilation of what I'm seeing. I only got one "Good 0" out of about 10 trys with 2.4.2 and 2.4.3. I am getting to Flash5 step though, then the error occurs.
>
> 2.4.2 - EEPROM0.syx
> 0C680
> 0E880
>
> 2.4.2 - EEPROM1.syx
> 19050
> 16E50 (or 1bE50, it didn't have a horizontal top line)
> 1GF50 (or 16F50, it did have a horizontal top line)
>
> 2.4.3 - EEPROM0.syx
> 0d140
> 01F40
> 0E940
>
> At least there's kind of a pattern here. Mike, please let me know if you have any insight into this problem. I have gone around a hit all the chips solder points and even pulled the EPROM to make an image of it in case that was bonky. I only saw one difference from the file online and I assume that's because you have changed something since the file was uploaded. Address 0x10 I have CC instead of C4. If you don't have any other tips I guess my next step is to de-solder the EEPROMs (ugh) and blank them out with my burner.
>
> Thanks,
> Everett
>
>
> --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@ .> wrote:
> >
> > Should have just waited to post... that didn't take long. Sequencer works fine now that I enabled that global parameter 24. I can't find any problems with this thing other than the SYSEX dumps. This time it failed with a 4 showing. Is there a way to access the memory at the moment of failure? I really don't see how I am able to do all this other stuff and it be a hardware problem. It takes a very long time to fail, like it just runs out of room or something. Is that possible?
> >
> > --- In korgpolyex@yahoogro ups.com, "Everett" <evy_newt@> wrote:
> > >
> > > I have not tried the sequencer, but the midi control works... actually everything I've tried works which seems weird. I have also copied the standard patches over from ROM with no problem (diag 6). I have seen two more failure modes now that I have tried a few times. The one time I did it, there was a 4, then a C, but mostly an H. Yes it is in the position where the word PATCH would be. I always have to "reboot" at that point. There is never a PATCH5, so I'll go back and touch up my soldering. Hopfully I find something there or I get lucky and it will just start working after I re-touch all the contacts.
> > >
> > > Thanks!
> > > Everett
> > >
> > > --- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ > wrote:
> > > >
> > > > Hi Everett,
> > > >
> > > > If you send a HAWK patch dump to your EX-800 while using "Flash" mode then you will write patch data over one of the flash ROM's that contains software. So you were right to reflash all of the ROM's again.
> > > >
> > > > Now, while sending a HAWK flash patch dump you say that the display changed to PATCH4. But did you also see it change to PATCH5 even for just for a moment? Normally, the PATCH5 message will only show for less than a second but it is quite obvious if it does show up.
> > > >
> > > > Or did it just go from PATCH4 to "H" without ever showing PATCH5? I assume that the "H" is quite bright and it is in the position of the "H" in "PATCH" - right?
> > > >
> > > > If that is all true then I would say that you need to check your soldering of the 28C256 ROM on the HAWK board. Because when the display is showing PATCH4, the HAWK software is copying the uploaded software from RAM memory into the patch EEROM. And if it is able to successfully copy over all of the patch data then the display changes to PATCH5. And PATCH5 is the message that is displayed while the HAWK does a data integrity check. The integrity check only happens after all of the data is copied into the patch data EEROM.
> > > >
> > > > So I would check the soldering of the 28C256.
> > > >
> > > > Does all of the functions of the HAWK work? Have you tested the sequencer? The patch editing? Used some of the MIDI controllers?
> > > >
> > > > Mike
> > > >
> > > >
> > > >
> > > >
> > > > ____________ _________ _________ __
> > > > From: Everett <evy_newt@>
> > > > To: korgpolyex@yahoogro ups.com
> > > > Sent: Thu, November 12, 2009 8:10:18 PM
> > > > Subject: [korgpolyex] Freshly upgraded EX-800
> > > >
> > > >
> > > > Just received my second Hawk-800 kit... this time with the Atomahawk portion too! I have a few questions about this new sample dump feature. I had previously been running a Poly-800 with the original kit (1.2 BOOT ROM, who knows what software) so this is all new to me.
> > > >
> > > > Here's what's happening:
> > > >
> > > > I enter diag mode 8, send the bulk file from the 2.4.3 zip file... everything looks like the manual says (Flash4 etc.), but then I get a big fat H instead of a "Good". I'm pretty sure it locks up at this point because it won't respond to anything.
> > > >
> > > > I should say I accidentally loaded this bulk file once during the ROM flash routine (not realizing the difference). I did go back and re-load the three EEPROM files after that and everything seems to be working except these sysex dumps.
> > > >
> > > > Is it possible that there are still something hanging out in the EEPROMs from that instance? Also, how do I load the sysex patches posted in the files section. They show "Error 2" in this "Diag 8" mode and I can't seem to find any other reference to a different mode. As you can see I'm a little confused... don't use SYSEX much.
> > > >
> > > > Thanks,
> > > > Everett
> > > >
> > >
> >
>

So this will be implemented as a SYSEX dump eventually just like the SW upgrades? That will be nice... I like that you're going all flash. UV EPROMS are kind of a pain to deal with even though I have all the stuff to program and erase them.

I have been experimenting with those dumps and I don't seem to be getting the patch acknowledgment message "F0 42 21 06 F7" from the synth. I get the "F0 42 21 01 F7" message after the bulk dump though. There are some weird things with the MIDI CCs too, but I haven't played with them enough to figure out specific problems. The one thing I noticed is CC 32 (Bank Select) does not seem to work at all. Is there a better place to post possible bugs or would that just be on here?

I forgot to tell you that the board quality is very nice. Much improved from the original single sided board. I was looking through your blog posts and realized how long you've been at this. You have come a long way! Let me know what type of help I can lend and I'll do my best to pitch in.

Everett

--- In korgpolyex@yahoogro ups.com, Michael Hawkins <korgpolyex800@ ...> wrote:
>
> Everett and all HAWK owners,
>
> For those of you with EPROM programmers and who wish to upgrade the boot EPROM to the latest version of boot software, I uploaded the binary file onto the hawk800.com web tech support area. It's at the bottom of the page. The file is named boot.bin.txt so that after you download it to your PC you will need to rename it as boot.bin. The boot file is version 1.5 which has the extra flash download integrity checking etc.
>
> All kits that are shipped out now are sent with a EEROM (28C64) for the boot ROM and an extra 28 pin socket is shipped too. This socket is used for the first software ROM after the boot ROM. This allows HAWK owners to upgrade the boot ROM by sending the boot code to the first normal software flash ROM and then swapping it with the original boot ROM.
>
> It sounds complicated but is really quite easy to do. I will be writing up the procedure soon and will add it to the owners manual.
>
> As a simple alternative, I will be adding a new "buy it now" button to the website so that owners can just buy the boot ROM upgrade which I will ship out. I am thinking about 7.50 plus a buck or two for shipping.
>
> You don't have to upgrade the boot ROM but as I add more diagnostic and checking functions, it will become more attractive to do so.
>
> Mike.
>