Unfortunately it seems the same thing has happened to my Kiwisix yesterday.
I installed Kiwisix a couple of years ago although not had much time to use it due to other things. But it worked when I did use it but mostly without any midi conneted. Anyway, I had recently read on the KiwiTechnics website about this bug and how turning the synth on while midi was being sent to it could corrupt the firmware memory on the chip so I thought I had better get around to installing the latest update. So yesterday I updated to the latest version K6_P400_B301_Build1. The bootloader seemed to update fine and the Bank D button was lit at the end of that. Then when I turned off the synth and powered on again holding Load Bank B button and updated with K6_Prog_v400_Build1.SYX, the process seemed to stall about 30 seconds to a minute into the update. I left it for about 5 minutes just in case but it just sat there with several lights on seemingly frozen. So I had no choice but to turn off. When I turned it back on the synth seemed to load up ok, first showing
lights 4 and 7&8 I think, then those went off and light 1 went on, which is the normal case. I read that I would need to restore the factory programs so I tried Factory 1 reset procedure and set 'Tape Enable' Switch to On and the LED turned on, then I tried to press Bank D button, but it didnt flash which it was supposed to for this procedure. So I thought maybe I have done this wrong. So I powered off and then back on again in order to try a factory restore again. But instead of turning on normally again, all the LED lights from Arp to 8 and from Bank A to Write are On. I have tried turning off and unplugging the IEC cable for 10 mins, and I disconnected all midi
cables. But each time I turn on the synth it is frozen with all those lights on, no sound when playing keys and totally frozen so it seems.
I have emailed Murray so will wait for his reply, and while doing that I thought I would post here as it sounds
exactly like what has happened to me, and sounds exactly like the bug that this update was supposed to fix. Sod's law so it seems, but somewhat disappointing.
If anyone has any ideas on what I can try please let me know, but I guess realistically I will have to wait and find out what Murray advises. I do have a Programmer so it might be easier to try reprogramming the chip than having to send the board back to NZ, but on my board the chip is soldered directly, and not on a daughterboard as I see on some photos so its going to be a real pain to desolder and resolder that chip due to the tiny legs on it.
Thanks in advance for any help.