Downloads:
732
Downloads of v 6.0.0.2710:
53
Last Update:
31 May 2020
Package Maintainer(s):
Software Author(s):
- Texas Instruments
Tags:
uniflashUniflash
Downloads:
732
Downloads of v 6.0.0.2710:
53
Maintainer(s):
Software Author(s):
- Texas Instruments
Tags:
uniflashUniflash
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
This package was rejected on 13 Aug 2020. The reviewer chocolatey-ops has listed the following reason(s):
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.
#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
$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)"}
}
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
}
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.
- uniflash.6.0.0.2710.nupkg (c9ab848d0b26) - ## / 63
- uniflash_sl.6.0.0.2710.exe (4081e62eed5f) - ## / 70
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.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
uniflash (Install) 5.1.0.2397 | 428 | Sunday, October 13, 2019 | Approved | |
uniflash (Install) 5.0.0 | 251 | Monday, July 29, 2019 | Approved |
2019 Uniflash TI
Ground Rules:
- This discussion is only about Uniflash and the Uniflash 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, 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.
n3rd4i (maintainer) on 31 May 2020 13:36:18 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 31 May 2020 14:10:23 +00:00:
uniflash has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
n3rd4i (maintainer) on 31 May 2020 16:30:32 +00:00:
User 'n3rd4i' (maintainer) submitted package.
chocolatey-ops (reviewer) on 31 May 2020 17:05:10 +00:00:
uniflash has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 31 May 2020 18:43:45 +00:00:
uniflash has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 31 May 2020 19:01:25 +00:00:
uniflash has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/dd517aecc53fd1194ec498b7249c1df3 for details.
This is an FYI only. There is no action you need to take.
n3rd4i (maintainer) on 01 Jun 2020 12:33:25 +00:00:
All of these issues are not valid:
The BugTrackerUrl element in the nuspec file should be a valid Url. Please correct this More...
The LicenseUrl element in the nuspec file should be a valid Url. Please correct this More...
The ProjectUrl element in the nuspec file should be a valid Url. Please correct this More...
The MailingListUrl element in the nuspec file should be a valid Url. Please correct this More...
They all have valid URL's in latest package (forced) updated version.
To check use:
Software License
Software Docs
Software Mailing List
Software Issues
Don't understand why it complains.
n3rd4i (maintainer) on 01 Jun 2020 12:34:30 +00:00:
maybe Validation Testing re-run will fix it, not sure.
flcdrg (reviewer) on 17 Jun 2020 10:51:27 +00:00:
Rerun validation
Auto Validation Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 17 Jun 2020 10:54:46 +00:00:
uniflash has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
n3rd4i (maintainer) on 27 Jun 2020 10:43:34 +00:00:
I don't understand why the validation fails.
flcdrg (reviewer) on 09 Jul 2020 07:15:21 +00:00:
Rerunning validation again
Auto Validation Change - Validation tests have been set to rerun.
chocolatey-ops (reviewer) on 09 Jul 2020 07:19:40 +00:00:
uniflash has failed automated validation.
Requirements
Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
chocolatey-ops (reviewer) on 29 Jul 2020 07:18:10 +00:00:
We've found uniflash v6.0.0.2710 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
chocolatey-ops (reviewer) on 13 Aug 2020 07:18:24 +00:00:
Unfortunately there has not been progress to move uniflash v6.0.0.2710 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.
Status Change - Changed status of package from 'submitted' to 'rejected'.