Nbox BZZB 5800sx Decoder: Startup Failures, Uboot Issues and Debug Connector Flashing

Hello,

I own a decoder NBox 5800sx BZZB. The tuner is converted and Enigma was uploaded. One day the tuner stopped turning on. I moved the jumper , however, did not upload the uboot again. Now again the tuner stopped working (no response on the display) and switching between jumpers does not help. I understand that the uboot at addresses A19 and A20 is defective. If I remove the jumper completely, it shows TEST.
Is there any chance to save this tuner? Any flashing directly through the DEBUG connector? Please help.

A very common malfunction of these devices is damage to the electrolytic capacitors on the motherboard and/or on the head board.
See if they are not swollen, or have someone inspect and repair them.
The symptoms of damaged capacitors can range from not turning on, to hangs during operation....

I looked at the capacitors and they do not look swollen. Anyway, they were replaced.
Is there any way to check if the uboot is not damaged? Or what points to measure to rule out the capacitors?
I would not want to re-solder the board if it is not necessary.

It is the failure of the decoder to boot from U-boot (selected by shorting point A19 or A20 to +3.3)
that proves that both are defective.

OK. Yes, and I understand that. The question is, how can I re-flash the uboots? Because if they both don't get up then the USB option is out.

You are operating returns from GSM, and modification of nBox BZZB on E2, however, is very different from the "cell" flashing.
Generally - program NAND in an external programmer (or buy a programmed one)
and solder NAND with u-boots.
Register and read the rest about this decoder and E2:
http://forum.dvhk.to/showthread.php?t=833978

Does this mean that if both uboots (from under address A19 and A20) die, there is no way to program them other than in an external programmer?

This is what you should do in the case of the first malfunction and working u-boot spare:
http://sat-mar.com.pl/wp-content/uploads/2009...BZZB-BXZB-pod-A020-z-Zapasu-A019-27.07.17.rar
Now have someone who can fix the decoder.

I would just like to find out what needs to be done to fix it. The fact that I should wave the uboot and not go to the A19 is something I've known for a long time.

In post #6 I stated what to do; how to do it and where to read about it - I provided a link.
What do you expect more? A golden platter?

Is it possible to fire ubot still from another address? For example, A17, or A18? Do they have to be uploaded there during the conversion?
Could someone please mark in the following picture where A18, A19 and A20 are located?

.

The picture below from the subject [url=]https://www.elektroda.pl/rtvforum/topic2748290.html[/url]

If there are programmed bypasses in the M28W320FST memory of type NOR then they can be started by applying a high state >1.9V to a single address line or to several lines, e.g.:
A20 runs a bypass from address A0200000
A19 ----------------------------------A0100000
A18 A0080000
A17 A0040000
A20+ A19 A0300000
It is possible that a bypass at address A0300000 survived, so I would additionally supply 3.3V from the disk connector to the second line of A20.To the board you need to have a cable connected to the debug connector or connected display then you will see if the uboot is there.

Super, thanks for the factual answer.
In that case, since I have the modchip and brought out A19 and A20 on the jumper it is enough to short all 3 pins with each other. Am I right
I shorted A19+A20, but it looks like there is nothing there, because immediately TEST turned on. The same with A16.

If you connect two points A20 and A19, the voltage will be too small for the processor to read this as high state H.I wrote that you have to connect the second line, that is, give a jumper-cable between +3.3V from the disk connector and point A20 . Point A19 you have already connected to 3.3V of the debug connector and there is about 1.9V or state H.Voltage to the debug connector is given by three resistors 100 Ohm connected in parallel and therefore the voltage drops when we connect more current consumers - in this case, these are the address lines .

In my case, 3.3V is not taken from DEBUG (taken from the transistor near the HDD power supply). It looks like the following pictures.
On the modchip pins I have in sequence (counting from the DEBUG side):
1 - A20
2 - 3.3V
3 - A19
With the jumper disconnected I have pin 1 = 0V, pin 2 = 3.3V, pin 3 = 3.3V. Is this how it should be?
.

To check if there is a bypass at address A0300000 then:
1.Unplug the RESET cable from the first photo
2.From the modchip board, unsolder both cables A20 and A19 and solder to 3.3V - drive power
If it displays a bypass then you can continue to upload the other bypasses, and if not then replace the NOR memory (this is the one closer to the processor and the other is the NAND memory)
Programmed memory can be purchased, for example, on Allegro.

Thanks for your help.
Unfortunately I touched one of the components of the board to the case while checking.
Now I have to fix the board first. :o )
)
Element pictured.

It's the L38 choke.The current that powers the fan flows through this choke and does not affect booting.The schematics in this post may help click click[/url] click

Thanks a lot for the info on the choke and the link to the schematics. I desoldered all the wires from the modchip and shorted A20+A19 to the 3.3V supply to the HDD. Unfortunately the display is still dark.

After shorting A19+A20, I hooked up to DEBUG this time and got this info.
Any tips on what to do next?
.

Zelu00 wrote:

Does this mean that if both uboots (from under address A19 and A20) die, there is no way to program them other than in an external programmer?

exactly as you write


--> https://www.elektroda.pl/rtvforum/topic3524676.html
programmed new processor and decoder lives

marcin.koz2910 what you wrote is not true !There may be other bypasses in NOR memory and not only at address A0200000 and A0100000.Above you have proof of this in the form of reporting the bypass at address A0300000 after shorting A20 and A19 to 3.3V.
Zelu00 further :
After reporting the bypass, you can reprogram the tuner via cable or reanimation using a usb memory with the bypass file and img script.
The second way is simpler:
You download the package http://sat-mar.com.pl/wp-content/uploads/2009...BZZB-BXZB-pod-A020-z-Zapasu-A019-27.07.17.rar
In the case of a healthy uboot under A0300000, the procedure is a little different ie:
1.On the flash drive put the files from the folder ubootA020+env.You turn off the tuner, pen you put into the tuner.
2.On line A19 mount a switch or something that will facilitate quick disconnection of current between A19 and 3.3V from the disk.The switch is to initially short A19 and 3.3V !Line A20 is to be connected to 3.3V from the disk.
3.Turn on the tuner with the POWER key pressed.While holding POWER (the display should say PROG) you disconnect cable A19 and release POWER.When OK appears on the display you turn off the tuner.
4.The A19 line has to be disconnected !
Turn on the tuner and if everything was successful then on the display should be written u-boot 1.3.1 053
5.Restore connections to the modchip i.e. A19, A20, RESET
6.After reporting the bypass you select the NAND boot source and confirm OK
7.Wait until the tuner loads the soft from NAND
When it will be ok then upload the backup bypasses from:
http://andrewkore.pl/warsztat.html.

Thanks a lot! Tuner works from under A20.
However, after uploading u-boot under A19 only nbox text appears.
Debug shows:
U-Boot 1.3.1 (Sep 21 2014 - 19:22:00) - stm23_0053

DRAM: 128 MiB
NOR: 4 MiB
NAND: 64 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
nbox>

I understand that I should upload env yet? Just how?

In a tuner with a modchip, only the "main" bypass from under the A20 jumper should give a soft boot from nand, which is why the main bypass has a larger size because it contains ENV, or configuration data.The other "auxiliary" bypasses are for rescuing the tuner when the main bypass gets damaged.

I guess that's not quite the case, because in my case it was so that when a uboot from under A20 died I switched to A19 and everything worked until under A19 died. That's why I lost both uboots.

I will dig up the topic a bit... I got to the stage that the uboot loads with the given method, OK at the end, however, after restarting on a disconnected line with a19 the uboot does not start.... Any idea? What is wrong?

It is possible that you remove the jumper from A19 too late and program a completely different area.

After PROG shows up, I first disconnect the jumper, then let go of Power....