Grigori Goronzy
Grigori Goronzy
This might be a duplicate of #8.
With fake chips, of course, all bets are off. It could be anything. As far as I know, there are several FTDI fakes. I don't know of any specific compatibility...
Note that it could be phantom power issue with the fake FTDI, too. Maybe the fake chip is able to inject more power through I/O pins. As a first experiment,...
> Serial communication of STC15F104W is 8E1 (EVEN PARITY) but `stcgal` configures communication to 8N1 (NONE PARITY). **There is a BUG in `stcgal`!** Hm... stcgal should use the correct parity...
Thanks, that's good to know. Autodetection mode starts off with 8N1 mode and after detecting the MCU, it switches to the correct parity for the protocol. That usually works... but...
Yeah, 8E1 sounds like a good idea, I'm just wary of changing anything as it might affect compatibility with other MCUs or other UART chips and the like. 9N1 is...
I think that isn't possible (by design of STC's boot loader protocol), but I have to check.
Editor reload is required to make changes in compile_command.json take effect for already-open files
Is there anything missing to make this work? When I change a define (for instance), it's usually not picked up until I close and reopen the file in VSCode. So...
Okay, but it would still be nice to have *some* indication of what clangd is doing, maybe something simple like displaying an icon if it's not idle. It looks like...
I'm also seeing this, but I'm using Android 11. Edit: it seems to be crucial to actually wait for the returned `Promise` to be resolved. After changing my code to...