Workbench Core v1.14.11 — New settings?

The Particle extension Workbench Core has been updated to v1.14.11.

The solution for [SOLVED] Particle Web IDE: Uploading a project — SOLUTION: Customise Particle Workbench - #4 by nrobinson2000 no longer works when I try to target the Core+Photon.

Visual studio Code with the Particle Workbench extension now throws an error when I load the project:

Invalid toolchain manifest!
Error: Invalid toolchain manifest!
	at module.exports.validateJSON (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/node_modules/@particle/toolchain-manager/src/manifest/loader.js:103:9)
	at module.exports.mergeJSON (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/node_modules/@particle/toolchain-manager/src/manifest/loader.js:66:3)
	at Object.module.exports.mergeOverrideFileSync (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/node_modules/@particle/toolchain-manager/src/manifest/loader.js:88:9)
	at Function.mergeManifestForDeviceOSSync (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/node_modules/@particle/toolchain-manager/src/toolchain.js:83:25)
	at loadManifestAndReportErrors (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/src/index.js:165:13)
	at module.exports.activate (/Users/USER/.vscode/extensions/particle.particle-vscode-core-1.14.11/src/index.js:32:3)
	at Function._callActivateOptional (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:17454)
	at Function._callActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:17119)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:88:14937
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async _activate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:8180)
	at async _waitForDepsThenActivate (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:8122)
	at async _initialize (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:83:7486)

- - - -

[
    {
        "keyword": "required",
        "dataPath": ".platforms[11]",
        "schemaPath": "#/required",
        "params": {
            "missingProperty": "baseMcu"
        },
        "message": "should have required property 'baseMcu'"
    }
]

- - - -

I searched the Particle Workbench documentation for baseMcu but found no answer so far.

How to keep building against the Core and

Thank you for your help!

@rei_vilo

Setting a baseMcu field works for me:

Example .workbench/manifest.json:

{
    "version": "1.0.0",
    "toolchains": [{
        "firmware": "deviceOS@source",
        "compilers": "gcc-arm@5.3.1",
        "debuggers": "openocd@0.11.2-adhoc6ea4372.0",
        "platforms": [1],
        "scripts": "buildscripts@1.9.2",
        "tools": "buildtools@1.1.1"
    }],
    "platforms": [{
        "id": 1,
        "name": "core",
        "generation": 1,
        "baseMcu":"blahblah"
    }]
}
1 Like

It works, thanks!

Let’s hope Particle provides some documentation…

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