NanoVNA-H white screen after installing NanoVNA-H4_20200221

[SheetLightning]

First time every updating the firmware on this. I checked the version message which indicated that my unit was running the -H version and pointed me to this GitHub. I downloaded NanoVNA-H4_20200221.bin from here:

https://github.com/hugen79/NanoVNA-H/releases

Unfortunately on completion of the firmware update my NanoVNA booted to a white screen.
Mine is the -H version and I am updating from a PC running Linux Mint 19.2 so I used the instructions from here:

https://nt7s.com/2019/11/updating-the-nanovna-firmware/

Also here:

https://oristopo.github.io/nVhelp/

Used the following command line:

dfu-util -d 0483:df11 -a 0 -s 0x08000000:leave -D NanoVNA-H4_20200221.bin

My screen came up with a white and blank and nothing else happened even after a wait of a few minutes. No menu, no control functions. Nothing. I then tried bridging the link to get into DFU mode, turned the NanoVNA off then on but the white screen persisted. After a bit of a panic moment I decided to just try uploading the firmware anyway and to my surprise the firmware upload worked, it was just that the display was not telling me that the NanoVNA was in DFU mode. Uploading the same firmware resulted in a white screen again, so I tried the ch.dfu firmware from edy55. This uploaded and booted fine, except my SWR readings seemed to be incorrect (yes I did calibrate).

After a bit of further searching, I noticed that in the previous releases of your firmware (18th January) included an "antena analyser" or "AA" variant, file name NanoVNA-H_AA_20200118.bin. In the release notes it was mentioned that it has 4 traces, thereby implying that the non AA release does not. Since the original firmware on my unit provided four traces I tried uploading -H_AA firmware version 0.4.5-4-g96e7efe to my NanoVNA and found that it boots up and works fine.

I am not sure why the latest _H version does not boot or how much difference there is between that and the AA variant although it seems to be essentially the same code with an additional function enabled? I would have therefore expected it to work, so there does seem to be an issue with the latest version of the firmware. Thankfully reverting to the previous release and returned the unit to a working state.

I should also report that the .dfu version of the firmware file would not upload. This was the error message I got:

$ dfu-util -d 0483:df11 -a 0 -D NanoVNA-H4_20200221.dfu
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)

A lsusb showed the NanoVNA with the correct device ID:

Bus 003 Device 027: ID 0483:df11 STMicroelectronics STM Device in DFU Mode

Incidentally, would it be possible to add that "AA" suffix to the version number that is being reported by the AA firmware in order to distinguish it from the non-AA variant?

In any case, thank you for your work on this firmware.

[Pmax65]

Hi SheetLightning,
if your nanoVNA-H has a 2.8" display you must use the nanoVNA-H firmware not the nanoVNA-H4 one. The latest is for the 4" inch display version that uses the STM32F330 MCU instead of the STM32F072 installed in your device. for this reason your device is now locked.

Just download the right MCU firmware and you'll get back the device working.

By the way, since the device is hanged-up now, you must turn on the board while shortcutting the two P1 pins named Boot and VDD to start the DFU mode.

Have a great day.

Massimo - IK1IZA

[SheetLightning]

Thank you for your reply. That explains it. Looking at the releases the 18th Jan 2020 release is a -H release which is why going to the earlier release worked. The later 21st Feb 2020 release changed to -H4 but I had no idea of the reason for this change so thank you for the explanation. I managed to turn on DFU mode using the jumper on P1 as described. Thank you.

[evgsm1979]

Доброго времени всем кто читает. Приобрёл NanoVNA-H v.3.4 и при первом включение получил белый экран. При втором включении прибор заработал, я подумал, что это что-то с прошивкой и перепрошил на более свежую. Но даже после этого периодически включался с белым экраном. Прошивал прошивками для H версии. Теперь прибор включается только с белым экраном. Светодиод работы мигает, но изображения нет, в режим DFU переключал закорачиванием контактов на плате. NanoVNA Saver c прибором работает, значит процессор целый. Может неисправна TLV320? Как заставить экран заработать?

[Pmax65]

Hi evgsm1979,
it looks like there are some odds on the LCD connections.
Unluckily it is soldered on the other side and the LCD metallic back shield is glued to the pcb.
The only way to redo the soldering is to unlatch the shield clips as seen in this link:

https://1.bp.blogspot.com/-oQ5HUbjfH6o/XUhfoaIoAFI/AAAAAAAAEYM/R4ZhjcC1VxEfbgxrmp-qSZgWoxZG6AZsQCLcBGAs/s1600/NanoVna%2Btop%2Bguts.jpg

Check for the STM32F072 solderings too, especially for those by which the LCD is connected with.
I don't believe the TLV320 has something to do with this issue.

Have a nice day.

Massimo

[evgsm1979]

Good afternoon, Massimo. Thank you for your very quick response. I soldered the screen again. Not help. I will solder STM32F072 again. But I noticed that the device freezes in front of the white screen. The device often freezes and then turns on a white screen. The device itself works with a PC and Android, only the screen is white. This is quite inconvenient, I need to set up antennas with it. Stitched also always good versions for n. Good day UB9YWB 73!!!

[evgsm1979]

Or maybe it's just a defective screen, how can I check it to find out for sure?

[evgsm1979]

https://drive.google.com/file/d/15P-SOFXcuvib-plJeht2BXfw019qVZhz/view?usp=sharing,%20https://drive.google.com/file/d/165TWeE2D9kyg9Uqo5cQSdkoxXqVeGtmi/view?usp=sharing,%20https://drive.google.com/file/d/16FaPWjqLuECJDb-6csWQGunYUNd_UoYC/view?usp=sharing,%20https://drive.google.com/file/d/16ObS7pwfoOdGVYnoRpnB5T74zdlBkzJY/view?usp=sharing

[Pmax65]

Hi evgsm1979,
is the above the picture of your own LCD?
I don't know if the lower side of the LCD flexible pcb has a twin contact for any upper contact, but ground pin 8 looks broken in that picture.
Some LCDs have separated ground for the I/O controller, the LCD, the touchscreen and the serial interface.
In case that it's your LCD, I'll tried to redo that pin8 connection.

Have a great day

Best 73 from Massimo - IK1IZA

[evgsm1979]

Hello again. Photos of the display are mine. I took it off and re-soldered it. They call all the contacts everywhere. Also soldered STM and TLV320. There are no changes. The screen doesn't work, only the backlight is on. I'll attach a photo. What should I do next? Thank you for your answers.
https://drive.google.com/file/d/1k5z7e_XZYNlquH9XwBhgbrxOsQyBSUFM/view?usp=sharing

[evgsm1979]

Too bad, I don't have an Arduino yet. I can't check the TFT. Or how can I check the display without Arduino?

[Pmax65]

Hi evgsm1979,
everything lead to a defective LCD, but since you said that "The second time the device was turned on", I guess that you meant that the LCD at least one time worked right, is it that?
In that case, if you were lucky, you could redo all the soldering of the components on the flexible pcb.
Between them, there are the serial interface timings capacitors, maybe that one bad soldering inhibits the serial interface to run correctly.

Just try it, and let me know.

In the meantime, have a great day.

Massimo - IK1IZA

[evgsm1979]

Massimo good afternoon. Capacitors on a flexible loop soldered. It didn't help. Stood up with an oscilloscope on the display contacts and signals and go to it. So the display is probably faulty. Thank you for your assistance in Troubleshooting. You need to buy a suitable display on aliexpress, I live in the village and we do not have radio stores. Good Luck To You 73. UB9YWB.

[Pmax65]

Hi evgsm1979,
sad to read that.

Those LCDs are COGs and sometimes the slight difference in expansion between the silicon chip and the glass may lead to connection disjuncture.

Here is a research about that issue.
https://www.jim.or.jp/journal/e/pdf3/52/11/2106.pdf

It looks like you had been unlucky.

Have grat days,
Massimo

[evgsm1979]

Hi, Massimo. Well, then just bad luck with this instance. I will order a new one in China. Thank you for your help in solving the problem. Good luck in life and business, the topic is not closed yet, I will write the result on the screen. UB9YWB 73!

333,86 руб. | 3,5-дюймовый TFT ЖК-экран
https://a.aliexpress.com/_AX6C9l

[Pmax65]

Hi evgsm1979,

luckily it looks pretty cheap, so you have just to wait for its arrival.
Let me know how it will work.

In the meantime have great days.

All the best from Italy.

Massimo - IK1IZA

[evgsm1979]

Greetings from Siberia. You can wait until November 20. As soon as I install it, I will definitely write here. 73! UB9YWB.

[evgsm1979]

Hi, Massimo. Got a screen with Aliexpress. Set and the instrument is earned. So it was the display. All the best, health, take care of yourself. 73!!! UB9YWB.

[Pmax65]

Hi evgsm1979,
nice to read that you fully fixed the issue with little bucks and just some time to wait.
I hope you enjoy your nanoVNA.
Have great days.
I wish you all the best-

73 de IK1IZA

[schumar]

Just in case someone found this report because they were searching for the "does not match device" error:
It helps to simply not specify -d 0483:df11 when flashing, i.e. just do

dfu-util -a 0 -D NanoVNA-H_20210916.dfu