Help,rom seems damaged

Hi,
Did you well plug your Devo JUST before enter the dmesg command ? (If so I think it's really damaged)

The linux dmesg looks like being from a virtual machine - have you assured that the tx is associated to it and not to the host system?

got a linux boot usb
here is the result

lsusb


dmesg


try to flash

I haven't used PBs tool yet but from the screenshots I would try to give the parameter "--txid 0000:0000" in addition. If your tx uses these values as you have written somewhere above it might work (although the output of dmesg makes me pessimistic).

PBs tool has not the parameter like "txid"

tony1157cn wrote: PBs tool has not the parameter like "txid"

Really?

Can you try another usb cable?

@sbstnp
tried a few usb cables, tried on mac,linux,window,returns the same error

@rbe2012
this is the result i tried with different command

mint@mint ~/Desktop/devo $ java -jar DeviationUpload-0.5-jar-with-dependencies.jar -send -dfu devo10.dfu
Error: Did not find matching device for VID:0x483 PID:0xdf11 alt:0

mint@mint ~/Desktop/devo $ java -jar DeviationUpload-0.5-jar-with-dependencies.jar -send -txid0000:0000 -dfu devo10.dfu
Error: Did not find matching device for VID:0x483 PID:0xdf11 alt:0

mint@mint ~/Desktop/devo $ java -jar DeviationUpload-0.5-jar-with-dependencies.jar -send -txid 0000:0000 -dfu devo10.dfu
Error: Did not find matching device for VID:0x483 PID:0xdf11 alt:0

mint@mint ~/Desktop/devo $ java -jar DeviationUpload-0.5-jar-with-dependencies.jar -send --txid 0000:0000 -dfu devo10.dfu
Error: Did not find matching device for VID:0x483 PID:0xdf11 alt:0

not work

OK, I'll try to open the Tx to see is there anything wrong with the usb socket or on the board.

I have just opened the Tx and checked the mainbord.
I can't see any physical damages.

then i checked the usb socket use a multimeter, it looks like the date+ and data- is connected with the chip very well. I heard the "bee" sound when i connect the the two points on the usb socket and chip with the multimeter.

I can't find where the VDD conntct to.

is this help to find out the problem?

here is the pic

OK ,i'll going to assembling the Tx after work,then post the logs
Hope it woks.

here is the log boot with ENT

lsusb:
mint@mint ~ $ lsusb
Bus 001 Device 003: ID 1005:b113 Apacer Technology, Inc. Handy Steno 2.0/HT203
Bus 002 Device 002: ID 1267:0201 Logic3 / SpectraVideo plc A4Tech SWOP-3 Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

dmesg:
[ 309.920027] usb 2-5: >new full-speed USB device number 3 using ohci_hcd
[ 310.100009] usb 2-5: >device descriptor read/64, error -62
[ 310.384015] usb 2-5: >device descriptor read/64, error -62
[ 310.664018] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 310.844010] usb 2-5: >device descriptor read/64, error -62
[ 311.128014] usb 2-5: >device descriptor read/64, error -62
[ 311.408019] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 311.816012] usb 2-5: >device not accepting address 5, error -62
[ 311.992011] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 312.400013] usb 2-5: >device not accepting address 6, error -62
[ 312.400027] hub 2-0:1.0: >unable to enumerate USB device on port 5

Is there any else to solve this problem?
Or maybe I should buy a new one?

Finally, I found the RXD / TXD foot,and the boot0 foot.It seems like the boot0 has been set to Hight level.
All those look well, maybe I coluld try to reinstall the bootloader, but I don't have the HEX file.Orz......

I think to weld the usb pins on the chip is very hard, because the pins are very small. But in
order to find whether the usb plug's problem or not, I'll try.

I have some microusb plug in hand,i'll check whether the pin assignments the same or not.
Or i'll get some miniusb plugs, which will take a few days.