Re: [coreboot] Chromebox debugging.

[Kyösti Mälkki]

On 01/24/2014 01:39 AM, Timothy Potter wrote:
> Hi Kyosti,   Thanks the pointers.  I tried adding the changes for dbgp from
> the bug20-2.6.35-linaro to the 2.6.32 kernel I'm running on the phone.  You
> can see the results here:
>
> https://github.com/DengueTim/jordan-kernel/commits/AeroKernel

You still need the two patches from
   http://www.coreboot.org/EHCI_Gadget_Debug

Looks like you reverted them for this attempt.
> On startup, in /proc/kmsg I see:
>
> <7>[    2.010284] dbgp gadget: setup: desc device
> <7>[    2.010314] dbgp gadget: setup complete: 0, 8/8
> <7>[    2.010467] dbgp gadget: setup: desc device
> <7>[    2.010467] dbgp gadget: setup complete: 0, 18/18
> <7>[    2.010589] dbgp gadget: setup: failure req 6 v 200
> <7>[    2.010681] dbgp gadget: setup: failure req 6 v 200
> <7>[    2.010772] dbgp gadget: setup: failure req 6 v 200
> <7>[    2.016204] dbgp gadget: setup: failure req 6 v 3ee

Ignore those, g_dbgp driver implements only a few USB requests required 
for this special debug gadget purpose.
> I've attached the full log in case there's more clues as to why it's
> failing.  Any more suggestions of what I should be looking at?

I requested "lsusb" and "sudo lsusb -v" and dmesg from the other end of 
the communication too. If you see a "Debug descriptor" listed there, you 
can connect and reboot the chromebook with usbdebug enabled and collect 
new dmesg from that android side.

Also run "cat /dev/ttyGS0" on that android before you restart your 
chromebook.

Kyösti

Chromebox debugging.

[Timothy Potter]

Sorry for not including all you asked for Kyösti,  I've not had much time
to spend on this.  So you are saying if lsusb -v reports a 'Debug
descriptor' I should be able to use that port as the EHCI debug port on the
target?

When you say 'dmesg from the other end', you mean the target end(the
Chromebox)?  How do I get this?  The Coreboot build the Chromebox ships
with has USB debugging right?.  Do I need to compile a new kernel to see it?

Tim.

Here is the sudo lsusb -v (From my laptop not the Chromebox):

Bus 003 Device 006: ID 0525:c0de Netchip Technology, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0525 Netchip Technology, Inc.
  idProduct          0xc0de
  bcdDevice            0.00
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      0
Debug descriptor:
  bLength                 4
  bDescriptorType        10
  bDebugInEndpoint     0x81
  bDebugOutEndpoint    0x01
Device Status:     0x0000
  (Bus Powered)

On the phone I see this in /proc/kmsg while connecting the phone to
different USB ports on the Chromebox:

<4>[  680.485443] USB connected!
<6>[  680.485473] musb_pullup2 - Enabling USB Pullups
<4>[  680.485473] Enable usb
<6>[  687.774627] MUSB BUS RESET as b_peripheral
<6>[  687.774688] musb RESET!
<7>[  687.774749] dbgp gadget: setup: desc device
<7>[  687.774810] dbgp gadget: setup complete: 0, 18/18
<6>[  687.847717] MUSB BUS RESET as b_peripheral
<6>[  687.847747] musb RESET!
<7>[  687.847747] dbgp gadget: disconnected
<7>[  687.859619] dbgp gadget: setup: desc device
<7>[  687.859619] dbgp gadget: setup complete: 0, 18/18
<7>[  687.859863] dbgp gadget: setup: failure req 6 v 200
<7>[  687.860321] dbgp gadget: setup: failure req 6 v 200
<7>[  687.860656] dbgp gadget: setup: failure req 6 v 200
<6>[  710.459197] MUSB BUS RESET as b_peripheral
<6>[  710.459228] musb RESET!
<7>[  710.459289] dbgp gadget: disconnected
<7>[  710.459320] dbgp gadget: setup: desc device
<7>[  710.459381] dbgp gadget: setup complete: 0, 18/18
<6>[  710.530242] MUSB BUS RESET as b_peripheral
<6>[  710.530273] musb RESET!
<7>[  710.530273] dbgp gadget: disconnected
<7>[  710.540527] dbgp gadget: setup: desc device
<7>[  710.540557] dbgp gadget: setup complete: 0, 18/18
<7>[  710.540649] dbgp gadget: setup: failure req 6 v 200
<7>[  711.141265] dbgp gadget: setup: failure req 9 v 0
<6>[  716.865600] cpcap_usb_det: SenseBits = 0x4114
<6>[  716.865631] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  716.865661] cpcap_usb_det: SenseBit = CPCAP_BIT_DP_S_LS)
<6>[  716.865661] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  716.865692] cpcap_usb_det: SenseBit = CPCAP_BIT_SESSVLD_S
<6>[  716.967895] cpcap_usb_det: SenseBits = 0x4010
<6>[  716.967926] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  716.967926] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.069213] cpcap_usb_det: SenseBits = 0x4010
<6>[  717.069213] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  717.069244] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.171142] cpcap_usb_det: SenseBits = 0x4010
<6>[  717.171173] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  717.171173] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.272369] cpcap_usb_det: SenseBits = 0x4010
<6>[  717.272369] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  717.272369] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.373901] cpcap_usb_det: SenseBits = 0x4010
<6>[  717.373931] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  717.373931] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.491210] cpcap_usb_det: SAMPLE_2 cable may not be fully inserted
<6>[  717.592773] cpcap_usb_det: SenseBits = 0x4010
<6>[  717.592803] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  717.592834] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  717.592864] cpcap_usb_det notify_accy: accy=NONE
<6>[  717.592895] cpcap spi2.0: notify_accy: accy=4
<4>[  717.605804] USB disconnected!
<4>[  717.605834] Disable usb
<6>[  717.605834] musb_pullup2 - Disabling USB Pullups
<7>[  717.605865] dbgp gadget: disconnected
<6>[  720.975646] cpcap_usb_det: cable connected.
<6>[  720.976379] cpcap_usb_det: SenseBits = 0x401c
<6>[  720.976409] cpcap_usb_det: SenseBit = CPCAP_BIT_CHRGCURR1_S
<6>[  720.976440] cpcap_usb_det: SenseBit = CPCAP_BIT_ID_FLOAT_S
<6>[  720.976470] cpcap_usb_det: SenseBit = CPCAP_BIT_SESSVLD_S
<6>[  720.976470] cpcap_usb_det: SenseBit = CPCAP_BIT_VBUSVLD_S
<6>[  720.976501] cpcap_usb_det: Sense Pattern = SENSE_USB
<6>[  720.976531] cpcap_usb_det: USB or USB_FLASH
<6>[  720.976562] cpcap_usb_det notify_accy: accy=USB
<6>[  720.976562] cpcap spi2.0: notify_accy: accy=0
<4>[  720.976593] USB connected!
<6>[  720.976623] musb_pullup2 - Enabling USB Pullups
<4>[  720.976654] Enable usb

I can sent you the complete log outside the list if you need it.

On Fri, Jan 24, 2014 at 1:07 AM, Kyösti Mälkki wrote:
> On 01/24/2014 01:39 AM, Timothy Potter wrote:
> > Hi Kyosti,   Thanks the pointers.  I tried adding the changes for dbgp
> > from
> > the bug20-2.6.35-linaro to the 2.6.32 kernel I'm running on the phone.
> >  You
> > can see the results here:
> >
> > https://github.com/DengueTim/jordan-kernel/commits/AeroKernel
>
> You still need the two patches from
>   http://www.coreboot.org/EHCI_Gadget_Debug
>
> Looks like you reverted them for this attempt.
>
> On startup, in /proc/kmsg I see:
> > <7>[    2.010284] dbgp gadget: setup: desc device
> > <7>[    2.010314] dbgp gadget: setup complete: 0, 8/8
> > <7>[    2.010467] dbgp gadget: setup: desc device
> > <7>[    2.010467] dbgp gadget: setup complete: 0, 18/18
> > <7>[    2.010589] dbgp gadget: setup: failure req 6 v 200
> > <7>[    2.010681] dbgp gadget: setup: failure req 6 v 200
> > <7>[    2.010772] dbgp gadget: setup: failure req 6 v 200
> > <7>[    2.016204] dbgp gadget: setup: failure req 6 v 3ee
>
> Ignore those, g_dbgp driver implements only a few USB requests required
> for this special debug gadget purpose.
>
> I've attached the full log in case there's more clues as to why it's
> > failing.  Any more suggestions of what I should be looking at?
>
> I requested "lsusb" and "sudo lsusb -v" and dmesg from the other end of
> the communication too. If you see a "Debug descriptor" listed there, you
> can connect and reboot the chromebook with usbdebug enabled and collect new
> dmesg from that android side.
>
> Also run "cat /dev/ttyGS0" on that android before you restart your
> chromebook.
>
> Kyösti