7i43 BITFILE issue for UART TX

More
10 years 6 months ago - 10 years 6 months ago #73327 by gandalf
Hi,
I did lot of BITFILE compilation but now I have an issue trying to use UART TX.
I addedd in the .vhd bitfile Mudile ID section the line:

(UARTTTag, x"00", ClockLowTag, x"02", UARTTDataAddr&PadT, UARTTNumRegs, x"10", UARTTMPBitMask),

As Mudule ID structure definition in IDROMConst.vhd the stride is x"10"
type ModuleRecord is -- probably need an alternate way for smart modules
record
GTag : std_logic_vector(7 downto 0);
Version : std_logic_vector(7 downto 0);
Clock : std_logic_vector(7 downto 0);
NumInstances : std_logic_vector(7 downto 0);
BaseAddr : std_logic_vector(15 downto 0);
NumRegisters : std_logic_vector(7 downto 0);
Strides : std_logic_vector(7 downto 0);
MultRegs : std_logic_vector(31 downto 0);
end record;


type ModuleIDType is array(0 to MaxModules-1) of ModuleRecord;

Bitfile was compiled but when AXIS start I get the error:

hm2: loading Mesa HostMot2 driver version 0.15
hm2_7i43: loading HostMot2 Mesa 7i43 driver version 0.3
hm2/hm2_7i43.0: inconsistent Module Descriptor for UART Transmit Channel, not loading driver
hm2/hm2_7i43.0: Version = 0, expected 0
hm2/hm2_7i43.0: NumRegisters = 4, expected 4
hm2/hm2_7i43.0: InstanceStride = 0x00000040, expected 0x00000010
hm2/hm2_7i43.0: MultipleRegisters = 0x0000000F, expected 0x0000000F
hm2/hm2_7i43.0: inconsistent Module Descriptor!
hm2/hm2_7i43.0: failed to parse Module Descriptor 5

So it is reported strides is 0x40 and it expects 0x10 but strides is configured as 0x10 in vhd file.

I attach .BIT and .vhd, can someone try to load this bitfile for a 7i43 ?





Any idea? The source come from mesanet.com,
Last edit: 10 years 6 months ago by gandalf.

Please Log in or Create an account to join the conversation.

More
10 years 6 months ago #73328 by gandalf
Here the attachment

File Attachment:

File Name: 7I47_7I44_48.tgz
File Size:230 KB

Please Log in or Create an account to join the conversation.

More
10 years 6 months ago - 10 years 6 months ago #73329 by PCW
Replied by PCW on topic 7i43 BITFILE issue for UART TX
in the top level file, comment out the InstStride1: integer := 64; line and uncomment the InstStride1: integer := 16; line

InstStride1: integer := 64; -- instance stride 1 = 64 bytes = 16 x 32 bit registers sserial
-- InstStride1: integer := 16; -- 4..7 16 for BSPI/UART Ick double Ick

This does mean you cannot currently combine BSPI or UARTs with SSERIAL
(you can use the PktUART however)

I intend to fix this mess with the next IDROM version
Last edit: 10 years 6 months ago by PCW.
The following user(s) said Thank You: gandalf

Please Log in or Create an account to join the conversation.

More
10 years 6 months ago #73335 by gandalf
I will try PktUART.
Do hm2_uart_* API calls manage PktUART?
I am compiling source code from mesanet.com/software/parallel/7i43.zip , does it contain the latest source code version?

Please Log in or Create an account to join the conversation.

More
10 years 6 months ago #73356 by PCW
Replied by PCW on topic 7i43 BITFILE issue for UART TX
I'm not sure about PktUART support. It uses a different driver and I dont know if it has been merged with LinuxCNC (it was written for Machinkit)

the 7I43.zip file should be the latest
The following user(s) said Thank You: gandalf

Please Log in or Create an account to join the conversation.

More
10 years 6 months ago - 10 years 6 months ago #73373 by gandalf
I think I will wait for the next IDROM version. I have a 7i44 and I want to try to reserve few rj45 ports for SSERIAL and others for UART. It would be a very flexible communication solution.
Last edit: 10 years 6 months ago by gandalf.

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.064 seconds
Powered by Kunena Forum