If I were starting out, I'd familiarize myself with the MCU by thoroughly learning its architecture and instruction set. Then, I'd download a free macro-assembler/editor/simulator, of which there is at least one, and go through some of the assembly language exercises that are published on 8052.COM, particularly those related to setup of the UART, Timers, etc.

Many people see 'C' or other high-level-languages as a shortcut, but, sadly, they're not. They're a tool that does some things for you, possibly makes your code more easily maintainable even if not particularly readable and understandable, which some believe it does. Sooner or later you'll find that some portions of your code have to be written in assembly language because it's just easier to manage some low-level details that way.

Once you've learned the architecture and instruction set, moving to 'C' won't be any more difficult, and you'll better understand why you have to do certain things, whether in ASM or in a High Level Language. The programming process is not the same as the programming language. The things you learn about programming, no matter how and with which language you learn them won't change. High level languages isolate you from the low-level details with which you constantly have to deal when using assembly language. Most of the time that's convenient. Sometimes, well, not so much. When all is said and done, the languages are just a tool and it's up to you to decide which works best for you.

RE