NAS200 developers read this

Discussion in 'Cisco/Linksys Network Storage Devices' started by jac_goudsmit, Aug 4, 2008.

  1. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    If you have tried to compile the R75 firmware from the Linksys source tarball, you will have probably noticed that the result won't work. It will build just fine but after you download the result into the NAS200, you're not even going to be able to reach it from the network. In fact, the only way to recover from this is to use the "upgrade" command in the ecos command prompt in combination with a program such as Upslug.

    As it turns out, many files are missing from the Linksys source tarball (for example, the CGI files for the web pages) and a number of closed-source binaries that are in the source/mipsel/target-default.tgz directory won't load, including the ones that are needed to read the configuration from flash and bring the disks online.

    The good news is that there is an easy workaround: it's easy to extract the ROM filesystem (and hence the missing files) from the R75 bin file. Alternatively you can use the console serial port on the NAS200 and write the files to the harddisk.

    I took the liberty of doing this, and making a tarball of the files that are different from the files in the target-default.tgz file inside the Linksys R75 sources. The result is here:

    To use it, download the .tgz file to the source/mipsel directory and change the source/Makefile as follows:

    --- /home/jac/NAS200_V34R75_GPL/source/Makefile 2008-03-23 23:06:57.000000000 -0700
    +++ Makefile    2008-08-03 16:04:36.000000000 -0700
    @@ -65,6 +65,7 @@
            tar -xvzf $(PLATFORMDIR)/target-default-media.tgz -C $(PLATFORMDIR)/
    +       tar -xvzf $(PLATFORMDIR)/target-v34r75.tgz -C $(PLATFORMDIR)/
            @for i in ${SUBLIBS} ;  do                                                    \
            echo "-----------------------------------------------------------------"; \
            echo -e "\033[;35m                         $$i                 \033[;0m"; \
    Note, this is the minimum change to make a working R75 build for yourself. If you want to make changes to the target filesystem, you will probably want to modify the Makefile further so that it won't destroy and rebuild the target filesystem from scratch each time you do a build.

    I will integrate the change into the Nasi200 project shortly.

  2. mdsilva

    mdsilva Addicted to LI Member

    Great, how is NASi200 going? I can't wait to try it
  3. jac_goudsmit

    jac_goudsmit Super Moderator Staff Member Member

    The current SVN version will compile a working R75 and the first feature has been added in change #172: the missing symlinks for Busybox are now added to the target filesystem. Stay tuned!

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice