1 2 Previous Next 17 Replies Latest reply on Nov 7, 2015 3:03 PM by playwithittoo

    SS4000-e RedBoot binaries


      Hello there!


      I know that this question is far beyond support call and my device (SS4000-E) is not under warranty as I hacked the box and I installed Debian armel on it.

      While I was hacking the box I put a <fis init> on RedBoot prompt (how stupid me) and all the files in RedBoot listing are gone. What I really miss is RAMMODE. Can I get this file somehow from Intel? I want to transfer it through xmodem and write back to the unit RedBoot flash and get faster kernel flashes in the future.


      Thank you for reading. And more thanks for helping me out.



        • 1. Re: SS4000-e RedBoot binaries



          Not sure what you're looking for. The file that the SS4000 uses for software updates is a .pkg file. This file can't be decompressed any further to get individual files out of it. Are hte files you're looking for in the SS4000 directory structure somewhere? I've got one in stock form and can possibly get what you need, but need some help to help you.


          Let me know what you need.




          • 2. Re: SS4000-e RedBoot binaries

            Hi John,


            Thank you for offering your help.

            I'll need you to copy a partition to a file and send me as an attachment. I'll describe step-by-step what you'll need to do.


            First you have to SSH to your device. SSH is not turned on by default, it has to be turned on which is described here. (Basically you have to open a page on your device to get to this hidden setting).

            Than you need to logon through SSH to get to the console of SS4000-E. You'll need a software like putty.

            If you logged in than you'll need to get some listings.

            # cat /proc/mtd

            dev:    size   erasesize  name

            mtd0: 00040000 00020000 "RedBoot"

            mtd1: 00200000 00020000 "zImage"

            mtd2: 00400000 00020000 "ramdisk.gz"

            mtd3: 00001000 00020000 "RedBoot config"

            mtd4: 00020000 00020000 "FIS directory"


            What I really need is a copy of your mtd partition that is named "rammode" which is obviously missing from my list. You'll need mtd partition index (mtdx).

            Than type the following command which dumps rammode partition to /tmp/rammode on your root device.


            # dd if=/dev/mtdx of=/tmp/rammode

            (Don't forget to substitute x with the number of rammode partition from the above list.)


            Than you'll be please so kind to send me this rammode file by e-mail. (It's around 262 kb, you can zip it if you like).


            If any of the above steps are not clear than please let me know to be able to clarify.

            My e-mail is : cina - at - haemo.szote.u-szeged.hu

            Thank you for your patience and help.



            • 3. Re: SS4000-e RedBoot binaries



              Here's what I get if I follow your insctructions:

              # cat /proc/mtd
              dev:    size   erasesize  name
              mtd0: 00040000 00020000 "RedBoot"
              mtd1: 00080000 00020000 "unallocated"
              mtd2: 00200000 00020000 "zImage"
              mtd3: 00400000 00020000 "ramdisk.gz"
              mtd4: 01880000 00020000 "vendor"
              mtd5: 00080000 00020000 "wmdata"
              mtd6: 00001000 00020000 "RedBoot config"
              mtd7: 00020000 00020000 "FIS directory"
              # dd if=/dev/mtd0 of=/tmp/rammode
              512+0 records in
              512+0 records out
              # dd if=/dev/mtd2 of=/tmp/rammode
              4096+0 records in
              4096+0 records out
              # dd if=/dev/mtd3 of=/tmp/rammode
              8192+0 records in
              8192+0 records out
              # dd if=/dev/mtd6 of=/tmp/rammode
              8+0 records in
              8+0 records out
              dd if=/dev/mtd7 of=/tmp/rammode
              256+0 records in
              256+0 records out
              # cd tmp
              # pwd
              # ls -al
              drwxr-xr-x    2 root     root         1024 Jul 20 20:34 .
              drwxr-xr-x   21 root     root         1024 Mar 24 22:18 ..
              prw-------    1 root     root            0 Jul 20 17:56 .falconstor
              -rw-r--r--    1 root     root            2 Jul 20 17:56 .network-eth0
              -rw-r--r--    1 root     root            2 Jul 20 17:56 .network-eth1
              -rw-r--r--    1 root     root           85 Jul 20 20:30 nas_used_temp_file
              -rw-r--r--    1 root     root       131072 Jul 20 20:34 rammode
              -rw-r--r--    1 root     root         2255 Jul 20 17:57 smb.tmp


              Is that correct? My rammode looks like it's half what you expect.



              1 of 1 people found this helpful
              • 4. Re: SS4000-e RedBoot binaries



                I am running FW version 1.4-b709



                • 5. Re: SS4000-e RedBoot binaries



                  Thank you for the quick answer but it looks like your RedBoot flash does not contain rammode partition. Your listing should contain something like the list below which is listed directly from RedBoot prompt. (RedBoot prompt can only be reached through a serial console connection).

                  RedBoot> fis list
                  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


                  I'm quite sure that it should be there as I used rammode before. And I was flashing the latest Intel firmware like you before Debian.


                  Thank you for your effort anyway.

                  • 6. Re: SS4000-e RedBoot binaries

                    An idea:

                    FIS list contains the correct RedBoot partition structure. It is a binary file but the first few bytes lists the correct setup. But it is unlikely that the "unallocated" space is rammode indeed.

                    Can you post me the result of


                    # dd if=/dev/mtd7 of=/tmp/FISList


                    file? Or you can look into it to check for rammode existence.



                    • 7. Re: SS4000-e RedBoot binaries



                      The stuff I did above was through hyperterminal via a serial connenction. How do I stop the boot process to get to the RedBoot> prompt? From there does the dd if=/dev/mtdx of=/tmp/... work too?



                      1 of 1 people found this helpful
                      • 8. Re: SS4000-e RedBoot binaries

                        The resulting /tmp/FISList file was 256 records and 131072 bytes.



                        1 of 1 people found this helpful
                        • 9. Re: SS4000-e RedBoot binaries

                          grep -a 'rammode' FISList didn't reveal any instance of rammode.



                          • 10. Re: SS4000-e RedBoot binaries
                            During reboot you'll see the following text on Hyperterminal.

                            +No network interfaces found

                            EM-7210 ver.T04 2005-12-12 (For ver.AA)
                            == Executing boot script in 1 seconds - enter ^C to abort


                            Than you'll have to press Ctrl-C (you'll have 1 second to do that!)
                            if you type fis list at RedBoot prompt you'll get the a listing like above.
                            To get out of redboot simply enter reset.

                            Probably you don't have that module anyway (if grep cannot find it).
                            Thank you for your effort.
                            • 11. Re: SS4000-e RedBoot binaries

                              Did you ever get the files you where after?

                              • 12. Re: SS4000-e RedBoot binaries

                                Yes, I did but not from Intel Support. I got it from Debian guys who are developing armel for ss4000e. It is up and running right now with squeeze on it.




                                • 13. Re: SS4000-e RedBoot binaries

                                  dont supose you could point me in the right direction to get them?

                                  i did the same thing you did and need to restore

                                  • 14. Re: SS4000-e RedBoot binaries

                                    Hello there


                                    I have the same problem now. Are you able to help out another in need. Please give me a crumb to where you found the files and info you need to restore the redboot files.


                                    Thanx in Advance

                                    1 2 Previous Next