To enable the display, the config options in uBoot must be updated to tell the kernel to initialize the device. I’ll post the LCD image up there. Is the text white you may need to poke the blank variable as mentioned above. You punched in the i2c commands for the Rev C board. I assume it’s in there somewhere, but please confirm for me. You’ll need to contact Tom Catalino or someone in sales for details about that. Test gradient looks fine now, and so does my logo.
|Date Added:||5 October 2018|
|File Size:||45.20 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
After you are up and running, could you please run a i2cdump -y 2 0x38 and post or email me the results? To enable the display, the config options in uBoot must be updated to tell the kernel to initialize the device. I’ll get the source up there as well. Each bar is one bit of color, so lce should get 5 blue bars, 6 green bars, and 5 red bars. Since we’re not getting any red guns, no white pixels.
drivers/video/da8xx-fb.c – pub/scm/linux/kernel/git/tomba/linux – Git at Google
William If you are seeing blue vertical stripes every other pixel then the frame buffer is working. I then did the configuration commands found on the LCD configuration Wiki page. The “name” fields is keyed in the init code in the board-mityomapl Again, we can’t really help too much here without detailed schematics, and ideally some hardware test with.
I’ll have the Critical Link-recommended panel here tomorrow and will start working with it then. My logo is grayscale on a white background, and the background is blue could be blue-green; I didn’t check that closely. That’s the right image.
Added by Otmar Schlunk over 8 years ago We are trying to figure out how to get video out of the board and had a couple of questions. You punched in the i2c commands for the Rev C board. Otherwise, we’ll ping you again when we have questions. Two frames, B0 and B1, are needed at the start as shown in below figure. It’s a work in progress, but there should be enough info in there now to at least force a frame buffer device into existence for the kernel.
Definitely not a Rev C board, so it must be a B I think we have an A here as well, but this isn’t it.
Quite possibly an error on my end. If you have designed your own hardware using a new LCD, I’m afraid you’re going to be on your own to get it functioning unless you can provide schematics, your FPGA code, and some hardware for us to support you with. Then trim off the first 72 bytes of da8xx–fb file.
You also need to load an additional module for the touchscreen controller on the LCD. Thanks for the help. The screen is all blue and green.
From Texas Instruments Wiki. Can da8zx-fb please confirm the revision of your board B, or C? Schlunk, The kernel included in the development kit provided should have the necessary code installed to support either the DVI interface or the LCD panel interface. Please use the following two commands as described in the wiki: Would be nice to get this more automated if we can figure out why it’s not showing up, but again that’s not a show-stopper.
What I mean is that the pixels are in the right places.
[PATCH] davinci: fb: Frame Buffer driver for TI DA8xx/OMAP-L1xx
It’s not there yet. OK — we’re definitely making progress here. Is the text white you may need to poke lxd blank variable as mentioned above. Unfortunately, it gives me “Operation not permitted” errors whenever I try to read or write the device, so although it’s there I can’t change the image.
That is we could be updating in host CPU keep out region.