Documentation Errors

Forum for anything not suitable for the other forums.

Re: Documentation Errors

Postby mhonman » Thu Nov 14, 2013 7:46 pm

Now onto software exceptions. Architecture reference 4.13.09.29 section 7.5 Status Flags - EXCAUSE describes this as a 3-bit field and refers to Appendix C for more info. The info is in appendix D and describes this as a 4-bit field (also in the description of the STATUS register).
mhonman
 
Posts: 112
Joined: Thu Apr 25, 2013 2:22 pm

Re: Documentation Errors

Postby timpart » Thu Mar 06, 2014 7:57 am

Thanks for the new versions of the E16G301 data sheet and Arch Ref manual.

I'm having difficulty understanding the eLink protocol explanation on page 19 of revision 14.02.21 of E16G301.

Are there mistakes in the row of {datamode[1:0],write,read} values? They seem to have read and write reversed.

Should they say "0X10 1010 1110 XX01 XX11" ?

p18 The link in the green box is wrong, needs "ell" inserted towards the end.
p19 In the green box the consequences of not using an optimal sequence seem to have been censored.

Later edit:
For byte and half word writes are the data always in the lower numbered bytes (5 and 6) with bytes 7 and 8 always zero, or are they positioned in the appropriate spot within the whole word? If the latter, that would have to depend on destination address.

Thanks,

Tim
timpart
 
Posts: 302
Joined: Mon Dec 17, 2012 3:25 am
Location: UK

Re: Documentation Errors

Postby aolofsson » Tue Mar 11, 2014 9:17 pm

Tim,
Thanks for the feedback! These have been fixed in the new datasheets.
We do data alignment on write "to the right". The byte is sitting on the 64bit bus as is in the right spot. This detail is exposed on the eLink and must be taken care of inside the FPGA logic (an example of this can be found in the AXI master interface)

Andreas
User avatar
aolofsson
 
Posts: 1005
Joined: Tue Dec 11, 2012 6:59 pm
Location: Lexington, Massachusetts,USA

Re: Documentation Errors

Postby timpart » Wed Mar 12, 2014 12:23 pm

I'm not entirely sure about the data sheet fix for the eLink. You seem to have changed the caption from "write, read" to "read write". I thought the original caption was correct but the bit patterns are wrong, but I'm not very good with HDL to confirm that. The byte zero line description still describes the order as "write, read".

Tim
timpart
 
Posts: 302
Joined: Mon Dec 17, 2012 3:25 am
Location: UK

Re: Documentation Errors

Postby mranderso » Sun Mar 23, 2014 8:08 pm

Epiphany SDK Reference REV 5.13.09.10

Description end abuptly

13.6.6 e_barrier_init()
Synopsis
#include “e-lib.h”
void e_barrier_init(volatile e_barrier_t bar_array[], e_barrier_t *tgt_bar_array[]);
Description
Initialize a workgroup barrier. The bar_array and tgt_bar_array parameters are defined as arrays of size equal to the number of cores in the workgroup. The barrier is mutual to all cores in the workgroup, so care must be taken w
User avatar
mranderso
 
Posts: 6
Joined: Mon Dec 17, 2012 3:28 am
Location: New Orleans, LA, US

Re: Documentation Errors

Postby Gravis » Sun Apr 27, 2014 4:57 pm

Epiphany SDK Reference REV 5.13.09.10

in section 2 it reads that there isnt a port for the ARM platform. Also, is the Eclipse IDE up to date yet?

2. Epiphany Multicore Development IDE (ECLIPSE)

Note: The Eclipse based Epiphany IDE is outdated and not in sync with the current generation of
Epiphany platforms, which means platforms newer than the EMEK3 and EMEK4 boards. Some
of the features presented in this chapter are not applicable to the ZYNQ based system such as
Parallella Prototype (ZedBoard) and Parallella computers.

In particular, the debugging and launching of an Epiphany application from the Eclipse IDE is
currently not supported. It is still a valuable tool for writing Epiphany applications, especially for
the host-accelerator model.

Currently, the IDE is not supported on the ARM based platforms, so one needs an x86 (PC)
based machine to use it.
User avatar
Gravis
 
Posts: 445
Joined: Mon Dec 17, 2012 3:27 am
Location: East coast USA.

Re: Documentation Errors

Postby adexmont » Tue Jul 01, 2014 11:21 am

it's a less important error i suppose but in https://github.com/parallella/parallell ... recipe.txt on line 98 is it supposed to be evince ? cause evincea made me thinking for 5 min
adexmont
 
Posts: 121
Joined: Thu Oct 24, 2013 12:58 pm

Re: Documentation Errors

Postby Gary_Cattley » Sat Jul 05, 2014 10:23 pm

Minor one in the SD Creation online document http://www.parallella.org/create-sdcard/

Section: Linux SD Installation Instructions
Item: 5 Copy the Parallella Linux kernel and FPGA files to the SD card

The last linux command should be sync and not syn

"
$ tar -zxvf <kernel-name>.tgz -C <sd-device-path>/BOOT
$ cp <parallella-bit-release>.bin <sd-device-path>/BOOT/parallella.bit.bin
$ syn
"

Regards

Gary
Gary_Cattley
 
Posts: 1
Joined: Sun Jun 29, 2014 3:39 pm

Re: Documentation Errors

Postby 9600 » Sun Jul 06, 2014 6:24 pm

Gary_Cattley wrote:The last linux command should be sync and not syn


Thanks for spotting this! Now fixed.

Cheers,

Andrew
Andrew Back (a.k.a. 9600 / carrierdetect)
User avatar
9600
 
Posts: 997
Joined: Mon Dec 17, 2012 3:25 am

Re: Documentation Errors

Postby sebraa » Tue Jul 29, 2014 8:36 pm

Epiphany Architecture Reference, Rev. 14.03.11

Page 108 (MBKPT): It allows all cores to stop at approximately the same time, simplifying multicore code debugging easier.

Page 157 (Appendix E): Two typos in "Fixed lots of typos (an probably added some more..)" If that's on purpose, I would recommend shuffling some letters in probably instead. :lol:
sebraa
 
Posts: 495
Joined: Mon Jul 21, 2014 7:54 pm

PreviousNext

Return to General Discussion

Who is online

Users browsing this forum: No registered users and 15 guests

cron