Hi all Im am using the DVSDK6467 board. Even I am facing the same problem. I change the encodedecode demo and encode demo to work with the composite port. But in my setup it is not working. When I run it, it gives the following errors:
Encodedecode demo started. Error: Failed to create display device Error: Failed to create Cpu Object Error: Failed to create capture device, DI component input connected For one of my friend the same encodedecode application is working. Please help me ?Thanks & Regards Deepanshu Gupta -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, June 25, 2008 9:40 PM To: [email protected] Subject: Davinci-linux-open-source Digest, Vol 30, Issue 107 Send Davinci-linux-open-source mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Davinci-linux-open-source digest..." Today's Topics: 1. Re: (no subject) (Valentina Ivanovic) 2. Premption of DSP side codecs. (Omkiran Sharma) 3. Demo on DVEVM 6467 is not starting (Ondrej Pindroch) 4. Flashing NAND for u-boot from Linux - ECC differences? (Bernard Blackham) 5. Devrocket (Stephen Berry) 6. RE: Flashing NAND for u-boot from Linux - ECC differences? (Jon Povey) 7. Re: Flashing NAND for u-boot from Linux - ECC differences? (Diego Dompe) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Jun 2008 04:43:50 -0700 (PDT) From: Valentina Ivanovic <[EMAIL PROTECTED]> Subject: Re: (no subject) To: [EMAIL PROTECTED] Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Hi Rajesh, Have you configured your kernel with MTD partitions enabled ? Valentina --- On Wed, 6/25/08, rajesh <[EMAIL PROTECTED]> wrote: From: rajesh <[EMAIL PROTECTED]> Subject: (no subject) To: "'Davinci_linux_open_source (E-mail)'" <[email protected]> Date: Wednesday, June 25, 2008, 10:26 AM Hi I am using DVEVM (TMS320DM6446) and MVL401 Linux 2.6.10 (older version) I want to create partitions in the NOR flash on DVEVM. there are 2 patches related to NOR provided by ti. 1.ti_davinci_mv_1_0_nor_flash_driver_008 2.ti_davinci_mv_1_0_nor_partition_fix_023 I have applied the patch 1 successfully it will create a new c file davinci_nor_flash.c in the ti-davinci/driver/mtd/chips directory. This file contains the partition definition for NOR flash. I created uImage and boot the board with this uImage it is not showing any partition in NOR flash. when i tried to apply the patch 2, it is giving eror. So can anybody please help me to create partitions in the NOR flash under MVL401 Linux 2.6.10 kernel (older version) Thanks and Regards Rajesh G The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it. Contact your Administrator for further information._______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/200806 25/ada832f7/attachment-0001.htm ------------------------------ Message: 2 Date: Wed, 25 Jun 2008 18:23:25 +0530 From: "Omkiran Sharma" <[EMAIL PROTECTED]> Subject: Premption of DSP side codecs. To: "[email protected]" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" All, Is there any way apart from having two threads on the DSP with different priorities for one thread to pre-empt another. Here is the problem: I have two codec instances of a codec which is pre-emptable. I am guessing each gets its own thread on DSP. Is there any way for these two threads to run concurrently on the DSP? As far as I know, the only way one thread gets pre-empted today on the bios is that if a higher priority thread arrives. Another way would be for a thread to give itself up and I think there is a way of one thread to yield itself. But will this gaurantee that the other thread (at the same priority level) and not itself gets picked up for execution? Regards, Omkiran -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/200806 25/25b5a21c/attachment-0001.htm ------------------------------ Message: 3 Date: Wed, 25 Jun 2008 15:44:56 +0200 From: "Ondrej Pindroch" <[EMAIL PROTECTED]> Subject: Demo on DVEVM 6467 is not starting To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="us-ascii" Hi all I have build whole demo on DVEVM 6467 but I am still not able to run it. This is what i get, when I tried to lounche decode. [EMAIL PROTECTED]:/opt/dvsdk/dm6467# ./decode -y5 -o -i -v ./data/videos/dust_1080i_30fps.m2v Decode demo started. Error: Failed to create display device Error: Failed to create Cpu Object Demo interface started at level 4. Interface Error: Failed to create display device instance Have you any sugestion, what to do? Regards, Ondrej Pindroch -------------- next part -------------- An HTML attachment was scrubbed... URL: http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/200806 25/73686576/attachment-0001.htm ------------------------------ Message: 4 Date: Wed, 25 Jun 2008 23:24:00 +0800 From: Bernard Blackham <[EMAIL PROTECTED]> Subject: Flashing NAND for u-boot from Linux - ECC differences? To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii U-boot: 1.3.3 Linux kernel: 2.6.24 + patches to approximate current git NAND: 256MiB with 128KiB blocks and 2KiB pages I tried flashing a kernel image into NAND on an mtd device using the nandwrite utility from within Linux. u-boot cannot read the image and it fails with "read error". If I flash the image with u-boot's nand write, u-boot can boot it. Reading it from Linux generates loads of correctable and uncorrectable bitflip errors in dmesg. Also, comparing the result read through Linux with the original image indeed shows a whole bunch of bit flips all over the place (but with no pattern or regularity). This leads me to believe that perhaps the ECC layouts used by u-boot and the kernel differ slightly. It seems that u-boot defines a custom nand_oobinfo in davinci_nand_oobinfo. However, the davinci_nand driver in the kernel does not and I gather it uses the defaults in nand_base.c, which are significantly different. Should these be both using the same ECC layout? Has anybody else run into this, or am I doing something silly? All I want to be able to do is drop a new kernel in for u-boot but from Linux. TIA, Bernard. ------------------------------ Message: 5 Date: Wed, 25 Jun 2008 11:41:15 -0400 From: Stephen Berry <[EMAIL PROTECTED]> Subject: Devrocket To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Are there any Devrocket users out there? I was playing with devrocket to create a custom stripped down filesystem for our product, but for the life of me I can't get it to actually DO anything. I follow the steps in the wizard to create a platform image, and the only files that seem to get created are in /etc for passwd and a couple of others. Adding packages doesn't seem to do anything at all... I'm using version 2.0.4 of eclipse, and montavista pro 4.0.1. Oh - and yes this would be a question that I would normally ask the vendor, but our 15.75 seconds of support ran out as I was unpacking the software last year... Steve ------------------------------ Message: 6 Date: Wed, 25 Jun 2008 16:55:34 +0100 From: "Jon Povey" <[EMAIL PROTECTED]> Subject: RE: Flashing NAND for u-boot from Linux - ECC differences? To: "Bernard Blackham" <[EMAIL PROTECTED]>, <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="utf-8" (Reformat as list-mail as I realise it might have useful information in it) Bernard, I haven't tried this but I can tell you that the kernel image on the DM355 EVM uses the hardware ECC as documented in the DM355 datasheets. I have a Ronetix PEEDI to program the flash through JTAG, as it turned out I was the first customer with a DM355 (although they advertised compatibility on their site.. hmm!) and had to work with the firmware developer, providing flash dumps of the EVM, so he could implement the ECC. (To give the guy his due, he was very helpful and got it all working quickly). This "special ECC mode" is active for programming the UBL, uboot magic (read by UBL), uboot itself, the uboot enviroment and the kernel image. We haven't got as far as programming the filesystems with PEEDI, getting a blank flash up to kernel booting was enough for me to be getting on with for now, so I don't have more information about the ECC used for YAFFS/JFFS partitions. Hope this info is useful. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Blackham Sent: 25 June 2008 16:24 To: [email protected] Subject: Flashing NAND for u-boot from Linux - ECC differences? U-boot: 1.3.3 Linux kernel: 2.6.24 + patches to approximate current git NAND: 256MiB with 128KiB blocks and 2KiB pages I tried flashing a kernel image into NAND on an mtd device using the nandwrite utility from within Linux. u-boot cannot read the image and it fails with "read error". Racelogic is a limited company registered in England. Registered number 2743719 . Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, Bucks, MK18 1TB . The information contained in this electronic mail transmission is intended by Racelogic Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender's address records can be corrected. The views expressed by the sender of this communication do not necessarily represent those of Racelogic Ltd. Please note that Racelogic reserves the right to monitor e-mail communications passing through its network ------------------------------ Message: 7 Date: Wed, 25 Jun 2008 10:08:59 -0600 From: Diego Dompe <[EMAIL PROTECTED]> Subject: Re: Flashing NAND for u-boot from Linux - ECC differences? To: Bernard Blackham <[EMAIL PROTECTED]> Cc: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Bernard, DM6446 and DM355 uses a different OOB layout for NAND booting than the one used by the Linux kernels. This forces the bootloader to use a custom OOB layout since the UBL needs to be loaded by the ROM code of the SoC. The OOB layout is not only different in the position of the ECC bytes, but in the location of the OOB, which uses syndrome mode (at least on DM355, not sure on DM6446). I assume for simplicity uboot should be using the same OOB for himself and the images it writes (our bootloader uses the custom OOB only for the UBL, and the standard one for the rest of the software). If you want to be able to burn the software from Linux, the best you can do is to modify the OOB layout of the davinci nand driver in Linux to match the one used by your u-boot, or write and small application in user space that uses a custom oob to write the nand (take a look at the nandwrite program of the mtdutils package). Diego Dompe RidgeRun Engineering On Jun 25, 2008, at 9:24 AM, Bernard Blackham wrote: > U-boot: 1.3.3 > Linux kernel: 2.6.24 + patches to approximate current git > NAND: 256MiB with 128KiB blocks and 2KiB pages > > I tried flashing a kernel image into NAND on an mtd device using the > nandwrite utility from within Linux. u-boot cannot read the image > and it fails with "read error". > > If I flash the image with u-boot's nand write, u-boot can boot it. > Reading it from Linux generates loads of correctable and > uncorrectable bitflip errors in dmesg. Also, comparing the result > read through Linux with the original image indeed shows a whole > bunch of bit flips all over the place (but with no pattern or > regularity). > > This leads me to believe that perhaps the ECC layouts used by u-boot > and the kernel differ slightly. It seems that u-boot defines a > custom nand_oobinfo in davinci_nand_oobinfo. However, the > davinci_nand driver in the kernel does not and I gather it uses the > defaults in nand_base.c, which are significantly different. Should > these be both using the same ECC layout? > > Has anybody else run into this, or am I doing something silly? All I > want to be able to do is drop a new kernel in for u-boot but from > Linux. > > TIA, > Bernard. > > _______________________________________________ > Davinci-linux-open-source mailing list > [email protected] > http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source ------------------------------ _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source End of Davinci-linux-open-source Digest, Vol 30, Issue 107 ********************************************************** _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
