Compiler/TM4C129XNCZAD: very big issue

Kangho,

I had the impression that posters had entered a competition for the most compelling thread title! This one is called VERY BIG ISSUE, while another one on the same day is called WHAT A PROBLEM!!! Only to find out that both are a repeated message from yourself...

A word of advice here: try to write your title in a way that they make sense to other readers when searching for answers.

Now, for some answers:

kangho lee said:

I am trying to configure CCS on one computer. Is this possible?

Yes, it is possible to configure CCS on one computer. It is not possible to configure CCS in a football.

kangho lee said:

If so, how should I structure it?

What does that mean? Maybe the answer to help is: download the TivaWare examples from TI site, and import one of the projects into your workspace, after you installed CCS (in one computer).

kangho lee said:

What communication method is suitable for communication between two boards (except UART)?

Why don't you like UART? Do you have a specific project requirement to which UART won't suffice? If you provide more details, we may be able to suggest a more adequate method.

kangho lee said:

Also, is there a problem with trying to configure I2C?

Yes: it only works if configured correctly.

Sorry if the anwers are not exactly what you had in mind, but it is very important that questions on the forum relate what has been attempted, what did not work, or the exact goal one is trying to achieve.

Regards

Bruno

Any post titled (anywhere near) Very BIG ISSUE - is sure to yield - "Very SMALL INTEREST!"

Posters must realize that, "The world does not (always) Revolve upon them!"     What (may) be "big" for one - proves NOT the case for many.

Some attempt should be made to, "SELL your Post" - and such broad, effortless "tag lines" are NOT compelling! 

Avoiding the compiler questions.

kangho lee said:

2. What communication method is suitable for communication between two boards (except UART)?

1. Ethernet
2. CAN
3. UART
4. SPI
5. IIC

The last two are good for micro to I/O communication although I would consider IIC to be a protocol of last resort. I'd consider bit-banging SPI first. IIC does have a multi-master mode but there are more effective methods that avoid that complexity. Neither SPI or IIC are designed for off board communication but rather for a single board or board + daughterboard combinations.

Depending on the communications needs usually Ethernet (for large data) or CAN (for control) are superior.

UART is now probably most useful for legacy communication where you need to match an existing UART setup. Also for simple console/terminal communications.

For any inter-board/inter-micro communications where you are considering IIC I expect CAN would be superior.

Robert