NXP NCF29A1 official Software ChessDE initial compilation link failed solution

1. Introduction
        When customers first come into contact with NCF29A1 series keys, they can usually obtain the “PKE/RKE Token family” development package through official channels, which contains the hardware reference design “Token Demo Hardware-Version” and the software demo “Token Demo Software-Version”.


        The user is using the software demo for the first time to import. During the prx project, I compiled it, but found that the compilation of a single file is normal, but when I enter the linking stage, it will prompt “The file type is not defined, and the file is read incorrectly." If the user encounters such a problem during use, please don't panic, because this is the first time I have used it.I have to taste the stage that I will go through more or less often.


        In fact, here users only need to perform simple operations to solve the above problems. Please listen to me.

Second, the solution
        If the user pays careful attention, he will find that “Readme.” exists under the path “Software_20xx-xx-xx\Software\DemoSoftware_MRK3\lib". txt" ”It is recommended that everyone pay attention to the relevant “Readme” file when using unfamiliar projects, which contains the original factory's prompts). Among them is an explanation of the situation：

       “Libraries in this folder have been compiled with the MRK-IIIe IP Programmer release as stated in the release notes. If you are using a different release, linking errors might occur.  ” 

        This means that although the original factory can control the version of the software you are currently compiling, the version of ChessDE, the development environment used by the user, is uncontrollable, and there are some differences between different ChessDE versions, which is also the cause of the link error. The solution is also provided by the original factory：

        “In this case, the librariesIn this case, the librarie smust be re-built using the supplied project (.prx) files.
           This applies to
           1. Device support library for type <type>:    \external\<TYPE>\lib<TYPE>.prx   
               For instance the TOKEN case:    \external\ncf29A1\libncf29A1.prx

           2. System calls interface library:    comps\SysFuncLib\toolsupport\chessde\<TYPE>\<ROMMASK>\SystemLib_<TYPE>_<ROMMASK>. prx   
               Examples:    comps\SysFuncLib\toolsupport\chessde\ncf29A1\RC005\SystemLib_ncf29A1_RC005. prx     
                                    comps\SysFuncLib\toolsupport\chessde\ncf2957\RC001\SystemLib_ncf2957_RC001. prx”

        The customer needs to specify the key model used, and then enter the corresponding key directory to proceed. prx engineering recompilation. Taking NCF29A1 as an example, at this time we need to find the library file of NCF29A1：


        By importing the file into ChessDE (ensure that ChessDE only opens one project at the same time, otherwise an error may be reported), and then compile it：


        Then you need to find the system library file of NCF29A1：


        Also import it into ChessDE and compile it：


        After recompiling the above two library files, the Demo project can be compiled. At this time, it can be found that the project compilation and linking are normal.：


3. Summary
        Finally, it is recommended that users, in the process of using the software, if they encounter problems, give priority to the documents and materials that come with the project. Many of the pits that the previous people have stepped on are actually summarized in it. .