How to make filesystem for dm365

Copying files won't help as the binaries you are copying may have other dependencies that you are not taking care of.

Also, depending upon your build tools (versions, etc.) more incompatibilities can creep in. You should be building everything together.

There isn't a one way for building filesystem? You could start with busybox and build everything on your own OR use scratchbox OR OpenEmbedded or similar to build the filesystem. Each build system as its own nuances that you need to get used to.

Hi Sanjeev, I am using dvsdk_2_10_01_18 and also fbdev_loopback from PSP_02_10_00_14 which I modified successfully for my own application.  Now I need to put it in flash and used the PSP's demo fiilesystem but do not have any SSH support any more.  Do you know what I must change in the filesystem (baserd) to enable SSH?  Or what tools TI used to make the baserd demo filesystem as I can maybe continue using it as my manual trying to coppy files I think is ssh related over from the development filesystem is not working.  These changes once ended up copying the whole rc.d directory and all ssh stuff also but no luck.  Can I assume the PSP_02_10_00_14 dependancies will match DVSDK_2_10_01_18 the way it was built by TI?  If not, what else should I then change and rebuilt to make the dependancies match?  I am desparate to get over this hurdle.....

Thanks, Jinh T.

Jinh,

Building your own filesystem is much easier than debugging possible problems due to manually copying contents from one filesystem to another. The problems may not show for quite long. You can also look at arago-project [http://www.arago-project.org/] OR OpenEmbedded  OR Angstrom/Narcissus [http://www.angstrom-distribution.org/narcissus/] to get filesystem with desired capabilities.

Jinh said:

Can I assume the PSP_02_10_00_14 dependancies will match DVSDK_2_10_01_18 the way it was built by TI?

I haven't used them myself - but it would be very difficult to say one way or other.

Jinh said:

used the PSP's demo fiilesystem but do not have any SSH support any more.  Do you know what I must change in the filesystem (baserd) to enable SSH?

You would need to cross compile ssh daemon which may have its own dependencies esp. specific versions of other components in filesystem e.g. glibc;

I would still suggest try one of the options above that suits you. Narcissus will be the easiest - with minimal effort.

Hi Sanjeev,

Thanks for the info.  I will go that route and see if I can get this thing working.  A question about the filesystme and kernel:  When I do changes to the filesystem, do I need to build a new uImage file from that filesystem as I am all the time using the kernel image built on the original development file system?  Is this maybe something I am not doing that is throwing depencies out of sync?

Thanks, Jinh T.

Jinh said:

When I do changes to the filesystem, do I need to build a new uImage file from that filesystem as I am all the time using the kernel image built on the original development file system?

No, You really don't need to rebuild the kernel all the time - unless there is a big difference between the toolchains used to build filesystem and kernel.

For example: If you build one with GCC v3.2 and other with GCC4.4 - you could see potential issues; may be immediately - but some could be latent. BTW, same applies to components within the filesystem as well.

I assumed that I did not need to rebuild the kernel while changeing stuff in the filesystem but was told so by a colleague that only works with linux 2.4. 

Just to clarify your example above:  I have always only built stuff with the mvpro compiler that came with my DVSDK and never udpated or changed anything along the way (the hope was to get to the stage where I am now and have a demo that is working without including to many variables)  so I assume I am stillusing the same compiler as that whole DVSDK and it support packages was built with and do not have to worry about incompatibilities like you mention?

Some more questions for a newbie:  Where do I run menuconfig from that I assume set up a menu file that is used when I rebuild the kernel.  I have rebuilt the kernel many times while changing stuff in drivers to get my app going but never bothered to get rid of the stuff in the kernel that I do not need like the previewer and resizer for instance.  Is menuconfig the correct place to do these changes for cutomising my kernel?  I jumped into the deep en with linux and lots of things are getting clearer as I get to the shallow end so please excuse some trivial questions...  He also mentions "make dep" that sets up dependencies in the kernel and filesystem? If this is applicable, could this be what is making my system not to work now?

Thanks, Jinh T.

Thanks for all the help.  Got the demo file going with ssh support.  Size increased from 5.6MB to 9.2MB.  Also got the menuconfig going after going back to GSG and fixing ncurses.  Now I can continue customising my system....

Regards, Jinh T.