Open bluecmd opened 1 year ago
I have this one and had no issues flashing the firmware:
Bus 003 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
I have this one and had no issues flashing the firmware:
Bus 003 Device 010: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
Interesting. I have this one: https://vi.aliexpress.com/item/2027583503.html - do you have something else? Granted, I have no idea if it is an actual PL2303 or a clone IC that just pretends to be one. My IC is totally clean of any markings, so that makes me suspect it might be a clone.
Retry 0: NAK on sector
should not be the problem, and process shall continue, on normal xmodem devices
I have exactly same looking device as yours from https://github.com/starfive-tech/Tools/issues/6#issuecomment-1634182961, but mine shows as
067b:2303 Prolific Technology, Inc. PL2303 Serial Port / Mobile Action MA-8910P
(note additional P
)
Might be difference.
Reporting success with CP2102N Friend adapter from Adafruit web store and tio
serial terminal software on Linux host.
Just chiming in for posterity as I encountered the same issue OP has described while experimenting with my VisionFive2 board. In my case however, the FT232 refuses to work with xmodem unfortunately. I'm using a Waveshare TTL-USB dongle with supposedly a FT232RL on-board, but judging by the issues it may not be genuine after all (or there's some other variable at play that makes xmodem fail here).
Appears the same in lsusb
:
$ lsusb
...
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Failure looks similar (using screen
, minicom
yields the same result):
CCCCCCCCCCCCCCCCCCCSending jh7110-recovery-20221205.bin, 1291 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 0/ 0kRetry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Xmodem sectors/kbytes sent: 13/ 1kRetry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: NAK on sector
Retry 0: Retry Count Exceeded
Transfer incomplete
Error
Will update this issue if I can figure out something more than the chip just being plain bad.
Useless to spend more time on StarFive tools, they do not release source code.
There are tools to do this work that have source code available, now.
Hi!
I was playing around with the recovery feature on VisionFive2 and I had no luck getting it to work at all with a TTL-USB converter using this device:
This is the errors:
However, when I switch to using my trusty
Future Technology Devices International, Ltd FT232 Serial (UART) IC
based one the XMODEM inside Minicom worked on the first try. (115200 8N1, No flow control).Might be worth mentioning on the recovery guide so that people don't pull their hair out trying to debug something that is due to a less-than-ideal TTL-serial-converter.
I repeated this experiement more than three times to ensure it was conclusive and it is. 0% success rate with my
PL2303
adapter, 100% success rate with myFT232
one.