/dev/fb0 problem on beaglebone

hi,

I am also facing the same problem.

I am using linux 3.1.0-rc8 which comes default with beagle bone board.

as it is not crating /dev/fb0 device, I tried configuring and compiling the kernel mannually, but still the frame buffer device is not getting created.

I want to run one small QT application on it.

Can anyone suggest me how to go ahead......

Regards,

mahanteshwari.

mahanteshwari,

If you don't use daughter board, you have to add "lcdc_init" and if you want tsc_init to beaglebone_dev_cfg[] in arch/arm/mach-omap2/boardam335xevm.c file .

/* Beaglebone Rev A3 and after */
static struct evm_dev_cfg beaglebone_dev_cfg[] = {
	{mii1_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
	{usb0_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
	{usb1_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
	{mmc0_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
/**
	Mehmet Kurnaz		13/01/12
	enable lcd and ts on beaglebone without daughter board
*/
	{lcdc_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
	{tsc_init,	DEV_ON_BASEBOARD, PROFILE_NONE},
	{NULL, 0, 0},
};

Thanks

Mehmet Kurnaz

Greetings,

As a linux newbie, this post has been most helpful along with several links to the Graphics SDK GSG and Adding DVI resolutions.

We wish to add a 320x240 custom panel to the BeagleBone running in portrait vs. landscape orientation.

I've found the generic_dpi_panels structure in the .../drivers/video/omap2/displays/panel-generic-dpi.c file and the modedb (fb_videomode) structure in drivers/video/modedb.c.

Should making changes in these two areas along with adding the omap.dvi setting in the bootargs be sufficient to begin running the SDK Matrix demo on our LCD?

I'm preparing for on the hardware development of an interface board and want to be ready when it's available.

Dave

Hi Mehmet Kurnaz,

after entering this change:

        {lcdc_init,DEV_ON_BASEBOARD, PROFILE_NONE},
	{tsc_init,	DEV_ON_BASEBOARD, PROFILE_NONE},

we rebuild the kernel? I ask because I find the file boardam335xevm.c only after compiling 
the kernel and not on the source.

Thanks
Giulo Dalla Vecchia

hello... me also..lcd cape 4' no working in my beaglebone a6 using ti sdk.05.06.

i can remote matrix app but nothing appear in my lcd.when i ssh ti sdk and when ts_calibrate appear no such file / directory.

dont have /dev/fb0 in root but before compile i can see /dev/fb0 in targetNFS.

anyone can help me step by step how to display matrix app in lcd cape 4.0.

sorry for inconvenience for my bad english.

thanks.

When I do this (for beaglebone-black), when compiling the kernel, I get:

arch/arm/mach-omap2/board-am335xevm.c:2208:3: error: ‘tsc_init’ undeclared here (not in a function)

I am using TI-SDK 6.0

It is true that tsc_init function does not exist in this file. Am I missing something?

Thanks,

JBM

In the beagleboneblack to activate the LCD need to edit the device tree of the device. You have to edit the file *.dts. Studied well the device tree.

Best reguard.

Giulio

Will that be enough?

I read from http://e2e.ti.com/support/arm/sitara_arm/f/791/p/232437/995684.aspx#995684

that LCD3 capes are not supported. Do I have to make modifications to board-am335xevm.c in addition to editing the device tree?

Also, is there any board-am335xevm.c file available that currently support LCD3 capes for beaglebone black?

Thanks,

JBM