Appendix A.      blockHDL Error Messages

1            

Error reading blockdiagram/flowdiagram to be bound.        

Reason:   A corrupt file cannot be read into the workspace.

Solution: Check for flowdiagram file corruption.

If no information on file corruption is found, contact KBS.

2

Error initializing blockdiagram/flowdiagram tool with bound file. 

Reason:    A corrupt file cannot be read into the workspace. 

Solution:  Check for flowdiagram file corruption.

If no information on file corruption is found, contact KBS.

3

Error binding text file.

Reason:   Empty text files cannot be bound.

Solution: Define the contents of bind file.

Sections 5.6.2.1 and 6.2

4

Error re-binding block to blockdiagram/flowdiagram file.

Reason:   Blocks cannot be rebound directly.

Solution: Remove the current block binding and create a new binding.

Section 5.6.2.5

5

Error binding to pre-existing bound file.

Reason:   A file can only be bound to one block directly.

Solution: Bind block using reference or copy original bound block.

Section 6.1

6

File name is currently bound to another block in this workspace.

Reason:   Duplicate bound file names are not permitted  in the workspace.

Solution: Use another file name or bind block using reference or copy original bound block.

Section 6.1

7

Block is not empty.

Reason:   Block containing a structural description cannot be bound.

Solution:  Delete the contents of the block.

Section 6.1

8

No local blocks available for binding.

Reason:   There are not any local blocks to bind to.

Solution:  Describe other local blocks for binding.

Sections 5.6.2.4 and 6.5

9

No bound designs available for binding.

Reason:   There are not any references to bind to.

Solution: Create References by binding blocks to block diagram/flowdiagram designs.

Sections 5.6.2.2, 5.6.2.3, 6.3, and 6.4

10

Block bind file path invalid.

Reason:   Error during updating the bind file contents.

Solution: Check for correctness of path and file permissions.

If path and file permission is correct, contact KBS.

13

Read only block.

Reason:   Only locally defined/described blocks can be edited.

Solution: Select locally defined text or architectural blocks.

Section 6.6

15

Blockdiagram file is not selected.

Reason:   Operation requires a file name.

Solution: Highlight a block diagram file name.

Section 5.6.2.2

16

Export flowdiagram file is not selected.

Reason:   Operation requires a file name.

Solution: Highlight a flowdiagram file name.

Section 5.6.2.3, Chapter 9

17

Attempting to export block containing port width greater than 32 bits to flowHDL v 2.1.7 or lower.

Reason:   Block with ports of width greater than 32 cannot be exported to flowHDL v 2.1.7 or lower.

Solution: Export block files whose port widths are 32 or less or export to flowHDL v 2.2 or higher.

Section 5.6.3

18

Export HDL file is not selected.

Reason:   Operation requires a file name.

Solution: Highlight/specify a file name for HDL output.

Section 5.6.3

19

Blockdiagram bind file is not selected.

Reason:   Operation requires a file name.

Solution: Highlight a flowdiagram file name.

Sections 6.4 and 5.6.2.2

20

Blockdiagram file name is not entered.

Reason:   Operation requires a file name.

Solution: Enter a non-null value as a file name.

Section 5.6.2.2

21

Illegal block diagram file name.

Reason:   Operation requires a valid file name.

Solution: Enter a valid file name.

Section 5.6.2.2

22

Print file name is not entered.

Reason:   Operation requires a file name.

Solution: Enter a non-null value as a file name.

Section 5.1.5.1

23

Illegal print scale.

Reason:   Limits exist for print scale values.

Solution: Enter a value from 25 to 400.

Section 5.1.5.2

24

Design file name is not entered.

Reason:   Operation requires a file name.

Solution: Enter a non-null value as a file name.

Section 5.7.2.2

25

Design name is not entered.

Reason:   Operation requires a design name.

Solution: Enter a non-null value as a design name.   

Section 5.7.2.1

26

Design name is not legal.

Reason:   Operation requires a legal design name.

Solution: Use alphanumeric characters for the design name.

Section 5.7.2.1

27

Block name prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value block name prefix.

Section 5.7.3

28

Input pin/port prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value input pin/port name prefix.

Section 5.7.3

29

Output pin/port prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value output pin/port name prefix.

Section 5.7.3

30

Buffer pin/port prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value buffer pin/port name prefix.

Section 5.7.3

31

Bidirectional pin/port prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value bidirectional pin/port name prefix.

Section 5.7.3

32

Junction box prefix is not entered.

Reason:   Null prefix value is not acceptable.

Solution: Enter a non-null value as a junction box name prefix.

Section 5.7.3

33

Block name is not entered.

Reason:   Null block name is not acceptable.

Solution: Enter a non-null value as a block name.

Section 4.1

34

Pin name is not entered.

Reason:   Null pin name is not acceptable.

Solution: Enter a non-null value as a pin name.

Sections 4.6 through 4.9

35

Port name is not entered.

Reason:   Null port name is not acceptable.

Solution: Enter a non-null value as a port name.

Sections 4.2 through 4.5

36