Downloads of v 1.14.0:


Last Update:

20 Oct 2019

Package Maintainer(s):

Software Author(s):

  • nashif
  • ukkar
  • jhedberg
  • andrewboie
  • tbursztyka
  • galak
  • finikorg
  • Vudentz
  • wrsPeterMitsis
  • etc.


zephyr-ide zephyr ide development embedded

zephyr-ide (Install)

1.14.0 | Updated: 20 Oct 2019



Downloads of v 1.14.0:



Software Author(s):

  • nashif
  • ukkar
  • jhedberg
  • andrewboie
  • tbursztyka
  • galak
  • finikorg
  • Vudentz
  • wrsPeterMitsis
  • etc.

zephyr-ide (Install) 1.14.0

This Package Contains an Exempted Check

1 Test Passing and 1 Exempted Test

Validation Testing Passed

Verification Testing Exempt:

Dependency requires reboot

To install zephyr-ide (Install), run the following command from the command line or from PowerShell:


To upgrade zephyr-ide (Install), run the following command from the command line or from PowerShell:


To uninstall zephyr-ide (Install), run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade zephyr-ide -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade zephyr-ide -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure zephyr-ide installed
    name: zephyr-ide
    state: present
    version: 1.14.0
    source: STEP 3 URL

See docs at

chocolatey_package 'zephyr-ide' do
  action    :install
  version  '1.14.0'
  source   'STEP 3 URL'

See docs at

    Name: zephyr-ide,
    Version: 1.14.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller zephyr-ide
   Name     = 'zephyr-ide'
   Ensure   = 'Present'
   Version  = '1.14.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'zephyr-ide':
  provider => 'chocolatey',
  ensure   => '1.14.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install zephyr-ide version="1.14.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator flcdrg on 20 Oct 2019.


Ready-to-start Windows IDE for developing with Zephyr platform

This package is a set of tools needed for a Windows user to start developing applications with Zephyr Project.
Using VSCode as main IDE with the source for the Zephyr Project together with GNU ARM toolchain.

### Components:
* VSCode based IDE (w/ ext. cpptools, cortex-debug)
* GNU Arm Embedded Toolchain
* CMake open-source system that manages the build process.
* nRF Command Line Tools
* J-Link Software and Documentation pack for Windows
* OpenOCD, the Open On-Chip Debugger
* pyOCD is an open source Python package for programming and debugging Arm Cortex-M microcontrollers

# $ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"

# Installed in 'User Space' using juntion
Start-ChocolateyProcessAsAdmin "/C if not exist `"$SOURCE_DIR`" mkdir `"$SOURCE_DIR`"" $ENV:COMSPEC
Start-ChocolateyProcessAsAdmin "/C if not exist $LOCAL_APP_DIR mklink /J $LOCAL_APP_DIR `"$SOURCE_DIR`"" $ENV:COMSPEC

Start-ChocolateyProcessAsAdmin '/C pip3 install -U west' $ENV:COMSPEC

& $ENV:COMSPEC /C pushd $LOCAL_APP_DIR '&&' west init $ZEPHYR_INSTALL_DIR --mr v$ENV:ChocolateyPackageVersion
& $ENV:COMSPEC /C pushd $ZEPHYRPROJECT '&&' west update
Install-ChocolateyEnvironmentVariable "ZEPHYR_BASE" "$ZEPHYR_BASE"

& $ENV:COMSPEC /C pushd $ZEPHYRPROJECT '&&' pip3 install -r zephyr/scripts/requirements.txt

## This line is here because could not use installargs to the choco dependency
## choco install cmake --installargs 'ADD_CMAKE_TO_PATH=System'
Install-ChocolateyPath 'C:\Program Files\CMake\bin' -PathType 'Machine'
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir commonEnv.ps1)"

$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'zephyr-ide*'
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
  $key | % {
    $packageArgs['file'] = "$($_.UninstallString)"
    if ($packageArgs['fileType'] -eq 'MSI') {
      $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
      $packageArgs['file'] = ''
    } else {
    Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$($key.Count) matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $($_.DisplayName)"}

Remove-Item -recurse -force $ZEPHYRPROJECT
Uninstall-ChocolateyEnvironmentVariable 'ZEPHYR_BASE'
# Generic environment variables
$GATE_DIR = 'localapp'
$SOURCE_DIR = "$(Join-Path $ENV:userprofile $GATE_DIR)"
$LOCAL_APP_DIR = "$(Join-Path $ENV:systemdrive $GATE_DIR)"

$ZEPHYR_INSTALL_DIR = 'zephyrproject'
$ZEPHYR_BASE = "$(Join-Path $ZEPHYRPROJECT zephyr)"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status

Discussion for the zephyr-ide (Install) Package

Ground Rules:

  • This discussion is only about zephyr-ide (Install) and the zephyr-ide (Install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or zephyr-ide (Install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus