Hi Freemaster Forum expert,
I am trying to include the freemaster SDK 2.0.0. After including this SDK i am getting following error.
make: *** No rule to make target 'FreeMaster_S32K144/src_platforms/S32xx/freemaster_S32xx.o', needed by 'LED.elf'. Stop.
"make -j8 all" terminated with exit code 2. Build might be incomplete.
Please suggest how to resolve this error ?
Regards,
Dinesh
已解决! 转到解答。
Unfortunately you cannot simultaneously use S32DS Debugger and FreeMASTER BDM plugin. You won't be able to:
or it may break the debug session/connection.
If you want to use minimum connections / external devices the best option would be to use the FreeMASTER UART communication & onboard OpenSDA interface for S32DS Debugging. In this case there won't be any conflicts and you would need only one USB cable.
Hi @Dinesh_Guleria,
Usually this issue is caused by some missing files required during compilation (may be caused by relative path or how those files were included into the project).
Are you including FreeMASTER SDK manually or using S32DS feature to attach the SDK ? Note that when you attach it - S32DS does not copy the files into your project by creates a symbolic link.
Could you check whether S32DS is able to locate correctly includes folders and links to source code files.
Hi Iulian,
Thanks for your reply & strong support.
After installing freemaster tool from this website, then using S32DS feature I attached the freemaster SDK , what i found this error is resolved:---
https://www.nxp.com/design/software/development-software/freemaster-run-time-debugging-tool:FREEMAST...
Actually i did not instatted this software previously & was using S32DS feature to attach the freemaster SDK. May be this was causing this error ?
Some question from my side :--
Please suggest on this point from my side, then i can use this tool more efficiently.
Thanks & Regards,
Dinesh
FreeMASTER SDK is also part of one of the S32DS S32k1xx Development packages and is installed in (C:\NXP\S32DS.3.4\S32DS\software). I guess you did not have it installed. Happy to hear that you were able to solve it.
Regarding your questions + some comments from my side:
1. Yes
BDM & PD-BDM plugins allows communication with FreeMASTER Tool via PE Debug probe. Note that there are 2 options to use this plugin, a more detailed answer here.
2. Yes
3. Yes, FreeMASTER does not configure any peripherals
* You need the interrupt only in FMSTR_LONG_INTR or FMSTR_SHORT_INTR modes. If you are using FMSTR_POLL_DRIVEN FMSTR_Isr will not be executed - your code won't be wrong, but just so you are aware.
4. Unfortunately - No
The only way is to define a variable and periodically update it with port value from your code.
The have a few webinars on FreeMASTER that may be helpful in case you did not see them.
Hi Iulian,
Thanks for your reply & strong support.
>>FMSTR_LONG_INTR or FMSTR_SHORT_INTR modes. If you are using FMSTR_POLL_DRIVEN
Please suggest. How & where to set this this mode in freemaster tool ?
Regards,
DInesh
The change is applied in the embedded code (the desktop tool will work seamlessly with either mode).
You can set it in freemaster_cfg.h:
/******************************************************************************
* Select interrupt or poll-driven serial communication
******************************************************************************/
#define FMSTR_LONG_INTR 0 /* Complete message processing in interrupt */
#define FMSTR_SHORT_INTR 1 /* SCI FIFO-queuing done in interrupt */
#define FMSTR_POLL_DRIVEN 0 /* No interrupt needed, polling only */
Hi Iulian,
Thanks for your reply & strong support.
One last question if i am debugging code using OPENSDA interface or PE Multilink universal on S32DS design studio. In this case can i use freemaster to get data from Target MCU using same OPENSDA interface or PE Multilink universal debugger ?
Means to say simultaneous debugging on S32DS design studio & use freemaster to get data from Target MCU, using OPENSDA interface or PE Multilink universal, is it possible ?
Please suggest.
Regards,
Dinesh
Unfortunately you cannot simultaneously use S32DS Debugger and FreeMASTER BDM plugin. You won't be able to:
or it may break the debug session/connection.
If you want to use minimum connections / external devices the best option would be to use the FreeMASTER UART communication & onboard OpenSDA interface for S32DS Debugging. In this case there won't be any conflicts and you would need only one USB cable.