VTOS Tools Release 2.2.0

Version 2.2.0

Release date: 25-aug-2016

What’s New

  • vAccess.dll API changes
  • VTOS Program NAND for NXP QorIQ P5040 and P5021
  • VTOS Program NAND for the NXP QorIQ P1 family.

 

VTOS Tools

  • Issue: Corrected an issue where a test suite would return PASSED even though one of the individual test FAILED.
  • Update to CodeWarrior CCS Build 449.

VTOS DDR

  • No specific changes in this release, see VTOS Tools for general product updates.

VTOS Program

  • Feature: VTOS Program NAND support for the NXP QorIQ P5 (P5040/P5021)
  • Feature: VTOS Program NAND support for the NXP QorIQ P1 family.  Note that this release does not include support for the P1010 and the P1014 processors.

VTOS Scan

  • No specific changes in this release, see VTOS Tools for general product updates.

vAccess

  • Feature: There are several vAccess API changes that are required with using the vAccess.dll 2.2 release:
    • This version reverts back to using __stdcall for all vAccess API calls, thus avoiding integration issues with third party tools that use vAccess.dll.
    • All function calls now return an enum labeled “vaccess_rc_e” for return status. Only three values are possible: VACCESS_SUCCESS, VACCESS_ERROR, and VACCESS_FATAL. The value VACCESS_FATAL represents that the connection was automatically disconnected and the caller must Connect() again.
    • The function ExecuteCommandExt() replaces ExecuteCommand().
    • The function ClearTestErrors() replaces ClearErrorCodes().
    • The function GetLastTestError() replaces ReadErrorCode(). This new function returns an integer error value and a string for that error. The caller must allocate space for the string buffer before the call.
    • The prototype for RegisterConsoleCallback() has a minor change to pass “unsigned int” instead of “int”.
    • The function GetLastErrorCodeExt() replaces GetLastErrorCode(). This function updates a struct labeled “vaccess_error_t”. This function returns detailed error information from vAccess and the hardware interface driver, along with text explanations of the error. The caller must allocate space for all string buffers before making a call to GetLastErrorCodeExt().

About Kozio

Kozio has been crafting embedded software since 2003 and has served the needs of thousands of engineers working for hundreds of companies, from the smallest to the largest.
This entry was posted in General, Hardware Interface Testing. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *