andypugh wrote: Look in the regmap file, that defines instance strides. (and lots of other things)
git.linuxcnc.org/gitweb?p=hostmot2-firmw...feddd7deb577;hb=HEAD
Thanks for your answer.
Did not know such a file is there. It is informative but it does not help me now
as Line 45 says:
45 Instance stride is address step to next register of same type but next channel
So if
sudo ./mesaflash --device 5i25 --readhmid yields:
Code:
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir
2 2 IOPort UARTTX 0 TXData (Out)
15 3 IOPort UARTRX 0 RXData (In)
is it correct that both UARTX and UARTRX belong to the same channel?
Or is this question senseless as UARTX and UARTRX are different types?
Anyway I get this error message:
Code:
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: inconsistent Module Descriptor for UART Transmit Channel, not loading driver
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: Version = 0, expected 0
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: NumRegisters = 4, expected 4
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: InstanceStride = 0x00000040, expected 0x00000010
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: MultipleRegisters = 0x0000000F, expected 0x0000000F
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: inconsistent Module Descriptor!
Nov 5 22:06:06 debian-cml2 msgd:0: hal_lib:3535:rt hm2/hm2_5i25.0: failed to parse Module Descriptor 5 of 8 gtag UART Transmit Channel
grep 'inconsistent Module Descriptor * , not loading driver' shows
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...d0908c8f5b7e9d1#l752
int hm2_md_is_consistent_or_complain(...) .
Variables of
hm2_module_descriptor_t *md are set one function before in
static int hm2_read_module_descriptors(hostmot2_t *hm2)
git.linuxcnc.org/gitweb?p=linuxcnc.git;a...d0908c8f5b7e9d1#l656
So let's look at the interesting part of the function:
Code:
static int hm2_read_module_descriptors(hostmot2_t *hm2) {
int addr = hm2->idrom_offset + hm2->idrom.offset_to_modules;
for (
hm2->num_mds = 0;
hm2->num_mds < HM2_MAX_MODULE_DESCRIPTORS;
hm2->num_mds ++, addr += 12
) {
rtapi_u32 d[3];
hm2_module_descriptor_t *md = &hm2->md[hm2->num_mds];
if (!hm2->llio->read(hm2->llio, addr, d, 12)) {
HM2_ERR("error reading Module Descriptor %d (at 0x%04x)\n", hm2->num_mds, addr);
return -EIO;
}
.................................................................................................................
md->base_address = (d[1] >> 00) & 0x0000FFFF;
md->num_registers = (d[1] >> 16) & 0x000000FF;
md->register_stride = (d[1] >> 24) & 0x0000000F;
if (md->register_stride == 0) {
md->register_stride = hm2->idrom.register_stride_0;
} else if (md->register_stride == 1) {
md->register_stride = hm2->idrom.register_stride_1;
} else {
HM2_ERR("Module Descriptor %d (at 0x%04x) has invalid RegisterStride %d\n", hm2->num_mds, addr, md->register_stride);
return -EINVAL;
}
md->instance_stride = (d[1] >> 28) & 0x0000000F;
if (md->instance_stride == 0) {
md->instance_stride = hm2->idrom.instance_stride_0;
} else if (md->instance_stride == 1) {
md->instance_stride = hm2->idrom.instance_stride_1;
} else {
HM2_ERR("Module Descriptor %d (at 0x%04x) has invalid InstanceStride %d\n", hm2->num_mds, addr, md->instance_stride);
return -EINVAL;
}
md->multiple_registers = d[2];
..........................................................................
}
return 0;
}
So in my case
d[1] for UARTTTag would consist of:
Code:
BASE ADDRESS, NUMBER OF REGISTERS, STRIDES
UARTTDataAddr&PadT, UARTTNumRegs, x"10"
x"61" & x"00" , x"04" , x"10"
01100001 00000000 , 00000100, 00010000
I suppose we have to turn over these 32 bits as otherwise the right shift operator would not make any sense.
So we have then:
Code:
00010000 00000100 01100001 00000000
Then these three make sense
Code:
md->base_address = (d[1] >> 00) & 0x0000FFFF; // = 0110000100000000
md->num_registers = (d[1] >> 16) & 0x000000FF; // = 00000100
md->register_stride = (d[1] >> 24) & 0x0000000F; // = 00000000
But what about:
Code:
md->instance_stride = (d[1] >> 28) & 0x0000000F; // = 00000001
if (md->instance_stride == 0) {
md->instance_stride = hm2->idrom.instance_stride_0;
then:
Code:
else if (md->instance_stride == 1) {
md->instance_stride = hm2->idrom.instance_stride_1; // 0x0000040:= 64 in decimal
}
This also confirms the error message from /var/log/linuxcnc.log.
However, we expect UARTS to have an Instance Stride equal to x"10" or 16 in decimal.
Is this a bug in hostmot2.c ?
