Analogue-sequencer

I adopted the early P3 formerly played by John Duval.  Shortly after 
it arrived, I upgraded the bootloader and then up to firmware 
3.1.005 with no problems.

Time goes by; the instrument is great.  I decided ti was time to 
upgrade to 3.1.006 tonight.  I used the sys file from sequentix.com 
with MidiOx through an M-Box 2 into the P3.  This is what worked for 
me previously.  FUNC + PAGE at power up, F3 to accept f/w, then send 
on the sysex from MidiOx through USB to MBox2 and MIDI cables to P3.

BAD DATA appears almost immediately in the window.  The firmware 
does not updgrade.  Now when I turn on the P3 I get CHK FAIL = 
9C43.  I select F3 and try again.  I check MidiOx for buffer and 
milliseconds pause after F7.  No dice.  I pull out ym old MidiSport 
USB 4x4; no difference.

Any obvious issues or solutions here?  I am very inexperienced with 
Midi in general.

I have not changed PCs, drivers, OS, firewalls or anything since the 
last successful upgrade.

Thanks in advance,
Jim W.
San Mateo, CA

Hi,

I had almost exactly the same issue with an older P3 last week. I was 
using MidiOx as well and got the BAD DATA messages when sending the 
upgrade. I tried a few times to no avail. 

What solved my problem was using P3 Tools to send the firmware to the 
P3. I believe that MidiOx had been trying to send the firmware at a 
rate that was too fast for the P3. P3 Tools is available in 
the 'Files' section.

Cheers

Simon

--- In analogue-sequencer@yahoogroups.com, "synchro1" <synchro1@...> 
wrote:
>
> I adopted the early P3 formerly played by John Duval.  Shortly 
after 
> it arrived, I upgraded the bootloader and then up to firmware 
> 3.1.005 with no problems.
> 
> Time goes by; the instrument is great.  I decided ti was time to 
> upgrade to 3.1.006 tonight.  I used the sys file from sequentix.com 
> with MidiOx through an M-Box 2 into the P3.  This is what worked 
for 
> me previously.  FUNC + PAGE at power up, F3 to accept f/w, then 
send 
> on the sysex from MidiOx through USB to MBox2 and MIDI cables to P3.
> 
> BAD DATA appears almost immediately in the window.  The firmware 
> does not updgrade.  Now when I turn on the P3 I get CHK FAIL = 
> 9C43.  I select F3 and try again.  I check MidiOx for buffer and 
> milliseconds pause after F7.  No dice.  I pull out ym old MidiSport 
> USB 4x4; no difference.
> 
> Any obvious issues or solutions here?  I am very inexperienced with 
> Midi in general.
> 
> I have not changed PCs, drivers, OS, firewalls or anything since 
the 

> last successful upgrade.
> 
> Thanks in advance,
> Jim W.
> San Mateo, CA
>

> I had almost exactly the same issue with an older P3 last week. I was 
> using MidiOx as well and got the BAD DATA messages when sending the 
> upgrade. I tried a few times to no avail. 

When P3 receives a firmware block, it takes a little while to decode and
write it into the flash ROM.
When it's done the writing, it sends a handshake message.

MIDI Ox doesn't wait for handshake messages, so it needs to put a long
enough gap between blocks so that the writing is finished before it sends
the next block.

P3 Tools waits for the handshake message, so it will send the code as fast
as P3 can write it, but no faster.

To set up the correct delay in MIDI Ox:

Start Midi Ox
Go to "View", "Sysex..."
In the Sysex View and Scratchpad window, go to "Sysex", "Configure..."
Make sure the "Delay after F7:" checkbox is ticked, and enter a delay of
100ms
Click "OK" to go back to the sysex window, then you can send the sysex file

Alternatively, you can use the MID file version of the firmware, and play it
with Windows Media Player, or a.n.other midi file player.
The MID file has the delay encoded into it.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

> BAD DATA appears almost immediately in the window.  The firmware 
> does not updgrade.  Now when I turn on the P3 I get CHK FAIL = 
> 9C43.  I select F3 and try again.  I check MidiOx for buffer and 
> milliseconds pause after F7.  No dice.  I pull out ym old MidiSport 
> USB 4x4; no difference.

Ah, I missed that you had already checked the delay time earlier...

Could it be you have a MIDI loop ?
When P3 sends the handshake messages, if MIDI Ox sends them back to P3, it
can cause problems.
Make sure you have only MIDI out on the PC to MIDI in on the P3.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

On Tue, 11 Apr 2006, Colin f wrote:

> Could it be you have a MIDI loop ?
> When P3 sends the handshake messages, if MIDI Ox sends them back to P3, it
> can cause problems.
> Make sure you have only MIDI out on the PC to MIDI in on the P3.

What you are describing sounds exactly like what I've experienced when
I've accidentally left the MIDI out plugged in. Make sure it's unplugged,
then try again.

- F.

At 02:32 AM 4/11/2006, you wrote:
>
> > BAD DATA appears almost immediately in the window.  The firmware
> > does not updgrade.  Now when I turn on the P3 I get CHK FAIL =
> > 9C43.  I select F3 and try again.  I check MidiOx for buffer and
> > milliseconds pause after F7.  No dice.  I pull out ym old MidiSport
> > USB 4x4; no difference.
>
>Ah, I missed that you had already checked the delay time earlier...
>
>Could it be you have a MIDI loop ?
>When P3 sends the handshake messages, if MIDI Ox sends them back to P3, it
>can cause problems.
>Make sure you have only MIDI out on the PC to MIDI in on the P3.
>
>Best regards,
>Colin Fraser
>Sequentix Music Systems Ltd
>http://www.sequentix.com

Yes, it was a MIDI loop.  I should know better.  Thanks to everyone 
for the prompt replies.