Beagle-XM P8 memory issues ?

Hi !

My Beagle-XM P8 only boots with mem=256M (2.6.36-rc7-d2) ? Known issue ? Solution ?

Best,
Jan-Simon

and what kernel is that?

Build with/from :

https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.36-devel

Best,
Jan-Simon

Yeap, that's about the only workaround on those early P8 boards that
seems to work. (known bad memory)

Where'd you get your's, hopefully not ebay? The only ones for sale
should be the production A2's..

Regards,

Hehe, P8 is an early pre production one. I also got one and can only
boot with 256MB, this is expected.

Cheers,

>>> > Hi !

>>> > My Beagle-XM P8 only boots with mem=256M (2.6.36-rc7-d2) ? Known issue ? Solution ?

>>> and what kernel is that?

>> Build with/from :

>>https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.36-devel

> Yeap, that's about the only workaround on those early P8 boards that
> seems to work. (known bad memory)

> Where'd you get your's, hopefully not ebay? The only ones for sale
> should be the production A2's..

Hehe, P8 is an early pre production one. I also got one and can only
boot with 256MB, this is expected.

There were a handful of unscreened P8s that went out, but P8s in
general should work fine with 256MB of RAM once the right MLO/u-boot/
kernel are used (really just MLO/x-loader). Try out the images on
http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext
and see if you have problems with using the full 512MB of memory. I
suspect that you are just using an old MLO.

> >>> > Hi !

> >>> > My Beagle-XM P8 only boots with mem=256M (2.6.36-rc7-d2) ? Known issue ? Solution ?

> >>> and what kernel is that?

> >> Build with/from :

> >>https://code.launchpad.net/~beagleboard-kernel/+junk/2.6.36-devel

> > Yeap, that's about the only workaround on those early P8 boards that
> > seems to work. (known bad memory)

> > Where'd you get your's, hopefully not ebay? The only ones for sale
> > should be the production A2's..

> Hehe, P8 is an early pre production one. I also got one and can only
> boot with 256MB, this is expected.

There were a handful of unscreened P8s that went out, but P8s in
general should work fine with 256MB of RAM once the right MLO/u-boot/

Typo here.......................^^^^

I meant the full 512MB of RAM. The only unscreened units went out
prior to ESC Chicago at the first of June. There is only a chance
your RAM was unscreened if you got it before June. You can run
'testmem' using the diagnostic image below to confirm the RAM is
working fine.

Hello to all,

I'm facing a problem related to my USB hub. whenever i'm disconnecting
all the devices from the hub, it gives a mesg
hub 1-0:1.0: unable to enumerate USB device on port 2
and stops responding at all. I'm using BB revc3. Hub is self powered.
To make it work i have to restart BB then only i'm able to work.
It detects the device if i start my BB with the device connected to it.
But if dont attch the device and after booting i try to connect usb it
gives a msg that "unable to enumerate device"

The bootdmesg related to usb are as follows:
usbcore: registered new interface driver asix
[ 1.459381] usbcore: registered new interface driver cdc_ether
[ 1.466674] usbcore: registered new interface driver net1080
[ 1.473480] usbcore: registered new interface driver cdc_subset
[ 1.480590] usbcore: registered new interface driver zaurus
[ 1.489532] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
Driver
[ 3.507904] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 3.519866] ehci-omap ehci-omap.0: new USB bus registered, assigned
bus number 1
[ 3.528686] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 3.547088] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 3.554931] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 3.562133] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 3.569854] usb usb1: Product: OMAP-EHCI Host Controller
[ 3.575531] usb usb1: Manufacturer: Linux 2.6.36-rc7-08946-g99cf630
ehci_hcd
[ 3.583038] usb usb1: SerialNumber: ehci-omap.0
[ 3.593872] hub 1-0:1.0: USB hub found
[ 3.598114] hub 1-0:1.0: 3 ports detected
[ 3.633728] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 3.643188] usbcore: registered new interface driver cdc_acm
[ 3.649322] cdc_acm: v0.26:USB Abstract Control Model driver for USB
modems and ISDN adapters
[ 3.659118] usbcore: registered new interface driver cdc_wdm
[ 3.665283] Initializing USB Mass Storage driver...
[ 3.671264] usbcore: registered new interface driver usb-storage
[ 3.677734] USB Mass Storage support registered.
[ 3.684356] usbcore: registered new interface driver libusual
[ 3.692169] usbcore: registered new interface driver usbserial
[ 3.699829] USB Serial support registered for generic
[ 3.707122] usbcore: registered new interface driver
usbserial_generic
[ 3.714202] usbserial: USB Serial Driver core
[ 3.719573] USB Serial support registered for DeLorme Earthmate USB
[ 3.727050] USB Serial support registered for HID->COM RS232 Adapter
[ 3.734680] USB Serial support registered for Nokia CA-42 V2 Adapter
[ 3.742309] usbcore: registered new interface driver cypress
[ 3.748291] cypress_m8: v1.10:Cypress USB to Serial Driver
[ 3.754852] USB Serial support registered for FTDI USB Serial Device
[ 3.762573] usbcore: registered new interface driver ftdi_sio
[ 3.768768] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[ 3.775909] USB Serial support registered for qcaux
[ 3.781921] usbcore: registered new interface driver qcaux
[ 3.788391] USB Serial support registered for Qualcomm USB modem
[ 3.795654] usbcore: registered new interface driver qcserial
[ 3.802612] usbcore: registered new interface driver usbtest
..........
[ 4.155212] usb 1-2: New USB device found, idVendor=0409,
idProduct=005a
[ 4.162475] usb 1-2: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 4.176788] hub 1-2:1.0: USB hub found
[ 4.182250] hub 1-2:1.0: 4 ports detected
[ 4.477325] usb 1-2.4: new full speed USB device using ehci-omap and
address 3
[ 4.586456] mmc0: new high speed SD card at address 1234
[ 4.595397] mmcblk0: mmc0:1234 SA02G 1.83 GiB
[ 4.607513] mmcblk0: p1 p2
[ 4.618377] usb 1-2.4: New USB device found, idVendor=0403,
idProduct=6010
[ 4.625915] usb 1-2.4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4.633789] usb 1-2.4: Product: Crossbow MIB520CA
[ 4.638824] usb 1-2.4: Manufacturer: Crossbow
[ 4.643493] usb 1-2.4: SerialNumber: XBQ9JO76
[ 4.655517] ftdi_sio 1-2.4:1.0: FTDI USB Serial Device converter
detected
[ 4.664672] usb 1-2.4: Detected FT2232C
[ 4.668762] usb 1-2.4: Number of endpoints 2
[ 4.673400] usb 1-2.4: Endpoint 1 MaxPacketSize 64
[ 4.678466] usb 1-2.4: Endpoint 2 MaxPacketSize 64
[ 4.683624] usb 1-2.4: Setting MaxPacketSize 64
[ 4.690582] usb 1-2.4: FTDI USB Serial Device converter now attached
to ttyUSB0
[ 4.704071] ftdi_sio 1-2.4:1.1: FTDI USB Serial Device converter
detected
[ 4.712799] usb 1-2.4: Detected FT2232C
[ 4.716888] usb 1-2.4: Number of endpoints 2
[ 4.721557] usb 1-2.4: Endpoint 1 MaxPacketSize 64
[ 4.726776] usb 1-2.4: Endpoint 2 MaxPacketSize 64
[ 4.731842] usb 1-2.4: Setting MaxPacketSize 64
[ 4.738555] usb 1-2.4: FTDI USB Serial Device converter now attached
to ttyUSB1

What could be the problem ??? Any suggestion??

Yesterday night when i enabled the usb debug mesg in my kernel, i found the following log mesgs.

usb 1-2.1: unregistering interface 1-2.1:1.0
Jan 1 05:35:21 beagleboard kernel: [ 341.916687] usb 1-2.1: unregistering interface 1-2.1:1.1
Jan 1 05:35:21 beagleboard kernel: [ 341.923583] usb 1-2.1: unregistering interface 1-2.1:1.2
Jan 1 05:35:22 beagleboard kernel: [ 342.092895] hub 1-2:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
Jan 1 05:35:25 beagleboard kernel: [ 344.959655] hub 1-2:1.0: hub_suspend
Jan 1 05:35:25 beagleboard kernel: [ 344.959716] usb 1-2: unlink qh256-0001/cf8e4d80 start 1 [1/0 us]

here hub is suspended by the kernel as it doesnot find any device connected to the hub

Jan 1 05:35:25 beagleboard kernel: [ 344.959930] usb 1-2: usb auto-suspend
Jan 1 05:35:28 beagleboard kernel: [ 347.959777] hub 1-0:1.0: hub_suspend
Jan 1 05:35:28 beagleboard kernel: [ 347.959838] usb usb1: bus auto-suspend
Jan 1 05:35:28 beagleboard kernel: [ 347.959838] ehci-omap ehci-omap.0: suspend root hub

when i connected a usb device, it tried to resume…

Jan 1 05:35:39 beagleboard kernel: [ 359.283050] ehci-omap ehci-omap.0: port 2 remote wakeup
Jan 1 05:35:39 beagleboard kernel: [ 359.283203] usb usb1: usb resume
Jan 1 05:35:39 beagleboard kernel: [ 359.283203] ehci-omap ehci-omap.0: resume root hub
Jan 1 05:35:39 beagleboard kernel: [ 359.326843] hub 1-0:1.0: hub_resume
Jan 1 05:35:39 beagleboard kernel: [ 359.326934] ehci-omap ehci-omap.0: GetStatus port 2 status 001005 POWER sig=se0 PE CONNECT
Jan 1 05:35:39 beagleboard kernel: [ 359.326965] hub 1-0:1.0: port 2: status 0503 change 0004
Jan 1 05:35:39 beagleboard kernel: [ 359.327026] hub 1-0:1.0: state 7 ports 3 chg 0004 evt 0000
Jan 1 05:35:39 beagleboard kernel: [ 359.327087] ehci-omap ehci-omap.0: GetStatus port 2 status 001809 POWER sig=j PEC CONNECT
Jan 1 05:35:39 beagleboard kernel: [ 359.350280] usb 1-2: usb wakeup-resume
Jan 1 05:35:39 beagleboard kernel: [ 359.350341] usb 1-2: finish reset-resume
Jan 1 05:35:39 beagleboard kernel: [ 359.412933] ehci-omap ehci-omap.0: port 2 full speed → companion
Jan 1 05:35:39 beagleboard kernel: [ 359.412994] ehci-omap ehci-omap.0: GetStatus port 2 status 003801 POWER OWNER sig=j CONNECT

But here, some issue came and it says that port 2 not reset yet…

Jan 1 05:35:39 beagleboard kernel: [ 359.413055] hub 1-0:1.0: port 2 not reset yet, waiting 50ms
Jan 1 05:35:39 beagleboard kernel: [ 359.475372] ehci-omap ehci-omap.0: GetStatus port 2 status 003002 POWER OWNER sig=se0 CSC

and then it disconnects the port 2

Jan 1 05:35:39 beagleboard kernel: [ 359.475433] hub 1-0:1.0: logical disconnect on port 2
Jan 1 05:35:39 beagleboard kernel: [ 359.475463] usb 1-2: gone after usb resume? status -19
Jan 1 05:35:39 beagleboard kernel: [ 359.475463] usb 1-2: can’t resume, status -19
Jan 1 05:35:39 beagleboard kernel: [ 359.475494] hub 1-0:1.0: logical disconnect on port 2
Jan 1 05:35:39 beagleboard kernel: [ 359.475524] hub 1-0:1.0: resume on port 2, status -19
Jan 1 05:35:39 beagleboard kernel: [ 359.475555] hub 1-0:1.0: port 2, status 0501, change 0006, 480 Mb/s
Jan 1 05:35:39 beagleboard kernel: [ 359.475555] usb 1-2: USB disconnect, address 2

and itself it unregisters the device which results in my not responding usb hub

Jan 1 05:35:39 beagleboard kernel: [ 359.475585] usb 1-2: unregistering device
Jan 1 05:35:39 beagleboard kernel: [ 359.475585] usb 1-2: usb_disable_device nuking all URBs
Jan 1 05:35:39 beagleboard kernel: [ 359.475616] usb 1-2: unregistering interface 1-2:1.0
Jan 1 05:35:39 beagleboard kernel: [ 359.655059] hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x100
Jan 1 05:35:39 beagleboard kernel: [ 359.655090] hub 1-0:1.0: state 7 ports 3 chg 0000 evt 0004
Jan 1 05:35:42 beagleboard kernel: [ 361.959777] hub 1-0:1.0: hub_suspend
Jan 1 05:35:42 beagleboard kernel: [ 361.959808] usb usb1: bus auto-suspend
Jan 1 05:35:42 beagleboard kernel: [ 361.959838] ehci-omap ehci-omap.0: suspend root hub

What could be the possible issues?? i tried connecting different usb device but the same issue??
Please suggest the possible reason…

regards
Abhishek Singh

There is an issue with suspend/resume on the EHCI port in the processor silicon. You can find more information on it by reading the errata from TI.

http://focus.ti.com/lit/er/sprz278e/sprz278e.pdf

Gerald