Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 16:57
    pabloandresm synchronize #8140
  • 16:52
  • 15:02
  • 14:57
    d-a-v synchronize #8154
  • 14:11
    d-a-v labeled #8154
  • 14:11
    d-a-v labeled #8154
  • 14:06
    d-a-v synchronize #8154
  • 12:43
    HamzaHajeir edited #8155
  • 12:41
    HamzaHajeir opened #8155
  • 10:07
    d-a-v edited #8154
  • 10:06
    d-a-v edited #8154
  • 10:04
    d-a-v synchronize #8154
  • 09:58
    d-a-v synchronize #8154
  • 09:58
    d-a-v edited #8154
  • 09:58
    d-a-v milestoned #8154
  • 09:57
    d-a-v opened #8154
  • 09:12

    d-a-v on master

    Add missing menu.UploadTool nam… (compare)

  • 09:12
    d-a-v closed #8153
  • 09:01
    silvanocerza synchronize #8153
  • 08:48
    d-a-v milestoned #8153
Jeff Eberl
@jeffeb3
Thanks.
Markus
@Links2004
yes, this one of the reasons why i wrote the http updater ;)
Jeff Eberl
@jeffeb3
Well thank you. And get it documented! The people must know!
seclorum
@seclorum
@igrr thanks, is the config for crostool-ng available somewhere in the repo, i may have overlooked it .. for compliance/testing reasons, where possible I prefer to build toolchains from source...
tzapu
@tzapu
hi guys, does OTA work with ide 1.6.6 now ? or still limited to 1.6.5 ?
Ivan Grokhotkov
@igrr
@seclorum "config" is actually within crosstool-ng itself, it is called xtensa-lx106-elf

So on Linux you just follow crosstool-ng manual and do something like

./bootstrap && ./configure --prefix=`pwd` && make && make install
./ct-ng xtensa-lx106-elf
./ct-ng build

After that the toolchain will be inside builds/xtensa-lx106-elf directory

On OS X things get a bit more tricky: you need to run crosstool-ng on a case-sensitive volume, plus you need some GNU tools from macports or homebrew
Ivan Grokhotkov
@igrr
@seclorum btw, @kireevco has been working on build scripts for the toolchain recently: https://github.com/kireevco/packages/tree/master/xtensa-lx106-elf
perhaps that's what you need
Dmitry Kireev
@AutomationD
@seclorum @igrr it works on all platforms, now I’m making my jenkins work
@seclorum I don’t think it’s for crosstool-ng. it’s building all components separately
I was not able to make esp-open-sdk work on windows (yet)
mac+linux works ok
@seclorum work for esp-open-sdk has been done here https://github.com/kireevco/packages/tree/master/esp-open-sdk
seclorum
@seclorum
superlative, thanks @igrr @kireevco
Ivan Grokhotkov
@igrr
damn, OTA thing in 1.6.6 is worse than I thought.
Markus
@Links2004
you mean the ssh problem?
Ivan Grokhotkov
@igrr
originally i thought the issue to be just with the UploaderFactory, but it turns out there is another one
Basically IDE checks if the advertised port accepts TCP connections
And since we are using UDP, this check fails.
Markus
@Links2004
k that is bad, and open one of our limited tcp sockets isnt the best idea.
Ivan Grokhotkov
@igrr
@reaper7 stumbled upon this in #970
yeah. I was about to open a pull request for the UploaderFactory issue (basically a one-line change), but i have no idea how to work around this BoardReachabiltyFilter
Markus
@Links2004
is is possible to disable the filter for udp ports.
and change the code to:
    MDNS.addService("arduino", "udp", _port);
Ivan Grokhotkov
@igrr
possible, but less likely to be accepted
Markus
@Links2004
yes, that is the main problem, i think.
Ivan Grokhotkov
@igrr
on the IDE side this will also need a change in that case:
jmDNS.addServiceListener("_arduino._tcp.local.", this);
Markus
@Links2004
may simple adding as seconde jmDNS.addServiceListener("_arduino._udp.local.", this); is working.
Ivan Grokhotkov
@igrr
nah, this still doesn't work: BoardReachabiltyFilter still runs, and it call NetUtils.isReachable, which tries to open TCP socket.
there is no provision for UDP there
i.e. that information is not passed from board discovery mechanism
I am tempted to write a plugin, similar to ESP8266FS tool, which will implement OTA uploads.
downside of this approach is that users will not be able to do OTA with "Upload" button
upside is that Arduino team is less likely to break our OTA mechanism with future changes
Markus
@Links2004
I think that the Upload button will not work will be the biggest problem for the most normal Users,
but get it working is not easy to reach.
for user who read the documentation its not the problem, but the most simply try without reading and then we get more issues.
Markus
@Links2004
we have to many Issues oO
try to clean up but no end in sight.
Ivan Grokhotkov
@igrr
well you have reduced the number of issues by 10%. if we do this every day, in two weeks we will be back to normal :)
Me No Dev
@me-no-dev
I also attempted to modify the mainstream IDE to be able to upload using the upload button
I got to the point of uploading, but had to modify more than what you just said
the main difference is that they stopped filtering boards that have "using_ssh" and just treat all network boards as such
the best aproach I thought of was to branch from that point and filter network devices that have let's say "upload_using_programmer" or something like it
then it can go the regular upload_tool way and just add a couple of lines in it to detect network device and replace the serial port with the network address
overall 10-15 lines can get it to upload
the Monitor is another story all together
Me No Dev
@me-no-dev
I think if it's done smart and in a way that can not possibly interfere with AVR/SAM boards, then the arduino team might take it
Me No Dev
@me-no-dev
maybe I should give it another go?
Ivan Grokhotkov
@igrr
@me-no-dev that would be awesome
I think it might be better to start without Monitor function, with just the minimum we need to support OTA