Bernhard,
> P.S.: For testing purposes, you can find updated binaries under
> https://ci.appveyor.com/project/n1tehawk/sunxi-tools/build/v1.4%20%2346/artifacts
I haven't tried them yet. But if I do and if I have any additional questions as
a result of that I'll let you know.
Regards, Jk.
--
Hi John!
Has this been solved for you and/or were you able to test the reworked
binaries?
Am 13.12.2016 um 13:44 schrieb Bernhard Nortmann:
Hello John,
I intend to fix this "inconsistent" behaviour by explicitly reporting
invalid options (that sunxi-fel did not recognize). See
P.S.: For testing purposes, you can find updated binaries under
https://ci.appveyor.com/project/n1tehawk/sunxi-tools/build/v1.4%20%2346/artifacts
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving
Hello John,
I intend to fix this "inconsistent" behaviour by explicitly reporting
invalid options (that sunxi-fel did not recognize). See
https://github.com/linux-sunxi/sunxi-tools/pull/87/commits/1d2182c
That should get rid of "ERROR: Allwinner USB FEL device not found!" in
situations where
Alejandro, Bernhard,
It appears I wasn't entirely accurate, or complete rather, in my email
below.
When the board is NOT in FEL mode:
- listdevs results in "18d1:0003 (bus 2, device 2) path: 5"
- sunxi-fel -l results in no output whatsoever
- sunxi-fel --list results in no output whatsoever
-
Hi John!
Am 12.12.2016 um 21:08 schrieb John W. Kitz:
Alejandro, Bernhard,
When using the prebuilt Win32 binaries of "sunxi-fel", which I downloaded
from
"https://ci.appveyor.com/project/linuxsunxi/sunxi-tools/build/artifacts; I
noticed that in the same situation "sunxi-fel -l" and "sunxi-fel
