Barco 9xx flash memory back up

Yepp, definitely a difference between the two. Here some pics of my controllers. The one installed in my Cine 9 is R7631255, manufactured in 2003 and the spare one is R763125, manufactured in 2000. 

Like i already mensioned, they have Cine 9 V2.21 soft. now, they work like they should and the fan noise is the same ( low ).

Several PCB revisions has seen the light during the development of this controller. The PCB nr. of R763125 is 780822 rev.1 and the one from R7631255 is 780822 rev.4.

 On the new one, we can see indeed more components, connectors and a bit different lay-out. I doubt it is very relevant to the good working of the PJ, but theoretically newer should be beter.

I do have the schematics of both, i will post them soon.

Fox, i don't think there is a SEOS/BR with 2.21 soft. As far as i know, V2.20, V2.13 and V2.21 were CineMax/Cine 9 specific software versions. Could be, like in my situation, that the controller was flashed with Cine 9 V2.21 bin. file but the Lattice chip was not overwritten. The issue we were talking about with Dummyload.

Maybe here is also the difference between R763125 and R7631255. When i flashed the newer style controller from BR909 V3.11 to Cine 9 V2.21, the Lattice chip was overwritten too. The ID screen says Cine 9:

When i flashed the older style controller from whatever it was on ( remember, it was a dead controller ), the Lattice chip was not overwritten. The ID menu still says SEOS PRODAS:

I am not sure why you get diff. noise levels from both controllers. The version nr. should be relevant, not the ID.

Some clarification.

As far as I know there are different versions of the PCB of the controller, but the schematics are the same ?? .Chip I4, of lattice is programmed hardware,it's programmed to take care of the timming between the different chips in the core, they all are connected to the same data and adresslines so The lattice chip controls who is on and who is of  (compare it with traffic lights)

I do not yet have a drawing off the connections that has to be made.

Any programmer that supports a 29f800b should work in theory ,i used the TL866cs progger with socket adapter to support the 29f800b ,so i first bought a 29f800b so i could test the progger surely workt  , and it did.

 So there are two 29f800b memories on the controller (I6 andI7) ,some steps have to be taken so the progger only sees I6 or I7 (so nothing blows up when connecting together)

You can power the controller up with an external power supply of 9v through sr4 ,current is between 0.8A and 1.3A.

I used a five dipswitches to make the different modes.

You have to follow the following sequence.

Firstly you have to reset the whole core with dipswitch1, this is done by pulling the line "RST.ISPEN" to zero (massa).

Secondly you have to bring the lattice chip I4 in program mode ,this brings the outputs off the lattice chip in tristate mode with internall pullups (100k),this is done by pulling the "ISPEN" line to zero. (pull line " SDI" and "SCLK" to zero with 1k resistor ,to prevent this lines from floating ,to be shure nothing happens to the contents off the lattice chip ,that would distroy the board ,nowbody has the fusemap to reprogram the lattice chip , only barco has)

Thirdly we have to select the memorie that we want to read or write to ,because there are two memories there are two dipswitches for select a memories one for I6 and one for I7 , of course )only one can be set at a time , this done by connecting  line " CS.FL0 " (I6) or "CS.FL1 " (I7) to the " CE " line of the progger.(pin26)

Fourtly we have to release the reset of the memories only ,this is done by pulling line " DIS.RST.FL " to zero.

Now you can read out or write to the selected memorie .

Better would be to connect the reset line of the memories to the reset line of the progger  (pin12) but then you have to invert the signal, so i manualy give a reset between every read or write with the dipswich of the fourth step.

The plug itself is the biggest challence, but latter on that.

To be clear i'm not responsble for any damage to controller progger or bought ,use it only if you now what you're doing.

I had to ad a resistor on the progger to because the data and adress lines from the controller are pulled to 5v through 100k internal. The progger does not expect any voltage on its lines

and without the resistor i had always socket error.

I hope you can make something out of it .