You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
had the same problem, but i used the "package_esp32_dev_index.json" link and that worked for me..
still are RC's (RC4 at this moment!)
i was wondering if there will come some sort of Arduino Library Manager updater for the arduino-esp32 toolchain in the near future, now updating the toolchain and components is quiet some steps to follow in the correct order... i used Git for that, but i'm not sure it is updating to the latest version of the arduino-esp32 library...
Please explain what you mean, @ydsdsy. The Arduino IDE boards manager will alert you when updates to the package are released. It checks the json file at IDE startup to see if it has changed. The package will contain all the necessary submodules. The dev packages will be released fairly frequently, while the stable package will be less frequent and (hopefully) be less buggy.
You should only need to use the git repo if you want to be a contributor or test a particular feature before it is released in a package.
@lbernstone :
Do you mean that the toolchain will also be updated with this link in the arduino IDE??
(note : with toolchain, i mean al the header and project files that are needed to work with the ESP32 within the Arduino IDE)
my idea was that is was only for the boards using the ESP32, no?
If it really updates the toolchain and the boards also, that's a awesome thing you guys did for the community !!!
if I misunderstood the whole thing, i'm sorry for that...
Thanks,
Yves
@lbernstone Currently me-no-dev is creating a new(differently named) json file with every new release. Instead of just modifying the contents of the old file. The "new" file has entries for each of the RC's. I would change this to just have a "release-candidate" json and a "stable-release" json.
I think I need more coffee. My comprehension is low today. @ydsdsy : The boards maanger will install everything the old instructions did. You will not need to install anything additional to use an ESP32. In fact, you should remove the old git repository from your hardware directory or else you will have double entries for the ESP32 boards. @stickbreaker The json links are the critical piece in there. I'll see if I can figure out how to differentiate b/w the pre-release and full release once we have one of those 😄
Push the stable release json out front and list the dev branch at github. That way most users would never find github unless they put some effort into it.
Not hardware. The arduino-esp32 repository. Usually Arduino/hardware/espressif/esp32. @stickbreaker : The json files will be hosted at dl.espressif.com. The appropriate file will be updated whenever a package is created. These will then point back to the actual package download on github. Users won't have to go to the releases page at all to install. Should I just remove the version stuff from this page entirely and relocate it to the main README.md?
For the record, the new JSON link works beautifully. Updates are delivered directly through the Arduino GUI. Love it
Sent from my iPhone 7!
Charley Jones, PMP
On Jul 27, 2018, at 11:09 AM, lbernstone ***@***.***> wrote:
Not hardware. The arduino-esp32 repository. Usually Arduino/hardware/espressif/esp32.
@stickbreaker : The json files will be hosted at dl.espressif.com. The appropriate file will be updated whenever a package is created. These will then point back to the actual package download on github. Users won't have to go to the releases page at all to install. Should I just remove the version stuff from this page entirely and relocate it to the main README.md?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
@lbernstone i like the detail that me-no-dev has added to the release page on github, but, most users would not understand it. Putting that info in readme.md would cause their eyes too glaze over!! The only info in readme should be the 90% stuff, analogWrite() gpio6-11, gpio0, gpio5 gpi36-38, Wire() ReSTART handling differences. Wire.onRequest(),onReceive() the differences.
Activity
ydsdsy commentedon Jul 27, 2018
Hi,
had the same problem, but i used the "package_esp32_dev_index.json" link and that worked for me..
still are RC's (RC4 at this moment!)
i was wondering if there will come some sort of Arduino Library Manager updater for the arduino-esp32 toolchain in the near future, now updating the toolchain and components is quiet some steps to follow in the correct order... i used Git for that, but i'm not sure it is updating to the latest version of the arduino-esp32 library...
lbernstone commentedon Jul 27, 2018
Please explain what you mean, @ydsdsy. The Arduino IDE boards manager will alert you when updates to the package are released. It checks the json file at IDE startup to see if it has changed. The package will contain all the necessary submodules. The dev packages will be released fairly frequently, while the stable package will be less frequent and (hopefully) be less buggy.
You should only need to use the git repo if you want to be a contributor or test a particular feature before it is released in a package.
ydsdsy commentedon Jul 27, 2018
@lbernstone :
Do you mean that the toolchain will also be updated with this link in the arduino IDE??
(note : with toolchain, i mean al the header and project files that are needed to work with the ESP32 within the Arduino IDE)
my idea was that is was only for the boards using the ESP32, no?
If it really updates the toolchain and the boards also, that's a awesome thing you guys did for the community !!!
if I misunderstood the whole thing, i'm sorry for that...
Thanks,
Yves
stickbreaker commentedon Jul 27, 2018
@lbernstone Currently me-no-dev is creating a new(differently named) json file with every new release. Instead of just modifying the contents of the old file. The "new" file has entries for each of the RC's. I would change this to just have a "release-candidate" json and a "stable-release" json.
Chuck
lbernstone commentedon Jul 27, 2018
I think I need more coffee. My comprehension is low today.
@ydsdsy : The boards maanger will install everything the old instructions did. You will not need to install anything additional to use an ESP32. In fact, you should remove the old git repository from your hardware directory or else you will have double entries for the ESP32 boards.
@stickbreaker The json links are the critical piece in there. I'll see if I can figure out how to differentiate b/w the pre-release and full release once we have one of those 😄
stickbreaker commentedon Jul 27, 2018
I woud recommend two json's be created, the dev(pre-release) one at:
https://github.com/espressif/arduino-esp32/releases/download/package_esp32_dev_index.json
And, the stable release at:
https://github.com/espressif/arduino-esp32/releases/download/package_esp32_index.json
Push the stable release json out front and list the dev branch at github. That way most users would never find github unless they put some effort into it.
Just add another
platform
entry for new versions.Chuck.
ydsdsy commentedon Jul 27, 2018
@lbernstone
so i need to delete the complete [Users]Mydocs/Arduino/hardware directory then?
OK, will do that right now!
Thanks,
Yves
lbernstone commentedon Jul 27, 2018
Not hardware. The arduino-esp32 repository. Usually Arduino/hardware/espressif/esp32.
@stickbreaker : The json files will be hosted at dl.espressif.com. The appropriate file will be updated whenever a package is created. These will then point back to the actual package download on github. Users won't have to go to the releases page at all to install. Should I just remove the version stuff from this page entirely and relocate it to the main README.md?
ydsdsy commentedon Jul 27, 2018
Worked for me!!
Thanks!!
dataman commentedon Jul 27, 2018
stickbreaker commentedon Jul 27, 2018
@lbernstone i like the detail that me-no-dev has added to the release page on github, but, most users would not understand it. Putting that info in readme.md would cause their eyes too glaze over!! The only info in readme should be the 90% stuff,
analogWrite()
gpio6-11, gpio0, gpio5 gpi36-38,Wire()
ReSTART handling differences.Wire.onRequest(),onReceive()
the differences.Chuck.
lbernstone commentedon Jul 27, 2018
@stickbreaker Oh no. Not more detail, just the basic facts. Look at https://github.com/lbernstone/arduino-esp32/tree/pr1 and the boards_manager.md in that branch. I'm not involved in the releases page itself. You can comment on that at #1683.
combs commentedon Jul 27, 2018
https://dl.espressif.com/dl/package_esp32_index.json
lbernstone commentedon Jul 28, 2018
SPECIAL FOR THIS WEEK ONLY!
Use https://dl.espressif.com/dl/package_esp32_dev_index.json
There is no stable release yet.
copercini commentedon Jul 28, 2018
Released now =)
8 remaining items