HI Craig,
I've found 9 flash files that I got from someone. I've reordered the fis list by flash address, and it looks like I have everything except the "FIS directory". And that actually makes sense, since the flash system would need to know it's own directory, and each entry would be added to that when you run "fis create". So, that narrows it down to
Name FLASH addr Mem addr Length Entry point
0 = RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
1 = log 0xF0040000 0xF0040000 0x00020000 0x00000000
2 = rammode 0xF0060000 0x00200000 0x00040000 0x00200000
3 = naskey 0xF00A0000 0xF00A0000 0x00020000 0x01008000
4 = zImage 0xF00C0000 0x01008000 0x00200000 0x01008000
5 = ramdisk.gz 0xF02C0000 0x01800000 0x00400000 0x01800000
6 = vendor 0xF06C0000 0xF06C0000 0x01880000 0x01800000
7 = wmdata 0xF1F40000 0xF1F40000 0x00080000 0x01800000
8 = RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
9 = FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000
So, if the lengths of your files are in this order, then you should be good to go. (Decimal lengths: File 0 = 262144, etc: 131072, 262144, 131072, 2097152, 4194304, 25090112, 524288, 4096). You would just load rammode, naskey, zImage, ramdisk.gz, vendor, and wmdata. I doubt you'd need log.
Otherwise, someone's going to have to remind me how to make a copy of the flash data, as I can't remember how I did it the one time I did. Come to think of it, my flash data won't be the ones you want to restore to the factory version, as mine would have the bootloader etc for Debian Wheezy.
Bob
From: craig guest <lucky021969@gmail.com>
To: debian-arm@lists.debian.org
Sent: Wednesday, November 11, 2015 6:46 PM
Subject: Re: SS4000E install problem
Hi Bob, JFS, Theo
Thank you all for your insight. I had started trying to do what Bob was describing. It looked like I was moving in the right direction. My next issue was that the backups I was using were named block0 and so on. I was unsure of the correlation between the files named block and mtd. Is it possible to backup your partitions and send them to me so I know which is which to restore. I really appreciate the help. I have some hope again and I really hate to let machines win lol.
Craig
On Nov 11, 2015 6:37 PM, "JF Straeten" <
jfstraeten@scarlet.be> wrote:
Hi Bob,
On Wed, Nov 11, 2015 at 10:39:18PM +0000, Bob Stewart wrote:
[...]
> Name FLASH addr Mem addr Length Entry point
> RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000
> RedBoot config 0xF1FC0000 0xF1FC0000 0x00001000 0x00000000
> FIS directory 0xF1FE0000 0xF1FE0000 0x00020000 0x00000000
> rammode 0xF0060000 0x00200000 0x00040000 0x00200000
> log 0xF0040000 0xF0040000 0x00020000 0x00000000
> naskey 0xF00A0000 0xF00A0000 0x00020000 0x01008000
> zImage 0xF00C0000 0x01008000 0x00200000 0x01008000
> ramdisk.gz 0xF02C0000 0x01800000 0x00400000 0x01800000
> vendor 0xF06C0000 0xF06C0000 0x01880000 0x01800000
> wmdata 0xF1F40000 0xF1F40000 0x00080000 0x01800000
>
> Next is the info that JFS provided:dev: size erasesize name
> mtd0: 00040000 00020000 "RedBoot"
> mtd1: 00020000 00020000 "log"
> mtd2: 00040000 00020000 "rammode"
> mtd3: 00020000 00020000 "naskey"
> mtd4: 00200000 00020000 "zImage"
> mtd5: 00400000 00020000 "ramdisk.gz"
> mtd6: 01880000 00020000 "vendor"
> mtd7: 00080000 00020000 "wmdata"
> mtd8: 00001000 00020000 "RedBoot config"
> mtd9: 00020000 00020000 "FIS directory"
Well, Bob ;-)
All the lengths match, at least ; you're right it's worth giving a
try, I think...
> C do the following. Note that it assumes you're using a webserver
> on your PC. "-m http" could be "-m xmodem" or whatever
Craig should use ?modem since the rammode which loads the lan is
destroyed, but it's seems possible...
Good luck, Craig ;)
A+
--
JFS.