TI E2E Community
"OMAPLFBInit failed" when supporting high resolution LCD on DevKit-V1
As tested on Devkit-V1, on AM3517 EVM board, to support 1440*900 resolution via below command, it will report "omaplfb: OMAPLFB_Init: OMAPLFBInit failed".
From DSS driver point of view there should not be any differences which will limit the resolution support. If it is working on OMAP3530, then I don't see any reason why it is not working on AM3517.
The very first thing is, the resolution 1440x900 is not supported by modedb.c file, you have to add it manually to configure timing params for this resolution. Please make sure that, your kernel running on AM3517 devkit supports this resolution.
Also I have couple of questions here,
- Can you provide complete boot log?
- What makes you think that, code restricts max resolution to 1M pixel?
- Can you please let me know which PSP release are you using?
- If you are not based out of PSP release then what is your kernel version?
Please find the log files(1400x900 and 1400x1050) as attachments. And we tested it on Devkit-V1 + am3517 evm. The psp version should be 03.00.01.06.
As checked code, there is 4MB memory allocation limitation for video frame buffer application, so we guess this should be the reason.
By the way, we will try to add 1400x900 with timing, and try again. Will udpate you soon.
Attached 1400x900 resolution log.
Can you please also let me know the PSP Kernel Version? Just do "cat /proc/ti-psp-version"?
I am bit confused here, the kernel version you are using is 2.6.32, and the boot argument you are trying to set is from 2.6.29. Also the error message clearly mentions about the failure, it is failing because driver could not able to allocate required memory. You have to pass additional boot argument to reserve memory. Please use following boot argument (which I created from your boot log)
setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait init=/init vram=10M omapfb.vram=0:10M omapfb.vrfb=y omapfb.rotate=0 omap_vout.vid1_static_vrfb_alloc=y omapfb.mode=dvi:1440x900MR-16 omapdss.def_disp="dvi"
After the new bootargs, no error message again. And psp version is 03.00.01.06. please find attachment. Since I am on business trip and have no high resolution LCD, we will update you the final result a little bit later.
Thanks a lot!
You can check for device nodes on your system, if /dev/fb0 is being created then things are fine and Fbdev has been initialized without any issues.
We have tested, and 1440x900@58hz resolution could work on AM3517 EVM+DEVKIT V1 now.
Thanks a lot for your support.
I have a similar request.
I am running v2 Gnome on AM3517. DVI works fine when I run at omapfb.mode=dvi:1280x720@60
However, customer is requesting if we can run the demo on 1366x768 resolution screen – So I generated boot.scr with
omapfb.mode=dvi:1366x768@50 (as 60 Hz will exceed the 75MHz output clock on AM3517). When I do this, I get the following error on console
Any ideas on how I can get the display working at this resolution ?. Is this error because my dell monitor cannot support it or is it the display driver ?.
I do appreciate any help on this.
omapdss DSS error: Requested pixel clock not possible with the current OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.
mmc0: new SD card at address bca9
DSS error: Requested pixel clock not possible with the current OMAP2_DSS_MIN_FCK_PER_PCK setting. Turning the constraint off.
omapdss DISPC error: SYNC_LOST, disabling LCD
regulator_init_complete: incomplete constraints, leaving LDO2 on
regulator_init_complete: incomplete constraints, leaving LDO1 on
davinci_emac_probe: using random MAC addr: ca:a8:a3:01:5f:0c
rtc-s35390a 1-0030: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
omapdss DPI error: display already enabled
omap_vout omap_vout: 'dvi' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
omap_vout omap_vout: : registered and initialized video device 2
Can you please make sure that you have enabled DSI clock as a source clock? You may have to tune the timing parameters here, since the available timing parameters is not working for you.
i do not have readily available timing params for this resolution which are working on OMAP3, but should be easy to get one. You can update/add timing params in driver/video/modedb.c file or you can also use sysfs interface for changing timing params.
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. 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 respect to these materials. 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.