I’m extremely impressed with the Electron and am on the cusp of moving my next projects to it. The problem is I don’t think I can live with the web IDE, and the command-line build produces a different and unusable *.bin file from what the web IDE produces. I’ve been beating my head on this for almost two full workdays. I sure wish I could find a hint of what to look for!
My system is Ubuntu 17.04 and all of my tools are the latest po-util and particle-cli. The compile process seems flawless - alerting errors and warnings as it should. I’d be extremely happy if I could get an LED-blink example to work.
Symptoms: No errors anywhere. Project builds without warnings and downloads via “flash” without error. The downloaded firmware boots up with the RGB LED going through the regular cell connect patterns. When it reaches the end of the fast blue blink and you’d expect it to start breathing cyan, it kicks back into breathing magenta. It never transitions to the section of the code that blinks the LED on D7! Using the web IDE, the EXACT SAME SOURCECODE compiles to a *.bin which I download with dfu-util exactly the same as the CLI-built code and it works exactly as it should - blinking happily along.
I’ve built some impressive evaluation firmware with the web IDE but it is time to get serious about development on the Electron and use a decent editor and quick compile/flash process from the command line. It is in Particle’s best interest to assist with some pointers because I’m essentially in a race with another developer who wants to use a Digi XBee LTE-M. One of us will get our test to a functional state first which determines the direction of the project.