Do you have any suggestions on which register I should check to resolve my problem?Īny insights on what may be wrong or how to troubleshoot this problem would be extremely helpful. In case I do not configure the AD9172 properly. Could you tell me how the computed checksum was generated?ģ. Is there any possibility that the AD9172 failed to calculate the computed checksum of lane 6?Ģ. 0x436 = 0x54 (lane 5), 0x446 = 0x56 (lane 7)Īs you can see that the computed checksum of lane 6 was wrong and it equaled the value of lane 5. 0x43E = 0x54 (computed checksum of lane 6) which was equal to the computed checksum of lane 5. SHA-512 is 51.7 slower that SHA-1 for short strings and 20. SHA-256 is 15.5 slower than SHA-1 for short strings and 23.4 for longer strings. MD5 is 7.6 slower than SHA-1 for short strings and 1.3 for longer strings. 0x43D = 0x55 (received checksum of lane 6)ħ. SHA-1 is fastest hashing function with 587.9 ms per 1M operations for short strings and 881.7 ms per 1M for longer strings. They were matched with each other and the link parameters above.Ħ. 0x472 = 0xBF (checksum is incorrect on lane 6)ĥ. The actual run out of the tire can be as much as 2 to 3 inches less than what the circumference of the tire measures. 0x470 = 0xFF (CGS achieved on all lanes)ģ. To determine your tires true diameter in relation to determining what speedometer gears you need, measure from the ground up to the center of the axle then multiply by two. The problem is that after successfully configuring all the devices, I checked registers on AD9172 for link status and I observed that the good_checksum bit for lane 6 (LID=6) was 0 which meant the checksum is not correct. On FPGA, I use JESD204 IPs from Analog Devices to communicate with AD9172 through multiple gigabit lanes. I'm using a VCU128 FPGA board to push data to a DAC9172 on the HTG board ( part number: HTG-FMC-12ADC-16DAC).
0 kommentar(er)
