From ba347a83dc68a490dd2ec924ace32108e2b51b53 Mon Sep 17 00:00:00 2001 From: Thorsten von Eicken Date: Mon, 9 Nov 2015 21:20:37 -0800 Subject: [PATCH] readme tweaks --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 7c96b3f..426abf5 100644 --- a/README.md +++ b/README.md @@ -286,6 +286,14 @@ synchronization with optiboot has been achieved by issuing a GET to the same URL issue a POST request to `http://esp-link/pgm/upload` with your hex file as POST data (raw, not url-encoded or multipart-mime. Please look into the avrflash script for the curl command-line details or use that script directly (`./avrflash esp-link.local my_sketch.hex`). +_Important_: after the initial sync request that resets the AVR you have 10 seconds to get to the +upload post or esp-link will time-out. So if you're manually entering curl commands have them +prepared so you can copy&paste! + +When to use which method? If port 23 works then go with that. If you have trouble getting sync +or it craps out in the middle too often then try the built-in programmer with the HTTP POST. +If your AVR doesn't use optiboot then use port 2323 since esp-link may not recognize the programming +sequence and not issue a reset if you use port 23. ### Flashing an attached ARM processor