|
It would be helpful if the question I am replying to were visible at the time of preparing a reply. It's my out-of-sight, out-of-mind brain at issue. I pasted the forum page into Word for visibility.
Last night I spent several hours in Creator Help, Documents, Blogs and Forum, each having a different search mechanism. Please make sure that Google and other search engines can catalog all of your information sources.
> Organize the data on the PSoC Creator website so that the information you need is easier to find
A page for current status (known issues and workarounds, ongoing development, est. next release) of Creator and Components
Direct navigation to information about a specific component (or other subject) where links to all areas (help, docs, blogs, forum, app. notes) would be found all together in one list. For example, I am wrestling with a UART problem and would want to focus on anything involving UART even if "UART" is not in the title.
> Improve our Getting Started tutorial or other documents that helps you to quickly understand and use PSoC Creator
I used the FirstTouch Starter Kit Guide and am now seeing the above referenced document for the first time. I think this should be included in the Starter Kit, as it says some things not present in the Starter Kit Guide.
> A list of relevant application notes that give you information about different ways to use PSoC Creator
Perhaps a table with app. notes for the rows and technology (component, etc.) for the columns, with an X in the cells to indicate which technologies are covered in a particular app. note. A person may not be interested in an applicaion, but want to see "best practice" for use of particular technologies.
In general, I have found PSoC Creator easy to use for simple designs. More challenging designs require careful research in documents and "reading between the lines" in some cases. Help would be better if it stated why a particular thing would be used (non-obvious menu item for example). "Select Component Instance Debug Windows" is in Help, but I haven't found how to get there.
Component documents would be better if there were examples of how to use API functions. Not every function, but the ones that are not obvious or would typically be used in conjuction with other functions.
UART document: RX timing diagram lacks rts_n; TX timing diagram is absent altogether; FIFO timing diagrams might be useful, especially with rts_n and cts_n in play.
|