[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+EaD-a6NXsrm5MXMY7s8V3Xthqg3MAWnr5BEntrU3X3UZL=Og@mail.gmail.com>
Date: Thu, 24 Oct 2013 14:54:41 +0200
From: Katja Malvoni <kmalvoni@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: ZedBoard: bcrypt
On Tue, Oct 22, 2013 at 8:28 PM, Katja Malvoni <kmalvoni@...il.com> wrote:
> I haven't managed to figure out where is the problem yet, especially
> because both cores use the same logic.
>
The problem is in writing computed data to block RAM. Second core doesn't
write anything. The problem is in BRAM. If I let second core write to
beginning of BRAM (where first core normally writes), correct result is
returned. However, when second core uses addresses with offset, nothing is
written. The same happens if I use offset with first core. I don't know why
does this happen, there is nothing wrong with that offset, it's a regular
address, there is no reason for BRAM to have problems with it (BRAM size is
64 KB while offset is 0x10A4).
Katja
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
