LCD screen rebooting

[jye1]

Thank you for the detailed description. The scope did not work in stable state. A common cause for this is power supply. I'd like to suggest you do the following.

1 ) Bypass BOB3 for the time being. BOB3 could cause power supply problem so we take it out of the loop first.
2 ) Use a good USB power supply. You can tell the quality of power supply by checking VBUS with scope turned on. VBUS should be close to 5V. The closer the better.
3 ) Check +5V voltage with scope turned on to see whether it is stable.
4 ) If the problem is still there with a stable power supply then try to reflash the firmware with bootloader.

[GTNMUDY]

Jumped JP2, connected to USB power.

Voltage at JP4 is 4.98Vdc.

Voltage did not change when power up or change menu.

Still have garbled LCD screen

Will try to reflash firmware .

UPDATE:

I was able to convert the .RAR files to .ZIP and uncompress files.

Following instructions "how to upgrade firmware by bootloader"

I was able to load and exe, AVRUBD.exe

I was able to open hex file (AVRUBD.HEX)

I checked the baud rates, Hex FILE SIZE (64k)

Set file length 128 bytes

Basic time int. = 500ms

Max connect count = 25

Baud rate 9600

Data bit = 8
Stop bit = 1

The com port defaulted to com3 and not com1 as your instructions say.

I decided to try it anyway.

After 25 tries I got X connect fail

I then edited the hex file to com 3, saved it and reloaded again into AVRUBD

Confirmed that it was changed to com3 by looking a hex files.

Again tried to load firmware.

After 25 tries I got X connect fail again.

The following is a copy of the upload screen on computer:


V Loading file success: [C:\Users\My\Downloads\DSO086\Main\Hex\113-06805-010.hex]
> File length: 0x2300/8960
> Flash size: 0x10000/65536
> Buffer size: 0x2300/8960

> Start download
$ Send reset command: [7E ]
> Start connect
$ <1> Send connect key: 64
X connect fail

During the process my LCD screen did not vary or change during any functions.

I tried a different USB cable (in case first one defective)

I have confirmed that my Silicon labs CP210x driver is working and does reconize device.

At this time I still have issue with LCD screen and signal of scope operation. All other functions of DSO068 operate fine.

My next move was to use a logic probe and look at the signal from BOB1 to U4 (RXD/TXD). I do see a pulse on the RXD pin (J11, pin 1) and no pulse on J11, pin 2 (TXD).

What to do next??

Just for info, If I short out the probe leads to ground I should have no marks on the lCD screen when power up Corrtect?
In my case my power up LCD screen as shown in the LAST pic I posted to this thread if what is displayed when probe leads shorted and power up..

[jye1]

Please change the connect count to 100 or so. The default 25 sometimes is too short for DSO068 to get ready to talk to AVRUBD.

[jye1]

Please also do a VPOS alignment by setting couple switch to GND and hold down VPOS button for 3 seconds.

[GTNMUDY]

I tried 3 times to connect 100 tried and no connect.

> Start download
$ Send reset command: [7E ]
> Start connect
$ <1> Send connect key: 64
$ <2> Send connect key: 64
$ <3> Send connect key: 64
$ <4> Send connect key: 64
$ <5> Send connect key: 64
$ <6> Send connect key: 64
$ <7> Send connect key: 64
$ <8> Send connect key: 64
$ <9> Send connect key: 64
$ <10> Send connect key: 64
$ <11> Send connect key: 64
$ <12> Send connect key: 64
$ <13> Send connect key: 64
$ <14> Send connect key: 64
$ <15> Send connect key: 64
$ <16> Send connect key: 64
$ <17> Send connect key: 64
$ <18> Send connect key: 64
$ <19> Send connect key: 64
$ <20> Send connect key: 64
$ <21> Send connect key: 64
$ <22> Send connect key: 64
$ <23> Send connect key: 64
$ <24> Send connect key: 64
$ <25> Send connect key: 64
$ <26> Send connect key: 64
$ <27> Send connect key: 64
$ <28> Send connect key: 64
$ <29> Send connect key: 64
$ <30> Send connect key: 64
$ <31> Send connect key: 64
$ <32> Send connect key: 64
$ <33> Send connect key: 64
$ <34> Send connect key: 64
$ <35> Send connect key: 64
$ <36> Send connect key: 64
$ <37> Send connect key: 64
$ <38> Send connect key: 64
$ <39> Send connect key: 64
$ <40> Send connect key: 64
$ <41> Send connect key: 64
$ <42> Send connect key: 64
$ <43> Send connect key: 64
$ <44> Send connect key: 64
$ <45> Send connect key: 64
$ <46> Send connect key: 64
$ <47> Send connect key: 64
$ <48> Send connect key: 64
$ <49> Send connect key: 64
$ <50> Send connect key: 64
$ <51> Send connect key: 64
$ <52> Send connect key: 64
$ <53> Send connect key: 64
$ <54> Send connect key: 64
$ <55> Send connect key: 64
$ <56> Send connect key: 64
$ <57> Send connect key: 64
$ <58> Send connect key: 64
$ <59> Send connect key: 64
$ <60> Send connect key: 64
$ <61> Send connect key: 64
$ <62> Send connect key: 64
$ <63> Send connect key: 64
$ <64> Send connect key: 64
$ <65> Send connect key: 64
$ <66> Send connect key: 64
$ <67> Send connect key: 64
$ <68> Send connect key: 64
$ <69> Send connect key: 64
$ <70> Send connect key: 64
$ <71> Send connect key: 64
$ <72> Send connect key: 64
$ <73> Send connect key: 64
$ <74> Send connect key: 64
$ <75> Send connect key: 64
$ <76> Send connect key: 64
$ <77> Send connect key: 64
$ <78> Send connect key: 64
$ <79> Send connect key: 64
$ <80> Send connect key: 64
$ <81> Send connect key: 64
$ <82> Send connect key: 64
$ <83> Send connect key: 64
$ <84> Send connect key: 64
$ <85> Send connect key: 64
$ <86> Send connect key: 64
$ <87> Send connect key: 64
$ <88> Send connect key: 64
$ <89> Send connect key: 64
$ <90> Send connect key: 64
$ <91> Send connect key: 64
$ <92> Send connect key: 64
$ <93> Send connect key: 64
$ <94> Send connect key: 64
$ <95> Send connect key: 64
$ <96> Send connect key: 64
$ <97> Send connect key: 64
$ <98> Send connect key: 64
$ <99> Send connect key: 64
$ <100> Send connect key: 64
X Connect fail

The picture below is the LCD screen after holding down VPOS for 3 seconds.

[jye1]

Questions to your earlier post. What did you mean by "edited the hex file to com 3“？ There should be no need to edit HEX file. The comport is selected in the Comport tab under Options. Hex file can be downloaded from www.jyetech.com. It is with filename 113-06801-XXX.hex.

Did you reboot the scope right away after clicking on the "Dn" button in AVRUBD? The scope needs to enter bootloader in order to response to AVRUBD. Rebooting is to make it enter bootloader.

[GTNMUDY]

I did not understand that I needed to reboot DSO during the connecting mode.

I did get the FW 113-06805-010 loaded into DSO.

V Connect success

> Packag [70/70], Data [8.8k/8.8k], Retry [0/0]
V Update success: time elapsed: [10.2s], speed: 0.9k/s.

Now my keypad and adj functions do not work correctly.

Do I need to load the keypad.HEX (113-06804-010.hex) code next????

[GTNMUDY]

After several attemps to repair my DSO 068,, I finally got it working.

If you ever attempt to upgrade firm ware please make sure you use the correct one.

The website and instructions are somewhat un clear and after several attemps and emails to JYE I got it straight.

At this time the latest and correct firmware is: 113-06801-061

Good luck to all

Thanks for JYE tech support