Treat C like scripted assembly. You'll be fine. It doesn't do much magic like the newest C++, Java or other languages may perform.
First determine where to get information. Since the company who made the chip might not be the company making the cpu, and the compiler might be some other entity as well. For example: ST makes a chip with an ARM Cortex processor core that you can compile code for using a compiler the GNU Project in an Eclipse IDE.
Then there are the architecture intricacies...
Those that involve the storage specifiers, volatile and static.
Also platform details, what memory you may access when and how wide.
Knowing what arithmetic you chip can do, or does slow. How to accelerate it with the FPU or crypto engine. (this often isn't automatic)
How much stack there is left, you often can't ask the OS.
How to real-time debug, since at some point you can't breakpoint the chip anymore without hardware damages.
The performance impact of the volatile keyword, or pointers. At only 20 Mhz these things count.
What functions your standard library offers, or not, or not optimized for the architecture.
Many little things....
Take a copy of the standard so you can lookup yourself if the people on the internet are correctly describing the intended behavior of the language.
Since I've seen a lot of different ways to describe what some keywords do.
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdfYou can make it your job!