Main Site Documentation

Serial Camera L2 does not work with display TE35 when T socket is connected


#1

Hi,
I just started playing around with my hydra and I was running the sample code from https://www.ghielectronics.com/docs/176/serial-camera-module.

The only thing I changed from the code is to connect T socket of TE35 display.
When T socket is connected, camera does not work and I am see the below debug output.
The thread ‘’ (0x3) has exited with code 0 (0x0).
#### Exception System.Exception - 0x00000000 (6) ####
#### Message:
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadBytes [IP: 0022] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadFrameBuffer [IP: 006b] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::UpdateStreaming [IP: 003a] ####
A first chance exception of type ‘System.Exception’ occurred in GTM.GHIElectronics.SerCam.dll
#### Exception System.Exception - 0x00000000 (6) ####
#### Message:
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadBytes [IP: 0022] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadFrameBuffer [IP: 006b] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::UpdateStreaming [IP: 003a] ####
A first chance exception of type ‘System.Exception’ occurred in GTM.GHIElectronics.SerCam.dll
#### Exception System.Exception - 0x00000000 (6) ####
#### Message:
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadBytes [IP: 0022] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadFrameBuffer [IP: 006b] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::UpdateStreaming [IP: 003a] ####
A first chance exception of type ‘System.Exception’ occurred in GTM.GHIElectronics.SerCam.dll
#### Exception System.Exception - 0x00000000 (6) ####
#### Message:
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadBytes [IP: 0022] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::ReadFrameBuffer [IP: 006b] ####
#### Gadgeteer.Modules.GHIElectronics.SerCam::UpdateStreaming [IP: 003a] ####
A first chance exception of type ‘System.Exception’ occurred in GTM.GHIElectronics.SerCam.dll

When I disconnected T socket, camera works.
Did I do something wrong? Is it just me or a known issue?


#2

Hi Zerojozhan, and most importantly welcome to the forum.

I don’t think anyone has ever raised this specific issue before. I think the GHI team or someone with both these will need to test it. Can you confirm, the same app, when you don’t have T socket connected, will work successfully, no code changes? Can you also confirm the socket you have the camera in?


#3

What is your firmware version?

Welcome to the forum.


#4

I am using the latest 4.2.5.
Yes, I was connecting the same sockets in the develop guide and I can confirm it word without T socket connected.


#5

I’ve confirmed the test case here. We will investigate.


#6

Thanks, Jeff.
And thanks for your warm welcome, guys. :slight_smile:


#7

@ Jeff - where can I get information about known issues and whether they have been fixed?


#8

@ zerojozhan - We keep a link to known issues on our support page: http://www.ghielectronics.com/support/.net-micro-framework. We try to keep it up-to-date, but reports are first entered into bug trackers for programmers to check, so until the programmer looks into it, there may be a lag with the entry into known issues. I don’t think there is a consolidated list available to the public as to what has been fixed (in general if it’s in known issues, somebody has/is working on a fix). And fixes, in general mean “next SDK release.” If the fix is a change to a Gadgeteer driver for a module, we sometimes publish the change so people can update their code (http://www.ghielectronics.com/docs/122/gadgeteer-driver-modification)

We are busy at work on a new SDK release.


#9

This issue has been fixed.
Thanks for your feedback.