From: Ignacio G. P. <ig...@gm...> - 2009-10-21 14:51:30
|
Hi, I'm trying to get a custom camera board working with a gumstix overo, and this is what I tried: 1- bitbake linux-omap-2.6.29 This compiles the OE 2.6.29 kernel which seems to include the ISP patches (ISP is the OMAP camera module interface). The kernel booted but I wasn't able to even get the camera interface clock output working. I noticed some strange things in the code of the ISP patches so instead of debugging the whole thing I though I'd better give a try to the latest omap3camera code. BTW, doing bitbake linux-omap3-2.6.29 doesn't include the ISP patches. Can anyone explain why there are "omap" and "omap3" flavors of evey kernel?. 2- Compiled the camera branch of the omap3camera project: This is supposed to be based on the latest linux-omap mainline. Compiled fine but the kernel didn't boot. The "uncompressing kernel" message is shown followed by the dots and a newline. Nothing else. This means the kernel hangs in a very early initialization step, even before being able to say "hello world". 3- Just to be sure there wasn't something weird in the omap3camera code, I decided to try the linux-omap mainline. I checked out the 2.6.29, 2.6.30 and 2.6.31 branches and compiled all using overo_defconfig that comes with each. The first two booted, but the 2.6.31 just doesn't boot (same as before). So I'm a bit baffled because I'm at a point where the linux-omap mainline compiled as-is for overo doesn't even get to boot. Any clues on what's wrong here? Thanks. |
From: Jason C. M. <jas...@am...> - 2009-10-21 18:13:19
|
I don't have any solutions for you, but I did experience the same frustrations. I'm surprised you were able to successfully bitbake linux-omap-2.6.29 within the Overo Branch. I tried it just a couple months ago (when it got added ) and it failed with some error message, yet the omap3 kernel bitbaked/compiled just fine. My take on the difference is one is just maintained by a different group, but I don't know if that's really true. It would be nice if there was just one linux-omap. I'm not sure why there needs to be two. I probably just don't have a complete understanding of it. The only successful camera code I have is based on the PSP kernel. I had to apply a bunch of patches (contained with the Overo branch) to it in order to get it to boot, and to work properly. I only went through all that work because I had the Camera working on an OMAP3EVM board which uses the PSP kernel. I might be mistaken, but I think the PSP kernel is based on linux-omap (maybe it is linux omap). Keep in mind that even if you don't use it the manual has good information on the ISP/OMAP34XXCAM/etc. http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_00/latest/index_FDS.html FYI - I haven't tried the latest, and what I had it working with was a few months ago. I also don't know if the Clock out works because my sensor board has an onboard clock. When I got it working I quickly let the software developer take over, and I ran back to hardware design. In my experience with trying to use the Gumstix Overo with a Camera I'd like to see the following changes. 1 - All the Camera related code (ISP,OMAP34XXCAM, resizer, IOMMU (if its even necessary anymore) into the linux-omap3-2.6.X kernel. My attempt at this was a complete failure (I couldn't get any video, but it did show up under /dev/video0. 2 - That the DSS2 is considered linked to the Video4Linux Display driver (or output driver). Without this you won't get good frame rates because you'll wind up using software color conversion. This allows the Camera to convert the image to YUV, and the display to accept YUV. There are probably other ways of doing this that I'm not aware of. I'm not a software developer and the Code I was using was designed for v4l-in -> v4l-out. 3 - There isn't anything that can be done about this, but I think the flex cable was a huge mistake on gumstix's part. It's likely going to be electrically noisy, and I have a collection of flex cables that have failed after only one or two insertions. I wish they would have used the expansion connectors on the bottom. It was a heck of lot easier using the OMAP3EVM board to develop the Sensor Driver. 4 - That the people that created the beagleboard would just add a darn Camera Connector. Even if they turn around and charge and arm and leg for a camera board. With all the robotic applications, augmented reality application that decision just boggles me. Its frustrating because that community is pretty amazing, and I know this OMAP3 camera issue would be mute had the beagleboard had it. Just a simple 26 pin expansion connector is all. I find it ironic they they now have a camera board they advertise for use with it, but it's an Ethernet camera. I know at least one company is coming out with a Sensor Head for the Gumstix so hopefully there will be patches that are straight forwards, and this camera issue will finally come to an end. They are supposed to get back to me on its availability, but they haven't done so yet. There is a Camera Sensor board for the OMAP3EVM now (thankfully)from leopard imaging that comes with free Linux drivers. All that being said I'm still really thankful gumstix actually has a camera connector, and didn't just ignore that capability. I think its going to really benefit them down the road. From: Ignacio García Pérez [mailto:ig...@gm...] Sent: Wednesday, October 21, 2009 7:51 AM To: gum...@li... Subject: [Gumstix-users] linux-omap kernel not booting Hi, I'm trying to get a custom camera board working with a gumstix overo, and this is what I tried: 1- bitbake linux-omap-2.6.29 This compiles the OE 2.6.29 kernel which seems to include the ISP patches (ISP is the OMAP camera module interface). The kernel booted but I wasn't able to even get the camera interface clock output working. I noticed some strange things in the code of the ISP patches so instead of debugging the whole thing I though I'd better give a try to the latest omap3camera code. BTW, doing bitbake linux-omap3-2.6.29 doesn't include the ISP patches. Can anyone explain why there are "omap" and "omap3" flavors of evey kernel?. 2- Compiled the camera branch of the omap3camera project: This is supposed to be based on the latest linux-omap mainline. Compiled fine but the kernel didn't boot. The "uncompressing kernel" message is shown followed by the dots and a newline. Nothing else. This means the kernel hangs in a very early initialization step, even before being able to say "hello world". 3- Just to be sure there wasn't something weird in the omap3camera code, I decided to try the linux-omap mainline. I checked out the 2.6.29, 2.6.30 and 2.6.31 branches and compiled all using overo_defconfig that comes with each. The first two booted, but the 2.6.31 just doesn't boot (same as before). So I'm a bit baffled because I'm at a point where the linux-omap mainline compiled as-is for overo doesn't even get to boot. Any clues on what's wrong here? Thanks. |
From: Ignacio G. P. <ig...@gm...> - 2009-10-21 18:34:42
|
Ok, I reply to myself to say FIXED. Sort of. It turns out the kernel won't boot unless CONFIG_TLW4030_USB is set. I bet this is something worth investigating for gumstix techs. That's it. And it sucks. El 21 de octubre de 2009 16:51, Ignacio García Pérez <ig...@gm...>escribió: > Hi, > > I'm trying to get a custom camera board working with a gumstix overo, and > this is what I tried: > > 1- bitbake linux-omap-2.6.29 > > This compiles the OE 2.6.29 kernel which seems to include the ISP patches > (ISP is the OMAP camera module interface). The kernel booted but I wasn't > able to even get the camera interface clock output working. I noticed some > strange things in the code of the ISP patches so instead of debugging the > whole thing I though I'd better give a try to the latest omap3camera code. > > BTW, doing bitbake linux-omap3-2.6.29 doesn't include the ISP patches. Can > anyone explain why there are "omap" and "omap3" flavors of evey kernel?. > > 2- Compiled the camera branch of the omap3camera project: > > This is supposed to be based on the latest linux-omap mainline. Compiled > fine but the kernel didn't boot. The "uncompressing kernel" message is shown > followed by the dots and a newline. Nothing else. This means the kernel > hangs in a very early initialization step, even before being able to say > "hello world". > > 3- Just to be sure there wasn't something weird in the omap3camera code, I > decided to try the linux-omap mainline. I checked out the 2.6.29, 2.6.30 and > 2.6.31 branches and compiled all using overo_defconfig that comes with each. > The first two booted, but the 2.6.31 just doesn't boot (same as before). > > So I'm a bit baffled because I'm at a point where the linux-omap mainline > compiled as-is for overo doesn't even get to boot. > > Any clues on what's wrong here? > > Thanks. > |