DM368 ip camera

Mayank,

Comments included below

Regards,

Raghu

I have purchased a reference design from Appropho DM368 with sony sensor.

I have the following questions:

1.We will be working entirely on embedded linux so is CCS necessary to be installed for working with the reference design.

Comment> you will need CCS for burning initially UBL and UBoot using fresh boards, also, you might need it for debug and developing individual components. Other than this, i don't see a need for CCS

2.In the appropho user guide it is mentioned to have montavista toolchain 5.0,where can we get this montavista toolchain since it hasn't come from Appropho package or is it possible to work without Montavista toolchain also.

 Comment>For MVL tools, please use these links

 http://processors.wiki.ti.com/index.php/GSG:_DM365_DVEVM_Software_Setup_for_MontaVista_Kernel

 http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_2_10/latest/index_FDS.html

 3.How can we go about starting the project,we have seen the quality of the camera,its very good so how can we proceed building our own ip camera like that,i mean writing the algorithms for image quality and integrating them with the appropho reference design.

Comment> Most of the requirment are covered in the reference deisgn kit, it depends what are the requirement you want to accomplish. I would say to evaluate the RDK with regard to your requirements and check what you need to develop extra. We can give our inputs based on the algorithm you want to use and requirements you want to implement

CCS Will only be necessary if you wish to implement your own image processing algorithms on the DSP side of the processor (I'm assuming your cpu has one, haven't checked) if it doesn't have one you really won't need it.

as for how to start, I have found that it helps to simply be able to build the camera as it is, get it all working, and then load and run the kernel you built to ensure that you can at least build what it is you have in your hands and run it. From there, start digging into it and making it be what you want it to be.

Rick

Hi

      Thanks for your reply.

      While following the IP Network Camera Reference Design on DM36x user's guide i came across the following step:

      Set <installDir>/Utils/bin folder as the path to tftpboot directory at <TFTP SERVER UTILITY>.

      I am trying to install ubl and uboot on the DM368 board without using CCS.

      And i am not getting what to do in this step and what it is trying to accomplish.

      Thanks and Regards,

      Mayank

Hi

I am following the chapter 3 Building Application of IP Network Camera Reference Design
on DM36x User’s Guide  document.I am trying to configure the board by first setting up the environment

by building the application.

I am running make sysall command in the directory

/home/mayank/DM36x

but i am getting the following errors:

make[4]: Leaving directory `/home/mayank/DM36x/ipnc/ti-davinci'
make[3]: Leaving directory `/home/mayank/DM36x/ipnc'
cp /home/mayank/DM36x/ipnc/ti-davinci/arch/arm/boot/uImage /home/mayank/DM36x/ipnc/tftp/uImage_ipnc_DM368_IMX036
cp: cannot stat `/home/mayank/DM36x/ipnc/ti-davinci/arch/arm/boot/uImage': No such file or directory
make[2]: *** [lsp] Error 1
make[2]: Leaving directory `/home/mayank/DM36x/ipnc'
make[1]: *** [lspall] Error 2
make[1]: Leaving directory `/home/mayank/DM36x/ipnc'
make: *** [sysall] Error 2

If we have to make uImage first and then copy it in the arch/arm/boot directory.

Thanks and Regards,

Mayank

Ah, yeah, loosely.. what they are saying is, Tell the (TFTP SERVER) on your host computer that you are compiling on, that the directory <installDir>/Utils/bin folder is to be made accessible via tftp.  This is how you will let your camera get at the files you are creating for later download via tftpboot.

I'm using the dm365, not the dm368, however, with the dm365, we need to do the build sysall in the ipnc directory. IN you case it would be /home/mayank/DM36x/ipnc  Try from there.   This is also the directory where "Makefile" and "Rules.make" are.

There's also the question of, did you chown everything to you and away from root? and did you set permissions on everything so that you can delete them? 

Also, when it comes to the final build, i had issues where I had to go create the final filesys tree manually for the stuff that was being built to land in as the makefile did not properly do that on its own.

Hi Mayank,

I am getting same error while building lsp

make[2]: Leaving directory `/home/alam/appro/ipnc_psp/ti-davinci'
make[1]: Leaving directory `/home/alam/appro/ipnc_rdk'
cp /home/alam/appro/ipnc_psp/ti-davinci/arch/arm/boot/uImage /home/alam/appro/ipnc_rdk/tftp/uImage_ipnc_dm365
cp: cannot stat `/home/alam/appro/ipnc_psp/ti-davinci/arch/arm/boot/uImage': No such file or directory

How did you solved your problem?

Regards

Alam

Hi Alam,

Are you sure kernel was build properly? Are you getting any errors before completion of kernel build? (Check the log)

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!

Hi Anil,

Kernel is getting build properly. There is a line in a Makefile for copying uImage to tftp folder. 

cp /home/alam/appro/ipnc_psp/ti-davinci/arch/arm/boot/uImage /home/alam/appro/ipnc_rdk/tftp/uImage_ipnc_dm365

But "/home/alam/appro/ipnc_psp/ti-davinci/arch/arm/boot/" contains "Image" file not "uImage". I am wondering if uImage is produced as Image. Some Makefile TARGET error.

If I comment above cp line, then it compiles successfully.

Please suggest.

Regards

Alam

Hi Mohammad,

Add uboot tools link to PATH along with your tool-chain and build uboot before building the kernel.

export PATH=/media/anil/uboot/tools:$PATH

("uboot" is the uboot source folder)

Regards

AnilKumar

Please mark this Forum post as answered via the Verify Answer button below if it helps answer your question.  Thanks!