From: "Marc Reilly" <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Subject: Splash screen on mx35 3 stack
Date: Wed, 31 Mar 2010 20:59:53 +1100 [thread overview]
Message-ID: <007101cad0b8$eba13150$c2e393f0$@cpdesign.com.au> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1476 bytes --]
Hi,
I have a freescale IMX35PDK (3 stack) and want to get a bmp showing as a
splash screen, but am not having any luck. (Just getting a white screen,
although the backlight comes on). All hardware is as-original, using the
CLAA 800x480 LCD.
Has anyone had success getting something showing on the screen with the mx35
pdk? (or any other platform I can use as a reference).
To test, I'm simply using the "bmp" command with a small 100x100 test
picture. No errors are reported, but the screen never changes.
From the barebox prompt if do "devinfo fb0" I get some info, but the enable
is 0.
If I do fb0.enable=1 it doesn't make a difference.
Also:
- The fb works fine once booted into linux.
- Start-up messages indicate that the driver and device is
recognized:
Any ideas?
Cheers
Marc
PS. Snip of startup messages: (shows the driver/device is being loaded)
barebox 2010.03.0-00100-gf4a5a39-dirty (Mar 31 2010 - 18:32:31)
Board: Freescale MX35 3Stack
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd5 (Samsung NAND 2GiB 3,3V
8-bit)
Bad block table found at page 1048448, version 0x01
Bad block table found at page 1048320, version 0x01
cfi_probe: cfi_flash base: 0xa0000000 size: 0x04000000
cfi_protect: protect 0xa0040000 (size 524288)
imx-ipu-fb@imx-ipu-fb0: i.MX Framebuffer driver
mc13892@mc138920: revision: 0x41d0
[-- Attachment #1.2: Type: text/html, Size: 9277 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2010-03-31 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 9:59 Marc Reilly [this message]
2010-03-31 12:19 ` Sascha Hauer
2010-04-05 4:55 ` Marc Reilly
2010-04-06 6:30 ` 'Sascha Hauer'
2010-04-06 6:48 ` Peter Korsgaard
2010-04-01 5:58 ` Eric Bénard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007101cad0b8$eba13150$c2e393f0$@cpdesign.com.au' \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox