Everything Phatty.
-
odavy
- Posts: 11
- Joined: Sun Apr 19, 2009 2:41 pm
Post
by odavy » Sun Jun 06, 2010 5:39 pm
Just chiming in to report another dead LP (stage 1)
I'm using a PC with a MOTU Midi Express XT interface. Demo version of the editor librarian, going from OS 2.0 to 2.1. Got to RX STAGE 2 (or similar wording) on the LP and now is stuck saying SEND FIRMWARE SX CODE ERROR 2.
I've emailed Moog and will share anything useful here. Just really upset that my prize possession is now a paperweight.

-
Amos
- Posts: 2438
- Joined: Wed Jul 23, 2003 3:11 pm
Post
by Amos » Mon Jun 07, 2010 8:44 am
it is always always a good idea to make sure you're using the very latest drivers for your MIDI hardware before attempting a firmware update. Sounds like something failed during stage 2 in this case. Still worth trying to update your MIDI drivers before attempting to send firmware again... the only question now is, "will the unit respond" to a successful firmware-sending attempt. If so, you can recover gracefully from this. If not, you will need a USB debug adapter from silicon labs in order to re-load the firmware. The debug adapter is available for $35 from SiLabs, or perhaps another forum member could loan you one. I'll email you with more info here in a moment.
Sincere apologies,
Amos
-
JWaltman
- Posts: 159
- Joined: Mon Feb 22, 2010 4:13 pm
Post
by JWaltman » Mon Jun 07, 2010 11:17 am
maybe we can make a list with owners of this box? I wouldn't mind helping people out with my debugger. I"m from Amsterdam, Netherlands.
would be nice to make a sticky thread with a list of places with people who are willing to do the same.
btw. I used the litter (de)bugger in VMWare Fusion running windows XP on my Macbook Pro, worked fine.
-
odavy
- Posts: 11
- Joined: Sun Apr 19, 2009 2:41 pm
Post
by odavy » Mon Jun 07, 2010 6:51 pm
Fixed mine! Woo!
Turns out the solution for me was as follows. Download MIDIOX, set the buffers to 1024 over 256 for both input and output, and manually send the sysex file to the phatty. It went through all five stages of recieving the file (rather than bombing out on stage 2 like last time) and now works perfectly. And if that wasn't enough, its kept all my presets. Amazing.
I would like to thank Rosser and Amos for answering my query here and via email in a remarkably short space of time, and just generally being brilliant to a customer. Guys, you have confirmed my status as a Moogaholic. I'm addicted to Moogahol!
-
diSapia
- Posts: 1
- Joined: Sun Jan 02, 2011 5:30 am
Post
by diSapia » Sun Jan 02, 2011 5:42 am
My Slim Phatty is dead - please help!
I was trying to sync logic to send the midi clock to the Slim Phatty and I went into the Arpeggiator settings on the master settings on the SP and then a message flashed up on the screen saying 'erasing flash....'. Nothing happened for 10 mins so I assumed it had crashed and turned off the SP. Now when I turn it back on the screen is blank and all the four LED dials point to the bottom right. It is not responsive so I can't update the firmware!
Also, It might be worth noting that I am using a powered USB hub with a Macbook 2.4gz Intel Core Duo. I wonder if the USB hub has send mixed up messages to wipe the SP??
Happy New Year!
Thanks
-
Sir Nose
- Posts: 1024
- Joined: Sat Sep 20, 2008 11:15 am
Post
by Sir Nose » Sun Jan 02, 2011 11:09 am
Wow, that's a completely new bug to me. Definately email or call moog support. They will work to recreate the bug and come up with a fix. I would guess the "erase flash" command is a hidden service/manufaturing command. Between the info that was being sent by midi and the knob turns/button pushes while you were menu diving, somehow it was activated.