Loading to SDRAM via TFTP should not update env.

ngc
 
Posts: 10
Joined: Mon Dec 12, 2016 10:42 pm

Loading to SDRAM via TFTP should not update env.

Sun Dec 18, 2016 6:08 am

My v2u reached to me. Thanks for works.

Now I'm trying new system image with "1: load system code to SDRAM via TFTP".
I noticed a bad point about it.

After loading system image (load ***-sysupgrade.bin as 'uImage'), u-boot said:
------
NetBootFileXferSize= 00380004
Erasing SPI Flash...
Writing to SPI Flash...
------

The above messages indicate updating environment variable on SPI FLASH.
It is no needs and u-boot should not update environment vars when only loading to SDRAM, because choice "1" is mainly used for debugging.
Updating endurance of SPI FLASH is not much.

noblepepper
 
Posts: 240
Joined: Sat Nov 29, 2014 3:22 pm

Re: Loading to SDRAM via TFTP should not update env.

Sun Dec 18, 2016 9:54 am

1. It will take writing the flash once per minute for 2 months continuously to reach the MINIMUM flash Erase/Program Endurance. While it is possible to wear out the flash if human interaction (i.e not a program doing this) is required I'm not going to worry about it, I'll just buy a new board at that point.

2. The messages you see indicate Das U-Boot is calling the functions that modify flash, they print a "." on the next line each time they modify a sector. Since there isn't a next line nothing is actually modified.

3. I don't know why you think this is writing the environment variables, but if the u-boot-env partition wears out Das U-Boot will start using compiled in defaults, you won't be able to change environment variables but the VoCore2 will boot up normally.

Return to VoCore2/Lite/Ultimate

Who is online

Users browsing this forum: No registered users and 42 guests