Verified, we can tftp without a usb-ethernet adapter dongle. ptsentor, yay, we don't have to buy more hardware.
It turns out the PE and a lot of other devices have a CDC usb ethernet hardware in them. An example of this is the old cable modem, you can connect to a cable modem with USB, your cable modem acts like a usb ethernet nic into itself.
nikkie, try this:
Connect up your serial console cable.
Plug a mini-usb cable from your computer into the PE.
Boot PE, and "break" quickly with your terminal program as usual
(at this point, in my linux box's messages I see that it sees a usb disk, but no partitions)
Then type, "tftpboot"
Quote:
Edge>> tftpboot
***** Plug-in USB cable & config usbdnet now ******
exit check_usb_connection:1
*** Warning: no boot file name; using 'C0A80265.img'
Using u2o-eth device
TFTP from server 192.168.2.100; our IP address is 192.168.2.101
Filename 'C0A80265.img'.
Load address: 0x500000
Loading: T T T T T T T T T T T
|
And now on my Linux box:
Quote:
[34684.114687] usbcore: registered new interface driver usb-storage
[34684.114689] USB Mass Storage support registered.
[34685.595300] scsi 6:0:0:0: Direct-Access Android File-Stor Gadg etff PQ: 0 ANSI: 2
[34685.596274] sd 6:0:0:0: Attached scsi generic sg2 type 0
[34685.690992] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[34760.467194] usb 2-2: USB disconnect, address 7
[34869.080063] usb 2-2: new high speed USB device using ehci_hcd and address 8
[34869.298676] cdc_subset 2-2:1.0: usb0: register 'cdc_subset' at usb-0000:00:1d.7-2, Boot Loader OBject, de:d4:3c:00:4e:08
[34869.298883] usbcore: registered new interface driver cdc_subset
|
On my Linux box, I then have a "usb0" with no IP set yet.
Almost there.......!!!
I'm sure I could tftp boot a kernel at this point, but I'm already booting the recovery kernel it seems on the device, so tftp in itself is not helping me. I need the recovery root/initrd accessible to go through the reflash motions.