This is a common recommendation, since the compiler vendor may have grouped similar chips into a common header file. Sometimes, the compiler documentation will be needed to "decode" the naming convention used for supplied header files.


This is a common recommendation, since the chip manufacturer often have information about what header file to use - it isn't uncommon that a header file for at least one bigger compiler is available on the manufacturers web site. If not, then the datasheet contains the information for compiling a header file, or for updating a generic header file with the unique extras of your specific chip.


And Andy is right. The name "8952.h" is not enough to tell us where you got the file from. That also means that we can't possibly know what information it contains - if it is a generic file, or a file specifically inteded for a very specific chip model.



Once more - this is the common method to use if the file you have is missing some symbols, and you can't find a better file somewhere else. And files that does contain the symbols for all SFR may not have defined symbols for all possible flags and masks, so it is very common to have to complement the file based on the datasheet information.

It can't be humiliating to get a list of things to look at if you are asking for help. If you consider some of the suggestion too "noobish", then you must spend more time with your original post, telling what steps you have already considered.