ciminaghi
commented
6 years ago Hi,
when the library was written, file uploads within the arduino environment were done by means of the python script called arduino_mcuota.py or something like that. Such script simply split the .hex file in chunks and sent them via http post. This used to work, and it still does, I use it for my tests (since I personally don't like the arduino environment, I just launch the script as a command line program). From what you're saying, and from a comment in your code (// handles upload with new mcu_ota tool), I understand that there is a new mcu ota tool, which does things in a different way. If that is the case, then I'd rather have two different rx methods, for the moment at least: the "old" arduino and the new one, with different names, because I'd like to do my tests with the script I've used so many times. By the way, do you know why the ota tool has been changed ? I can't remember any serious technical flaws, and the new one doesn't look simpler, at least on the rx side.
As far as branches are concerned, nordic-zip and red are the newest ones. red comes from nordic-zip and adds support for the red board by what's next. nordic-zip adds support for the arduino primo. While I still have to do serious tests on the primo, the red board should work well, so I think red will eventually become the new master.
Davide
JAndrassy
Hi Davide. me again :-). Some months ago I added to a copy of your library code to receive upload from the default OTA upload tool in IDE. I would add it as pull request, but to which branch? Here it is. Changes are only in arduino-server.cpp
The upload support was for some Latvian guy who sells Arduinos and wanted to reflash Uno WiFis, he had on stock, with WiFi Link. But he didn't. Then I thought that WiFi Link is dead so I left it. But now I see that WiFi Link lives in "red" and more important that your library supports it. So the default upload would be good for "red".