# \[Workbench\] Not flashing the firmware I think it's flashing?

**URL:** https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950
**Category:** Developer Tools
**Tags:** electron
**Created:** [May 2, 2020, 12:42am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950 "2020-05-02T00:42:22Z")
**Posts on this page:** 16
**Page:** 1

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 12:42am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/1 "2020-05-02T00:42:22Z")

</div>

I’m trying to use the VS Code Workbench to locally flash firmware that turns off the cellular device on my Electron; but after flashing, the LED on the Electron just goes back to blinking cyan and then breathing cyan, which (according to [https://docs.particle.io/tutorials/device-os/led/electron/#sts=Electron](https://docs.particle.io/tutorials/device-os/led/electron/#sts=Electron)) means it’s still using the cellular module to connect to the Cloud. I’m concerned that it’s not flashing the firmware that I think it’s flashing.

Here’s my .ino program:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/8/d/8d37bb829fc814d05bd6899cde29af45636380d6.png)

I used the ‘Particle: Compile application (local)’ command to compile it locally  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/e/f/efd0a7c60a4bf0a17f381dc28637915cc943b86b.png)  
which generated the terminal in the previous screenshot

Now I’m using the ‘Particle: Flash application (local)’ command to flash it to my Electron  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/9/4/9410ad88369079d43f27e3ae2058f100898ec5df.png)

After flashing, the terminal shows this:

```auto
> Executing task: make -f 'C:\Users\spenc\.particle\toolchains\buildscripts\1.9.2\Makefile' flash-user -s <

:::: PUTTING DEVICE INTO DFU MODE

Done.

:::: FLASHING APPLICATION

   text data bss dec hex filename
   4412 108 1392 5912 1718 c:/Users/spenc/Documents/Particle/Projects/test/target/1.5.0/electron/test.elf
dfu-suffix (dfu-util) 0.9

Copyright 2011-2012 Stefan Schmidt, 2013-2014 Tormod Volden
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Suffix successfully added to file
Serial device PARTICLE_SERIAL_DEV : not available
Flashing using dfu:
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 2b04:d00a
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 4096
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08080000, size = 4520
Download [=========================] 100% 4520 bytes
Download done.
File downloaded successfully

***FLASHED SUCCESSFULLY***

Press any key to close the terminal.

```

But after flashing, the Electron goes back to blinking cyan (connecting to the Cloud) and then breathing cyan (connected). It could be helpful to mention, the target device is not a personal device. It’s registered as a development device for a product I’m working on.

Also, I’m checking the Event Feed on the console and I’m seeing events being published from a previous firmware

 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/d/3/d3432c21cebcede101a8ec36dab117581d666461.png)

Any idea why my Workbench isn’t flashing the firmware in front of me when I try the ‘Particle: Flash application (local)’ command, even though the terminal says ‘FLASHED SUCCESSFULLY’?

EDIT: I got it to flash the firmware in front of me by choosing the ‘Particle: Flash application & DeviceOS (local)’ option, instead of ‘Particle: Flash application (local)’.  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/a/7/a7ae9628f04f166e15f4da3e63c18da5a308d68f.png)

I tried this after reading this here: [https://docs.particle.io/tutorials/developer-tools/workbench/#local-build-and-flash](https://docs.particle.io/tutorials/developer-tools/workbench/#local-build-and-flash)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/6/0/60898ead65f197361ca13a0ffe32991d5ecd7235.png)

I don’t understand anything about these 3 paragraphs

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 2:49am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/3 "2020-05-02T02:49:55Z")

</div>

Follow-up question:

![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/8/1/81e4d0fad5da10760d901b706df4fc58dffc3855.png)

Any idea why this firmware binary is created only when I input `particle compile electron` in the CLI, and not created when I use the command from the command palette or click the ‘Compile Project’ button in the top right?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/5/b/5bb2e7c7a47c3cde479f3f7686d733c6205c1742.png)

Also, what uses that firmware binary? EDIT: My best guess is that firmware binary can be used when uploading new firmware to the Cloud console (specifically for developing a Product).

 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/c/2/c2fdcc92e562af4175d0eb7d50fa5f4a6b2b66a6.png)

And is it necessary for that to be created when flashing new firmware to my device? EDIT: No, I’ve been able to flash locally to my device without creating the firmware .bin by choosing ‘Particle: Flash application & DeviceOS (local)’ option from the command palette 🙂

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 6:09am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/4 "2020-05-02T06:09:14Z")

</div>

> [@spe](#):
>
> Any idea why this firmware binary is created only when I input `particle compile electron` in the CLI, and not created when I use the command from the command palette or click the ‘Compile Project’ button in the top right?

I don't think that was the root cause.  
Looking at your first (not working) screenshot and the latter working one I see that you hadn't saved your changes before compiling but later had  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/c/9/c95c1f6c883e9e6790105721a335da47a9ad253d.png)  
_(note the dot in the file tab - this tab holds unsaved changes)_

The file explorer even tells you so  
 ![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/b/5/b52cf7f523a95d80ac00dd14daae7ec90340aba8.png)

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 6:55am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/5 "2020-05-02T06:55:51Z")

</div>

> [@ScruffR](#):
>
> Looking at your first (not working) screenshot and the latter working one

@ScruffR Thanks for taking a look! By the "latter working one", are you referring to the first picture in my "Follow-up question:" post? If so, just clarifying, I didn't post that picture to show that it was now working; that whole post was a separate somewhat-related question.

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 8:33am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/6 "2020-05-02T08:33:15Z")

</div>

Yes, I was refering to that, but even if there was no direct relation to your inital issue, chances are that you had saved the file at some point between seeing the issue and then not seeing it when building with CLI.

So my point still stands that I’d put my money not on _Workbench build task vs. CLI_ but rather _unsaved vs. saved_

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 2:28pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/7 "2020-05-02T14:28:42Z")

</div>

@ScruffR Hmm maybe I’m misunderstanding you. I just pulled up a new program, made sure it was saved, and then tried these out:

1. Clicking the ‘Compile Project’ button  

2. Using the ‘Particle: Compile application (local)’ command  

3. Using ‘particle compile electron’ in the CLI  

So, even when the .ino I’m working on is saved, I’m still seeing that only using the CLI actually creates the .bin file. Am I understanding you correctly?

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 2:39pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/8 "2020-05-02T14:39:47Z")

</div>

Have you looked inside the `target` folder and therein again inside the `electron` folder?

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 2:44pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/9 "2020-05-02T14:44:23Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/e/a/eaf7a4c26c89add86dae9fecec5f6db756d353fc.png)

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 2:47pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/10 "2020-05-02T14:47:52Z")

</div>

> [@spe](#):
>
> I’m still seeing that only using the CLI actually creates the .bin file. Am I understanding you correctly?

obviously not 😉

![image](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/8/0/808e722519e376f440edc6af13d626f387073f28.png)

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 3:00pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/11 "2020-05-02T15:00:29Z")

</div>

I’m confused - Could you elaborate?

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 3:07pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/12 "2020-05-02T15:07:45Z")

</div>

Your screenshot clearly shows that `analyze.bin` _ **was** _ created during `Particle: Compile application (local)`, so the assumption that _ **only** _ CLI would create a `.bin` file is false.

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 3:11pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/13 "2020-05-02T15:11:08Z")

</div>

What’s the difference between ‘electron\_firmware\_1588429389905.bin’ and ‘analyze.bin’?

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 3:13pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/14 "2020-05-02T15:13:25Z")

</div>

I’d say the name only 😉  
Have you compared the sizes?

But you can run `particle binary inspect analyze.bin` and `particle binary inspect electron_firmware_1588429389905.bin` if you see any difference.

---

<div class="post-metadata">

### Author: ![spe](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/spe/32/24310_2.png) [@spe](https://community.particle.io/u/spe)
#### Post date: [May 2, 2020, 3:22pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/15 "2020-05-02T15:22:31Z")

</div>

They look to be the same size. So sounds like a difference between the different ways of compiling in the Workbench is that they put the .bin file in different places and call it different things?

---

<div class="post-metadata">

### Author: ![ScruffR](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/scruffr/32/6952_2.png) [@ScruffR](https://community.particle.io/u/ScruffR)
#### Post date: [May 2, 2020, 3:23pm UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/16 "2020-05-02T15:23:30Z")

</div>

Pretty much so

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/6/4/64635adccc35238caa19e9b553ec3e98b163d026.png) [@system](https://community.particle.io/u/system)
#### Post date: [November 1, 2020, 3:23am UTC](https://community.particle.io/t/workbench-not-flashing-the-firmware-i-think-its-flashing/55950/17 "2020-11-01T03:23:35Z")

</div>

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
