Owon DS7104 oscilloscope, stopped at the start logo.

[rubennss]

I have already written a forum post about this oscilloscope, I suspected that the reason for stopping on the start logo was the failure of one of the inverters.
All voltage inverters seem to be working properly.


 I was able to connect to the oscilloscope using the PUTTY program and here is what I got in response:
NAND: 512 MiB


U-Boot 2008.10 (Apr 14 2014 - 09:37:23)

OMAP35X-Family-GP rev 2, CPU-OPP2 L3-165MHz
OMAP3 SPQ board + LPDDR/NAND
readenv ERR*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x1ff80000, size 0x40000
NAND read from offset 1ff80000 failed -117
 262144 bytes read: ERROR
## Executing script at 80800000



Everything points to damaged NAND memory, damaged tin balls under the memory or damaged firmware.
I wrote to the manufacturer about the firmware, I did not get any answer,  nor could I find  it on the Internet ( it used to be available, but is no longer).
If anyone had a similar problem please guide me to a solution.
I plan to solder out the memory, put new balls on, solder back in and see what happens.

There is a tiny battery on the motherboard ( it had 1.9V instead of 3V), replacing it with a new one did not help.

[m k]

So low battery voltage corrupted a memory somewhere.

Maybe there is a factory default boot something procedure.
Like press this and that button when powering the machine.

[rubennss]

Thanks for the answer.
Before I wrote the forum post, I checked several possibilities and combinations by pressing different “buttons” and turning on the oscilloscope. I also pressed the buttons in different combinations as the oscilloscope was on.
I already have a second Owon ( different model) which has exactly the same problem. All indications are that this is a manufacturing defect in Owon oscilloscopes, depletion of the memory backup battery causes CRC failure.
I also did not find any jumper on the board with which to perform a reset, unplugging the battery pack from the board and shorting the contacts does not help either.
I heard back from the manufacturer, he asked for the serial number, I sent it to him, I am waiting for a reply back.
I found on the web a program to replace the firmware in the Owon, unfortunately for the program to work, it must connect to the oscilloscope and see its serial number, then you can upload new firmware.
The program can't see the serial number, because the boot loader didn't start, and the circle closes.
If there is not some simple method to reset the memory, then you will need the contents of the memory ( memory batch) to progrom it.
I am waiting for information from the manufacturer.
If it is a factory defect and nothing can be done about it, it will not make sense to buy new oscilloscopes of this brand.
 

[GGMM]

hello,

look here.
two videos  in polish



if it's an help you
cdt

[rubennss]

These are my videos, I discussed in them what I asked in my post on this forum.
 You can turn on the translator and English subtitles.

[GGMM]

Re,

I had a bit of a feeling. The coincidence was troubling LOL

I think there is only one solution, Reflasher.
There are lots of posts on equivalent cases of locked oscilloscopes (Ex Rigol 1052)
example:  https://www.eevblog.com/forum/blog/the-dark-side-of-the-rigol-hack-bricked-scope-how-to-fix-it/msg5753045/#msg5753045
But, you have to find a flash for it.
Normally there should be a connector to connect a programmer (ex a wriggler or segger)
With  a Wriggler and software Topjtag, it's very slow. 12Hrs for 64 mo.

But you have no answer at this time for a flash
https://www.eevblog.com/forum/repair/owon-ds7104-(tds7104)-oscilloscope-firmware-needed/


see also here:


cdt

[GGMM]

Re,

try some search with OWON word
example: https://www.eevblog.com/forum/testgear/owon-sds7102v-scope-freezing-up-please-help/msg4566394/#msg4566394

cdt

[m k]

Is it any kind of regular U-Boot?
There are monitor commands, regular 'Help' also.

[rubennss]

Help is, I am not an IT specialist, if you know the right command, please write me.

[m k]

Have you tried its PC software?

Since you have a low battery situation the actual scope software is probably fine.

The '0' after 'Hit any key', is it you or a countdown?

First error is 'readenv', that is probably not NAND.
NAND is big and battery backed NVRAM is smaller.

Then its 'using default environment' can be wrong.
And so NAND read can be something that doesn't fit.

GitHub has U-Boot monitor commands.
Simple '?' for help is also present.

But I guess you need a working buddy to compare how things should be.
U-Boot is just a boot manager, it can't know how your environment variables should be.