General Issues
23592 - The device debug feature does not work if the chain is constructed through auto-chain-construction.
This happens because the software is not able to resolve the target device using JTAG IDCODE. The auto-chain-construction holds up the programming.
Workaround:
- Select the appropriate programming file, or manually resolve the device to a specific device.
- Savethe FlashPro project.
- Run Scan Chain, or execute read_idcode action in the programming file.
24344 - The DRC check is missing when the memory content file of eNVM client uses an obsolete path, and as a result, .efc file is not generated.
Workaround: Open the eNVM configurator within the MSS and fix the error related to the memory content file. Then, regenerate the MSS.
25918 - PROGRAM_NVM page address is incorrect on error code.
ERROR_CODE = 0x8080: On eNVM programming failure the page address reported is incorrectly reported and incremented by 1. This will be fixed in v9.0 SP1.
Workaround: Decrement the page address reported by 1.
25675 – Chain STAPL for SmartFusion design with STAPL file is incorrect
If you generate a chain STAPL with the STAPL file loaded with a SmartFusion device, it will result in an invalid chain STAPL file.
Workaround: Use the PDB file when exporting chain STAPL files.
25439 - FlashPro fails to export chain STAPL/SVF with Array and another feature (FROM, EFMB) (ProASIC3/E, IGLOO, SmartFusion, Fusion)
Chain STAPL/SVF fails when source programming file has an Array in addition to the FlashROM or EFMB (Embedded Flash Memory Block).
Workaround: Contact technical support. This will be fixed in v9.0 SP1 (June 2010).
23423 – Error when using Inspect Device if JTAG chain is constructed by performing Auto-Chain Construction
If the JTAG chain is constructed automatically by selecting the Construct Chain Automatically in the Configuration Menu, and you click on the Inspect Device button, you will see the following error:
Error: Cannot initialize debug engine: Cannot initialize the programmer: No available Actel products found on USB port.
Workaround:
- Option 1: Construct the device chain by manually specifying the list of devices in the chain using the Add Actel Device or Add non-Actel Device options, and save the FlashPro project.
- Option 2: Manually resolve the device by selecting the Actel device that is in the chain, and save the FlashPro Project.
- Option 3: Load the programming file for the devices in the chain, execute read_idcode action in the programming files, and save the FlashPro Project.
24049 - Previously secured programming files with user pass key will erase the security when ERASE_ALL/ERASE action is run for IGLOO, ProASIC3, SmartFusion and Fusion devices.
Workaround: Do not use ERASE_ALL/ERASE action. Use separate actions to erase individual features. Use ERASE_ARRAY, if present, to only erase the array. Use ERASE_FROM, if present, to only erase the FlashROM.
24173 – Programming Error: Error on line xxx: syntax error.
Workaround: If using STAPL Player and your STAPL file programs or verifies the ARRAY. Do not generate STAPL file using Libero IDE/FlashPro v9.0. Use Libero IDE/FlashPro v8.6 SP1 or earlier STAPL files.
6871 - Cannot load the same PDB for multiple devices or copy and paste
Workaround: Use STAPL files. Generate STAPL files from Libero IDE or FlashPro.
6859 - When using FlashPro programmer with Windows Vista operating system, the Refresh/Rescan may remove the programmer from the programmer list
Workaround: Restart the FlashPro software. This action will refresh the list of programmers.
52280 - Parallel FlashPro programming is not a supported programming mode
Parallel programming via USB 1.1 with FlashPro programmers (not FlashPro3) is disabled. If you attempt to program using parallel FlashPro programmers, a message will alert you that this is not possible. Use only one FlashPro programmer at a time for programming.
24433 - IEEE 1532 programming Error on line xxx: syntax error. No associated test data register for instruction U_ACTIVE.
Workaround: 1532 programming files generated using v8.6 SP1 or v9.0 have syntax errors. Use 1532 programming files from v8.6 release.
23987 - When attempting to use the permanent lock feature Save PDB generates message: "You must correct invalid data values before continuing…"
Workaround: Turn off the permanent lock setting and generate SmartFusion programming files without permanent lock feature.
23570 – Data reported through DEVICE_INFO action is incorrect for SmartFusion devices programmed with IAP
Workaround: None
24624 - Fusion design specific BSDL files created from Libero IDE v9.0 are invalid.
Workaround: This issue is fixed in Libero IDE v9.0 SP1.