[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [microblaze-uclinux] VGA controller in Microblaze

To: microblaze-uclinux@xxxxxxxxxxxxxx
Subject: Re: [microblaze-uclinux] VGA controller in Microblaze
From: pcolodron@xxxxxxxx
Date: Tue, 31 Mar 2009 17:49:26 +0200
Reply-to: microblaze-uclinux@xxxxxxxxxxxxxx
Sender: owner-microblaze-uclinux@xxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) H3 (4.1.4)

Hi John,

I finally could see the boot messages in the monitor. I had to add thedevice registration that you told me and I have to change someparameters that I didn't realise that were basic. In xilinxfb.c, theparameter REG_CTRL was set to 1, however, as I am using SPLB interfaceit must be set to 4 (I saw this in Xilinx TFT IP Core datasheet).

However, after showing the boot messages, I could show anything elseon the monitor. I tried "cat /dev/urandom > /dev/fb0" but the garbageis only shown in the hyperterminal that I use to comunicate with theserial port, not on the monitor (I wish I knew why). Moreover there issomething wrong because the Linux logo (penguin) colours are wrong (Ijust see yellow and black shadows...).


I configure 'bootargs' with console=tty0 and console=ttyS0,115200.

I thought that a linux prompt would be seen on the monitor as well,however I am not sure about this. Should I see it or there issomething more that have to configure?


Thanks a lot and kind regards John,

Pablo


John Williams escribió:

Hi Pablo,

What happens if you do

$ cat /dev/urandom > /dev/fb0

?

Ideally you should see random garbage on the monitor.

Regards,

John

On Tue, Mar 31, 2009 at 11:24 PM,  <pcolodron@xxxxxxxx> wrote:

Hi Inaki,

I have done what you told me but it did not work either. As I mentioned in
the previous post, when I boot the system I receive the following new
information:

Console: switching to colour frame buffer device 80x30
xilinxfb xilinxfb.0: regs: phys=86e00000, virt=86e00000
xilinxfb xilinxfb.0: fb: phys=8fc00000, virt=8fc00000, size=1e0000

However there is no information about the framebuffer of the framebuffer
console (which I have activated in menuconfig). Should this information
appear when booting the system?

Due to this, the vga monitor is black. I was wondering how the kernel
associate the device /dev/fb0 with the framebuffer. I mean, in the same way
as xgpio0 is associated with /dev/gpio0 and uartlite is associated with
/dev/ttyS0. Maybe the problem could be there but I don't know.

I have observed the following:

# cat /proc/fb
0 Xilinx
# cat /proc/ioports
00000060-0000006f : i8042
86e00000-86e0ffff : xilinxfb.0

Is this right? In the first command it seems that there is a framebuffer
registered. However, xilinxfb.0 should be in ioports?

Thanks a lot Inaki and John for your kind help.

Regards,

Pablo Colodron


Val Inaki escribió:

Hi Pablo,

 here is the code you need to add, first the definition of the device
structure:

static struct platform_device xilinxfb_device={
       .name = "xilinxfb",                             \
       .id = 0,                                        \
       .num_resources = 1,                             \
       .resource = (struct resource[]) {               \
               {                                       \
                       .start  = CONFIG_XILINX_TFT_0_SPLB_BASEADDR,    \
                       .end    = CONFIG_XILINX_TFT_0_SPLB_HIGHADDR,    \
                       .flags  = IORESOURCE_IO                 \
               }                                                       \
       }                                               \

};

In the driver initialization function you must register the device with
'platform_device_register' function:

static int __init
xilinxfb_init(void)
{
       int rc;
       rc = xilinxfb_of_register();
       if (rc)
               return rc;

       rc = platform_driver_register(&xilinxfb_platform_driver);
       if (rc)
               xilinxfb_of_unregister();

       platform_device_register(&xilinxfb_device); /* Device
initialization */

       return rc;
}

I hope this work for you.

Regards,

 Inaki



-----Mensaje original-----
De: owner-microblaze-uclinux@xxxxxxxxxxxxxx en nombre de
pcolodron@xxxxxxxx
Enviado el: lun 30/03/2009 14:58
Para: microblaze-uclinux@xxxxxxxxxxxxxx
Asunto: Re: [microblaze-uclinux] VGA controller in Microblaze
 Hi John,

Thanks for your help, it helped me to understand better how to work  with
new devices and drivers. As you told me, I created a file  xilinxfb.c in
arch/microblaze/platform/common, which content is:

#include <linux/autoconf.h>
#include <linux/init.h>
#include <linux/resource.h>
#include <linux/xilinx_devices.h>

/* Fake definitions of IRQ channels for XGPIOs that don't actually have
one.
   This is not super clean, but it does allow us to use a generic
   platform_device initialiser macro - see below */

#ifndef CONFIG_XILINX_TFT_0_IRQ
#define CONFIG_XILINX_TFT_0_IRQ -1L
#endif

#ifndef CONFIG_XILINX_TFT_1_IRQ
#define CONFIG_XILINX_TFT_1_IRQ -1L
#endif

#ifndef CONFIG_XILINX_TFT_2_IRQ
#define CONFIG_XILINX_TFT_2_IRQ -1L
#endif

#ifndef CONFIG_XILINX_TFT_3_IRQ
#define CONFIG_XILINX_TFT_3_IRQ -1L
#endif

#ifndef CONFIG_XILINX_TFT_4_IRQ
#define CONFIG_XILINX_TFT_4_IRQ -1L
#endif

#ifndef CONFIG_XILINX_TFT_5_IRQ
#define CONFIG_XILINX_TFT_5_IRQ -1L
#endif

/* Generic XGPIO platform_device initialiser macro.  Sinec we can nets
#ifdef
   conditionals inside macros, we have two resources for each device, but
in
   non-IRQ peripherals, the resource type is set to zero, otherwise it's
   IORESOURCE_IRQ as expected.  The kernel will just ignore zero-flagged
   resources.  We waste a small number of bytes - c'est la vie*/
#define XILINX_FB_PLATFORM_INITIALISER(n) \
{                                                               \
       .name = "xilinxfb",                                     \
       .id = (n),                                              \
       .dev.platform_data = 0,                                 \
       .num_resources = 2,                                     \
       .resource = (struct resource[]) {                       \
               {                                               \
                       .start  = CONFIG_XILINX_TFT_##n##_SPLB_BASEADDR,
     \
                       .end    = CONFIG_XILINX_TFT_##n##_SPLB_HIGHADDR,
     \
                       .flags  = IORESOURCE_IO,                        \
               },                                                      \
               {                                                       \
                       .start  = CONFIG_XILINX_TFT_##n##_IRQ,          \
                       .end    = CONFIG_XILINX_TFT_##n##_IRQ,          \
                       .flags  = IORESOURCE_IRQ,                       \
               },                                                      \
       },                                                              \
}

// dev.platform_data se define como 0. En el archivo
 .../drivers/video/xilinxfb.c se utiliza un platform_data por defecto  que
define de la resolucion de la pantalla 640x480. Si aquí definimos  un
platform_data, utiliza estos para aplicar la resolución y si no lo
 definimos utiliza los que vienen por defecto.
// num_resources lo definimos igual a 2, así lo hace el resto de los
 drivers en esta carpeta excepto xgpio (parece que este parámetro  depende
de si hay interrupciones?).
// Será necesario definir la direccion donde se encuentra el  framebuffer?
(parece que no, debería buscarla usando baseaddr).

static struct platform_device xilinx_fb_device[]= {
#ifdef CONFIG_XILINX_TFT_0_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(0),
#endif
#ifdef CONFIG_XILINX_TFT_1_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(1),
#endif
#ifdef CONFIG_XILINX_TFT_2_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(2),
#endif
#ifdef CONFIG_XILINX_TFT_3_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(3),
#endif
#ifdef CONFIG_XILINX_TFT_4_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(4),
#endif
#ifdef CONFIG_XILINX_TFT_5_INSTANCE
XILINX_FB_PLATFORM_INITIALISER(5),
#endif
};

static int __init xilinx_fb_platform_init(void)
{
       int i;

       for(i=0;i<ARRAY_SIZE(xilinx_fb_device); i++)
               platform_device_register(&xilinx_fb_device[i]);

       return 0;
}

device_initcall(xilinx_fb_platform_init);


As a result, now I have a xilinxfb device:

    # ls /sys/bus/platform/devices/
    i8042          uartlite.0     xilinx_gpio.0  xilinx_gpio.1  xilinxfb.0

However this device is not assigned to fb0. I receive the following
 message when booting the board:

xilinxfb xilinxfb.0: regs: phys=86e00000, virt=86e00000
xilinxfb xilinxfb.0: fb: phys=8fc00000, virt=8fc00000, size=1e0000

However there are no messages about the framebuffer. Moreover, when I  try
to see the I/O memory space I obtain the following:

    # cat /proc/iomem
    81400000-8140ffff : xilinx_gpio.0
      81400000-8140ffff : xilinx_gpio
    81420000-8142ffff : xilinx_gpio.1
      81420000-8142ffff : xilinx_gpio
    84000000-8400ffff : uartlite.0
      84000000-8400000f : uartlite
    86e00000-86e00007 : xilinxfb

As you can see, there is no memory assigned to xilinxfb.o. I am surely
 missing some steps when creating the framebuffer but I am not able to  see
where is the error. Do you have any hint about what I am not doing  right?

Thanks a lot for your kind help John.

Regards,

Pablo Colodron



John Williams escribió:

Hi Pablo,

On Wed, Mar 25, 2009 at 8:50 PM,  <pcolodron@xxxxxxxx> wrote:

Hi Inaki,

That is what I was checking just right now :) I have found out that
although
it enters in function 'platform_driver_register', it does not enter in
function 'xilinxfb_platform_probe', which is the one that initialize the
framebuffer. I don't know why this happens but I'll try to figure it
out...
Thanks a lot for your help Inaki. I'll let you know my progress.

The problem is that you have not registered a platform device - that
is the kernel doesn't know you have a xilinx_fb device in the system,
so it never calls the _probe() function.

To do this, look in arch/microblaze/platform/common - you need to
create a file called xilinxfb.c here.  Link it in to the Makefile of
this directory.

This code must create a platform_device structure, and then call
platform_device_register() on that object.

There are other examples in this same directory for other devices -
e.g. xilinx_spi.c.  The pattern should be clear.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
 http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/



___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/



___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive :
http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/




___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/

Prev by Date: Re: [microblaze-uclinux] User Apps and Library successful builds
Previous by thread: Re: [microblaze-uclinux] VGA controller in Microblaze
Next by thread: [microblaze-uclinux] FSL driver interruption management
Index(es):
- Date
- Thread