[Strong] Post deleted by ToxicQ

[Gast]

@TeeBee<P>Het minste wat men kan doen van STRONG & Co uit is een uitleg geven hoe we de bootloader terug moeten installeren. Dat zal hun al een hoop werk besparen denk ik.<P>IQ

[Gast]

Dit heb ik alvast gevonden (en effe vertaald vanuit het SPAANS) :<P>***********************************************<BR>My Strong is dead (display does not ignite)<P>This problem is solved of different ways, some of them to probably fixes the terminal you. It remembers that in the forum you can find aid in case that this does not work: <P>Solution 1: It verifies that your terminal gives life signs, that is to say, test if connecting it to the PC and forming port COM, when igniting it, loader it detects that deco exists. It will have to put something in the inferior window, although it is only a rare sign. The important thing is that intercommunication exists. If you have been able to put it in way CHA (although you do not see it in display because it is in black), test to introduce firmware again. It can that way CHA is only put if it detects some error in firmware, so you do not worry if you do not see display. If the new load is made correctly, your deco will return to normality and will return to illuminate display. If this has not worked it follows with the following thing: <P>Solution 2: We continued supposing that something of intercommunication between deco exists and PC has perhaps not let to us load firmware, can that deco continues waiting for data. First of all we must say to the Strong that lets hope. This becomes of the following form: <BR>1. - Pon in march the Strong (non-modal CHA). <BR>2. - It executes the Loader2000 and it chooses the COM to which it is connected. 3. - In the window of down always in small letters and without comiles it presses: " h " leaves something? " control + c " several times leaves something? " g " ignites display? <BR>4. - If it is not thus it ignites the Strong putting it in way CHA and returns to try to load firmware again. If this to continued either does not happen to the following solution: <P>Solution 3: In some cases the previous thing is not sufficient. Then we must act as it is indicated: <BR>1 Abre the hyperterminal and configuralo (you know to form it) <BR>2 Enciende the terminal. <BR>3 Pulsa a key <BR>4 Aparecerá something like: " Acces Code " (password is requesting you to enter UNDER) <BR>5 Quickly you key in " cafe " (without the comiles) <BR>6 If it has not given time you and it leaves " aim acces code ", it returns to point 3. <BR>7 Already you are in UNDER <BR>8 Pulsa " c " and the Rx will be hoping that him loadings a file. <BR>9 Cierra the hyperterminal. <BR>10- Abre loader, forms the COM and selects the file that you want to send. <BR>11- Pulsa START When doing this, will load new firmware, but it is possible that it follows without igniting display. As soon as loadings firmware and you reinitiate the terminal (to pay and to ignite with the button of the frontal) would be due to ignite. <P>Solution 4: Sometimes the problem is not firmware, that is to say, ours deco apparently is dead because a condenser is overloaded. That condenser is in the frontal of the Rx, and can cause that micro does not work micro of the frontal (this controls everything: display, remote control, keys of the frontal, clock...) The case that has occurred changing the frontal of the terminal by another equal one if it worked perfectly. It is not necessary that you prove to put another frontal to prove, is possible to be fixed of the following form if this it is your case: We extinguished to the Rx. Removing the frontal, in the board it has a condenser of 0,22 uF that uses as a batería.(Es green and with form of small battery) we must cortocircuitar It (uniting pins both) during seconds (I could jump a spark). One does not forget to you to again connect the frontal to the board before closing it If this era the problem, when igniting deco everything will go OK display will ignite and it is possible to be returned to load firmware. <P>Solution 5: It can that micro of which it is spoken before always is reseteado, doing that does not work anything, but that is not due to the condenser that is indicated. Not if bypassing a transistor that is alongside fixes, but if that there are to have fixed experiences it resoldando it again. <P>Solution 6: This is the solution that cures everything almost, not to say the totality. It is the most tragic solution and the one than one is due to practice in last instance or case of having lost certainty to have boot of the terminal. Boot can be lost of diverse forms, and once it is had lost we were without the communication between PC and Strong. This means that we will not be able to reprogramar flash BFC0 to again introduce boot to him through loader. The form to do it will be more delicate. With very many taken care of we will have to desoldar flash BFC0 (it is identified in the photos of the inner section " of the terminal ") Is flash has 48 pins, with which in addition you must have very many patience. Which remembers that to find this type of flash in a store he is very complicated, with if we spoiled it can that is the aim of deco, we do not have spare part. Once we have it loose, we will have it to take to some store that programs flashes (if we do not have the clear programmer) and we take the special file to him for programmers whom boot contains so that they introduce it. Once programmed, with end again taken care of, we will weld the flash in its site well, fixing to us that we placed it in the correct and not invested position. If it beams in complete instance, can that you take a joy. <P> <P>********************************************<P>Ik hoop dat het iemand kan helpen ???<P> <P>IQ<p>[ 29-06-2001: Message edited by: IQ ]

[Gast]

Wanner zijn ze begonnen met deze updates te sturen?<BR>Ik heb nl een Galaxis IRD2000, en 5 weken geleden was hij plotseling 'dood', met de originele kaart erin !<BR>Ik heb hem nu teruggestuurd, vanuit griekenland, maar dat kost nogal wat! Dan zal ik zeker een claim bi ze indienen als het daardoor is ....

[Ron]

dat lijkt me sterk want canal+ heeft deze upgrade pas deze week uitgevoerd.<P>Toxic[Q]

[Gast]

Gaat deze "Update" in de uitzendnorm ook gevolgen hebben voor CI ontvangers, of hebben die er niets mee te maken. <BR>(ik wil toch wel graag de NL zenders op mijn Humax kunnen blijven bekijken...)

[Gast]

De update voor de nokia en Strong is nodig omdat deze ontvangstproblemen hebben. Het signaal dat canal plus nu zend is aangepast zodat er geen problemen meer waren met de nokia en strong. Nu is canal plus van plan te stoppen met deze 'speciale' uitzend norm en wil weer gewoon op de 'normale' manier gaan uitzenden. en daarom moeten de nokia en de strongs voorzien worden van nieuwe software. In deze software zit natuurlijk ook de regiocode in. <P>De wijziging van uitzenden zal de humax en andere CI ontvangers dus niet beinvloeden.

[Ron]

om het overzichtelijk te houden is dit topic gesloten en kan men in het andere (enige) topic dat nu nog open is, verder talken.<P>Toxic[Q]