It would be nice to put some words about the different decice classses, e.g: "TARGET_IS_SNOWFLAKE_RA0",
What are the different options? and who is affected by them during compilation? link?
Amir
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
It would be nice to put some words about the different decice classses, e.g: "TARGET_IS_SNOWFLAKE_RA0",
What are the different options? and who is affected by them during compilation? link?
Amir
Hello Amir,
Do you mean the device class needs to be documented for which TM4C device you are using along with what it affects?
Regards
Amit Ashara
Hi Amit, Thanks.
What I ment is general understanding what are those MACROS.
They are listed in TIVAWARE recommendation as of compiling C code for TM4C129x
but with no explanation what's they stand for.
I believe they are documented somewhere....but where? :-)
Hi Amir,
Which document are you referring to? If you can send me the name/ti web link of the document, it would make it easier to answer the query.
Regards
Amit Ashara
Each and Every example project file, YOU shipped.
e.g:
"C:\ti\TivaWare_C_Series-2.0.1.11577\examples\boards\dk-tm4c129x\hello\hello.ewp" line 138
"C:\ti\TivaWare_C_Series-2.0.1.11577\examples\boards\dk-tm4c129x\hello\Makefile"
"C:\ti\TivaWare_C_Series-2.0.1.11577\examples\boards\dk-tm4c129x\hello\hello.uvproj"
If you still don't understand what we're asking, leave it.
Do I really have to explain to TI support employee about compilation flags that TI uses???
Amir Yungman1 said:Do I really have to explain to TI support employee about compilation flags
Ouch! May I (outsider - just like you) rise to the defense of Amit, here?
Indeed - your request has merit. You must realize that this vendor's web-site & document inventory is enormous - I've been @ this site and MCU originator (LMI) "forever" - and just "barely" recall Snowflake. (btw - that's name of my shipboard cat)
Amit has quickly, properly responded. He's in no way responsible for vendor's failure to, "connect all the (many) dots!"
Your point has value - your "method/madness" - not so much...
Dears,
I can only mourn that the fastest, agressive support company becomes similar to the "ones" that we left due to lots of shiny sites, forums, but without actual delivery...
moreover, I completly not accept your "help", cb1. I can explain you on a joint catamaran sailing...over a beer.
In few words,
when I pay for a product, and I post on a forum exactly for development on TivaWare, and ask a basic question, not deep in the vage cordner of some unknown obsolete part number, I think the vendor should be ready for that.
I'm sorry that I am not using the FORUM as a "Facebook" to gosip about travel's.
I would LOVE to do it, but not here.
so, thanks for nothing. really. no hard feeling.
I'll find it somehow, from someone that actually work on the TivaWare.
BR
CB2
Hi Amir,
The information that you are looking for is in the User Guide for TIVAWare Peripheral Library (1 of 233 documents to be precise in the User Guide Section)
To simplify your search
http://www.ti.com/lit/ug/spmu298/spmu298.pdf
The document is not up to date for TARGET_IS_SNOWFLAKE_RA0 but will give you the data that you have originally requested for with respect to TARGET_IS_XXX_YYY and what it impacts. A more up to date document is required to reduce the next round of questions, but this should help you.
I will take this input back into documentation so that it is kept up to date in the fastest time possible.
Regards
Amit Ashara
Hi Amit,
Thank you, that's gave us the missing link, appriciate your help.
Amir