Hi
We have just started experimenting with PN7462 using NXP's development. We have tried the Basic Discovery Loop example and successfully build it with NULL_OS option.
The door access example seems to be the most relevant and we are trying to build it with the same NULL_OS option but getting build errors - 2 of 34 pasted below:
c:/nxp/mcuxpressoide_11.1.1_3241/ide/plugins/com.nxp.mcuxpresso.tools.win32_11.1.0.202001081728/tools/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld.exe: ./phOsal/src/NullOs/portable/phOsal_Port_CM4.o: in function `phOsal_InitTickTimer':
C:/Users/Shoaib/Documents/NxpPn7462/phOsal/src/NullOs/portable/phOsal_Port_CM4.c:61: multiple definition of `phOsal_InitTickTimer'; ./phOsal/src/NullOs/portable/phOsal_Port_CM3.o:C:/Users/Shoaib/Documents/NxpPn7462/phOsal/src/NullOs/portable/phOsal_Port_CM3.c:59: first defined here
c:/nxp/mcuxpressoide_11.1.1_3241/ide/plugins/com.nxp.mcuxpresso.tools.win32_11.1.0.202001081728/tools/bin/../lib/gcc/arm-none-eabi/8.3.1/../../../../arm-none-eabi/bin/ld.exe: ./phOsal/src/NullOs/portable/phOsal_Port_CM4.o: in function `phOsal_StartTickTimer':
Now having looked at the main file phExDoorAccess.c, it looks like this particular project doesn't support NULL_OS option?
Please could we get a confirmation if that is the case. Our application demands use of LPCD and there around 20uA average idle current from the device when in LPCD..
Thanks
Solved! Go to Solution.
Hi Shoaib,
I just confirmed with the expert, NULLOS option is not available now for this demo, so you have to include freeRTOS in the building.
Sorry for the confusion that has caused.
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi Shoaib,
Please exclude these two files from build as below:
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi Kan,
Thanks for looking into this.
Unfortunately, when I exclude these 2 files from the built, I get the following error:
17:54:42 **** Build of configuration DebugPN7462AU for project PN7462AU_ex_phExDoorAccess ****
make -r -j4 all
Building target: PN7462AU_ex_phExDoorAccess.axf
Invoking: MCU Linker
arm-none-eabi-gcc -nostdlib -L"C:\Users\Shoaib\Documents\NxpWorkspace\PN7462AU\phHal\phhalRf\lib" -Xlinker .... and so on
c:/nxp/mcuxpressoide_11.1.1_3241/ide/plugins/com.nx ... and so on
_cr__main.c:(.text.__main+0x6): undefined reference to `main'
collect2.exe: error: ld returned 1 exit status
make: *** [makefile:126: PN7462AU_ex_phExDoorAccess.axf] Error 1
"make -r -j4 all" terminated with exit code 2. Build might be incomplete.
Hi Shoaib,
I just confirmed with the expert, NULLOS option is not available now for this demo, so you have to include freeRTOS in the building.
Sorry for the confusion that has caused.
Have a great day,
Kan
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------
Hi Kan,
Thanks for clarification :smileyhappy:.
User manual probably needs to specify this too.