Thanks! Really appreciated :)pstnotpd wrote: Good work!!
I'm not an experiended user I suppose, but still...
I am learning about the XCore myself and writing these posts as I go :)
Tile and core lack a clear distinction in the documentation. My understanding is that a tile is the physical processor, complete with its 8 XCore threads, memory, I/O and resources. An 8 thread chip is one tile, while a 16 thread chip is two tiles.pstnotpd wrote: You might want to add a short explanation how the new "Tile" naming convention relates to the "Xcore" convention used in the original document. I.e. Tile==Xcore (or so I believe).
Anyone from the XCore team want to chime in on this?
I'm trying to limit my posts to the scope of the StarterKit intentionally. My main objective is to hopefully create a series of simplified tutorials to help newbies like myself get off the ground and get their training wheels off.pstnotpd wrote: Also, with the XC2 specification I believe it is possible to do a kind of "soft threading" with the combinable and distributable task feature. The architecture document only mentions hardware threads.
Still, if you have any reference to any documents I haven't mentioned in this thread, or newer versions of the ones I did, I'd greatly appreciate it.
Agreed. This continues to be my biggest gripe. Most of the documents I've found have been through Google, as even the links within the documents can't be trusted.pstnotpd wrote: It's all very confusing for newbies and my personal main gripe with the current state of documentation.
For example, the old Programming guide, X9577A, is the one I found referenced in other documents. But this has been superseded by X1009B (which I found by complete accident also through Google). However, the new one omits Appendix B which provides a lot of helpful code examples in various port configurations and Appendix C which provides a nice, cheat sheet sort documentation for xs1.h (I know xs1.h is pretty well documented, but this provides a nice quick reference for the most used functions). Ditto for the secion explaining port to pin mappings.