¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Freeze after upgrade. NanoVNA-H


 

I bought this NanoVNA-H almost a year ago and it has always come up with "si5351 init Failed" Error. Yesterday I decided to see if a firmware upgrade would sort out the error. I no longer have the error but the device does not resopnd to either the jog wheel or the touch screen. Basically it is doing nothing other then powering on.The image I ghave used is NanoVNA.H4.v1.2.00.dfu. I have also tried the previous version NanoVNA.H4.v1.1.00.dfu with the same results.

Any help would be greatly appreciated.


 

On Mon, Feb 20, 2023 at 11:52 AM, <chad@...> wrote:


I bought this NanoVNA-H almost a year ago and it has always come up with
"si5351 init Failed" Error. Yesterday I decided to see if a firmware upgrade
would sort out the error. I no longer have the error but the device does not
resopnd to either the jog wheel or the touch screen. Basically it is doing
nothing other then powering on.The image I ghave used is
NanoVNA.H4.v1.2.00.dfu. I have also tried the previous version
NanoVNA.H4.v1.1.00.dfu with the same results.

Any help would be greatly appreciated.

The si5351 chip has failed so you need to replace it or buy another NanoVNA. si5351 are scarce so you may have to use the Chinese clone version of this chip.

Roger


 

I bought this NanoVNA-H
You cannot load the H4 firmware on an H device - it wont work. You need to
use the firmware with just -H in the filename (same version number ok).
If yours is really a -H rather than a -H4, I would try the correct firmware
before declaring that the si5351 chip is dead.
If your si5351 chip is dead, the best bet is to get another nanovna, unless
you are skilled with surface-mount part assembly and have the right tools.
Stan

On Mon, Feb 20, 2023 at 12:51 PM Roger Need via groups.io <sailtamarack=
[email protected]> wrote:

On Mon, Feb 20, 2023 at 11:52 AM, <chad@...> wrote:


I bought this NanoVNA-H almost a year ago and it has always come up with
"si5351 init Failed" Error. Yesterday I decided to see if a firmware
upgrade
would sort out the error. I no longer have the error but the device does
not
resopnd to either the jog wheel or the touch screen. Basically it is
doing
nothing other then powering on.The image I ghave used is
NanoVNA.H4.v1.2.00.dfu. I have also tried the previous version
NanoVNA.H4.v1.1.00.dfu with the same results.

Any help would be greatly appreciated.

The si5351 chip has failed so you need to replace it or buy another
NanoVNA. si5351 are scarce so you may have to use the Chinese clone
version of this chip.

Roger






 

Ok Just to clear up my previous message. It is a NanoVNA-H as marked on the board but it is the unit with the 4" screen, so using the NanoVNA.H4.v1.2.00.dfu is correct. As for the other comments that the failed chip "si5351 init Failed", I no longer get the message after upgrading the firmware, however the jog wheel and the touch screen are not active. I have attached an image of the unit to show the screen after the upgrade. Unfortunatly, I did not take a photo of the error before I did the upgtade.


 

On Fri, Feb 24, 2023 at 04:39 AM, <chad@...> wrote:

Ok Just to clear up my previous message. It is a NanoVNA-H as marked on the
board but it is the unit with the 4" screen, so using the
NanoVNA.H4.v1.2.00.dfu is correct. As for the other comments that the failed
chip "si5351 init Failed", I no longer get the message after upgrading the
firmware, however the jog wheel and the touch screen are not active. I have
attached an image of the unit to show the screen after the upgrade.
NanoVNA's made by Hugen with a 2.8" screen are -H and with a 4" screen -H4. Copies or modifications of his PCB layout and circuit design often use the -H/H4 markings but are not the same PCB layout and often use different components. Your device seems like one of these copycats.

The 4" screen is not the only difference between a -H and a -H4. The -H4 has a SD card, improved power supply, and component changes to give better performance. The biggest difference is the CPU chip used in the -H4. It was upgraded to accommodate the 4" screen and has more flash memory, RAM and onboard peripherals.

When the -H4 first came onto the market 3 years ago it did not need all the extra flash and RAM and still used 101 data points. Over time DiSlord and Hugen added capability to the firmware like 401 data points, SD card support and more functionality that required this extra flash/RAM.

The problem for copycat products of the -H4 is that they often used a CPU which could accommodate the 4" display but did not have the high end 303 processor. This situation got worse with the shortage of semiconductor chips during the pandemic. Th other issue was the si5351 clock chip. This part became rare and Hugen and others started using a MS5351 Chinese clone. Here are a few previous threads discussing these issues.

/g/nanovna-users/topic/85648812#24744

/g/nanovna-users/topic/69974156

So given this background information what do you do? A common problem observed when loading the wrong firmware is to see a si5351 init fail message or a frozen screen with no traces displayed on the screen. I suggest you try loading an old version of the Hugen firmware that still used 101 data points and had limited new features. See if that works and then try to update the firmware by successive versions until it does not work anymore.

Here is a link to the oldest 0.4.5-4 >>

Next try version the February 2020 version and if that works the 1.0.45 version



Roger


 

More info. I can still attach as via serial and get the info from the board. Basically it seems to be coming up, but not working on the touch and jog wheel.

Board: NanoVNA-H 4
2019-2021 Copyright @DiSlord (based on @edy555 source)
Licensed under GPL.

Donate support:

Version: 1.2.00 [p:401, IF:12k, ADC:384k, Lcd:480x320]
Build Time: May 28 2022 - 16:13:55
Architecture: ARMv7E-M Core Variant: Cortex-M4F
Platform: STM32F303xC Analog & DSP


 

Thank you for the reply.

Loading back to the oldest 0.4.5-4, has brought me back to the original status as my son and I got it a year ago as per the attached image.

I have not been able to find the image he sent me when he first got it but the error message is the same. I have attached an aimage of the screen now if it will help to narrow down a solution. I have aslo added a photo of the 5351 chip. It does not look like it is a SI5351 or a MS5351. I think my next step is to order a replacement and and replace it.

Thanks again


 

On Fri, Feb 24, 2023 at 11:37 AM, <chad@...> wrote:

I have not been able to find the image he sent me when he first got it but the
error message is the same. I have attached an aimage of the screen now if it
will help to narrow down a solution. I have aslo added a photo of the 5351
chip. It does not look like it is a SI5351 or a MS5351. I think my next step
is to order a replacement and and replace it.
Your chip looks like a 5351 since it has the right markings and was produced in 2000. See description below. The chips are now readily available again with stock at DigiKey and Mouser. It is a 10 pin MSOP so not hard to replace if you are careful. Before replacing I would check a couple of things. Make sure the 26 MHz. clock input is running. Probe the SCL and SDA data lines and see if they are active and I2C traffic is going to/from the chip.

Roger