Hi all, my electron seems to be having some uploading issues. When I upload my code over the CLI, it says “Flash Success!” but then when I check to see how the code is doing, the previous code is still on it and the new one isn’t. The thing is, my new code has functions, and my old code’s function still appear on the Particle app after several times of refreshing and exiting out of the app. I know the board isn’t just not connected to the cloud, because on the Particle app V2 when I click signal for ten seconds, the RGB lights up accordingly. I’m wondering if I’m doing something wrong or if my board is malfunctioning.
Yes.
I press the button that’s like a cloud with an arrow pointing down. It’s next to the name of the project.
Thanks for your suggestions, I got it to work!
I have same issue with Firmware version 0.5.2. Anything I update via serial using Particle CLI has no effect! The old code on the device continue to execute!. I’ve even tried the Blinking LED sample and it does not turn the LED on even though the flash was successful according to CLI output.
Just complied and download the Blinlking LED example and here's the output of CLI (BTW - was done over USB-serial and not USB)
particle flash --serial firmware.bin
! PROTIP: Hold the SETUP button on your device until it blinks blue!
? Press ENTER when your device is blinking BLUE
sending file: firmware.bin
The point why --usb would be better is that you’ll get better feedback of what’s actually happening.
With --serial you even get a “Flash success!” when you try to flash a Photon binary onto an Electron - which would of course not stick.
That does explain a lot.
As expected your binary is not targeted for Electron (10) but for Core (0).
So rebuild that binary with the correct target device selected.
If so, try to upgrade to 0.6.0-rc.2 again flashing all three system parts and finally Tinker.
After that you should be back at in breathing cyan and then you can flash your code again.
Update your CLI, then do particle update followed by particle flash --usb tinker. That should get you to a working state. Should you want to try newer firmware than the latest stable one, you should update manually by flashing the respective system parts, as mentioned by @ScruffR.
Phewww…after a lot of trial and error. It works for now
So far my experience on the electron board has been really really bad. What I could do with any other platform and IDE’s (MPLAB, PSOS, Atmel Studio included beside Arduino or RPI or Intel) this takes 10 times the work and time to do something very simple…not sure if this is a good promise of so called rapid prototype board or simply misleading. This seems an over engineered tool and platform in my opinion.
I would recommend the following
A local IDE that does NOT rely on any cloud. Instead,
Could compile, do syntax highlight, go to the error (line) with a simple click, Perhaps integration with Arduino or some other IDE would be even better.
Simple firmware and embedded application update mechanism that works and consistent without 2-3 different methods and drivers and mode.
Simple, preferably one page guideline of all the operation.
Of course all these fancy stuff could still be relevant for people who thinks it’s helpful to them so please keep building.
