CC3200 camera + programming issues

Llia,

Is your device in force-AP mode - Can you please ensure P58 and VCC are not connected? I'd also want to check if you are getting a frame-end interrupt at first place - Can you please put a breakpoint in 'CameraIntHandler' where 'g_frame_end' is set and see if its getting hit? Also, if you have an LA, a screenshot showning the data-lines, VS and HS will help.

-Praneet

Hello Praneet,

Thank you for answering so quickly.

On the "status" tab of the main.html page, it shows the device in Access Point mode.

Not sure exactly where to force AP Mode...

Pin 58 is only connected to D3 data line from camera, and it seems to be getting data.

The interrupt was set at:

static void CameraIntHandler()
{
    if(g_total_dma_intrpts > 1 && MAP_CameraIntStatus(CAMERA_BASE) & CAM_INT_FE)
    {
        MAP_CameraIntClear(CAMERA_BASE, CAM_INT_FE);
        g_frame_end = 1;
        MAP_CameraCaptureStop(CAMERA_BASE, true);
    }

However, interrupt never fires.

For the LA portion, I will have to wait a few days until one becomes available. Will get back to you ASAP.

It may still be that a signal is not getting through...

Hello again,

I want to share some updates and comments on this.

1. Using the Logic analyser, I can clearly see that camera outputs nothing on startup. It is then fed I2C commands, and begins to output data.

2. This data all looks valid. In the following image we have:

D3: HRef      D4: Vsync      D5: XCLK    D6: PCLK   D7-D14: 8bit data

We can also see that Href and Vsync do what they should:

I have loaded the included, pre-compiled example code via Uniflash. Settings are 8MBit capacity, non-secure, non-alert. Program starts up normally.

At this point, I am unsure what could be wrong with simply displaying the image.

As a side note, I have found working with Code Composer studio extremely frustrating. A recent update invalidated all my setting from before, and now I have been unable to compile a simple light blinking program. Include folders are extremely hard to use, and more often than not broken. The default "simple" TI Resource explorer does not import files correctly (clicking import and then build invariably produces error gmake: *** No rule to make target `C:/ti/CC3200SDK/cc3200-sdk/main.c', needed by `main.obj'.)

This is not a good product in its current state, and I will have to seriously advise against it until efforts are made to improve the status of the product. It is admirable that so many different demos are included, but when not a single one actually works, this leads to wasted time and frustration.

These last 6 hours fighting to get even the most basic program working (again!) with your toolchain is a disaster.

Hi Ilia,

Appreciate your feedback and unfortunate to see you facing issues with even compilation. We definitely don't want user to face such issues.

Regarding the camera image not getting displayed, It might require some debugging but  I see you have already done well to confirm that camera capture is fine.

================================================================================

The issue in displaying might be related with browser caching/javascript or some network delay.

To confirm, it would help if you could follow below steps, 

1) Run Application, Connect to CC3200 AP, Open browser and load camera demo page

2) Press Capture Button

3) Wait about 10 seconds

4) At this point , you would see a blank image as you report.

5) Now type in your browser url field - http://mysimplelink.net/images/cc3200_camera_capture.jpg

6) it should display the image/raw data if capture was successful

If at step 6, image/raw data is displayed, it means capture is fine but display failed due to browser/network delay.

If nothing appears, it means capture was not successful.

================================================================================

Regarding CCS compilation issues, I guess it is due to a common practice of existing CCS users to

"copy the project in workspace"

 

Please check above guidelines from CC3200-Getting_Started_Guide.pdf and see if it helps solve your problem.

In next SDK 1.0.0, above limitation is addressed and user should be able to import and copy project in workspace.

Regards,

Kaushal

 

Hello again,

Going to the address provided shows nothing, so I guess capture is not working. This is very strange given signals are as they should be, at the right pins, with the camera working properly. Please remember, this was .bin files loaded directly with the UniFlash tool. Is there something wrong with the board?

I have board Rev 3.2

As a note, I uninstalled and removed everything from the install C:/ti folder. I then reinstalled everything following instructions exactly.

On using File->Import->CCS project->browse and select Camera Application->Ensure "Copy into workspace ins unchecked" I get:

Description Resource Path Location Type
fatal error: datatypes.h: No such file or directory camera_app.c /test1 line 47 C/C++ Problem
fatal error: datatypes.h: No such file or directory main.c /test1 line 58 C/C++ Problem
fatal error: hw_types.h: No such file or directory startup_ewarm.c /test1 line 39 C/C++ Problem
fatal error: hw_types.h: No such file or directory mt9d111.c /test1 line 47 C/C++ Problem
fatal error: hw_types.h: No such file or directory pinmux.c /test1 line 46 C/C++ Problem
gmake: *** [camera_app.o] Error 1 test1 C/C++ Problem
fatal error: hw_types.h: No such file or directory i2cconfig.c /test1 line 46 C/C++ Problem
gmake: *** [i2cconfig.o] Error 1 test1 C/C++ Problem
gmake: *** [main.o] Error 1 test1 C/C++ Problem
gmake: *** [mt9d111.o] Error 1 test1 C/C++ Problem
gmake: *** [pinmux.o] Error 1 test1 C/C++ Problem
gmake: *** [startup_ewarm.o] Error 1 test1 C/C++ Problem
gmake: Target `all' not remade because of errors. test1 C/C++ Problem

On using the CCS6->View->Getting started->Camera Application->Import->Build

I get:

Description Resource Path Location Type
gmake: *** No rule to make target `C:/ti/workspace/mt9d111.c', needed by `mt9d111.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/workspace/pinmux.c', needed by `pinmux.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/workspace/i2cconfig.c', needed by `i2cconfig.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/workspace/main.c', needed by `main.obj'. camera_application Unknown C/C++ Problem
This project contains unresolved buildable linked resources. It might not build as expected. camera_application project Problems
gmake: *** No rule to make target `C:/ti/workspace/camera_app.c', needed by `camera_app.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/common/udma_if.c', needed by `udma_if.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/common/startup_ccs.c', needed by `startup_ccs.obj'. camera_application Unknown C/C++ Problem
gmake: *** No rule to make target `C:/ti/common/uart_if.c', needed by `uart_if.obj'. camera_application Unknown C/C++ Problem

Both methods do not work. Solving either one would be great, but I am unfamiliar with the build tools and systems, and hence after working at it am still stuck.

My apologies if I sound frustrated, this is entirely not the experience I was expecting. I am usually quite happy with TI parts.

EDIT: Just tried the first method for the SSL example project. That seems to work fine. I wonder what is wrong with the camera project....

EDIT2: I am using Windows 8.1, and some projects do not seem to want to compile, (with similar issues to first method above) while others do. It is fairly random, with about 25% not working in my quick test (blinky is the simplest one I have that doesnt work)

Hi Ilia:

I am currently working on the same issue and I also cannot capture an image even though the signals and data from the camera look correct. Were you ever able to solve this issue and capture an image? If so, what changes did you make to the code or the configuration?

Any help you can offer would be very much appreciated.

Thanks!
- Will

Hi Praneet:

I'm hoping that you can help me with an issue which may be related to the issue in this link. I am working on the camera_application project and I am not able to capture an image. The signals from the camera look correct, but the 'g_frame_end' flag is not getting set. It appears that VSYNC is not triggering the interrupt on the falling edge.

See my original post here: http://e2e.ti.com/support/wireless_connectivity/f/968/t/393852

Thanks in advance!
- Will