Philippe Teuwen

thanks, I'll be away next two weeks, not sure if I'll take the risk to brick it :D but I'll try to progress on the other issues

Sorry man, but bt_transfers doesn't contain your branch commits :( You can run `gitk --all` to have a graphical view of the situation and try to fix it.

yeah, only very saturated signals will benefit from such basic strategy.

There are also obvious errors ``` armsrc/lfops.c: if (BUTTON_PRESS() && !usb_poll_validate_length()) armsrc/mifarecmd.c: if (BUTTON_PRESS() && !usb_poll_validate_length()) { armsrc/mifarecmd.c: if (BUTTON_PRESS() && !usb_poll_validate_length()) break; armsrc/iclass.c: if (BUTTON_PRESS() && !usb_poll_validate_length()) goto out;...

* https://github.com/hydrabus/hydrafw/wiki/HydraFW-UART-guide#bridge-mode * http://dangerousprototypes.com/docs/UART#Transparent_UART_bridge Effect is that you're speaking to whatever is connected to the FPC USART as it was directly connected to your PC with e.g. a FTDI cable....

yes, whatever is connected to FPC USART would answer

Still we've to be careful how to set it up... * newly compiled fw + newly compiled client = ok * newly compiled fw, latest client but not recompiled after...

Proposition : When client compiles it embeds info about armsrc/version.c. * client can be recompiled several times, still embeds same armsrc/version.c * if armsrc changed and reflashed, what to do?...

yes what you say is exactly what needs to be done, but for doegox/proxmark-internal#15 which is a different issue to tackle

FTR: beware people compiling from ZIP don't have git version info. What to do ? Two strategies: * ignore git version if missing, rely solely on compilation timestamp to see...