Page 5 of 8
Re: Documentation Errors
Posted:
Sun Jul 14, 2013 11:45 pm
by aolofsson
Gravis, Thanks for the detailed review and error finding!! All fixes will make it into the next architecture manual revision.
Andreas
Re: Documentation Errors
Posted:
Mon Jul 15, 2013 3:42 am
by Gravis
Re: Documentation Errors
Posted:
Mon Jul 15, 2013 4:04 am
by Gravis
Re: Documentation Errors
Posted:
Tue Jul 16, 2013 2:31 am
by Gravis
Re: Documentation Errors
Posted:
Tue Jul 16, 2013 11:50 am
by Gravis
Re: Documentation Errors
Posted:
Sat Jul 27, 2013 5:02 am
by LamsonNguyen
Re: Documentation Errors
Posted:
Sat Jul 27, 2013 8:02 am
by ysapir
@LamsonNguyen,
Thanks for your comments.
Re: Documentation Errors
Posted:
Sat Jul 27, 2013 9:08 am
by timpart
Architecture Reference Manual I'm looking at 4.13.01.14 The Adapteva website latest documentation has an out of date link to 3.12.12.18
In 4.2 I found parts of the discussion memory transaction ordering a bit confusing. Perhaps some examples with diagrams could be added after table 1 to make it clearer?
It says Load operations using data previously written use the updated values.
Does that mean written into a local register?
Table 1 says write to Core X followed by read from Core X is non deterministic. which contradicts this.
Also could you have a little table indicating which which instructions are Read and which are Write for the purposes of Table 1.
I presume LDR and TESTSET are Read and STR is write. The documentation for TESTSET is not clear on this point, but to my mind feels more like a Read with side effects.
I presume the reason that Read from X followed by Write to X is deterministic is that the core stalls until the Loaded data are returned? Otherwise the Write could easily overtake the Read if the loaded register wasn't referenced immediately.
EDIT: The Adapteva web site also calls version 4 of the SDK reference the latest, but I have 5.13.07.10 (from git hub)
Tim
Re: Documentation Errors
Posted:
Sat Jul 27, 2013 1:34 pm
by Gravis
Re: Documentation Errors
Posted:
Sat Jul 27, 2013 3:17 pm
by ysapir
Gravis,
The latest SDK reference is actually 5.13.07.10 that is included with the latest SDK release. You are probably referring to the document that appears in the website, and we should update that.