BBB LCD7 and 2013-06-20

Anyone got Beaglebone Black Rev A5B, Beaglebone LCD7 Cape Rev A3 to work with Flasher Image 2013-06-20 ?

According to the cape status, it’s green and should now work, but when I connect it and attempt any use,
I get mmcblk0 errors and the system crashes, in a variety of ways. I do get a display for a short while until it falls
over in a heap.

I’ve tried 2 LCD7’s and 2 beagle bones blacks. Both BBB’s work fine without the LCD7 connected. The LCD7 is the only
thing connected.

Example:

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.193610] omap2_mbox_probe: platform not supported
[ 0.204218] tps65217-bl tps65217-bl: no platform data provided
[ 0.304236] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.341344] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.378452] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.404161] bone-capemgr bone_capemgr.8: slot #5: BB-BONELT-HDMI conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.413755] bone-capemgr bone_capemgr.8: slot #5: Failed verification
[ 0.420527] bone-capemgr bone_capemgr.8: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 0.433010] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.442748] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.449527] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.471359] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.535144] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.546877] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.554210] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.714371] tilcdc 4830e000.fb: timeout waiting for framedone
[ 4.730165] mmcblk0: error -84 transferring data, sector 1402681, nr 128, cmd response 0x900, card status 0xb00
[ 6.989115] mmcblk0: error -84 transferring data, sector 550545, nr 48, cmd response 0x900, card status 0xb00
[ 8.991127] mmcblk0: error -84 transferring data, sector 1791057, nr 128, cmd response 0x900, card status 0xb00
[ 12.301774] libphy: PHY 4a101000.mdio:01 not found
[ 12.306867] net eth0: phy 4a101000.mdio:01 not found on slave 1
systemd-fsck[83]: Angstrom: clean, 50589/112672 files, 286996/449820 blocks

.—O---.

.-. o o

-----.-----.-----.| | .----…-----.-----.
__ | —’| ‘–.| .-’| | |

— || --’| | | ’ | | | |
‘—’---’–’--’–. |-----’’----’’–’ ‘-----’-’-’-’
-’ |
‘—’

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

beaglebone login: [ 79.749638] mmcblk0: error -84 transferring data, sector 3014921, nr 128, cmd response 0x900, card status 0xb00
[ 180.196825] INFO: task mmcqd/1:72 blocked for more than 60 seconds.
[ 180.203416] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[ 180.211635] Kernel panic - not syncing: hung_task: blocked tasks
[ 180.217928] [] (unwind_backtrace+0x1/0x8c) from [] (panic+0x55/0x14c)
[ 180.226463] [] (panic+0x55/0x14c) from [] (watchdog+0x153/0x1a0)
[ 180.234538] [] (watchdog+0x153/0x1a0) from [] (kthread+0x61/0x72)
[ 180.242713] [] (kthread+0x61/0x72) from [] (ret_from_fork+0x11/0x34)
[ 180.251148] drm_kms_helper: panic occurred, switching back to text console
[ 180.258317] [drm:drm_crtc_helper_set_config],
[ 180.262952] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:8] #connectors=1 (x y) (0 0)
[ 180.272143] [drm:drm_crtc_helper_set_config], [CONNECTOR:5:LVDS-1] to [CRTC:3]
[ 180.293629] [drm:drm_framebuffer_reference], FB ID: 8
[ 180.309886] [drm:drm_framebuffer_reference], FB ID: 8

I checked the support site (http://www.elinux.org/BeagleBone_Black_Capes) and it indeed says your LCD7 Cape Rev A3 is fully supported with the 6.20 image. I wish I could help, but I’m not really sure.

I had a lot of MMC errors while flashing.
I thougt it might be related to long unterminated eMMC (MMC1) lines so I did cut the 10 pins on the LCD7 related to eMMC.
After that I still had problems which were solved by using another power supply.
So first double check your power supply.

The answer is yes Beaglebone Black Rev A5B and LCD7 Cape Rev A3 works with Flasher Image 2013-06-20

/Benny

The power supply was 2A, but I tried hooking it up to a benchtop power supply (3A).

Still exhibits the same problems and it’s only using 0.85 Amps at it’s maximum, voltage is steady at 5V +/- 0.001V

LCD7 (Rev A3) works fine for me with BBB image 2013-06-20.

I also see that is draws less than 1A however that is reading it with a moving coil meter, it could well be drawing spikes significantly higher than that.

Are you just plugging it in and it just works and you’re running from eMMC?
Are you doing anything to the image, configuring anything?
Which revision of Beaglebone Black is it?
Are you using the image here: http://beagleboard.org/latest-images (Beagle Bone Black 2013-06-20)?

I’ve outruled the PSU / Spikes, hooked it up to 6A @ 5V, and it still crashes. I could have 2 faulty LCD displays, although
it seems unlikely.

Thanks

I still don’t like the long unterminated lines from the eMMC so if you don’t plan to use any cape on the LCD7 using those signals you could cut the pins as I did.
During flashing of the eMMC you could also try to log on via ssh and run dmesg to see if you get MMC errors at that time.

/Benny

Works for me when booting from either eMMC or SD card, both with 2013-06-20 image on them.

Not doing anything to the image - just as it comes downloaded.
BBB revision A5A and A5B both work for me.

I see exactly the same behavior as Jetty described with my BBB rev A5A and LCD7 rev A3.
I tried 2A and 4A 5V power supplies. Always get intermittent crash (kernel panic).
Sometimes it gets to touchscreen calibration screen and then crashes, in other times it does not even get to the calibration process.

Though, I never had a problem with debian image (which I had to compile myself), and touch screen works like a charm.

Which means: it’s hardly the layout (long traces mentioned by Benny Simonsen). It’s the software problem (in the latest BBB image, 2013-06-20)

genpix, have you checked dmesg to see if anything shows up there ?

And yeah, I’ve noticed that Debian is really solid myself.

What do you mean under “from either eMMC or SD card”?
As I understand, when you boot from SD card you boot into minimal system - just into ASCII terminal (and background process copies the “extended” image into eMMC).
When you boot from eMMC, you load the “extended” system - with GUI terminal and all bells and whistles. And if your touch screen calibration failed (kernel panic), you are doomed - after reboot from eMMC your touch screen is completely OFF.
You probably can delete calibration file and system will call for or new calibration procedure upon reboot, but I did not go that far (I never had a panic-free boot).

So, do you mean you can boot either into GUI (from eMMC), or into ASCII console (from SD)? Booting from SD probably screws your eMMC image (cause it starts to overwrite the current image).
Thus, you have to wait 45-50 minutes each time you boot from SD (to allow the eMMC writing procedure to complete), other wise you would not be able to boot from eMMC anymore.

genpix, have you checked dmesg to see if anything shows up there ?

And yeah, I’ve noticed that Debian is really solid myself.

Yeah, I see a lot of mmcblk0 errors (sector #'s with the error are all different after each reboot).

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.07.10 18:58:23 =~=~=~=~=~=~=~=~=~=~=~=

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img

U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)

I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: not set. Validating first E-fuse MAC
Phy not found
PHY reset timed out
cpsw, usb_ether
Hit any key to stop autoboot: 1 0
gpio: pin 53 (gpio 53) value is 1
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
mmc0(part 0) is current device
mmc_send_cmd : timeout: No status update
Card did not respond to voltage select!
No micro SD card found, setting mmcdev to 1
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
reading uEnv.txt
26 bytes read in 2 ms (12.7 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc …
gpio: pin 55 (gpio 55) value is 1
4270840 bytes read in 746 ms (5.5 MiB/s)
gpio: pin 56 (gpio 56) value is 1
24129 bytes read in 51 ms (461.9 KiB/s)
Booting from mmc …

Booting kernel from Legacy Image at 80007fc0 …

Image Name: Angstrom/3.8.13/beaglebone
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4270776 Bytes = 4.1 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum … OK

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
XIP Kernel Image … OK
OK
Using Device Tree in place at 80f80000, end 80f88e40

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.194190] omap2_mbox_probe: platform not supported
[ 0.204737] tps65217-bl tps65217-bl: no platform data provided
[ 0.304784] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.341892] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.379004] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.404710] bone-capemgr bone_capemgr.8: slot #5: BB-BONELT-HDMI conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.414305] bone-capemgr bone_capemgr.8: slot #5: Failed verification
[ 0.421078] bone-capemgr bone_capemgr.8: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 0.433560] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.443293] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.450073] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.471908] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.535689] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.547422] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.554759] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.714922] tilcdc 4830e000.fb: timeout waiting for framedone
[ 10.276986] mmcblk0: error -84 transferring data, sector 414513, nr 96, cmd response 0x900, card status 0xb00
[ 10.803959] mmcblk0: error -84 transferring data, sector 1787081, nr 88, cmd response 0x900, card status 0xb00
[ 13.438402] mmcblk0: error -84 transferring data, sector 1717969, nr 112, cmd response 0x900, card status 0xd00
[ 13.449021] end_request: I/O error, dev mmcblk0, sector 1717969
[ 13.455219] end_request: I/O error, dev mmcblk0, sector 1717977
[ 13.461402] end_request: I/O error, dev mmcblk0, sector 1717985
[ 13.467589] end_request: I/O error, dev mmcblk0, sector 1717993
[ 13.473786] end_request: I/O error, dev mmcblk0, sector 1718001
[ 13.479974] end_request: I/O error, dev mmcblk0, sector 1718009
[ 13.486160] end_request: I/O error, dev mmcblk0, sector 1718017
[ 13.492342] end_request: I/O error, dev mmcblk0, sector 1718025
[ 13.498523] end_request: I/O error, dev mmcblk0, sector 1718033
[ 13.504705] end_request: I/O error, dev mmcblk0, sector 1718041
[ 13.511263] Aborting journal on device mmcblk0p2-8.
[ 13.532973] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.542585] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.552110] EXT4-fs error (device mmcblk0p2) in ext4_reserve_inode_write:4688: Journal has aborted
[ 13.561890] mmcblk0: error -84 transferring data, sector 1702505, nr 128, cmd response 0x900, card status 0xb00
[ 13.574712] journal commit I/O error
[ 13.750598] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.759985] EXT4-fs (mmcblk0p2): Remounting filesystem read-only
[ 13.815771] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.834230] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.857642] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.873239] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.897675] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.925212] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.956657] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 13.981615] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.007385] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.028575] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.038172] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.047677] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
[ 14.058562] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:349: Detected aborted journal
systemd-fsck[84]: Angstrom: clean, 50595/112672 files, 286738/449820 blocks
[ 16.379907] mmcblk0: error -84 transferring data, sector 1404313, nr 112, cmd response 0x900, card status 0xb00
[ 18.885538] mmcblk0: error -84 transferring data, sector 1689865, nr 128, cmd response 0x900, card status 0xb00
[ 19.116511] libphy: PHY 4a101000.mdio:00 not found
[ 19.121568] net eth0: phy 4a101000.mdio:00 not found on slave 0
[ 19.127769] libphy: PHY 4a101000.mdio:01 not found
[ 19.132783] net eth0: phy 4a101000.mdio:01 not found on slave 1

.—O---.

.-. o o

-----.-----.-----.| | .----…-----.-----.
__ | —’| ‘–.| .-’| | |

— || --’| | | ’ | | | |
‘—’---’–’--’–. |-----’’----’’–’ ‘-----’-’-’-’
-’ |
‘—’

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

beaglebone login:

second boot attempt was even wors (it did not even get to login prompt):

Uncompressing Linux… done, booting the kernel.
[ 0.194189] omap2_mbox_probe: platform not supported
[ 0.204760] tps65217-bl tps65217-bl: no platform data provided
[ 0.304798] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.341901] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.379011] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.404727] bone-capemgr bone_capemgr.8: slot #5: BB-BONELT-HDMI conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.414326] bone-capemgr bone_capemgr.8: slot #5: Failed verification
[ 0.421102] bone-capemgr bone_capemgr.8: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 0.433610] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.443346] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.450127] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.471886] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.535710] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.547451] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.554765] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.714932] tilcdc 4830e000.fb: timeout waiting for framedone
[ 3.321872] mmcblk0: error -84 transferring data, sector 161393, nr 32, cmd response 0x900, card status 0xd00
[ 3.332254] end_request: I/O error, dev mmcblk0, sector 161393
[ 3.338353] Buffer I/O error on device mmcblk0p2, logical block 2101
[ 3.345005] end_request: I/O error, dev mmcblk0, sector 161401
[ 3.351100] Buffer I/O error on device mmcblk0p2, logical block 2102
[ 3.357743] end_request: I/O error, dev mmcblk0, sector 161409
[ 3.363837] Buffer I/O error on device mmcblk0p2, logical block 2103
[ 3.370488] end_request: I/O error, dev mmcblk0, sector 161417
[ 3.376597] Buffer I/O error on device mmcblk0p2, logical block 2104
[ 5.508731] EXT4-fs (mmcblk0p2): error loading journal
[ 5.519026] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
[ 5.527867] [] (unwind_backtrace+0x1/0x8c) from [] (panic+0x55/0x14c)
[ 5.536407] [] (panic+0x55/0x14c) from [] (mount_block_root+0x13b/0x178)
[ 5.545212] [] (mount_block_root+0x13b/0x178) from [] (mount_root+0x8b/0xa8)
[ 5.554370] [] (mount_root+0x8b/0xa8) from [] (prepare_namespace+0xc5/0x118)
[ 5.563537] [] (prepare_namespace+0xc5/0x118) from [] (kernel_init+0x7/0x90)
[ 5.572708] [] (kernel_init+0x7/0x90) from [] (ret_from_fork+0x11/0x34)
[ 5.581417] drm_kms_helper: panic occurred, switching back to text console
[ 5.588580] [drm:drm_crtc_helper_set_config],
[ 5.593209] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:8] #connectors=1 (x y) (0 0)
[ 5.601576] [drm:drm_crtc_helper_set_config], [CONNECTOR:5:LVDS-1] to [CRTC:3]

That does not look good.

here is a third reboot, when it finally went into GUI interface (even with few mmcblk0 errors present during boot process).
I was able to move the cursor (with a stylus), but GUI did not respond to any clicks.
And finally, after about a minute kernel panicked:

Uncompressing Linux… done, booting the kernel.
[ 0.194084] omap2_mbox_probe: platform not supported
[ 0.204650] tps65217-bl tps65217-bl: no platform data provided
[ 0.304690] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.341793] bone-capemgr bone_capemgr.8: slot #2: No cape found
[ 0.378903] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.404616] bone-capemgr bone_capemgr.8: slot #5: BB-BONELT-HDMI conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.414212] bone-capemgr bone_capemgr.8: slot #5: Failed verification
[ 0.420985] bone-capemgr bone_capemgr.8: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 0.433475] bone-capemgr bone_capemgr.8: slot #6: BB-BONELT-HDMIN conflict P8.45 (#0:BB-BONE-LCD7-01)
[ 0.443208] bone-capemgr bone_capemgr.8: slot #6: Failed verification
[ 0.449986] bone-capemgr bone_capemgr.8: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.471786] omap_hsmmc mmc.4: of_parse_phandle_with_args of ‘reset’ failed
[ 0.535593] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.7
[ 0.547332] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.7) status -22
[ 0.554661] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
[ 0.714824] tilcdc 4830e000.fb: timeout waiting for framedone
[ 6.924501] mmcblk0: error -84 transferring data, sector 1717065, nr 24, cmd response 0x900, card status 0xb00
[ 10.048760] mmcblk0: error -84 transferring data, sector 1638337, nr 128, cmd response 0x900, card status 0xb00
[ 12.135896] mmcblk0: error -84 transferring data, sector 1961185, nr 128, cmd response 0x900, card status 0x0
[ 18.949984] libphy: PHY 4a101000.mdio:01 not found
[ 18.955051] net eth0: phy 4a101000.mdio:01 not found on slave 1
systemd-fsck[83]: Angstrom: clean, 50606/112672 files, 288060/449820 blocks

.—O---.

.-. o o

-----.-----.-----.| | .----…-----.-----.
__ | —’| ‘–.| .-’| | |

— || --’| | | ’ | | | |
‘—’---’–’--’–. |-----’’----’’–’ ‘-----’-’-’-’
-’ |
‘—’

The Angstrom Distribution beaglebone ttyO0

Angstrom v2012.12 - Kernel 3.8.13

beaglebone login: [ 48.759079] mmcblk0: error -84 transferring data, sector 2425929, nr 80, cmd response 0x900, card status 0xb00
[ 51.215734] mmcblk0: error -84 transferring data, sector 3004049, nr 128, cmd response 0x900, card status 0xb00
[ 53.103255] mmcblk0: error -84 transferring data, sector 2999233, nr 128, cmd response 0x900, card status 0xb00
[ 55.150347] mmcblk0: error -84 transferring data, sector 2958665, nr 128, cmd response 0x900, card status 0xb00
[ 116.976933] mmcblk0: error -84 transferring data, sector 2990289, nr 128, cmd response 0x900, card status 0xb00
[ 117.497710] mmcblk0: error -84 transferring data, sector 2975937, nr 128, cmd response 0x900, card status 0xb00
[ 117.560728] mmcblk0: error -84 transferring data, sector 2976023, nr 42, cmd response 0x900, card status 0x0
[ 117.571035] end_request: I/O error, dev mmcblk0, sector 2976023
[ 125.977650] mmcblk0: error -84 transferring data, sector 3014921, nr 128, cmd response 0x900, card status 0x0
root

root
[ 240.197280] INFO: task mmcqd/1:72 blocked for more than 60 seconds.
[ 240.203922] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[ 240.212155] Kernel panic - not syncing: hung_task: blocked tasks
[ 240.218444] [] (unwind_backtrace+0x1/0x8c) from [] (panic+0x55/0x14c)
[ 240.226977] [] (panic+0x55/0x14c) from [] (watchdog+0x153/0x1a0)
[ 240.235068] [] (watchdog+0x153/0x1a0) from [] (kthread+0x61/0x72)
[ 240.243242] [] (kthread+0x61/0x72) from [] (ret_from_fork+0x11/0x34)
[ 240.251678] drm_kms_helper: panic occurred, switching back to text console
[ 240.258840] [drm:drm_crtc_helper_set_config],
[ 240.263470] [drm:drm_crtc_helper_set_config], [CRTC:3] [FB:8] #connectors=1 (x y) (0 0)
[ 240.271934] [drm:drm_crtc_helper_set_config], [CONNECTOR:5:LVDS-1] to [CRTC:3]
[ 240.289707] [drm:drm_framebuffer_reference], FB ID: 8
[ 240.305962] [drm:drm_framebuffer_reference], FB ID: 8

I get similar problems, BBB A5B, and LCD7 A3.

With the LCD7, at best I can get it up, select a menu, but I can do nothing after that except move the mouse.

If I plug it into a regular monitor without the LCD7, it works fine. It has been running a perl script to generate a million random numbers between 0 and a million, add them up and show the sum, for the last 21 hours, and it still talks to me. I can fire up new windows etc…

The LCD7 doesn’t seem as robust as one might like.

Hmm does that LCD use some same pins that the eMMC uses ?

Ah and after re-examining the messages there you have a definite pin conflict with HDMI and that LCD screen it seems.

Once in about 10 tries I have just gotten it to come up and talk. One thing I notice is that the heartbeat is always around 0.9 seconds when on a regular monitor, and it runs faster on the LCD7. Every other time I counted 10 beats it was about 5.6 seconds on the LCD7 until it stopped, and this time it is more like 6.6 seconds for 10 beats.

It is running at the moment running a little perl script adding random numbers.

This time I skipped the touchscreen calibration, and just used the mouse. Even when I calibrate the touchscreen, I can’t get the cursor close enough to the edge to pick a menu item from the top bar, the gain is too low, whether I hit the crosses directly, inside or outside them.

Bruce

Yes, but because of the LCD / HDMI pin conflict capemgr won’t load HDMI so there should be no problems there (HDMI is all input).
eMMC signals is not used by the LCD7, but the lines are connected between the header where you connect the beagle and the cape expansion header.

As I wrote I had a problem with the powersupply. I did use a homebuild cable where I could connect my labtop USB to the +5V in on the LCD7. The voltage was just a little to low (did work fine without the LCD7).
The result were a lot of eMMC errors and random crash just like described by genpix.
Before solving the PSU problem I did cut the pins used by eMMC so I don’t know if my issue were only because of PSU problems or a combination of PSU and the unterminated eMMC lines.
Anyway I can now use the 2013-06-20 image without eMMC errors.

Regarding powersupply. Don’t trust the 5V / 2A label on a cheap USB hub type PSU. They might only give like 4.5V and the voltage might drop during load change (e.g when backlight turns on).

/Benny