973 - ispVM: How does user check the Lattice devices supported by ispVM Embedded?

• Related Articles

• 1698 - ispLEVER Classis: What limitations exist in ispVM Slim Embedded as compared to ispVM Embedded?

  The Slim ispVM Embedded (Slim VME) software is intended for use on microcontollers that, in general, has very limited memory resources. The small amount of memory available in these devices limits the types of operations that are available when using ...

• 596 - Lattice ispVM: Which Operating Systems are supported by ispVM?

  The operating systems supported in the current version of ispVM are listed in ispVM System Help Procedures > Using ispVM Utilities > Installing/Uninstalling Parallel Port Driver and USB Driver ispVM version 17.9.1 officially supports the following ...

• 606 - Lattice ispVM: What could cause the “JTAG-NOP” error message in ispVM System tool?

  Description: "JTAP-NOP" indicates that a device was detected, but its JTAG IDCODE is not in the ispVM System database. There are a few reasons this may occur. Solution: The device is a newer Lattice device and is not yet supported by the version of ...

• 1120 - ispVM: What needs to be modified in ispVM Embedded to target an embedded system?

  In general, most of the modification will involve the hardware.c file. This module contains functions that are specific to the embedded system and compiler used. The major portions of hardware.c are: Pin assignments -- constant declarations ...

• 163 - Lattice ispVM: What is the difference between ispVM Embedded and the EPROM version?

  The difference is in how and when the VME data is linked to the executable. ispVM Embedded uses a pointer to link the VME data at run-time. The default implementation uses a file pointer with the filename passed in via command-line arguments, but can ...