For OpenWrt: fw_setenv
some foo bar variables.
For u-boot: a simply saveenv
will do it, wouldn't it?
I don't know what will happen when sysupgrade starts. Thats the point!
For OpenWrt: fw_setenv
some foo bar variables.
For u-boot: a simply saveenv
will do it, wouldn't it?
I don't know what will happen when sysupgrade starts. Thats the point!
Apologize for the delay - got tied up with work this week. Will try to get to this, this weekend!
Here you go, the image from the "failing" upgrade.
I said to force it (not saving settings), then ... upgrade fails,
============================================
Ralink UBoot Version: 4.1.0.0
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM component: 256 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 32 MBytes
Flash component: SPI Flash
Date:May 7 2014 Time:05:33:12
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768
##### The CPU freq = 580 MHZ ####
estimate memory size =32 Mbytes
raspi_read: from:40028 len:6
Initialize vs configure module
raspi_read: from:1d0000 len:1000
Initialize GPIO
check: 0
Input i key to enter menu 0
raspi_read: from:50000 len:180000
## Booting image at 80500000 ...
Bad Magic Number,4F4B4C49
But, TFTP "recovery" ... works fine!
Thank you very much! This looks good!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.