- Hardware & Machines
- Driver Boards
- Where to learn to build or modify custom bit files for my Mesa cards?
Where to learn to build or modify custom bit files for my Mesa cards?
21 Feb 2023 15:15 #264960
by DrKnow65
I am looking to find information on how to modify / build / compile custom bit files for some of the Mesa boards I am using with my builds.
I have 7i90hd's on parallel ports, 7i90hd on a raspberry pi, 7i92tm's, and 7i98's. I have a hand full of daughter boards, 7i85s, 7i88, 7i67d, 7i77, etc.
For example if I wanted to build a bespoke daughter board to condition signals for stuff like IO with a couple PWM DAC outputs using the empty P3 port on a 7i98+7i85+7i77, and was going to experiment and iterate frequently, where would I learn to manipulate the bit files?
I will also be doing some connecting of inexpensive breakout boards (17-IO) to the 50pin headers (24-IO) on the 7i90hd's which would the have (7) unused IO pins that I could make use of in various ways.
Specifically I am looking to remove burden from the helpful folks here on the forum (mostly PCW) as I fumble and bumble my way through learning the EE side of customizing my own daughter board hardware.
Google is showing me no love
where do I go looking?
Jeff
I have 7i90hd's on parallel ports, 7i90hd on a raspberry pi, 7i92tm's, and 7i98's. I have a hand full of daughter boards, 7i85s, 7i88, 7i67d, 7i77, etc.
For example if I wanted to build a bespoke daughter board to condition signals for stuff like IO with a couple PWM DAC outputs using the empty P3 port on a 7i98+7i85+7i77, and was going to experiment and iterate frequently, where would I learn to manipulate the bit files?
I will also be doing some connecting of inexpensive breakout boards (17-IO) to the 50pin headers (24-IO) on the 7i90hd's which would the have (7) unused IO pins that I could make use of in various ways.
Specifically I am looking to remove burden from the helpful folks here on the forum (mostly PCW) as I fumble and bumble my way through learning the EE side of customizing my own daughter board hardware.
Google is showing me no love

Jeff
Please Log in or Create an account to join the conversation.
21 Feb 2023 16:13 #264964
by PCW
Replied by PCW on topic Where to learn to build or modify custom bit files for my Mesa cards?
Not the most up-to-date but covers the basics:
tom-itx.no-ip.biz:81/~webpage/emc/xilinx...14_install_index.php
tom-itx.no-ip.biz:81/~webpage/emc/xilinx...14_install_index.php
The following user(s) said Thank You: DrKnow65
Please Log in or Create an account to join the conversation.
28 Feb 2023 17:36 #265581
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
ERROR:HDLCompiler:104 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 71: Cannot find <ibound> in library <work>. Please ensure that the library was compiled, and that a library and a use clause are present in the VHDL file.
Parsing entity <inm>.
ERROR:HDLCompiler:854 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 73: Unit <inm> ignored due to previous errors.
Parsing architecture <behavioral> of entity <inm>.
ERROR:HDLCompiler:374 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 94: Entity <inm> is not yet compiled.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 95: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 96: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 97: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 98: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 99: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 100: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 101: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 102: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 103: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 104: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 105: <inwidth> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 107: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 108: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 109: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 110: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 111: <std_logic_vector> is not declared.
Sorry, too many errors..
Looks like I am either missing a dependancy somewhere, or there was a problem "merging" the file into ISE 14.7?
Any advise where I might begin the search?
Parsing entity <inm>.
ERROR:HDLCompiler:854 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 73: Unit <inm> ignored due to previous errors.
Parsing architecture <behavioral> of entity <inm>.
ERROR:HDLCompiler:374 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 94: Entity <inm> is not yet compiled.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 95: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 96: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 97: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 98: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 99: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 100: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 101: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 102: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 103: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 104: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 105: <inwidth> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 107: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 108: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 109: <std_logic> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 110: <std_logic_vector> is not declared.
ERROR:HDLCompiler:69 - "/home/jeffs/linuxcnc/configs/7i90/configs/hostmot2/source/hostmot2/inm.vhd" Line 111: <std_logic_vector> is not declared.
Sorry, too many errors..
Looks like I am either missing a dependancy somewhere, or there was a problem "merging" the file into ISE 14.7?
Any advise where I might begin the search?
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:04 #265582
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
I did " sudo apt install ghdl " without it changing anything, just for information.
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:16 #265583
by PCW
Replied by PCW on topic Where to learn to build or modify custom bit files for my Mesa cards?
The various project files may not be up-to-date
to fix, add the missing file to the project (ibound.vhd in this case)
(in the GUI right click in the file area and select add file)
to fix, add the missing file to the project (ibound.vhd in this case)
(in the GUI right click in the file area and select add file)
The following user(s) said Thank You: DrKnow65
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:19 #265585
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
"A known limitation of the new parser"
Not sure what exactly the procedures are for finding and adding the files and compiling the library again....
Not sure what exactly the procedures are for finding and adding the files and compiling the library again....
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:26 #265586
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
You nailed it, I didn't expect the inbound.vhd and oneshot.vhd to be in the dropdown to add as sources.
Thank you again.
I am now down to one error,
Map:258 - A problem was encountered attempting to get the license for this
architecture.
I suppose something here is proprietary and needs a signature maybe?
Thank you again.
I am now down to one error,
Map:258 - A problem was encountered attempting to get the license for this
architecture.
I suppose something here is proprietary and needs a signature maybe?
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:34 #265590
by PCW
Replied by PCW on topic Where to learn to build or modify custom bit files for my Mesa cards?
Did you register your copy of webpack?
Please Log in or Create an account to join the conversation.
28 Feb 2023 18:39 #265593
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
I did, but I also had to change an nvme that went sideways and it changed my MAC or something.
I found that my "Host ID Matches" was red for the ISE in the license manager though everything else was green.
Getting the license sorted now.
You are good at this
I'm working on getting better too.
I found that my "Host ID Matches" was red for the ISE in the license manager though everything else was green.
Getting the license sorted now.
You are good at this

Please Log in or Create an account to join the conversation.
28 Feb 2023 19:20 #265599
by DrKnow65
Replied by DrKnow65 on topic Where to learn to build or modify custom bit files for my Mesa cards?
"Network Interface Card (NIC) ID: 000000000000" on the license manager I suspect is where I am getting shut down.
I have the correct (licensed) mac showing up when I "ip link show" in the terminal, it just isn't populating in the license manager.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether nn:nn:nn:nn:nn:nn brd ff:ff:ff:ff:ff:ff
(the "nn:nn:nn:nn:nn:nn: is my redacted mac)
I wonder if the license manager is somehow populating with the link/loopback ID?
I think a good Linux user is a good troubleshooter. I'm trying to persevere...
I have the correct (licensed) mac showing up when I "ip link show" in the terminal, it just isn't populating in the license manager.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether nn:nn:nn:nn:nn:nn brd ff:ff:ff:ff:ff:ff
(the "nn:nn:nn:nn:nn:nn: is my redacted mac)
I wonder if the license manager is somehow populating with the link/loopback ID?
I think a good Linux user is a good troubleshooter. I'm trying to persevere...
Please Log in or Create an account to join the conversation.
- Hardware & Machines
- Driver Boards
- Where to learn to build or modify custom bit files for my Mesa cards?
Time to create page: 0.082 seconds