Boron rc.26 in Workbench?


#1

Just tried to flash to my boron which I just realized has rc.26. Now I’m dead in the water.

Does workbench support rc.26? Or do I need to go back to rc .25 for all my devices?

Thanks.


Gen 3 improvements update - 12/17
#2

You can run rc.25 applications on an rc.26 device.
Workbench support for rc.26 will follow, but you are not stuck.

I have also moved your other post here, since double posting is not helpful and strongly discouraged in this forum.
Moderators are usually doing a good job in monitoring new messages and seeing the same question of the same person multiple times does not make us rejoice over their engagment :wink:


#3

is rc.26 supported by Particle Workbench?


#4

Copy on the double post. I’ll keep it in mind.

I tried to flash an application that worked just yesterday on a boron running r.25. Didn’t work on my r.26 devices flashing over USB in DFU mode from VS Code via Workbench in the terminal.

I was able to OTA flash a Boron r.25 with the same application successfully through Workbench after my unsuccessful attempt with r.26.


#5

I can assure you it works :wink:
This is what my Boron reports with system & application both rc.27

C:\Particle\Mesh\mesh-RC.27-draft2>particle serial inspect
Platform: 13
Modules
  Bootloader module #0 - version 215, main location, 49152 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  System module #1 - version 326, main location, 671744 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      Bootloader module #0 - version 101
      undefined module #0 - version 0
  User module #1 - version 5, main location, 131072 bytes max size
    UUID: 362808E0DB24B4ED309227C9121675856A32E73D5D16D2C7922C49C9AEF353C2
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #1 - version 326
      undefined module #0 - version 0
  empty - factory location, 131072 bytes max size

And this is what the same device reports after I flashed an application binary created by Particle Workbench targeting rc.25

C:\Particle\Mesh\mesh-RC.27-draft2>particle serial inspect
Platform: 13
Modules
  Bootloader module #0 - version 215, main location, 49152 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
  System module #1 - version 326, main location, 671744 bytes max size
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      Bootloader module #0 - version 101
      undefined module #0 - version 0
  User module #1 - version 5, main location, 131072 bytes max size
    UUID: 038536EC2ADB05748375331D9BD7B3B96F51511674BE83428672F7B2827990D3
    Integrity: PASS
    Address Range: PASS
    Platform: PASS
    Dependencies: PASS
      System module #1 - version 324
      undefined module #0 - version 0
  empty - factory location, 131072 bytes max size

Mark the System module #1 dependency entry under User module #1 326 stands for 0.8.0-rc.27 and 324 for 0.8.0-rc.25. So a rc.25 targeted application can run under rc.25 and anything above.

If your rc.25 binary doesn’t run on a rc.26 Boron there is something else wrong, but not with the system :wink:


#6

New day. Flashed successful. I have no idea what I did differently.

I’m sure there is a flaw in my work flow. I have found working with the 3rd Gen hardware often over my head. Trying to figure out when/how to use the CLI and when how to use Workbench, and often heading over to Particle Build to reflash Tinker to start fresh. It’s been a confusing process and trying to keep up has been nearly impossible.

My primary purpose for these devices is to have a 4G LTE modem. I am spending a lot of my time dealing with technical issues related to Particle when the focus of my work is on doing agricultural research. I’m very much on the consumer end of the spectrum then the developer end.

What I’m trying to get at is the 3rd Gen hardware very much feels like it was built and targeted at a customer base with a much larger back ground in development than I have. Especially with the bugs between the hardware and software from particle. As noted elsewhere on the forum the lack of straight forward documentation and work flow for the 3rd gen devices has been frustrating. Take or leave the feedback. I’m excited to be working with the technology and trying to wrap my head around it so it’s not all negative.


#7

It might feel like that since you have entered the field at a time of early adoption which very often starts off much more bumpy than the final product will be.


#8

Since I’m impatient and eager to use the Workbench and latest mesh firmware I patched my local 1.0.0-alpha.5 Workbench for rc.26 and rc.27.

If others are as impatient as I am, you can, at your own risk, copy this gist over the one in your local Workbench installation <user-home>.vscode/extensions/particle.particle-vscode-core-1.0.0-alpha.5/src/compiler/toolchain/manifest.json.


#9

lol. check yr mail everyone :+1:

i’ll take your impatience as enthusiasm for Workbench :wink: