Camera Interface - Beacon EmbeddedWorks - TDG Forum

Create Account

Create Account

You are here: >> >> >>

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

Forums
Search Forum
Advanced SearchTopicsPosts

Prev Go to previous topic

Go to next topic

Last Post 06 Jan 2014 09:55 AM by Richard Hendricks

Camera Interface

2 Replies

Sort:


You are not authorized to post a reply.

Author

Messages

steven.eckhoff

Basic Member
Posts:192

18 Dec 2013 11:14 AM
Q: 1. Is there any camera support for this device? 2. What is the best OS to use with a camera? 3. if there are camera drivers available can they be modified for another camera? A: 1. Yes, we have a friendly introduction to the camera interface in the Linux User's guide [1]. 2. Out of the box I would suggest using Linux. 3. Yes, but the level of work will depend on how similar the cameras are. I would highly suggest using one that has an existing driver that works. You can start with the camera suggested in the Linux User's guide. If that one does not suit your needs then, I would suggest buying evaluation kits first and test them on the Launcher 3 board before starting any development. [1] Linux User's Guide

Nick Ryhajlo

New Member
Posts:2

04 Jan 2014 05:23 PM
I am attempting to follow the directions in Section 7 for setting up the Cameras and DSP. I compiled the kernel as yaffs2 and I set the otherbootargs, but I can't seem to get the system to boot from the SD card. I get the following message: ... == Loading kernel file uImage to 0x81000000 == mmc1 is available reading uImage 3991776 bytes read == Loading rootfs file rootfs.ext2.gz.uboot to 0x82000000 == reading rootfs.ext2.gz.uboot Unable to read "rootfs.ext2.gz.uboot" from mmc 1:1 == Kernel bootargs == nand-ecc=chip console=ttyO0,115200n8 display=15 ignore loglevel early printk no_console_suspend mem=55M@80000000 mem=128M@88000000 mtdparts=omap2-nand.0:512k(x-loader),1664k(u-boot),384k(u-boot-env),5m(kernel),20m(ramdisk),-(fs) root=/dev/ram rw ramdisk_size=128000 bootm 0x81000000 0x82000000 ## Booting kernel from Legacy Image at 81000000 ... Image Name: Linux-3.0.0-BSP-dm37x-2.3-2 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3991712 Bytes = 3.8 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid OMAP Logic # On the SD card I have the following files: MLO, rootfs.yaffs2, u-boot.bin, u-boot.bin.ift, and uImage. I feel like I need another file, but there is only 2.4 MB left on the SD card (formatted with the mkLogicFATcard.sh).

Richard Hendricks

New Member
Posts:52

06 Jan 2014 09:55 AM
Nick, Are you wanting to burn your filesystem into YAFFS, or use a RAM based file system loaded from the SD Card? Your u-boot image is assuming a RAM-based file system. That is not compatible with your choice of the YAFFS-based file system. What you need to do is burn uboot and the rootfs.yaffs file directly to the NAND. You have already completed the steps in 2.5.4.1 of the Linux User's Manual and now you need to use the makeyaffsboot script in uboot from 3.2.10.2. This will use the rootfs.yaffs file and burn the filesystem to NAND as a YAFFS filesystem that will persist over power cycles. Once the burn is complete, you will need to eject the SD card and power cycle your system to boot.

You are not authorized to post a reply.

Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit