CC3220SF-LAUNCHXL: Camera interrupts are not triggered.

Taras Iakymchuk

Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF

This is the continuation of the previous issue with camera on CC3220SF. I investigated the interrupt handlers with gdb and I obsever that regardless of the CC_IRQENABLE register, the only interrupt that is triggered (if enabled) is FIFO_UF_IRQ, a FIFO underflow event. Then the CameraIntHandler is properly called. No other event is triggering the interrupt, even the DMA-unrelated events like frame start or line start. My logic analyzer, hooked to the camera, shows the HSYNC and VSYNC signals properly timed. What can be an issue for such behavior?

over 4 years ago

0 Michael Reymond over 4 years ago

TI__Mastermind 40965 points

Hi,

Have you checked the DMA control registers to see if the transfer has completed, or if it is stuck, or maybe even that it wasn't initialized correctly?

Regards,
Michael

0 Taras Iakymchuk over 4 years ago in reply to Michael Reymond

Prodigy 10 points

Hi,

We are using the code from the camera example. https://github.com/nqd/cc3200/blob/master/example/websock_camera After the MAP_CameraCaptureStart(CAMERA_BASE); the registers in the debugger look next:

CC_CTRL = 0x00012000

CC_IRQENABLE = 0x00090000

CC_IRQSTATUS still all zeroes.

Global interrupts are enabled. I can confirm with my oscilloscope that the frame start condition (VS=rising HS=high) occurs on the corresponding pins. But the interrupt handler is never reached.

The code for the DMA is also taken from the example. But without an interrupt, the DMA never starts.

What else can I check?

0 Michael Reymond over 4 years ago in reply to Taras Iakymchuk

TI__Mastermind 40965 points

Hi,

Just to clarify, it looks like the DMA transfer is initialized correctly in the DMA control struct, just that the DMA transfer never starts. Is that correct?

Regards

Michael

0 Taras Iakymchuk over 4 years ago in reply to Michael Reymond

Prodigy 10 points

I didn't change the DMA configuration, it's the same as in the example:

static void DMAConfig()
{
 //memset(g_image.g_image_buffer,0xF80F,sizeof(g_image.g_image_buffer));
 p_buffer = &(g_image.g_image_buffer[0]);
 //
 // Initilalize DMA 
 //
 UDMAInit();
 //
 // Setup ping-pong transfer
 //
 DMASetupTransfer(UDMA_CH22_CAMERA,UDMA_MODE_PINGPONG,TOTAL_DMA_ELEMENTS,UDMA_SIZE_32,
 UDMA_ARB_8,(void *)CAM_BUFFER_ADDR, UDMA_SRC_INC_32,
 (void *)p_buffer, UDMA_DST_INC_32);
 //
 // Pong Buffer
 // 
 p_buffer += TOTAL_DMA_ELEMENTS; 
 DMASetupTransfer(UDMA_CH22_CAMERA|UDMA_ALT_SELECT,UDMA_MODE_PINGPONG,TOTAL_DMA_ELEMENTS,
 UDMA_SIZE_32, UDMA_ARB_8,(void *)CAM_BUFFER_ADDR,
 UDMA_SRC_INC_32, (void *)p_buffer, UDMA_DST_INC_32);
 //
 // Ping Buffer
 // 
 p_buffer += TOTAL_DMA_ELEMENTS; 
 g_dma_txn_done = 0; g_frame_size_in_bytes = 0;
 g_frame_end = 0;
 g_total_dma_intrpts = 0;
 // // Clear any pending interrupt
 //
 HWREG(0x4402609C) |= 1 << 8;
 // // DMA Interrupt unmask from apps config
 //
 HWREG(0x44026094) |= 1 << 8;
}

Camera CC_CTRL_DMA = 0x00000107

I tried to switch on all possible interrupts for the camera (CC_IRQENABLE=0x000f0f1f) and yet I am not getting any interrupt. Global interrupts are enabled ( MAP_IntMasterEnable(); )

I believe there might be an error in the documentation SWRU465, Table 14-9. Bit 8 is desribed twice: as DMA1_DISABLE and DMA_EN.

0 Michael Reymond over 4 years ago in reply to Taras Iakymchuk

TI__Mastermind 40965 points

Hi,

Thanks for letting me know the DMA setup is unchanged. I haven't had a chance to look into your issue further today, will take a look tomorrow.

Regards,

Michael

0 Michael Reymond over 4 years ago in reply to Michael Reymond

TI__Mastermind 40965 points

Hi,

Just to close out this thread, there was offline discussion we had last week, where we discussed the current status of the camera issue. It was determined that the best course of action was to use a SPI-based camera solution instead.

Regards,

Michael

Wi-Fi

Wi-Fi forum

CC3220SF-LAUNCHXL: Camera interrupts are not triggered.