This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting memory model

To set a particular memory model, it appears I have to set pragma in each and every source code file. Is that true? Is there no Project option parameter I can use to set it globally?

Does anyone else find the documentation with the Keil tools to be as useless as I do? Just curious.

  • Does anyone else find the documentation with the Keil tools to be as useless as I do? Just curious.

    ALL documentation I use is as 'useless' as the Keil docs.
    I have found that all documentation of technical limited quantity stuff is extremely 'useful' once you almost do not need it. You need to know it to know what to look for.
    One particular issue is indexing, if you are looking for "the function that makes it whistle Yankee doodle dandy" you will only find it if you remember the name of that function.

    So, if you want the documentation to be 'useful' read it end to end 10 or more times and you will have an idea where and how to look for what.

    Erik

  • by the way why do you want to set the memory model? the unly useful one is the defaule, any other lead to bloating.

    Erik

  • "Is that true?"

    No, it's not.

    Look at the desription of each directive:

    http://www.keil.com/support/man/docs/c51/c51_small.htm
    http://www.keil.com/support/man/docs/c51/c51_compact.htm
    http://www.keil.com/support/man/docs/c51/c51_large.htm

    Each one tells you how to do it in uVision - and that will apply to the whole project.

    http://www.keil.com/support/man/docs/uv3/uv3_dg_target51.htm

    "Does anyone else find the documentation with the Keil tools to be as useless as I do?"

    Do they still "ship" the Getting Started guide with the tools - GS51.PDF for the 8051 tools?
    That one walked you through the whole toolchain, and would've answered your question.

    But I note that the trend seems to be away from PDF documentation...

    Also, the CD (both free and paid-for) used to include some introductory videous that walked you though all the tools and menus

  • Oh dear, Oh dear.

    Imagining manuals to be just a pot of letters, grouped together as bunches and lined up in sentences, yes. If you think like this, yes. KEIL Manuals are useless.

    I do not imagine the manuals as such collection of letters.

    They are repositories of ideas. The product of minds that dominate a language and a technique. These lines have a wealth of information on this technique. But they are encoded in a language.

    Getting the manual in Spanish or Italian, would make a English speaking only person think it is useless, for the collection of letters and bunching does not convey any information, although you can read the alphabet all right.

    This - I am afraid - is the main reason why interested people does not rapport very well to manuals in general. When people that devoted all their working hours to bits and chips must write a book, the shortcomings are evident.

    To value a manual one must learn the language. The lingo. Learn the jargon. Learn the flavour of tech-notalk KEIL talks. Be humble, put effor to it.

    This is a profitable exercise. Use the manual as a springboard to your knowledge. Do not reinvent the wheel.

    I read the manual, both in human way - page by page - as in digital way - by searching for keywords. I dislike it sometimes, It is not Pulitzer worth material, but it makes me learn faster and better than by trial and error.

    No, manuals from Keil are not below average.
    IMHO - They are very good.

    And English is not my native language, but I work hard to learn it and to feel confortable with it.