I played a little around an found out, that the nonce does'nt have to change the endian on arm.
Is it normal that a Generated target looks like this:
Generated target 0000000000000000000000000000000000000000000000ffff00020d7800780d
on a working stratum machine, it look like this:
[2012-10-13 00:01:34] Generated target 0000000000000000000000000000000000000000000000000000ffff00000000
No it is not normal. The last 8 hex characters should always be zero. The working stratum example is what a normal diff 1 target should look like.Is it normal that a Generated target looks like this:
Generated target 0000000000000000000000000000000000000000000000ffff00020d7800780d
on a working stratum machine, it look like this:
[2012-10-13 00:01:34] Generated target 0000000000000000000000000000000000000000000000000000ffff00000000
after the call swab256(target, rtarget); the last bytes of target are destroyed.
But rtarget looks good.
Code:
static void set_work_target(struct work *work, int diff)
{
unsigned char rtarget[36], target[36];
[2012-10-13 01:39:50] Generated target 0000000000000000000000000000000000000000000000000000ffff00000000
But still the same problem that i get rejected on stratum
[2012-10-13 01:40:01] RECVD: {"error": [-2, "lowdifficulty", null], "id": 68, "result": false}
[2012-10-13 01:40:01] PROOF OF WORK RESULT: false (booooo)
[2012-10-13 01:40:01] Rejected 4e8ec61a Diff 3/1 MM 6 pool 0 (lowdifficulty)