abelerr.mnu

自己编写的GAL可编程逻辑电路的编译软件abel4的windows界面

Fatal Error 2024: Latte (on-set) failed on 'file_name'.

While running '-reduce dt', the espresso program (latte)
was not found or produced an internal error.
*2025,A
Fatal Error 2025: Latte (off-set) failed on 'file_name'.

While running '-reduce dt', the espresso program (latte)
was not found or produced an internal error.
*2026,A
Fatal Error 2026: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2027,A
Fatal Error 2027: Design must use D or T flip flops.

The ABEL design must use the .D or .T detailed equations.
*2028,A
Fatal Error 2028: Can't open output file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2029,A
Fatal Error 2029: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2030,A
Fatal Error 2030: Can't open output file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2031,A
Fatal Error 2031: Latte failed on 'file_name'.

While running '-reduce dt', the espresso program (latte)
was not found or produced an internal error.
*2032,A
Fatal Error 2032: Latte failed on 'file_name'.

While running '-reduce dt', the espresso program (latte)
was not found or produced an internal error.
*2033,A
Fatal Error 2033: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2034,A
Fatal Error 2034: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2035,A
Fatal Error 2035: Can't open output file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2036,A
Fatal Error 2036: Latte failed on 'file_name'.

While running '-reduce dt', the espresso program (latte)
was not found or produced an internal error.
*2037,A
Fatal Error 2037: Latte failed on 'file_name'.

While running '-reduce gdt', the espresso program (latte)
was not found or produced an internal error.
*2038,A
Fatal Error 2038: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2039,A
Fatal Error 2039: Can't open input file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2040,A
Fatal Error 2040: Can't open output file 'file_name'.

While running '-reduce dt', PLAOpt could not open the file.
*2041,A
Fatal Error 2041: Could not rename 'file_name' to 'file_name'.
*--Selector--,A
*All these errors are for internal database problems*
*-----------------------------------------------------*
*3090,A
Warning 3090: internal error ddd when reading device architecture

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3094,A
Warning 3094: general internal error ddd with device architecture

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3381,A
Warning 3381: general error ddd when handling chip  xxx

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3098,A
Warning 3098: internal list handling error when handling arch to
chip

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3099,A
Warning 3099: internal list handling error when handling mfg to chip

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3382,A
Warning 3382: Should never Happen!. Duplicate record problem ...

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3100,A
Warning 3100: general error ddd when handling chip information

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3383,A
Warning 3383: internal error ddd when finding chip data to remove

DEVMRG only. Internal database error occurred. Maybe jammed
database. Contact Data I/O Customer Resource Center.

*3385,A
Warning 3385: internal error ddd when merging chip information

DEVMRG only. Internal database error occurred. Maybe jammed
database. Contact Data I/O Customer Resource Center.

*3101,A
Warning 3101: internal error ddd when handling mfg info

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3102,A
Warning 3102:  internal error ddd when reading mfg info

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3107,A
Warning 3107: general error ddd when handling mfg info

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3084,A
Warning 3084:   internal error ddd when initialize database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3086,A
Warning 3086: internal problem opening database...

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3088,A
Warning 3088: Internal error code ddd when initializing database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3089,A
Warning 3089: Sorter database could not be initialized!

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3391,A
Warning 3391: trouble updating arch record xxx  error was ddd

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3110,A
Warning 3110: *** internal database error ddd occurred ...

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3111,A
Warning 3111: Fatal internal database system error ddd occurred

Internal database error occurred. Could be anything from a
damaged database to someone defeating database interlock and
jamming your run of the program. If internal error is -905,
problem could be your PC configuration in not allowing enough
open files. Contact Data I/O Customer Resource Center.

*3168,A
Warning 3168:  internal error ddd, could not retrieve parent
architecture

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3171,A
Warning 3171: Line ddd Manufacturer xxx could not be written in
database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3200,A
Warning 3200: General database problem ddd when validating chip

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3216,A
Warning 3216: internal database error ddd when accessing arch to
chip list

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3220,A
Warning 3220: current chip xxx of arch yyy could not be added to
select list due to error ddd

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3273,A
Warning 3273: internal error ddd when doing a non-sorting move

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3276,A
Warning 3276: internal error index ddd is beyond the end of the
list size ddd

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3277,A
Warning 3277: Internal error, Could not connect item to empty list!

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3278,A
Warning 3278: internal error with movement in quicksort ...

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3280,A
Warning 3280: internal error ddd when connecting sorted chip

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3340,A
Warning 3340:  problems with the sorter database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3346,A
Warning 3346:  problems with the sorter database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3431,A
Warning 3431: Internal error ddd in opening database

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*3165,A
Warning 3165:  serious problem in storing parent architecture
xxx for alias line ddd

Internal database error occurred. Maybe jammed database. Contact
Data I/O Customer Resource Center.

*Errors caused by improper decoding of device or design information *
*-------------------------------------------------------------------*
*3016,A
Warning 3016: Error encountered reading ABEL-PLA file

An internal error occurred parsing the file containing your
design.  Either the file specified was not an ABEL-PLA file or
there is a bug. Contact Data I/O Customer Resource Center.

*3018,A
Warning 3018: Error generating signal information

Contact Data I/O Customer Resource Center.

*3130,A
Warning 3130:  don't know what this enable is ...

Contact Data I/O Customer Resource Center.

*3261,A
Warning 3261:  internal error, could not decode regtype ddd for
signal yyy

Contact Data I/O Customer Resource Center.

*3331,A
Warning 3331:  Internal error, ABEL-PLA parser failed!

Contact Data I/O Customer Resource Center.

*3354,A
Warning 3354:  internal error could not decode EQNtype ddd

Contact Data I/O Customer Resource Center.

*Problems with files (protection opening, closing, writing ...)*
*--------------------------------------------------------------------*
*3371,A
Warning 3371: Could not open Database Version file, ...

SmartPart could not find a certain file inside the database.
The directory specified may not contain a database or the
database was damaged in some way. Another possibility is that
you do not have permission to access the database (need
read/write).

*3373,A
Warning 3373: could not find a database and ABEL4DB is not set!

SmartPart could not find a device database. Set the environment
variable ABEL4DB to the directory of the database, or specify
the directory in the "Modify Criteria" menu.

*3375,A
Warning 3375: There is no database at 'xxx'

SmartPart could not find a device database. The environment
variable ABEL4DB or the database field in "Modify Criteria" has
the wrong directory, fix it.

*3137,A
Warning 3137: Could not open log file xxx

Obvious. Maybe bad pathname or a protection problem.

*3377,A
Warning 3377: Can't open file xxx

Obvious. Maybe bad pathname or a protection problem.

*3080,A
Warning 3080:  init_database got an ACCESS_FAILURE ...

Database could not be opened/created for some reason. The most-
likely cause is specifying an invalid directory in the
environment variable ABEL4DB, or damaging the database by
removing some internal files. There also could be a file
protection problem.

*3081,A
Warning 3081:  init_database got an ENVIRON_PROBLEM ...

In creating a database, the environment variable DB_DICT must
point to the directory containing the blank prototype database.


*3141,A
Warning 3141: could not open file xxx'

Could not find input file or there is a protection problem.

*3074,A
Warning 3074: File I/O problem, Could not open output stream xxx

Could not open the candidate device architecture list for writing.
May be bad pathname or a protection problem.

*3420,A
Warning 3420:  Problems with chip report file name xxx

The chip report file pathname did not pass the tests of illegal
characters or allowed length.

*3421,A
Warning 3421:  Note report file xxx could not be opened

The chip report file was not opened. Could be a bad pathname or a
protection problem.

*3468,A
Warning 3468: write error during chip report

The system could no longer write to the chip report file. Could be
an access problem or the disk is full.