Quote from: LateToTheParty on December 30, 2012, 01:59:38 PM

I had anticipated a few warnings/info messages, but 14,000 synthesis messages about trimming FF/Latches made me think I'd done something wrong. Is this as high as you'd expect?

I've been using the LX150_makomk_Test project as a start point. If these warnings are to be expected, I'll replace the ChipScope stuff with something else for comms (one of the other projects uses serial, I'll probably copy that) and go from there.

My comment about simulation was more directed at the use of the testbench code to smoke test the code before I program it. For the time being, I'm hoping there wont be much debugging required for the main algorithm!

Thanks for your help.

Don't sweat it....... the "trimming messages" are just the compiler doing its job.
As regards running, I hope you realize that again... hardware programming in NOT like C programming, you DO NOT debug on hardware, you debug in the simulator then when it works, you move to the hardware.

A simulation can compile in just under 15 seconds an "un-patitioned" "un-blackboxed" SHA256(SHA256(x)) compiled for hardware is going to take several hours,or on a portable maybe a day to compile.....

here is a 4 solution set.
Next thing you need.... is to find a 'solution" and use that in the test bed code:

Code:

00000001f1fc17f04446c70a6946bdfc0c50addb0157839b8226c2af000001a9000000005e8f39668534c41c8a3322239d6c0cfaf41c222ca8cb863929b440d5c48f38e0509057ad1a0513c5
00000001f1fc17f04446c70a6946bdfc0c50addb0157839b8226c2af000001a9000000005e8f39668534c41c8a3322239d6c0cfaf41c222ca8cb863929b440d5c48f38e0509057ad1a0513c5:b733aa28
00000001f1fc17f04446c70a6946bdfc0c50addb0157839b8226c2af000001a9000000005e8f39668534c41c8a3322239d6c0cfaf41c222ca8cb863929b440d5c48f38e0509057ad1a0513c5:1526ba33
00000001f1fc17f04446c70a6946bdfc0c50addb0157839b8226c2af000001a9000000005e8f39668534c41c8a3322239d6c0cfaf41c222ca8cb863929b440d5c48f38e0509057ad1a0513c5:c885e546
00000001f1fc17f04446c70a6946bdfc0c50addb0157839b8226c2af000001a9000000005e8f39668534c41c8a3322239d6c0cfaf41c222ca8cb863929b440d5c48f38e0509057ad1a0513c5:5b9c067f

Basically you load the hash into the test bench and set the nonce just below one of the solution values, then run the simulation.
You really do not want to scan the nonce from 0x00000000 to 0xffffffff, because the simulation will take forever to run.
Also watch the endian of the values above.