Analogue-sequencer

Folks,

I have identified a rarely occuring bug in the Atmel flash ROM 
programming API in the CPU used in production P3s, and later kits 
(serial numbers #2001 on).

The effect of the bug is to cause some CPU configuration bytes to be 
erased when firmware blocks are being written.
This means the CPU will not boot until it has been reset in a 
programmer.

The bug has very rarely occured - only 4 CPUs have become unbootable 
out of nearly 100 of this CPU type during all the firmware updates 
in the last year, so it's not a major risk, but the result is that 
your CPU needs to be swapped out, so it's a major inconvenience if 
it does happen.

Having now identified exactly what effect the bug has, I have 
updated the P3 bootloader to include a check and fix routine that 
should ensure no CPU ends up un-bootable.

A patch to update your bootloader can be found in Yahoo files, with 
the filenames:
   p3-bootloader-v3.3-AT.mid
or p3-bootloader-v3.3-AT.syx

The text file p3-bootloader-v3.3-AT.txt explains how to install it.

This update is not required for pre-production P3s using the older 
CPU type.

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

Hello, I have found some issues updating to the new SO. First I tried to do it with the P3 Tools 1.06 with no results, no data is received wit the P3. Even I tried later to receive patches to the utility and nothing. This application was working last time I used it, I checked midi channels, configs etc... Any idea?

My second try was with Midi OX and the P3 received data, but with each block I got a "Bad Data" message on the display. After all, rebooting the P3 shew a V 3.1006. Now it seems to be working and with the software updated but the "Bad Data" messages make me doubt. So, do you think I updated correctly the P3? Anybody experienced these issues?

Thanks for your comments.

Regards.

Miguel.


[Non-text portions of this message have been removed]

> Hello, I have found some issues updating to the new SO. First 
> I tried to do it with the P3 Tools 1.06 with no results, no 
> data is received wit the P3. Even I tried later to receive 
> patches to the utility and nothing. This application was 
> working last time I used it, I checked midi channels, configs 
> etc... Any idea?

That does sound like a MIDI problem at the PC end.
You could try deleting and re-defining the P3 connection in "Define P3s",
and make sure the ports are still OK.
IIRC, adding or reinstalling MIDI devices can cause them to be numbered
differently.
 
> My second try was with Midi OX and the P3 received data, but 
> with each block I got a "Bad Data" message on the display. 
> After all, rebooting the P3 shew a V 3.1006. Now it seems to 
> be working and with the software updated but the "Bad Data" 
> messages make me doubt. So, do you think I updated correctly 
> the P3? Anybody experienced these issues?

It could be a MIDI loop causing the BAD DATA messages.
If the newly installed firmware boots up without the bootloader giving a
'CHK error', then it has installed OK.

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

Well, it was booting untill right now. All leds on upper and step mode are on but the unit doesn't boot.

Any idea?

Thanks.

  ----- Original Message ----- 
  From: Colin f 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Wednesday, April 12, 2006 11:24 AM
  Subject: RE: [analogue-sequencer] Updating to 3.1006



  > Hello, I have found some issues updating to the new SO. First 
  > I tried to do it with the P3 Tools 1.06 with no results, no 
  > data is received wit the P3. Even I tried later to receive 
  > patches to the utility and nothing. This application was 
  > working last time I used it, I checked midi channels, configs 
  > etc... Any idea?

  That does sound like a MIDI problem at the PC end.
  You could try deleting and re-defining the P3 connection in "Define P3s",
  and make sure the ports are still OK.
  IIRC, adding or reinstalling MIDI devices can cause them to be numbered
  differently.

  > My second try was with Midi OX and the P3 received data, but 
  > with each block I got a "Bad Data" message on the display. 
  > After all, rebooting the P3 shew a V 3.1006. Now it seems to 
  > be working and with the software updated but the "Bad Data" 
  > messages make me doubt. So, do you think I updated correctly 
  > the P3? Anybody experienced these issues?

  It could be a MIDI loop causing the BAD DATA messages.
  If the newly installed firmware boots up without the bootloader giving a
  'CHK error', then it has installed OK.

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




------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "analogue-sequencer" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     analogue-sequencer-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



[Non-text portions of this message have been removed]

Hi Miguel, 

> Well, it was booting untill right now. All leds on upper and 
> step mode are on but the unit doesn't boot.
> 
> Any idea?

This is the same fault that should be resolved by the new bootloader
version, though if it has happened after you have already applied the
firmware update and power-cycled your P3 a few times, it is rather worrying.

Fortunately I just have found a way to fix this problem using MIDI Ox.

To give you a little background...

The CPU used in P3 has internal flash memory to hold program data.
It also has an extra section of memory which comes pre-loaded with an
in-system programming application that means you can install a user program
over the serial interface.
Once you have installed a user program, a configuration byte is set that
means when the CPU is next powered up, the user program runs rather than the
internal bootloader.

The few 'dead' CPUs that have appeared so far have lost the configuration
setting that indicates there is a user program installed.
There is no reason why this setting should have been lost - the firmware
update process doesn't change it, and the flash ROM is supposed to be
protected against spurious writes by a power control circuit.

When the configuration setting is lost, the CPU boots into the Atmel
bootloader program.
The way to fix the booting problem is to send the Atmel bootloader a 'start
application' instruction.
When you do this, it should run the installed user program - the P3
bootloader.

When you start the P3 bootloader, you must hold FUNC+PAGE to enter firmware
update mode, then you will be able to install the new bootloader which will
re-write the CPU settings so it boots normally.

I'll write up the instructions for fixing a dead CPU, and post them shortly.

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

perfect timing.  Last night I loaded 3.1.006 by removing the MIDI 
loop (d'oh!).  The update went over but the BAD DATA message appeared 
after the update.  I shut off, turned on ,and it came up showing 
3.1.006 and ran fine.  I played it for several hours with no 
problems.  However, I was workign through the User Guide & I stumbled 
into an advanced menu (apologies, I didn't write it down) and 
suddenly nothing worked, unit was frozen.  Turned off, turned on and 
nothing in the LCD, but the 2 sets of 3 vertical lights were constant 
on.

So, I will try this when I get home.  I did not update the bootloader 
since I was under the impression this was only for newer CPUs and my 
unit is quite old.

But talk about fast service!  Thanks.


--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@...> 
wrote:
>
>  
> > Hello, my P3 now doesn't boot anymore, all the upper and step 
> > mode leds remain on. Colin, maybe this is the bug you 
> > descreibed before? My unit is pretty new.
> 
> I have uploaded a file called "P3Resurrection.pdf" to the Yahoo 
files
> section.
> This file describes how to use MIDIOx to force a 'dead' CPU to boot 
up

> manually, so that you can install the latest bootloader.
> This should fix the problem.
> Download the file "p3-bootloader-v3.3-AT.syx" and the readme file
> "p3-bootloader-v3.3-AT.txt" as you'll need them also.
> 
> And let me know how you get on...
> 
> Best regards,
> Colin Fraser
> Sequentix Music Systems Ltd
> http://www.sequentix.com
>

Hello, my P3 now doesn't boot anymore, all the upper and step mode leds remain on. Colin, maybe this is the bug you descreibed before? My unit is pretty new.

Thanks.

Miguel.


[Non-text portions of this message have been removed]

> Hello, my P3 now doesn't boot anymore, all the upper and step 
> mode leds remain on. Colin, maybe this is the bug you 
> descreibed before? My unit is pretty new.

I have uploaded a file called "P3Resurrection.pdf" to the Yahoo files
section.
This file describes how to use MIDIOx to force a 'dead' CPU to boot up
manually, so that you can install the latest bootloader.
This should fix the problem.
Download the file "p3-bootloader-v3.3-AT.syx" and the readme file
"p3-bootloader-v3.3-AT.txt" as you'll need them also.

And let me know how you get on...

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

Just to be sure, is this the bug's that's done my cpu's in in P3's
#23&45 or was that something else?

grtz, Chiel

Hi Colin, unfortunatly it didn't work for me. The unit doesn't respond to any sysex message or file. The display doesn't show anything and the leds are still on.
Any idea?

Thanks.

Miguel.

  ----- Original Message ----- 
  From: Colin f 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Wednesday, April 12, 2006 4:20 PM
  Subject: RE: [analogue-sequencer] Updating to 3.1006 do Not boot anymore



  > Hello, my P3 now doesn't boot anymore, all the upper and step 
  > mode leds remain on. Colin, maybe this is the bug you 
  > descreibed before? My unit is pretty new.

  I have uploaded a file called "P3Resurrection.pdf" to the Yahoo files
  section.
  This file describes how to use MIDIOx to force a 'dead' CPU to boot up
  manually, so that you can install the latest bootloader.
  This should fix the problem.
  Download the file "p3-bootloader-v3.3-AT.syx" and the readme file
  "p3-bootloader-v3.3-AT.txt" as you'll need them also.

  And let me know how you get on...

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




  SPONSORED LINKS Music sampler  Midi sequencer  Sampler  


------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "analogue-sequencer" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     analogue-sequencer-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



[Non-text portions of this message have been removed]

> Just to be sure, is this the bug's that's done my cpu's in in P3's
> #23&45 or was that something else?

No, those were the older Temic parts.
When they corrupt their flash, the lose chunks of the main program.
That hasn't happened very often either, maybe 5 to 10 times out of 80 or so
CPUs of that type.
I had thought the Atmel parts were better, and I suppose they are in the
sense that they only seem to lose a configuration byte rather than the
program flash. But I'd much rather have CPUs with 100% flash reliability.
We'll see how the Atmel parts work out with the updated bootloader.

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

Same here.  When you send the 55, should you see anything anywhere - 
either on the P3 or the MIDIOx screens?

I can't tell that anything happens and I have to delete the 55 from 
the command window before entering the pasted string.

Any help appreciated.

--- In analogue-sequencer@yahoogroups.com, "Miguel Mendoza" 
<miguel@...> wrote:
>
> Hi Colin, unfortunatly it didn't work for me. The unit doesn't 
respond to any sysex message or file. The display doesn't show 
anything and the leds are still on.
> Any idea?
> 
> Thanks.
> 
> Miguel.
> 
>   ----- Original Message ----- 
>   From: Colin f 
>   To: analogue-sequencer@yahoogroups.com 
>   Sent: Wednesday, April 12, 2006 4:20 PM
>   Subject: RE: [analogue-sequencer] Updating to 3.1006 do Not boot 
anymore
> 
> 
> 
>   > Hello, my P3 now doesn't boot anymore, all the upper and step 
>   > mode leds remain on. Colin, maybe this is the bug you 
>   > descreibed before? My unit is pretty new.
> 
>   I have uploaded a file called "P3Resurrection.pdf" to the Yahoo 
files
>   section.
>   This file describes how to use MIDIOx to force a 'dead' CPU to 
boot up
>   manually, so that you can install the latest bootloader.
>   This should fix the problem.
>   Download the file "p3-bootloader-v3.3-AT.syx" and the readme file
>   "p3-bootloader-v3.3-AT.txt" as you'll need them also.
> 
>   And let me know how you get on...
> 
>   Best regards,
>   Colin Fraser
>   Sequentix Music Systems Ltd
>   http://www.sequentix.com
> 
> 
> 
> 
>   SPONSORED LINKS Music sampler  Midi sequencer  Sampler  
> 
> 
> -------------------------------------------------------------------
-----------
>   YAHOO! GROUPS LINKS 
> 
>     a..  Visit your group "analogue-sequencer" on the web.
>       
>     b..  To unsubscribe from this group, send an email to:
>      analogue-sequencer-unsubscribe@yahoogroups.com
>       
>     c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms 
of Service. 
> 
> 
> -------------------------------------------------------------------
-----------

> 
> 
> 
> [Non-text portions of this message have been removed]
>

Here's what I did.

I opened up Midi OX, turned on my P3, and saw the LED's.


I then opened up the Sysex window from view and typed 55 and then did a 
Send Sysex from the
Command Window menu.  Then I pasted over the top of 55 (so 55 was NOT 
there) the string
that is in the PDF.  I then went and hit Func and Page at the same time, 
and while still holding,
would then have MidiOX send Sysex.

I think the first time that I did nothing was on the screen, then I 
rebooted the box
and tried it again, and this time after sending of the longer string, 
the P3 then displayed
the F1)Boot F3) Flash menu.  I did the boot, so that it would write it 
into the P3 and then
had to load in the OS, before finally booting and seeing my P3 back to 
normal :)


Hopefully it will go as well a for you. Hope this helps a bit.

Dave


synchro1 wrote:

> Same here.  When you send the 55, should you see anything anywhere - 
> either on the P3 or the MIDIOx screens?
>
> I can't tell that anything happens and I have to delete the 55 from 
> the command window before entering the pasted string.
>
> Any help appreciated.
>
> --- In analogue-sequencer@yahoogroups.com, "Miguel Mendoza" 
> <miguel@...> wrote:
>   
>> Hi Colin, unfortunatly it didn't work for me. The unit doesn't 
>>     
> respond to any sysex message or file. The display doesn't show 
> anything and the leds are still on.
>   
>> Any idea?
>>
>> Thanks.
>>
>> Miguel.
>>
>>   ----- Original Message ----- 
>>   From: Colin f 
>>   To: analogue-sequencer@yahoogroups.com 
>>   Sent: Wednesday, April 12, 2006 4:20 PM
>>   Subject: RE: [analogue-sequencer] Updating to 3.1006 do Not boot 
>>     
> anymore
>   
>>
>>   > Hello, my P3 now doesn't boot anymore, all the upper and step 
>>   > mode leds remain on. Colin, maybe this is the bug you 
>>   > descreibed before? My unit is pretty new.
>>
>>   I have uploaded a file called "P3Resurrection.pdf" to the Yahoo 
>>     
> files
>   
>>   section.
>>   This file describes how to use MIDIOx to force a 'dead' CPU to 
>>     
> boot up
>   
>>   manually, so that you can install the latest bootloader.
>>   This should fix the problem.
>>   Download the file "p3-bootloader-v3.3-AT.syx" and the readme file
>>   "p3-bootloader-v3.3-AT.txt" as you'll need them also.
>>
>>   And let me know how you get on...
>>
>>   Best regards,
>>   Colin Fraser
>>   Sequentix Music Systems Ltd
>>   http://www.sequentix.com
>>
>>
>>
>>
>>   SPONSORED LINKS Music sampler  Midi sequencer  Sampler  
>>
>>
>> -------------------------------------------------------------------
>>     
> -----------
>   
>>   YAHOO! GROUPS LINKS 
>>
>>     a..  Visit your group "analogue-sequencer" on the web.
>>       
>>     b..  To unsubscribe from this group, send an email to:
>>      analogue-sequencer-unsubscribe@yahoogroups.com
>>       
>>     c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms 
>>     
> of Service. 
>   
>> -------------------------------------------------------------------
>>     
> -----------
>   
>>
>> [Non-text portions of this message have been removed]
>>
>>     
>
>
>
>
>
>
>
>  
> Yahoo! Groups Links
>
>
>
>  
>
>
>
>

> Same here.  When you send the 55, should you see anything anywhere - 
> either on the P3 or the MIDIOx screens?

Make sure you can see both the input monitor and output monitor windows in
MIDIOx, have the PC ouput connected to the P3, and the P3 input connected
back to the PC.
When you send the '55', it must be sent as a single byte - without any F0 or
F7 around it.
You should see the 55 sent, and echoed by P3 as in this image:
http://www.sequentix.com/images/MIDIOx.jpg

If you don't see that, it's possible that MIDIOx is filtering the byte, or
isn't configured quite right.
Make sure MIDI pass-through is not active - in the "Options", "MIDI
Devices..." window, turn off "Automatically attach inputs to outputs during
selection" and make sure there are no input ports shown in the 'port
mapping' for the output port.
Also make sure 'MIDI-Ox Events' are mapped to the output, like this:
http://www.sequentix.com/images/MIDIOx2.jpg

It's also possible that your MIDI drivers will refuse to send a MIDI message
without a status byte.
You could test the connection by connecting the MIDI output on your PC
directly back to the MIDI input, and see if the 55 is sent and received.

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