Hi, I have a UEVM5432G-02-01-00 ES 2.0 GP PandaBoard -- sometimes called Panda5 (I think).
The latest release for this appears to be Panda5AJ.1.5.1 (Sep 2013) from the list of releases here.
I downloaded the distribution from TI, and unzipped it on Ubuntu 12.04 virtual machine (under VMWare Fusion on Mac OS 10.7).
Here's what happens when I run usbboot fast mode:
$ sudo ./usbboot -f waiting for device... reading ASIC ID CHIP: 5430 rom minor version: 02 IDEN: 0000000000000000000000000000000000000000 MPKH: 0000000000000000000000000000000000000000000000000000000000000000 CRC0: 071a9a31 CRC1: 00000000 device is GP using built-in GP iboot of size 23-KB sending 2ndstage to target... waiting for 2ndstage response...
Then if I run fastboot.sh...
$ sudo ./fastboot.sh [sudo] password for davis: Fastboot - device detected: userdata.img
It just sits there and nothing proceeds. adb devices output:
$ sudo ./adb devices [sudo] password for davis: * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached
lsusb output of the TI device:
Bus 001 Device 002: ID 0451:d011 Texas Instruments, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0451 Texas Instruments, Inc.
idProduct 0xd011
bcdDevice 0.00
iManufacturer 33
iProduct 37
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 1
bmAttributes 0xc0
Self Powered
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
I read through the similar threads here:
- http://e2e.ti.com/support/omap/f/885/t/243310.aspx
- http://e2e.ti.com/support/omap/f/885/p/280200/981495.aspx
but was not able to resolve the issue through any of the recommended solutions.
I tried using the version of usbboot attached to that thread, and it did fix the discrepancy of iboot size from 23-K to 48-K (note in my output above it shows 23-K, which that thread claims is not correct), but fastbooth.sh still would not work and just sits there.
There was talk about having to cherry pick a specific commit from the git source and build usbboot / fastboot from that, but it isn't clear to me why or if that is applicable to my device.
Can someone please advise?
Thanks in advance
