Products > Test Equipment

Siglent SVA1015X and SVA1032X 1.5, 3.2GHz Spectrum & Vector Network Analyzers

<< < (205/208) > >>

tautech:

--- Quote from: IM3 on December 12, 2024, 06:00:55 pm ---The 60-second Flash mystery has yet to be solved.

--- End quote ---
Statement on this matter from HQ via EU HQ:

We use UBIFS.
This file system has a balanced management of Flash, which means it is NOT writing to the same physical address.
Our application determines whether the configuration has been modified, and if not modified, it will not be saved.

In our next FW version, we will add a user option that allows users to decide whether to enable the periodic check and save function.

Johnny B Good:

--- Quote from: tautech on December 17, 2024, 09:29:39 am ---
--- Quote from: IM3 on December 12, 2024, 06:00:55 pm ---The 60-second Flash mystery has yet to be solved.

--- End quote ---
Statement on this matter from HQ via EU HQ:

We use UBIFS.
This file system has a balanced management of Flash, which means it is NOT writing to the same physical address.
Our application determines whether the configuration has been modified, and if not modified, it will not be saved.

In our next FW version, we will add a user option that allows users to decide whether to enable the periodic check and save function.

--- End quote ---

 Thanks for winkling that nugget about the 60 seconds auto-save feature out of Siglent - it only took five months ::)  ;)

 That's not too far off my own hypothesis I'd posted here:

https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg5585383/#msg5585383

 The only bit I'd left out being about if no changes had been made to the sram buffered data, the flash would remain unmolested on the next shutdown whether a user instigated shut off via the on/off button or an unexpected power loss.

IM3:
Even though UBIFS is designed to work efficiently on raw flash memory, it still contributes to flash wear. UBIFS relies on the UBI layer for critical functions like wear leveling and bad block management, which help extend the lifespan of the flash. However, frequent write operations, such as making a backup every minute, can still exhaust the flash memory over time.

For example:

Writing every minute results in 1,440 writes per day, or over 525,000 writes annually. Even with good wear leveling, this can wear out blocks, especially if your flash has a typical endurance of 100,000 Program-Erase (PE) cycles.

UBIFS operates on large logical erase blocks, so even small data writes can trigger full block erases, increasing wear.

While UBIFS includes compression and buffering to reduce writes, it can't eliminate the fundamental limitations of flash memory.

In short, while UBIFS is efficient and reliable, heavy write patterns will still eventually wear out flash memory.


I skip this firmware update and wait for the next one.

Johnny B Good:
 From Siglent's reply to Tautech's enquiry, it seems the autosave every 60 seconds is only applied in ram and it is only written to the flash if the config data had been changed since the previous session on powering down or the result of the ac power being lost.

 Even if the config data has been changed, such flash updates will only be applied on power down, not 1440 times a day. I doubt anyone will be power cycling their SA every 15 minutes or so, let alone every minute. A more likely usage pattern would be power up for an hour or three perhaps once to three or four times a day.

 I'd very surprised if anyone ever power cycles such kit more than an average of three times a day. At that rate, assuming a 100K block write/erase cycle endurance, it would take something like a century to wear it out, even without wear leveling.

tautech:

--- Quote from: IM3 on December 18, 2024, 09:07:04 pm ---Even though UBIFS is designed to work efficiently on raw flash memory, it still contributes to flash wear. UBIFS relies on the UBI layer for critical functions like wear leveling and bad block management, which help extend the lifespan of the flash. However, frequent write operations, such as making a backup every minute, can still exhaust the flash memory over time.

For example:

Writing every minute results in 1,440 writes per day, or over 525,000 writes annually. Even with good wear leveling, this can wear out blocks, especially if your flash has a typical endurance of 100,000 Program-Erase (PE) cycles.

UBIFS operates on large logical erase blocks, so even small data writes can trigger full block erases, increasing wear.

While UBIFS includes compression and buffering to reduce writes, it can't eliminate the fundamental limitations of flash memory.

In short, while UBIFS is efficient and reliable, heavy write patterns will still eventually wear out flash memory.


I skip this firmware update and wait for the next one.

--- End quote ---
I think you misunderstood and missed the highlight portion below:

This file system has a balanced management of Flash, which means it is NOT writing to the same physical address.
Our application determines whether the configuration has been modified, and if not modified, it will not be saved.

If we go back to the FW release notes, this discussion only applies to Save Last settings every 60s when enabled and when no changes are made to settings, nothing is written to flash.

If there is no desire to reboot to Last used settings this feature can remain turned OFF so the analyzer boots to default settings.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod