Hi Sharat,
To give some context:
The adc5g has four cores, each of which has 8 parallel output lanes for the
8 bits of data. The software puts the adc in test mode, so that all cores
output a sample of 0xff, followed by 7 samples of 0x00. The delays of the
data lines relative to the clock are scanned and the number of glitches
counted for each bit. 0 glitches is good, anything other than 0 glitches
represents a bad clock and data phase relationship.
Looking at the scans from your debug messages, three of the cores behave as
expected -- that is, there are regions for all bits where the sampling of
the test pattern is glitch free. As the code suggests, the error comes
because bit 1 of core 3 appears to never be glitch free, no matter what the
delay setting. It's not obvious to me what could cause this. The script
should have lines for plotting that you can uncomment -- it would be
interesting to see what the output from different cores/bits looks like
before you run the calibration search to see if that suggests anything
useful about what's going on.
If you had another adc to test that would help rule out a genuine hardware
problem.
I assume your design met timing(?) If you clock it slower than you compiled
for, does it behave the same way?
Jack
On 6 September 2015 at 21:59, sharat varma <va...@hku.hk> wrote:
> Hi Jack,
>
> Thank you for the test scripts.
> When I run your script I get the following error. What could be the
> possible reason? I have not connected any input laft it floating as I have
> read that the ADC has its own ramp input which is used for the calibration.
> I have connected at 2500MHz clock. Hope I am not doing anything wrong.
>
> Regards,
> Sharat
>
> When I run test_cal
>
>
> 2015-09-07 12:59:55,761 - adc5g.tools - INFO - adc5g imported
> 2015-09-07 12:59:56,641 - adc5g.tools - DEBUG - setting delay 0
> 2015-09-07 12:59:57,236 - adc5g.tools - DEBUG - setting delay 1
> 2015-09-07 12:59:57,828 - adc5g.tools - DEBUG - setting delay 2
> 2015-09-07 12:59:58,420 - adc5g.tools - DEBUG - setting delay 3
> 2015-09-07 12:59:59,012 - adc5g.tools - DEBUG - setting delay 4
> 2015-09-07 12:59:59,605 - adc5g.tools - DEBUG - setting delay 5
> 2015-09-07 13:00:00,197 - adc5g.tools - DEBUG - setting delay 6
> 2015-09-07 13:00:00,788 - adc5g.tools - DEBUG - setting delay 7
> 2015-09-07 13:00:01,375 - adc5g.tools - DEBUG - setting delay 8
> 2015-09-07 13:00:01,962 - adc5g.tools - DEBUG - setting delay 9
> 2015-09-07 13:00:02,548 - adc5g.tools - DEBUG - setting delay 10
> 2015-09-07 13:00:03,134 - adc5g.tools - DEBUG - setting delay 11
> 2015-09-07 13:00:03,726 - adc5g.tools - DEBUG - setting delay 12
> 2015-09-07 13:00:04,313 - adc5g.tools - DEBUG - setting delay 13
> 2015-09-07 13:00:04,905 - adc5g.tools - DEBUG - setting delay 14
> 2015-09-07 13:00:05,498 - adc5g.tools - DEBUG - setting delay 15
> 2015-09-07 13:00:06,092 - adc5g.tools - DEBUG - setting delay 16
> 2015-09-07 13:00:06,686 - adc5g.tools - DEBUG - setting delay 17
> 2015-09-07 13:00:07,281 - adc5g.tools - DEBUG - setting delay 18
> 2015-09-07 13:00:07,872 - adc5g.tools - DEBUG - setting delay 19
> 2015-09-07 13:00:08,460 - adc5g.tools - DEBUG - setting delay 20
> 2015-09-07 13:00:09,057 - adc5g.tools - DEBUG - setting delay 21
> 2015-09-07 13:00:09,648 - adc5g.tools - DEBUG - setting delay 22
> 2015-09-07 13:00:10,237 - adc5g.tools - DEBUG - setting delay 23
> 2015-09-07 13:00:10,828 - adc5g.tools - DEBUG - setting delay 24
> 2015-09-07 13:00:11,415 - adc5g.tools - DEBUG - setting delay 25
> 2015-09-07 13:00:12,009 - adc5g.tools - DEBUG - setting delay 26
> 2015-09-07 13:00:12,600 - adc5g.tools - DEBUG - setting delay 27
> 2015-09-07 13:00:13,191 - adc5g.tools - DEBUG - setting delay 28
> 2015-09-07 13:00:13,787 - adc5g.tools - DEBUG - setting delay 29
> 2015-09-07 13:00:14,380 - adc5g.tools - DEBUG - setting delay 30
> 2015-09-07 13:00:14,972 - adc5g.tools - DEBUG - setting delay 31
> 2015-09-07 13:00:15,564 - adc5g.tools - DEBUG - ##### GLITCHES
> FOR CORE 0 BY IODELAY #####
> 2015-09-07 13:00:15,564 - adc5g.tools - DEBUG - 0: 0 0 0
> 0 41 0 0 0TOTAL 41
> 2015-09-07 13:00:15,564 - adc5g.tools - DEBUG - 1: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,564 - adc5g.tools - DEBUG - 2: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,564 - adc5g.tools - DEBUG - 3: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 4: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 5: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 6: 0 108 4
> 0 0 0 0 100TOTAL 212
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 7: 54 593 584
> 304 0 174 12 368TOTAL 2089
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 8: 599 6 0
> 577 227 383 580 371TOTAL 2743
> 2015-09-07 13:00:15,565 - adc5g.tools - DEBUG - 9: 27 0 0
> 0 371 2 222 291TOTAL 913
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 10: 0 0 0
> 0 2 0 0 0TOTAL 2
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 11: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 12: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 13: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 14: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,566 - adc5g.tools - DEBUG - 15: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 16: 0 135 137
> 0 0 0 0 0TOTAL 272
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 17: 417 726 337
> 524 0 165 6 291TOTAL 2466
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 18: 465 73 0
> 157 230 371 651 371TOTAL 2318
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 19: 0 0 0
> 0 353 2 471 369TOTAL 1195
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 20: 0 0 0
> 0 0 0 0 42TOTAL 42
> 2015-09-07 13:00:15,567 - adc5g.tools - DEBUG - 21: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,568 - adc5g.tools - DEBUG - 22: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,568 - adc5g.tools - DEBUG - 23: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,568 - adc5g.tools - DEBUG - 24: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,568 - adc5g.tools - DEBUG - 25: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,568 - adc5g.tools - DEBUG - 26: 3 72 220
> 3 0 0 0 0TOTAL 298
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - 27: 496 584 421
> 660 0 56 0 20TOTAL 2237
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - 28: 403 214 0
> 89 141 371 319 362TOTAL 1899
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - 29: 0 0 0
> 0 371 152 534 372TOTAL 1429
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - 30: 0 0 0
> 0 56 0 3 370TOTAL 429
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - 31: 0 0 0
> 0 0 0 0 18TOTAL 18
> 2015-09-07 13:00:15,569 - adc5g.tools - DEBUG - ##### GLITCHES
> FOR CORE 1 BY IODELAY #####
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 0: 02419 0
> 0 0 0 0 0TOTAL 2419
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 1: 02423 0
> 0 0 0 0 0TOTAL 2423
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 2: 02410 0
> 0 0 0 0 0TOTAL 2410
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 3: 02421 0
> 0 0 0 0 0TOTAL 2421
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 4: 02406 0
> 0 0 0 0 0TOTAL 2406
> 2015-09-07 13:00:15,570 - adc5g.tools - DEBUG - 5: 02422 0
> 0 0 0 0 0TOTAL 2422
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 6: 02408 0
> 272 0 0 2 404TOTAL 3086
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 7: 3672408 471
> 339 239 589 403 86TOTAL 4902
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 8: 1072409 54
> 0 397 12 167 0TOTAL 3146
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 9: 02432 0
> 0 2 0 0 0TOTAL 2434
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 10: 02434 0
> 0 0 0 0 0TOTAL 2434
> 2015-09-07 13:00:15,571 - adc5g.tools - DEBUG - 11: 02432 0
> 0 0 0 0 0TOTAL 2432
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 12: 02420 0
> 0 0 0 0 0TOTAL 2420
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 13: 02430 0
> 0 0 0 0 0TOTAL 2430
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 14: 02431 0
> 0 0 0 0 0TOTAL 2431
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 15: 02422 0
> 4 0 0 0 14TOTAL 2440
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 16: 02409 4
> 643 0 0 8 359TOTAL 3423
> 2015-09-07 13:00:15,572 - adc5g.tools - DEBUG - 17: 3622390 601
> 46 330 486 370 6TOTAL 4591
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 18: 852416 18
> 0 354 38 294 0TOTAL 3205
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 19: 02433 0
> 0 0 0 0 0TOTAL 2433
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 20: 02412 0
> 0 0 0 0 0TOTAL 2412
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 21: 02412 0
> 0 0 0 0 0TOTAL 2412
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 22: 02415 0
> 0 0 0 0 0TOTAL 2415
> 2015-09-07 13:00:15,573 - adc5g.tools - DEBUG - 23: 02432 0
> 0 0 0 0 0TOTAL 2432
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 24: 02409 0
> 0 0 0 0 0TOTAL 2409
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 25: 02409 0
> 2 0 0 0 110TOTAL 2521
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 26: 02415 2
> 620 0 0 0 361TOTAL 3398
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 27: 2122390 413
> 89 204 73 138 12TOTAL 3531
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 28: 2482390 190
> 0 371 334 371 0TOTAL 3904
> 2015-09-07 13:00:15,574 - adc5g.tools - DEBUG - 29: 02423 0
> 0 52 0 203 0TOTAL 2678
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - 30: 02413 0
> 0 0 0 0 0TOTAL 2413
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - 31: 02423 0
> 0 0 0 0 0TOTAL 2423
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - ##### GLITCHES
> FOR CORE 2 BY IODELAY #####
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - 0: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - 1: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,575 - adc5g.tools - DEBUG - 2: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 3: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 4: 0 0 0
> 0 19 0 0 0TOTAL 19
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 5: 0 0 0
> 9 353 0 48 102TOTAL 512
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 6: 0 33 427
> 687 374 8 371 371TOTAL 2271
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 7: 324 613 873
> 45 20 363 367 255TOTAL 2860
> 2015-09-07 13:00:15,576 - adc5g.tools - DEBUG - 8: 597 0 156
> 0 0 2 0 0TOTAL 755
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 9: 63 0 0
> 0 0 0 0 0TOTAL 63
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 10: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 11: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 12: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 13: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,577 - adc5g.tools - DEBUG - 14: 0 0 0
> 0 20 0 0 0TOTAL 20
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 15: 0 0 0
> 275 377 0 2 177TOTAL 831
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 16: 0 200 321
> 448 312 8 330 371TOTAL 1990
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 17: 366 484 962
> 0 0 385 369 20TOTAL 2586
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 18: 573 0 423
> 0 0 4 40 0TOTAL 1040
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 19: 6 0 0
> 0 0 0 0 0TOTAL 6
> 2015-09-07 13:00:15,578 - adc5g.tools - DEBUG - 20: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 21: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 22: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 23: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 24: 0 0 0
> 8 5 0 0 0TOTAL 13
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 25: 0 0 0
> 674 418 0 0 223TOTAL 1315
> 2015-09-07 13:00:15,579 - adc5g.tools - DEBUG - 26: 0 249 15
> 21 169 0 45 366TOTAL 865
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - 27: 179 407 539
> 0 0 305 371 71TOTAL 1872
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - 28: 639 14 552
> 0 0 261 347 0TOTAL 1813
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - 29: 0 0 3
> 0 0 0 10 0TOTAL 13
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - 30: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - 31: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,580 - adc5g.tools - DEBUG - ##### GLITCHES
> FOR CORE 3 BY IODELAY #####
> 2015-09-07 13:00:15,581 - adc5g.tools - DEBUG - 0: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,581 - adc5g.tools - DEBUG - 1: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,581 - adc5g.tools - DEBUG - 2: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,581 - adc5g.tools - DEBUG - 3: 0 0 52
> 0 0 0 0 0TOTAL 52
> 2015-09-07 13:00:15,581 - adc5g.tools - DEBUG - 4: 0 180 370
> 152 42 0 15 0TOTAL 759
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 5: 80 551 124
> 253 515 227 578 261TOTAL 2589
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 6: 639 0 0
> 0 0 211 30 671TOTAL 1551
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 7: 18 0 0
> 0 0 0 0 83TOTAL 101
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 8: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 9: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,582 - adc5g.tools - DEBUG - 10: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 11: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 12: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 13: 0 0 141
> 0 0 0 0 0TOTAL 141
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 14: 0 539 495
> 391 41 0 3 0TOTAL 1469
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 15: 271 264 2
> 162 519 383 548 227TOTAL 2376
> 2015-09-07 13:00:15,583 - adc5g.tools - DEBUG - 16: 322 0 0
> 0 0 50 159 706TOTAL 1237
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 17: 0 0 0
> 0 0 0 0 276TOTAL 276
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 18: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 19: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 20: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 21: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,584 - adc5g.tools - DEBUG - 22: 0 0 2
> 0 0 0 0 0TOTAL 2
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 23: 0 69 355
> 2 0 0 0 0TOTAL 426
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 24: 0 441 303
> 354 37 0 0 0TOTAL 1135
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 25: 259 78 0
> 276 529 350 147 30TOTAL 1669
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 26: 401 0 0
> 0 0 117 540 636TOTAL 1694
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 27: 2 0 0
> 0 0 0 0 302TOTAL 304
> 2015-09-07 13:00:15,585 - adc5g.tools - DEBUG - 28: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,586 - adc5g.tools - DEBUG - 29: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,586 - adc5g.tools - DEBUG - 30: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,586 - adc5g.tools - DEBUG - 31: 0 0 0
> 0 0 0 0 0TOTAL 0
> 2015-09-07 13:00:15,587 - adc5g.tools - DEBUG - tap_delay: 78.1 ps
> 2015-09-07 13:00:15,588 - adc5g.tools - DEBUG - taps_per_cycle:
> 10.2
> 2015-09-07 13:00:15,588 - adc5g.tools - DEBUG - Starting search
> for bit 0 eye at tap 5
> 2015-09-07 13:00:15,588 - adc5g.tools - DEBUG - found first
> glitch at 7
> 2015-09-07 13:00:15,588 - adc5g.tools - DEBUG - found eye start
> at 10
> 2015-09-07 13:00:15,588 - adc5g.tools - DEBUG - glitches
> before eye: 27
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - glitches
> after eye: 417
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - EYE CENTRE at
> 13.0
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - NEW START
> SEARCH REFERENCE POINT IS 3
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - Starting search
> for bit 1 eye at tap 3
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - found first
> glitch at 6
> 2015-09-07 13:00:15,589 - adc5g.tools - DEBUG - found eye start
> at 9
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - glitches
> before eye: 6
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - found eye end
> at 15
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - glitches
> after eye: 135
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - EYE CENTRE at
> 12.0
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - Starting search
> for bit 2 eye at tap 3
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - found first
> glitch at 6
> 2015-09-07 13:00:15,590 - adc5g.tools - DEBUG - found eye start
> at 8
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - glitches
> before eye: 584
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - found eye end
> at 15
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - glitches
> after eye: 137
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - EYE CENTRE at
> 11.5
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - TIEBREAK: EYE
> CENTRE at 12
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - Starting search
> for bit 3 eye at tap 3
> 2015-09-07 13:00:15,591 - adc5g.tools - DEBUG - found first
> glitch at 7
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - found eye start
> at 9
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - glitches
> before eye: 577
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - glitches
> after eye: 524
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - EYE CENTRE at
> 12.5
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - TIEBREAK: EYE
> CENTRE at 13
> 2015-09-07 13:00:15,592 - adc5g.tools - DEBUG - Starting search
> for bit 4 eye at tap 3
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - found first
> glitch at 8
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - found eye start
> at 11
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - glitches
> before eye: 2
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - found eye end
> at 17
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - glitches
> after eye: 230
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - EYE CENTRE at
> 14.0
> 2015-09-07 13:00:15,593 - adc5g.tools - DEBUG - Starting search
> for bit 5 eye at tap 3
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - found first
> glitch at 7
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - found eye start
> at 10
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - glitches
> before eye: 2
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - glitches
> after eye: 165
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - EYE CENTRE at
> 13.0
> 2015-09-07 13:00:15,594 - adc5g.tools - DEBUG - Starting search
> for bit 6 eye at tap 3
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - found first
> glitch at 7
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - found eye start
> at 10
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - glitches
> before eye: 222
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - glitches
> after eye: 6
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - EYE CENTRE at
> 13.0
> 2015-09-07 13:00:15,595 - adc5g.tools - DEBUG - Starting search
> for bit 7 eye at tap 3
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - found first
> glitch at 6
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - found eye start
> at 10
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - glitches
> before eye: 291
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - glitches
> after eye: 291
> 2015-09-07 13:00:15,596 - adc5g.tools - DEBUG - EYE CENTRE at
> 13.0
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - tap_delay: 78.1 ps
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - taps_per_cycle:
> 10.2
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - Starting search
> for bit 0 eye at tap 3
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - found first
> glitch at 7
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - found eye start
> at 9
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - glitches
> before eye: 107
> 2015-09-07 13:00:15,597 - adc5g.tools - DEBUG - found eye end
> at 16
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - glitches
> after eye: 362
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - EYE CENTRE at
> 12.5
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - TIEBREAK: EYE
> CENTRE at 12
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - NEW START
> SEARCH REFERENCE POINT IS 2
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - Starting search
> for bit 1 eye at tap 2
> 2015-09-07 13:00:15,598 - adc5g.tools - DEBUG - found first
> glitch at 2
> 2015-09-07 13:00:15,599 - adc5g.tools - CRITICAL - Couldn't find
> start of eye!
> Traceback (most recent call last):
> File "test_cal.py", line 25, in <module>
> adc5g.calibrate_all_delays(r, 0, snaps=[SNAPNAME], verbosity=5)
> File
> "/home/nfs/roach2/debian_stable_devel/boffiles/varma/adc_tests-disentangle/adc5g/tools.py",
> line 352, in calibrate_all_delays
> best_delay[core] =
> find_best_delay(glitches[core],verbose=(verbosity>2),reference=best_delay[0,0])
> File
> "/home/nfs/roach2/debian_stable_devel/boffiles/varma/adc_tests-disentangle/adc5g/tools.py",
> line 253, in find_best_delay
> raise Exception("Couldn't find start of eye")
> Exception: Couldn't find start of eye
>
> ********************************
> When I run
> test_adc ZDOCK 0
>
> breaking at ps:0 with 9651 glitches
> test if calibration finds optimal MMCM phase ... FAIL
>
> ======================================================================
> FAIL: test if calibration finds optimal MMCM phase
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "test_adc5g.py", line 105, in test_optimal_solution_found
> self.assertIsNotNone(self._optimal_phase)
> AssertionError: unexpectedly None
>
> ----------------------------------------------------------------------
> Ran 8 tests in 7.293s
>
> FAILED (failures=1)
> ************************
> When I run test _adc ZDOCK 1
> breaking at ps:0 with 238 glitches
> test if calibration finds optimal MMCM phase ... FAIL
>
> ======================================================================
> FAIL: test if calibration finds optimal MMCM phase
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "test_adc5g.py", line 105, in test_optimal_solution_found
> self.assertIsNotNone(self._optimal_phase)
> AssertionError: unexpectedly None
>
> ----------------------------------------------------------------------
> Ran 8 tests in 7.033s
>
>
> On 6 September 2015 at 08:40, Jack Hickish <jackhick...@gmail.com> wrote:
>
>> Hi Sharat,
>>
>> The disentangle(!) branch at
>> https://github.com/jack-h/adc_tests/tree/disentangle has my calibration
>> code. If you check out that branch and install it (cd adc5g; python
>> setup.py install) then the test_cal.py script is a simple template for
>> calibrating. If it doesn't work it should also print/plot various helpful
>> things that will help figure out what's wrong.
>> Turns out I don't actually have a working adc5g here, except in demux 1:2
>> configuration, so I haven't been able to test the code with your boffile.
>> Having said that, with the 2:1 demux card, it seems to behave sanely for
>> the bits that one would expect to work.
>>
>> Cheers,
>> Jack
>>
>> On Fri, 4 Sep 2015 at 04:48 sharat varma <va...@hku.hk> wrote:
>>
>>> Hi Rurik,
>>>
>>> Yes. I used the boffile ver2. I also generated bof using model file and
>>> tried using it. I checked both the ADCs using -z option. I get the same
>>> error.
>>>
>>> Thanks and regards,
>>> Sharat
>>> On 4 Sep 2015 18:37, "Primiani, Rurik" <rprimi...@cfa.harvard.edu>
>>> wrote:
>>>
>>>> Hi Sharat,
>>>>
>>>> Are you using the revision 1 or revision 2 version of the test suite
>>>> bitcode and does this match the version of the board that you have? By
>>>> default it uses revision 2 which is probably what you have but just to make
>>>> sure. To use the other bitcode you would need to use the -b flag with
>>>> test_adc5g.py.
>>>>
>>>> The adc_test provided bitcode and test script *should* work out of the
>>>> box. Have you tried running the test on ZDOK 1, you can use -z 1 for that.
>>>>
>>>> Best,
>>>> Rurik
>>>>
>>>>
>>>> On Fri, Sep 4, 2015 at 12:01 AM, sharat varma <va...@hku.hk> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thanks for the reply and sorry for the delayed response.
>>>>> Yes, the x-axis represent the time and y-axis represents the signed 8
>>>>> bit output. The negative bias is due to the nature of the input.
>>>>>
>>>>> I was trying to use the files in the link you mentioned, but I keep
>>>>> getting the error shown below. I am using the bof file provided for
>>>>> roach2.
>>>>>
>>>>> test roach connectivity ... ok
>>>>> check if requested bof is available ... ok
>>>>> test roach pingability ... ok
>>>>> program the requested bof ... ok
>>>>> estimate clock rate, should be within 1 MHz of expected ... ok
>>>>> confirm the design has the ADC SPI controller ... ok
>>>>> confirm the design has the needed scope ... ok
>>>>> test if calibration finds optimal MMCM phase ... FAIL
>>>>>
>>>>> ======================================================================
>>>>> FAIL: test if calibration finds optimal MMCM phase
>>>>> ----------------------------------------------------------------------
>>>>> Traceback (most recent call last):
>>>>> File "test_adc5g.py", line 107, in test_optimal_solution_found
>>>>> self.assertIsNotNone(self._optimal_phase)
>>>>> AssertionError: unexpectedly None
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> Ran 8 tests in 7.230s
>>>>>
>>>>> FAILED (failures=1)
>>>>>
>>>>> Please let me know if I am doing anything wrong or where could be the
>>>>> problem.
>>>>>
>>>>> For your information:
>>>>>
>>>>> System: roach2
>>>>>
>>>>> ADC : ASIAA ADC5G ADC
>>>>>
>>>>> Clock : 2500MHz.
>>>>>
>>>>> Thanks and regards,
>>>>>
>>>>> Sharat
>>>>>
>>>>>
>>>>> On 1 September 2015 at 23:01, Primiani, Rurik <
>>>>> rprimi...@cfa.harvard.edu> wrote:
>>>>>
>>>>>> Hi Sharat,
>>>>>>
>>>>>> The plot you provided has no labels or units so I will assume the
>>>>>> x-axis represents time in samples and the y-axis represents signed 8-bit
>>>>>> sample values. I'm not sure why there is such a negative bias but perhaps
>>>>>> that's particular to your instrument.
>>>>>>
>>>>>> Please, at the very least, run the MMCM calibration described at
>>>>>> https://github.com/sma-wideband/adc_tests to reduce glitches on the
>>>>>> interface. I believe Jack also has a more sophisticated approach which
>>>>>> adjusts the IODELAY for each individual data line; sadly I don't have a
>>>>>> link handy for that.
>>>>>>
>>>>>> Although you may not see these glitches with a sine wave, a
>>>>>> noise-like signal will cause more transitions on each bit and thus more
>>>>>> glitches with an uncalibrated interface.
>>>>>>
>>>>>> Thanks,
>>>>>> Rurik
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Sep 1, 2015 at 2:54 AM, sharat varma <va...@hku.hk> wrote:
>>>>>>
>>>>>>> Hi Jack,
>>>>>>>
>>>>>>> Thanks for the reply.
>>>>>>>
>>>>>>> I did not run mmcm calibration. Actually, we checked the ADC by
>>>>>>> feeding it a low frequency sine wave from a function generator and it
>>>>>>> works
>>>>>>> fine.
>>>>>>>
>>>>>>> The problem with spikes occurs when we feed the ADC with the
>>>>>>> photo-detector output.
>>>>>>>
>>>>>>> Regards,
>>>>>>> Sharat
>>>>>>>
>>>>>>>
>>>>>>> On 1 September 2015 at 13:52, Jack Hickish <jackhick...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Sharat,
>>>>>>>>
>>>>>>>> Are you running the adc mmcm calibration routine after programming
>>>>>>>> your roach?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Jack
>>>>>>>>
>>>>>>>> On 31 August 2015 at 22:41, sharat varma <va...@hku.hk> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi Casper,
>>>>>>>>>
>>>>>>>>> I am working as a post-doc working under guidance of Dr. Hayden So
>>>>>>>>> at The University of Hong Kong.
>>>>>>>>>
>>>>>>>>> We are using ROACH2 to capture data from optical cytometry. We are
>>>>>>>>> using ASIAA ADC5G ADC to capture data at 4 to 5 Gsps.
>>>>>>>>>
>>>>>>>>> We basically use the following parameters.
>>>>>>>>>
>>>>>>>>> Block parameter: two-channel, ZDOK0, demux 1:1 .
>>>>>>>>> System: roach2, clock source:adc0_clk, clock rate: 300 MHz.
>>>>>>>>>
>>>>>>>>> We are connecting the output of a photo-detector 1544-B from
>>>>>>>>> Newport Corp (the spec is attached) to the ADC input using SMA.
>>>>>>>>> We find that noisy spikes are introduced when we capture the data
>>>>>>>>> through the ADC (see attached fig). We double checked if the source
>>>>>>>>> had
>>>>>>>>> problems using a oscilloscope, but on the oscilloscope we do not see
>>>>>>>>> any of
>>>>>>>>> these spikes.
>>>>>>>>>
>>>>>>>>> We would be grateful if you could let us know if we are doing
>>>>>>>>> anything wrong.
>>>>>>>>>
>>>>>>>>> Rgards,
>>>>>>>>> Sharat
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>
