Downloads:

144

Downloads of v 5.1.0.2397:

32

Last Update:

13 Oct 2019

Package Maintainer(s):

Software Author(s):

  • Texas Instruments

Tags:

uniflash

uniflash (Install)

5.1.0.2397 | Updated: 13 Oct 2019

Downloads:

144

Downloads of v 5.1.0.2397:

32

Maintainer(s):

Software Author(s):

  • Texas Instruments

Tags:

uniflash

uniflash (Install) 5.1.0.2397

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install uniflash (Install), run the following command from the command line or from PowerShell:

>

To upgrade uniflash (Install), run the following command from the command line or from PowerShell:

>

To uninstall uniflash (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 https://chocolatey.org/api/v2. 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 https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade uniflash -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 uniflash -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure uniflash installed
  win_chocolatey:
    name: uniflash
    state: present
    version: 5.1.0.2397
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'uniflash' do
  action    :install
  version  '5.1.0.2397'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: uniflash,
    Version: 5.1.0.2397,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller uniflash
{
   Name     = 'uniflash'
   Ensure   = 'Present'
   Version  = '5.1.0.2397'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'uniflash':
  provider => 'chocolatey',
  ensure   => '5.1.0.2397',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install uniflash version="5.1.0.2397" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator mwallner on 24 Oct 2019.

Description

Uniflash is a tool for flashing firmware to TI specific chips.

Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.


tools\cert_installer.ahk
#NoEnv
#NoTrayIcon
#Warn
SendMode Input
SetTitleMatchMode, 2
SetControlDelay 0
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.

WinWait,Windows ahk_class #32770 ahk_exe rundll32.exe,mshelp, 180
ControlSend,Button1,{SPACE},Windows ahk_class #32770 ahk_exe rundll32.exe
while WinExist("ahk_class #32770")
{
	Sleep, 20
}

WinWait,Windows ahk_class #32770 ahk_exe rundll32.exe,mshelp, 180
ControlSend,Button1,{SPACE},Windows ahk_class #32770 ahk_exe rundll32.exe
while WinExist("ahk_class #32770")
{
	Sleep, 20
}

WinWait,Windows ahk_class #32770 ahk_exe rundll32.exe,mshelp, 180
ControlSend,Button1,{SPACE},Windows ahk_class #32770 ahk_exe rundll32.exe
while WinExist("ahk_class #32770")
{
	Sleep, 20
}

WinWait,Windows ahk_class #32770 ahk_exe rundll32.exe,mshelp, 180
ControlSend,Button1,{SPACE},Windows ahk_class #32770 ahk_exe rundll32.exe
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
. "$(Join-Path $toolsDir helper.ps1)"

$url        = 'http://software-dl.ti.com/ccs/esd/uniflash/uniflash_sl.5.1.0.2397.exe'
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  unzipLocation = $toolsDir
  fileType      = 'exe'
  url           = $url
  softwareName  = 'uniflash*'
  checksum      = '4EDD650A39F1227F4B2EACA6840A0487FDAFE8AC70917C3EEA686173D5118054'
  checksumType  = 'sha256'
  silentArgs    = "--unattendedmodeui minimal --mode unattended"
  validExitCodes= @(0, 3010, 1641)
}
$ahkProc = Start-Ahk('cert_installer.ahk')

Install-ChocolateyPackage @packageArgs

# minimum delay to ensure the autohotkey takes efect
& Start-Sleep 1
if (Get-Process -id $ahkProc.Id -ErrorAction SilentlyContinue) {Stop-Process -id $ahkProc.Id}
tools\chocolateyuninstall.ps1
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  softwareName  = 'uniflash*'  #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
  fileType      = 'exe' #only one of these: MSI or EXE (ignore MSU for now)
  silentArgs    = "--mode unattended"
  validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
}
$uninstalled = $false
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
  $key | % { 
    $packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
    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)"}
}
tools\helper.ps1
function Start-Ahk($ahkScript){
	$ahkFile = Join-Path $toolsDir $ahkScript
	$ahkEXE = Get-ChildItem "$env:ChocolateyInstall\lib\autohotkey.portable" -Recurse -filter autohotkey.exe
	$ahkProc = Start-Process -FilePath $ahkEXE.FullName -ArgumentList "$ahkFile" -PassThru
	Write-Debug "AutoHotKey start time:`t$($ahkProc.StartTime.ToShortTimeString())"
	Write-Debug "Process ID:`t$($ahkProc.Id)"

	return $ahkProc
}
tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
 
<Include details of how to verify checksum contents>
== Uniflash package source ==
1. Calculate sha1 checksum for each certificate and store that in a log file
%chocolateyinstall%\tools\checksum.exe -t sha1 tools\certificates\driver_ti_1.cer >> certs_verif.log
%chocolateyinstall%\tools\checksum.exe -t sha1 tools\certificates\driver_ti_2.cer >> certs_verif.log
%chocolateyinstall%\tools\checksum.exe -t sha1 tools\certificates\driver_ti_3.cer >> certs_verif.log
%chocolateyinstall%\tools\checksum.exe -t sha1 tools\certificates\driver_ti_4.cer >> certs_verif.log

== Chocolatey Test Environment ==
1. Clone the `Chocolatey Testing Environment` as specified here:
- https://chocolatey.org/docs/create-packages#testing-your-package

2. Clone the Uniflash source repository into the `Chocolatey Testing Environment` `packages` folder:
```cmd
git clone [email protected]:chocolatey-community/chocolatey-test-environment.git
cd chocolatey-test-environment\packages
git clone [email protected]:n3rd4i/uniflash.git
```

3. Comment all the lines which install the needed certificates from the chocolatey package source, powershell comment with '#':
- edit file "uniflash\tools\chocolateyinstall.ps1"
```
# This is needed for unattended installation of Texas Instruments Drivers
# & "C:\Windows\System32\certutil.exe" -addstore "TrustedPublisher" "$toolsDir\certificates\driver_ti_1.cer"
# & "C:\Windows\System32\certutil.exe" -addstore "TrustedPublisher" "$toolsDir\certificates\driver_ti_2.cer"
# & "C:\Windows\System32\certutil.exe" -addstore "TrustedPublisher" "$toolsDir\certificates\driver_ti_3.cer"
# & "C:\Windows\System32\certutil.exe" -addstore "TrustedPublisher" "$toolsDir\certificates\driver_ti_4.cer"
```

4. Install the chocolatey package manually in Chocolatey Test Environment:
- after the installation is almost done, there are 4 certificates pending user acceptance in VM
- accept each one pressing "Install"

5. After certificates are accepted installation should be successfully, then:
- open powershell (since your are in Chocolatey Test Environment it will start as Administrator, intended)
- command: `dir cert:LocalMachine\TrustedPublisher | findstr "Texas Instruments"`

6. Compare the sha1 checksums from, they should match:
- the step "Uniflash package source" step 1.
- the step "Chocolatey Test Environment" step 5.

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
uniflash (Install) 5.0.0 112 Monday, July 29, 2019 Approved
Discussion for the uniflash (Install) Package

Ground Rules:

  • This discussion is only about uniflash (Install) and the uniflash (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 uniflash (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