* Update README.md
syntax error in instructions. this command as written will not work because if flag --chip is used it needs to be --chip=bl70x with the "="
does not work: blisp write --chip bl70x --reset name_of_firmware.bin
or if "=" is not desired then "-c bl70x" could be used instead.
-c, --chip=<chip_type> Chip Type
* Update README.md
* Update README.md
* Update README.md
* Update README.md
* Update README.md
* Update README.md
---------
Co-authored-by: River <97197236+River-b@users.noreply.github.com>
Co-authored-by: Marek Kraus <gamelaster@users.noreply.github.com>
syntax error in instructions. this command as written will not work because if flag --chip is used it needs to be --chip=bl70x with the "="
does not work: blisp write --chip bl70x --reset name_of_firmware.bin
or if "=" is not desired then "-c bl70x" could be used instead.
-c, --chip=<chip_type> Chip Type
Add sp_drain() where needed. Without it FreeBSD won't pass the handshake
phase.
Also decreate max buffer size.
Tested with Pinecil v2 and it can write and check new firmware.
For some reason, macOS have issues with USB CDC,
surprisingly, CH340G convertor works just fine.
But FTDI and Bouffalo's USB CDC didn't worked.
Basically, without writing anything, we don't receive
response from board. This was fixed by adding drain
after writing BOUFALLOLABRESET handshake + adding
drains after every commmand write. Also, for some reason,
in USB CDC, the size of USB payload is limited, else
it will fail.
Modifications for MacOS to let it find data files in the same directory as the executable. This is totally wrong for a "normal" MacOS app bundle, but it follows the existing Linux convention.
This helped with handshake on CH340, but FT232H don't like it.
Currently, it is not needed, as current code can work properly
both on CH340G but also on FT232H.
