When I attempt to program a Lattice part 64_32_xxjc with iMPACT and assign the ".isc" file generated from Lattice software, the following message appears:
"A ISC file describing an m4a5 is about to be assigned to a device previously identified as an 64_32_xxjc. Are you sure you want to do this? Yes/No. "
If I select "Yes", the following message is reported:
"ERROR:iMPACT:1161 - Why so many entities?"
This message is followed by another set of error messages:
"ERROR:iMPACT:1111 - Can't locate bsdl file m4a5.
EXCEPTION:iMPACT:BsdlStorage.c:327:1.54 - File does not exist.
ERROR:iMPACT:533 - deviceManagerProxy->setDeviceAttribute() failed!"
These errors are caused by a 1532 BSDL file limitation. The following rules apply when third-party devices are used in 1532 mode:
- The ISC file can have multiple entities defined, but iMPACT always selects the BSDL file associated with the first listed entity name.
- The ISC file entity name must be the base name of the associated BSDL file.
- The BSDL file must be present in the same directory as the ISC file.
- The ISC entity name cannot have an underscore symbol ("_") in it, as iMPACT truncates the name at the underscore and uses that as the base name for the BSDL file.
- iMPACT allows Erase, Program and Verify operations only.
- The erase actions should be named "erase", "program - program" and "verify - verify."
- iMPACT executes all required and recommended flows.