IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
18 Dec 2023 02:20 #288451
by cornholio
I have some firmware I'm writing for a RV901T, spartan 6 based,
same card I was playing with for a SSREMOTE.
Setup has 2 ports with a 19 pins per port, modified mesaflash to recognise my board and all is good with the world.
The only issue I have is when loading the driver, based on the 7i90 EPP driver, I've had success modifying this driver to work with a 7c81 via EPP. The firmware I created was just 38 gpio pins. I saw some threads regarding the 7i93 & 7i98, but that didn't really help my situation. Any help would be great.
I'll include a dump of --readhmid via mesaflash.
Setup has 2 ports with a 19 pins per port, modified mesaflash to recognise my board and all is good with the world.
The only issue I have is when loading the driver, based on the 7i90 EPP driver, I've had success modifying this driver to work with a 7c81 via EPP. The firmware I created was just 38 gpio pins. I saw some threads regarding the 7i93 & 7i98, but that didn't really help my situation. Any help would be great.
I'll include a dump of --readhmid via mesaflash.
Attachments:
Please Log in or Create an account to join the conversation.
18 Dec 2023 02:28 #288453
by PCW
Replied by PCW on topic IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
The number of I/O ports in your pinout file does not match the number in your xxxcard file
Please Log in or Create an account to join the conversation.
18 Dec 2023 02:44 #288454
by cornholio
Replied by cornholio on topic IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
Card file seems ok, the guts
Pin file has 32 Module_ID entries.
I have 38 pins defined followed by 106 empty pin entries.
Mesa flash seems to detect everything and has no probs writing to flash.
package r01e_x16card is
-- r01e_x16 card specific info
constant ClockHigh: integer := ClockHigh90;
constant ClockMed: integer := ClockMed90;
constant ClockLow: integer := ClockLow90;
constant BoardNameLow : std_Logic_Vector(31 downto 0) := BoardNameMESA;
constant BoardNameHigh : std_Logic_Vector(31 downto 0) := BoardName9R01E;
constant FPGASize: integer := 16;
constant FPGAPins: integer := 256;
constant IOPorts: integer := 2;
constant IOWidth: integer := 38;
constant PortWidth: integer := 19;
constant LIOWidth: integer := 0; -- just txen on rev c cards
constant LEDCount: integer := 2;
constant SepClocks: boolean := true;
constant OneWS: boolean := false;
end package r01e_x16card;Pin file has 32 Module_ID entries.
I have 38 pins defined followed by 106 empty pin entries.
Mesa flash seems to detect everything and has no probs writing to flash.
Please Log in or Create an account to join the conversation.
18 Dec 2023 02:47 - 18 Dec 2023 02:47 #288455
by PCW
Replied by PCW on topic IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
Does your pinout file specify 2 I/O ports?
Last edit: 18 Dec 2023 02:47 by PCW.
Please Log in or Create an account to join the conversation.
18 Dec 2023 03:03 #288457
by cornholio
Replied by cornholio on topic IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
That would be the on the IOPortTag line the value after ClockLowTag ? Which is NumInstances of the ModuleRecord ?
Sorry for such a glaring mistake.
Sorry for such a glaring mistake.
Please Log in or Create an account to join the conversation.
18 Dec 2023 03:28 #288458
by PCW
Replied by PCW on topic IDROM IOPorts is 2 but MD IOPort NumInstances is 3, inconsistent
(IOPortTag, x"00", ClockLowTag, x"02", PortAddr&PadT, IOPortNumRegs, x"00", IOPortMPBitMask),
The following user(s) said Thank You: cornholio
Please Log in or Create an account to join the conversation.
Time to create page: 0.148 seconds