Michael Ossmann

@ktemkin was able to reproduce this on a Dell XPS 13 (similar to my test platform), but interestingly was able to achieve much higher speeds on different host hardware. hackrf_transfer...

I get: ``` $ gf benchmark --sync-usb Traceback (most recent call last): File "/usr/bin/greatfet_benchmark", line 11, in load_entry_point('GreatFET==2019.5.1+dirty', 'console_scripts', 'greatfet_benchmark')() File "/usr/lib64/python3.6/site-packages/GreatFET-2019.5.1+dirty-py3.6.egg/greatfet/commands/greatfet_benchmark.py", line 161, in main run_sync_benchmark(gf, args.length) File "/usr/lib64/python3.6/site-packages/GreatFET-2019.5.1+dirty-py3.6.egg/greatfet/commands/greatfet_benchmark.py",...

Oops. You are correct. I cleaned things up, and it works: ``` $ gf benchmark --sync-usb Starting a benchmark of synchronous USB communications: transferring 128.0 MiB. Transferred 128.0 MiB in...

I repeated some of the tests from my original post: ``` with -n 8: 34000000 sps: 33.4 MB/s 12000000 sps: 10.8 MB/s 6000000 sps: 5.9 MB/s 4000000 sps: 4.0 MB/s...

Now async USB is working perfectly for me. I was able to achieve 102 Msps with -n 2 by skipping the unpacking: https://github.com/mossmann/greatfet/tree/python-libusb1

- support bus pirate strings for things like I2C operations (e.g. "[0xd1 r:5]") - add a bus pirate compatible command-line tool that people can use when following a bus pirate...

Yes, AP22818AKEWT-7 looks like the drop-in replacement for AP22811AW5-7 which we have specified. AP22811AW5-7 is still expected to ship, so I don't think we need to make a change urgently....

Nice find! I think you are right that the output discharge function is not ideal for our application, although I don't know that I would say that it is faulty...

AP22818 has a discharge resistance of 140 to 200 ohms which is slightly less wasteful.

These are great finds! Thank you both! We are in the process of increasing the PCB size, so there will be plenty of space for a larger package. It's nice...