This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I'm working on the OMAP3530 Mistral EVM. In an attempt to update to dvsdk_3_00_00_31, I rebuilt u-boot, linux kernel, the dvsdk software and the nfs image. I successfully flashed the new linux kernel as per the Getting Started Guide. I've set the bootargs and bootcmd to boot from the flash using NFS file system. Though the system initializes correctly, when the kernel attempts to start the demo application, I receive the following error:
System initialization... Hostname : OMAP3EVM Filesystem : v1.0.2 Kernel release : Linux 220.127.116.11-omap3 Kernel version : #2 Mon Mar 30 11:39:16 CDT 2009 Mounting /proc : [SUCCESS] Mounting /sys : [SUCCESS] Mounting /dev : [SUCCESS] Mounting /dev/pts : [SUCCESS] Enabling hot-plug : [SUCCESS] Populating /dev : [SUCCESS] Disabling Power mgmt : [SUCCESS] Turn off LCD after 1 hour : [SUCCESS] Mounting other filesystems : [SUCCESS] Starting syslogd : [SUCCESS] Starting telnetd : Jan 1 00:00:15 OMAP3EVM syslog.info syslogd started: BusyBox v1.9.1[SUCCESS]System initialization complete. Starting Demo Application...ioremap_nocache(0x85800000, 16777216)=0xc7000000allocated heap buffer 0xc7000000 of size 0xea000cmem initialized 7 pools between 0x85800000 and 0x86800000dsplinkk: no version for "struct_module" found: kernel tainted.DSPLINK Module (1.51) created on Date: Aug 1 2008 Time: 19:28:58
My kernel command line is: mem=88M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.100:/tmp/gurnani/workdir/filesys,nolock ip=192.168.1.10:192.168.1.100:192.168.1.1:255.255.255.0::eth0:on
I also got a message saying "Failed to create display device instance."
I'd appreciate any guidance I can get on this. Thanks!
--- If you need more help, please reply. If this answers your question, please Verify Answer below this post ---
The dsplink message is normal. This sounds like something related to the display driver. I recommend making another post which focuses on that.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Brad Griffis:
The only message related to the display device I'm getting is this:
Demo interface started at level 0.Error: Failed to create display device instance
Would there be more information I can provide that can help?
In reply to Uday:
Has this issue been resolved?
I am also having a problem running the demos.
I am getting the same error:
Error: Failed to create display device instance
I am able to run the ./decode and get help and run the h.264 video, but can not display the UI, and clicking a button crashes the demo.
Thanks for any help.
In reply to msj:
The problem went away when I downgraded to dvsdk 3_00_00_30. Maybe you could try that, else post what you see on the terminal and someone who knows could jump in and help.
I am using "dvsdk_setuplinux_3_00_00_29.bin" , and I thought this was themost upto date version?
and the error I am getting:
"[root@OMAP3EVM dvsdk]# ./decode -o -v ./data/videos/davincieffect_ntsc_1.264Decode demo started.Error: Failed to create display deviceError: Failed to create UI"
There is also an interesting note in the DVSDK Getting Started Guide:
"NOTE: Since the DVSDK decode demos require the OSD planes to be rotated by 90 degrees, and sincethese are the demos that will be started by the DVSDK target file system start-up scripts, using thebootargs as mentioned above would result in the following output at the end of the boot process. Kindlyignore the error message and press “enter” key on the host PC to go to the target prompt.System initialization complete.Starting Demo Application...ioremap_nocache(0x85800000, 16777216)=0xc7000000allocated heap buffer 0xc7000000 of size 0x850000cmem initialized 5 pools between 0x85800000 and 0x86800000dsplinkk: no version for "struct_module" found: kernel tainted.dsplinkk: module license 'DSP/BIOS(TM) LINK' taints kernel.DSPLINK Module (1.51.00.08) created on Date: Jun 13 2008 Time: 08:28:01Demo interface started at level 0.Interface Error: Failed to create display device instance"
So how do we rotate the OSD planes 90 degrees?
Add "video=omap24xxfb:rotation=90" to your bootargs.
For example, my bootargs are set as
"setenv bootargs mem=88M console=ttyS0,115200n8 noinitrd rootdelay=1 rw ip=dhcp root=/dev/nfs nfsroot=192.168.1.100:/home/<username>/workdir/filesys,nolock video=omap24xxfb:rotation=90"
Thanks Uday. That did it!
The video demo is now booting automatically and the Boot Errors are gone, and the buttons are navigating as they should without crashing.
Glad it's working. Looking back at my kernel command line in the first post, I had that rotation=90 missing too!
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.