07/11/24

[badeaa3]

• [ ] 1. Debug the chip plugged in
• [ ] 2. Write routines to test IP1

[badeaa3]

Goal 1

Discussed with Cristian the scanLoad behavior we saw from #20. He is updating the firmware to set scanLoad to low for us to read out the data.

Status at the end of the day:

• scanIn is as expected
• scanLoad is as expected from update of Cristian firmware (low during the test = 2x768 bits)
• scanOut does not show anything on scope

[badeaa3]

Goal 2

This is a good opportunity to have Ben lead to write the python routines also. So we are going have the routines created by him.

1st routine

• test 3/4 (push slow or fast 1 MHz (divide by 100) clock to the configOut)
• write/read STATIC 0 and 1 then execute test 3/4 to see the clocks on the scope

2nd routine

• test 1 program all 5188 bits using fast clock
• program array 0 (4096) and array 1 (5188-4096). write/read back from ARRAY 0 and 1 and then execute test 1 in loopback mode to see it from OP_CODE_R_DATA_ARRAY_0 and OP_CODE_R_DATA_ARRAY_1

[badeaa3]

Things to check:

• Need ESD bracelets
• bonding diagram and mapping on the board
• things with Chinar
• look on the scope the scanOut pads to see if they are damaged
• is the board/chip actually damaged
• run IP2 test 2 where you parallel load and serial read
• force configClk manually 1 pin at a time
• scan power supply voltage and see if current at a certain point goes up
• check other output of chip like configOut (slow clock)