DVI-D cape foot prints in Dmesg ..Beaglebone

Hi,

When I have a DVI cape connected to beagle bone, I get the following logs in dmesg

[ 1.057617] BeagleBone cape EEPROM: found eeprom at address 0x54
[ 1.063964] BeagleBone cape: Beagleboardtoys. BeagleBone DVI-D CAPE…
., revision 00A0
[ 1.078460] BeagleBone cape: initializing DVI cape
[ 1.083892] da8xx_lcdc.0: alias fck already exists
[ 1.089263] da8xx_lcdc da8xx_lcdc.0: GLCD: Found 1024x768@60 panel
[ 1.119567] Console: switching to colour frame buffer device 128x48
[ 1.144012] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.210937] BeagleBone cape EEPROM: could not read eeprom at address 0x55
[ 1.218261] at24 3-0056: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.280944] BeagleBone cape EEPROM: could not read eeprom at address 0x56
[ 1.288269] at24 3-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.350952] BeagleBone cape EEPROM: could not read eeprom at address 0x57

EEPROM : could not read error …is is t a problem ?.

Thanks,
Aravind

How many capes do you have connected to the beaglebone? If you just
one, those other 3 read errors are perfectly fine (aka it didn't find
3 more capes installed.)..

Regards,

HI Robert,

Thanks.

I just got one cape. With a Pico connected to the cape …this is what I get …

[ 1.064846] BeagleBone cape EEPROM: found eeprom at address 0x54
[ 1.071172] BeagleBone cape: , revision
[ 1.075370] BeagleBone cape partnumber: @
[ 1.079643] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.112403] BeagleBone Cape EEPROM: wrong header 0xffffffff, expected 0xee335
5aa
[ 1.120169] Could not detect BeagleBone cape properly
[ 1.125499] at24 3-0056: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.158271] BeagleBone Cape EEPROM: wrong header 0xffffffff, expected 0xee335
5aa
[ 1.166018] Could not detect BeagleBone cape properly
[ 1.171367] at24 3-0057: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[ 1.204140] BeagleBone Cape EEPROM: wrong header 0xffffffff, expected 0xee335
5aa
[ 1.211904] Could not detect BeagleBone cape properly

It couldn’t detect the beagle cape properly…now what should I do ?.
it is Ti’s pico.

HI Robert,

Thanks.

I just got one cape. With a Pico connected to the cape ...this is what I get
...

[ 1.064846] BeagleBone cape EEPROM: found eeprom at address 0x54
[ 1.071172] BeagleBone cape: , revision
[ 1.075370] BeagleBone cape partnumber: @
[ 1.079643] at24 3-0055: 32768 byte 24c256 EEPROM, writable, 64
bytes/write
[ 1.112403] BeagleBone Cape EEPROM: wrong header 0xffffffff, expected
0xee335
5aa

So... why did that change from your previous message? (where it
clearly found the dvi-d cape)

[ 1.057617] BeagleBone cape EEPROM: found eeprom at address 0x54
[ 1.063964] BeagleBone cape: Beagleboardtoys. BeagleBone DVI-D CAPE..........
., revision 00A0
[ 1.078460] BeagleBone cape: initializing DVI cape
[ 1.083892] da8xx_lcdc.0: alias fck already exists
[ 1.089263] da8xx_lcdc da8xx_lcdc.0: GLCD: Found 1024x768@60 panel
[ 1.119567] Console: switching to colour frame buffer device 128x48

It couldn't detect the beagle cape properly...now what should I do ?.
it is Ti's pico.

Why are you expecting that to work? The dvi-d cape board is currently
hardcoded for 1024x768 and the TI pico is limited to 640x480... So
unless you hack up the da8xx frame buffer driver, it's not going to
work..

Regards,

I suspect the pico is plugged in and the EDID eeprom is interfering with the cape EEPROM. I see the same with one of my monitors :frowning:

EDID should be at address 0x 50, unless it is flawed and shows up at all addresses. That was the reason for starting at 0x54 was to miss the EDID EEPROM.

Gerald