Thomas

Yes job is done! Thanks for your time for the quick update;-)

Yes, now the debugscreen is showing all bytes. Thanks for updating the software, now it is also fast within my virtualbox session.

Yes, now it's working in all modes! One minor thing: when block transfer is active, the debug-screen is not showing all send bytes: Uploading program memory send: 00, 00, 00, 40; B8, receive: 43, send: 00, 00, 40, 40; 80, ..... etc In above sample, before the B8 and B0 all databytes are missing of the block.

Chip is a PIC18F14K22, baudrate 38k4; Debug-info in tool: Delay = 0, no block transfer: Checking device send: C1 receive: 62, 43 Uploading program memory send: 00, 00, 00, 40; A0, EF, 1F, F0, FF, FF, FF, FF, 1D, 52, 00, 00, 01, E1, 12, 00, FD, 0E, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, 00, B8, Here it stops.... so no receiving char is displayed But my logic...

Yes with the block transfer checkbox checked, the programming goes without delay, so that is looking very good! I also tested some other combinations, but 1 combination is not working now: Block transfer unchecked and a delay of 0, now I get this message: Uploading PROGMEM Uploading program memory no answer ERROR: Problem in uploading HEX file to device Closed COM12 serial port When a delay is set greater than 0, it is programming again. But thanks for your solution so far!

OK, I will looking forward to it!

I don't understand, the for-loop with the CRC calculation is still there, only in that same for-loop the single byte is not send to the PIC when the delay is 0, only that part is done after the loop (The memBlock array is send with blockLength number of bytes). I tested it and it is working very well so far; did you also do a test? I know from early days projects, that it is always more efficient to send more bytes in one serialport call instead of a number of separate calls.

Attached the changed file. For the fix only line 1199 and 1212/1213 are needed, the other 2 changes were needed to get the project to build in Visual Studio 2017.