do a little searching, also google is good at searches. You might try different variations with 8051,8052,
8031, howto and C compiler. Use the advanced search to limit the information. Also do a goole seach on the newsgroup (and probably a few others) as it may turn up a few intersting links.
The above maybe a little helpful. The grey'd out links on the HCS page are things I'm working on. The links work but the articles are a work in progress so pardon the grammer and spelling, I'm no where near done. I tend to rip, tear and throw free thoughts on a page. I wouldn't mind either emailing me or a reply here to anything you might find that is useful.
Linux Home Automation Neil Cherry email@example.com
http://home.comcast.net/~ncherry/ (Text only)
Hi, I would think again, switching to another language won't make your problems dissapear you just get some new ones. If C is the right chioce for your project then the 8051 is allmost certainly not the right processor.
Taking the second point first: C is absolutely fine for an 8051. Ideal, even.
The first point has an element of truth. If the problems are not related to code management (e.g. it's the wrong platform for the job regardless of language), then you're right - C won't help.
But often the "problems" with large assembler projects come down to an underlying lack of structure or organisation. Mastering C (which can take a while - I'd agree it's certainly not an instant magic bullet for a newcomer)
*should* help with gaining a means of adopting good structuring - i.e. good, modern design practice.
OTOH, I've seen some right pigs ears written in C - for any platform. To the OP: I frequently use C as a means of designing code, and then either hand- or machine-compile from there. The discipline that modern object-oriented C encourages, e.g. active control of scope of variables, is hugely helpful even in assembler - even if assembler doesn't demand it.
use Google and search for "final word on the 8051", you will find an online pdf file that should be quite helpful. (it assumes you are using the Keil compiler but is useful even if you use another one)
Hi, I have yet to see a project written in C where the 8051 was the best choice on either performance or price. C is to the 8051 what windows is to a pentium. Of course is your poduct doesn't need much performance then allmost anything would do.
firstname.lastname@example.org (CBarn24050) wrote in news: email@example.com:
I have yet to see one that wasn't. What kind of statement is that you are making? The 8051 is dog-simple to program, supplied by an unbelievable array of companies, has *excellent* C compilers available, wonderful peripheral choices, the core can be placed into an FPGA for SoC designs, Cygnal has JTAG debuggable version that run 12x the clock efficiency of the original 8051, you can use off-chip CODE and XDATA space if needed, fast interrupt context switching using register banks, etc. etc.
I guess you belong to the "Real Programmers use COPY CON PROGRAM.EXE" school of programming?
The choice between C and assembly isn't anything like as simple as you make out, and "performance" is measured in different ways. For almost any nontrivial piece of code where you're not actually down to the cycle-counting level of time criticality, the [potential] portability and [potential] productivity gains of using C are a strong argument against assembler - even in 8-bit platforms.
Are you sure you are in the right NG? This one is embedded...
I think only 5% of 8051 programmers still use assembler only. /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ \/\/\/\/\ Chris Hills Staffs England /\/\/\/\/\ /\/\/ firstname.lastname@example.org