About DM8127 IPNC raw capture.

Hi,Gomo,

you could make use of ISIF features to output raw buffer,

step 1, configure in advance ISIF_CADU,ISIF_CADL as the head address of memory you assigned and in which you want to hold raw data 

step 2,Enable DWEN bit of ISIF_SYNCEN,

By the way, we have implemented raw data as well as YUV capture features in latest ipnc RDK release GA 2.0,

you could take issTriggerRawCapture(raw capture,iss_comp.c) ,

IssCaptureYUVFrame,bufSwitchFull(YUV capture. issdrv_captureApi.c)

 for reference.

Best regards,

Christian.

Gomo,

Which DM8127 IPNC release package are you using right now?

Can you please add more details of your use-case? Would you want a continous RAW buffer stream and process it with ISP or its only for some snapshot download mode?

Regards

Rajat

Hi, Rajat

Rajat Sagar said:

Gomo,

Which DM8127 IPNC release package are you using right now?

Can you please add more details of your use-case? Would you want a continous RAW buffer stream and process it with ISP or its only for some snapshot download mode?

I have update to latest DM8127 IPNC, V2.0;

From the TI forum, I know the 8127 IPNC only support RAW capture now. We want  get a continous RAW buffer stream,  and add some information in the end , and then to ISIF--> YUV420--> MJPEG. Just like the head information of DM368 IPNC.

Thanks a lot.

Hi Gomo,

"From the TI forum, I know the 8127 IPNC only support RAW capture now. We want  get a continous RAW buffer stream,  and add some information in the end , and then to ISIF--> YUV420--> MJPEG. Just like the head information of DM368 IPNC."

This may require some changes in the capture driver. What I understood from this is that you want the RAW buffer first and then you would like to do memory to memory processing to get YUV and then encode. The IPNC rdk ga2.0 driver only supports on-the-fly processing right now. We are adding the memory-to-memory function and validating it. The tentative release date for the M2M driver is Apr20 2012.

Regards

Rajat

Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

Hi Rajat,

         Your are right, we want to do memory to meory processing. we want add our information to every raw frame, in the latter processing, so we can get our information and copy to next step in the latter every step. at last, after MJPEG encode, copy our information to the end of MJPEG encode data, modify the size of MJPEG and add the sizeof our information. and the using RTSP to transfer MJPEG data, the client can get MJPEG and information at every frame and same time. just like this flow.

And in your tentative release version at Apr20 2012, What function is include?

1) 8M capture and encode?

2)M2M driver?

3)???

Do  you sure it can come out at the end of April?

Anybody can give me a validate answer?

Hi Gomo,

In the April-end IPNC rdk release (version 2.8) the following will be supported:

1. Megapixel support up to 8MP till 4K width (capture + encode h.264 & mjpeg)

2. M2M driver for ISP

Regards,

Rajat

Hi Rajat

I'm using DM8127 IPNC V2.8 now.

My current usecase is Image sensor(RAW) --> ISIF --> IPIPE --> Resizer(YUV), in this case, my system has some problem at resizer DMA transfer(RESIZER DEAD)

so i would like to change the path to Image Sensor(RAW) --> IPIPEIF --> DDR --> IPIPEIF --> IPIPE --> Resizer(YUV).

To test this mode i did somethings like this

1. Change Rules.make file

    IPNC_CONFIG := LOW_POWER

    CAPTURE_DISPLAY_MODE_ON := YES

2. Change multich_Stream_CaptureDisplay.c

   enable #define M2M_DRV_TEST option

Please let me know exact procedure to test M2M test.

Thanks in advance

Hi KwangSu,

CAPTURE_DISPLAY_MODE_ON is only a basic test case which has been put for simple demo or especially activities like bringing up of a senor. It doesnt work in M2M mode i.e. Image Sensor(RAW) --> IPIPEIF --> DDR --> IPIPEIF --> IPIPE --> Resizer(YUV) mode.

To see M2M based demo:

1. Use the standard Full_feature build.

2. Go to the Camera section in InternetExplorer GUI and Enable "Dynamic Range Enhancement". This enables the M2M mode demo.

3. You can refer to the usecase file to learn how ISP link can be used for making your own M2M based usecase.

Regards
Rajat 

Hi Rajat,

                I have a query on the same topic discussed above.

I have enabled the DDR capture mode. Now my data path is IPIPEIF->DDR->IPIPEIF->IPIPE.

•  Now I want to read that RAW datam, stored in DDR in continuous mode. (not snapshots)
• After reading raw from DDR, i ll apply some processing on that data. I want to bipass IPIPE. but it shold be streamed through RTSP. (RAW data is 320*240-16bit. so BW may not be a issue!!)

Thanks in advance

gomo,

            Hope u can answer my querry, since u have worked on yhis already :)

Thanks a lot.

Sorry for delay.

Using low power feature, in the function of IspLink_drvProcessFrames, you can get raw buffer.

Hi gomo,

            Thank you for the precious reply.

Now I am using IPMCV3.00 & I want to work with full-feature mode only!!

I thought to refer Alg_ITK_Link_tskMain() function in alg_itk_Link_tsk.c.

In this function RAW dump is enabled, based on the cmd received from the DCC.

Instead of cmd from DCC, Can we put some commands to read RAW in continuous mode? Is this feasible?

Basically I want to copy the data in isif_dump buffer to my own set of buffers for further processing.

My data path will be Sensor->captDrv->My_Input_buffs-> *** some processing here *** -> My output buffs ->Disply/Dump to a file/RTSP streaming

Idea is to bipass ipipe and encoders.

Thanks in advance :)

sorry, I have not run with full feature mode.

cannot help you!

Hi,ravikiran.

you want to bypass ipipe and encoders.so you don't need full feature mode right?

please refer to Rules.make , afte you set FRAMES_TO_A8 := RAW

that will give you a sample in which raw data will be sent to A8,

it's only work under capture display mode, 

Hi Mingda Shen,

        First of all thank you for the response.

1. I am looking for full feature mode, bcz I want to send the raw data over RTSP.
2. Since I am looking to enable CSI2 also, I think, we need full feature mode.(correct me if i am wrong)
3. Right now we are done with some algo, which can Run on m3 side. So Its better If I can get RAW data on M3 instead of A8.
4. Referring to issdrv_captureApi.c  IssCaptureRawFrame() function does reading RAW data and dump it. I want to store it into my own set of buffers instead of sending it over DCC links.

Thanks a lot.