the new Angstrom package on Beagle

Hi,

I am working on the REV B board, I made the hardware replacement the
LED D3 to a capacitor.
I tried to run Angstrom with the new package provided Angstrom-
Beagleboard-demo-image-glibc-ipk-2008.1-test-20080628-beagleboard-
testlab/

And I got 2 surprises.

The first is good, When I plug, after the boot and the initialization
of Angstrom, a USB mouse to the OTG port combined with a USB Y cable,
The mouse is recognized and and event is created in /dev/input.

The Bad news for me is that the DVI screen automatically switch off
after printing 'BeagleBoard.org' and I think It comes from the error
i2c_omap : concroller timed out.

Finally, I can't enter inside the distribution. Previously my problem
was that the OTG USB mouse wasn't recognize and the keyboard on the
screen was waiting for it. And now this is the contrary I have the
mouse without an output to write on !!

There are the Bootargs

Texas Instruments X-Loader 1.41
Starting on with MMC
Reading boot sector

717948 Bytes Read from MMC
Starting OS Bootloader from MMC...

U-Boot 1.1.4 (Apr 2 2008 - 13:42:13)

OMAP3430-GP rev 2, CPU-OPP2 L3-133MHz
TI 3430Beagle 2.0 Version + mDDR (Boot ONND)
DRAM: 128 MB
Flash: 0 kB
NAND:256 MiB
In: serial
Out: serial
Err: serial
Audio Tone on Speakers ... complete
Hit any key to stop autoboot: 0

2176788 bytes read
## Booting image at 80300000 ...
   Image Name: Angstrom/2.6.25+2.6.26-rc8+r31+g
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 2176724 Bytes = 2.1 MB
   Load Address: 80008000
   Entry Point: 80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing
Linux............................................................................................................................................
done, booti.
Linux version 2.6.26-rc8-omap1 (koen@dominion) (gcc version 4.2.1) #1
PREEMPT Sat Jun 28 13:58:50 CEST 2008
CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f
Machine: OMAP3 Beagle Board
Memory policy: ECC disabled, Data cache writeback
OMAP3430 ES2.2
SRAM: Mapped pa 0x40200000 to va 0xd7000000 size: 0x100000
CPU0: D VIPT write-through cache
CPU0: cache: 768 bytes, associativity 1, 8 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on. Total pages:
32512
Kernel command line: console=ttyS2,115200n8 noinitrd root=/dev/
mmcblk0p2 rw rootfstype=ext3 rootdelay=3
Clocking rate (Crystal/DPLL/ARM core): 26.0/332/381 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP34xx GPIO hardware version 2.5
PID hash table entries: 512 (order: 9, 2048 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB 0MB = 128MB total
Memory: 125312KB available (4032K code, 368K data, 144K init)
SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1,
Nodes=1
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 324 bytes
NET: Registered protocol family 16
Found NAND on CS0
Registering NAND on CS0
Warning: L2 cache not enabled. Check your bootloader. L2 off results
in performance loss
OMAP DMA hardware revision 4.0
USB: No board-specific platform config found
i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1]
TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1]
Initialized TWL4030 USB module
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
i2c_omap i2c_omap.1: Transmit overflow
musb_hdrc: USB OTG mode controller at c8800000 using DMA, IRQ 92
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
NET: Registered protocol family 1
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 244
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
omapfb: configured for panel omap3beagle
omapfb: DISPC version 3.0 initialized
Console: switching to colour frame buffer device 128x48
omapfb: Framebuffer initialized. Total vram 1572864 planes 1
omapfb: Pixclock 48000 kHz hfreq 44.7 kHz vfreq 57.7 Hz
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing
enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.0: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.0: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
i2c /dev entries driver
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
i2c_omap i2c_omap.2: controller timed out
TWL4030 GPIO Demux: IRQ Range 384 to 402, Initialization Success
input: triton2-pwrbutton as /class/input/input0
triton2 power button driver initialized
Driver 'sd' needs updating - please use bus_type methods
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB
1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand":
0x00000000-0x00080000 : "X-Loader"
0x00080000-0x00260000 : "U-Boot"
0x00260000-0x00280000 : "U-Boot Env"
0x00280000-0x00680000 : "Kernel"
0x00680000-0x10000000 : "File System"
TI TSC2102 driver initializing
usbmon: debugfs is not available
Clock usbhost_48m_fck didn't enable in 100000 tries
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ether gadget: using random self ethernet address
ether gadget: using random host ethernet address
usb0: Ethernet Gadget, version: May Day 2005
usb0: using musb_hdrc, OUT ep1out IN ep1in STATUS ep2in
usb0: MAC be:39:35:47:9f:43
usb0: HOST MAC 16:f4:5a:d6:52:34
usb0: RNDIS ready
musb_hdrc musb_hdrc.0: MUSB HDRC host driver
musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 2
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mice: PS/2 mouse device common for all mice
twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0
twl4030_rtc twl4030_rtc: Power up reset detected.
twl4030_rtc twl4030_rtc: Enabling TWL4030-RTC.
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
Bluetooth: Broadcom Blutonium firmware driver ver 1.1
usbcore: registered new interface driver bcm203x
Bluetooth: Digianswer Bluetooth USB driver ver 0.9
usbcore: registered new interface driver bpa10x
Bluetooth: Generic Bluetooth SDIO driver ver 0.1
cpuidle: using governor ladder
cpuidle: using governor menu
Registered led device: beagleboard::led0
Registered led device: beagleboard::led1
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.16.
usbcore: registered new interface driver snd-usb-audio
ASoC version 0.13.2
OMAP3 Beagle SoC init
TWL4030 Audio Codec probe
TWL4030 Audio Codec init
TWL 4030 Register dump for Audio Module
Register[0x01]=0x93
Register[0x02]=0xc3
Register[0x03]=0x00
Register[0x04]=0x00
Register[0x05]=0x34
Register[0x06]=0x14
Register[0x07]=0x0a
Register[0x08]=0x00
Register[0x09]=0x00
Register[0x0a]=0x0c
Register[0x0b]=0x0c
Register[0x0c]=0x00
Register[0x0d]=0x00
Register[0x0e]=0x01
Register[0x0f]=0x00
Register[0x10]=0x00
Register[0x11]=0x00
Register[0x12]=0x6c
Register[0x13]=0x6c
Register[0x14]=0x00
Register[0x15]=0x00
Register[0x16]=0x00
Register[0x17]=0x0c
Register[0x18]=0x00
Register[0x19]=0x00
Register[0x1a]=0x00
Register[0x1b]=0x4b
Register[0x1c]=0x4b
Register[0x1d]=0x00
Register[0x1e]=0x00
Register[0x1f]=0x00
Register[0x20]=0x00
Register[0x21]=0x00
Register[0x22]=0x24
Register[0x23]=0x0a
Register[0x24]=0x00
Register[0x25]=0x00
Register[0x26]=0x00
Register[0x27]=0x00
Register[0x28]=0x00
Register[0x29]=0x00
Register[0x2a]=0x00
Register[0x2b]=0x00
Register[0x2c]=0x00
Register[0x2d]=0x00
Register[0x2e]=0x00
Register[0x2f]=0x01
Register[0x30]=0x00
Register[0x31]=0x00
Register[0x32]=0x00
Register[0x33]=0x00
Register[0x34]=0x00
Register[0x35]=0x00
Register[0x36]=0x00
Register[0x37]=0x00
Register[0x38]=0x00
Register[0x39]=0x00
Register[0x3a]=0x16
Register[0x3b]=0x00
Register[0x3c]=0x00
Register[0x3d]=0x00
Register[0x3e]=0x02
Register[0x3f]=0x00
Register[0x40]=0x00
Register[0x41]=0x00
Register[0x42]=0x00
Register[0x43]=0x00
Register[0x44]=0x00
mmc0: host does not support reading read-only switch. assuming write-
enable.
mmc0: new SD card at address e624
Register[0x45]=0x00
mmcblk0: mmc0:e624 SU02G 1985024KiB
mmcblk0:<6>Register[0x46]=0x00
p1 p2
Register[0x47]=0x00
Register[0x48]=0x00
Register[0x49]=0x00
asoc: twl4030 <-> omap-mcbsp-dai mapping ok
OMAP3 Beagle TWL4030 SoC init
TWL4030 Audio Codec probe exit
ALSA device list:
  #0: omap3beagle (twl4030)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
ieee80211: 802.11 data/management/control stack, git-1.1.13

royerfa@yahoo.fr wrote:

Hi,

I am working on the REV B board, I made the hardware replacement the
LED D3 to a capacitor.
I tried to run Angstrom with the new package provided Angstrom-
Beagleboard-demo-image-glibc-ipk-2008.1-test-20080628-beagleboard-
testlab/

And I got 2 surprises.

The first is good, When I plug, after the boot and the initialization
of Angstrom, a USB mouse to the OTG port combined with a USB Y cable,
The mouse is recognized and and event is created in /dev/input.

The Bad news for me is that the DVI screen automatically switch off
after printing 'BeagleBoard.org' and I think It comes from the error
i2c_omap : concroller timed out.

Finally, I can't enter inside the distribution. Previously my problem
was that the OTG USB mouse wasn't recognize and the keyboard on the
screen was waiting for it. And now this is the contrary I have the
mouse without an output to write on !!

Unfortunately I can't help you with DVI issue. Maybe Koen knows how
the screen behaves for him.

But I don't think that your screen issue is related to

i2c_omap i2c_omap.2: controller timed out

As discussed in

http://groups.google.com/group/beagleboard/browse_thread/thread/ff79a14907cc8805

thread on this list, this is because nothing is connected to I2C2 at
beagle's expansion connector. And most probably this isn't related to DVI.

To avoid I2C2 error messages, you can do several workarounds:

- Connect something to I2C2 at expansion connector (with additional
pull ups)

- Add some additional external pull ups to unused I2C2 lines

- Disable usage of I2C2 in board-omap3beagle.c
(omap_register_i2c_bus(2, 400, NULL, 0);). I will post a patch for
this hopefully soon.

Dirk