GitHub PushEvent at 2014-07-17 20:53:43
Repository: securePUF
Actor: praveendath92
Payload: {"shas":[["ebc4240bacab022627b9152eb1424b1096c04b2d","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","PDL constraint rellocations.","Praveen Kumar Pendyala",true],["44b40eeb5e30e4edbc294742f16d1feb5c765960","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Fixed slow read memory issue.\n\nAdded a wait time of 10 fast clock cycles for every read.","Praveen Kumar Pendyala",true],["9b350faa3338bffbd9cd22036a169145a5ff2011","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Added trigger choosing, generated challenge assign and ran tests\n\nWorking.","Praveen Kumar Pendyala",true],["86fd14b2f815d4a7d635b54e87c426c7ab986314","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","securePUF now gives results. Not the good ones though.\n\nTested with one of the challenge bits as response and siam's tests passed with good results. Tested one of the raw_responses as response in this version. Doesn't give so much good results. About ~59 - 90 (HEX) range on one test. Rest all 0s :(","Praveen Kumar Pendyala",true],["b438eff5bae205a29adb6e0b00f12eb5ab16f341","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Fixed double writing of last byte into test memory\n\nIssue introduced in last version. Not serious. Fixed.","Praveen Kumar Pendyala",true],["632c8b19200a5db05a22079744f7502fdba919ca","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Deleted obsolete backups.","Praveen Kumar Pendyala",true],["bb0f027da80310697d21aef81c6e6194fecf3633","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","First partially working full securePuf.\n\nThe PUF is failing some of the randomness tests though. Have to check if this is because of some of the trimmed signals in the randomness checking modules.","Praveen Kumar Pendyala",true],["595ab79b08594dcf05e6694cada13b9413ca1469","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Updated test_puf design in compliance with timing diagram planned.\n\ntrigger runs FSM and NIST. Negedge is used for FSM.","Praveen Kumar Pendyala",true],["9e96136d1d67afd74d33d7126fd0d44143387cb2","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Using shifted clk_1 as trigger. trigger = ~clk_1. Good results.\n\nThis ensures that FSM doesn't have to run at half the frequency and we won't be using a buffer (trigger) as clk to drive FSM - Siam's had some bad experience with using a buffer as clk.","Praveen Kumar Pendyala",true],["08dd12d6865d68011f377fc1c549110a7f3a45bb","d3a4a17a005686c349aeae1c66d68df23bcc7914@gmail.com","Tried with clk_1 as trigger and negedge clk_1 for FSM.\n\nResults are not as good as before :(","Praveen Kumar Pendyala",true]],"size":10,"ref":"refs/heads/master","head":"08dd12d6865d68011f377fc1c549110a7f3a45bb"}