I am currently working on a project using the MC56F81666 digital signal controller and attempting to establish communication with FreeMASTER via the P&E Micro Multilink Universal debugger.
I have configured the JTAG pins (TCK, TDI, TDO, TMS, RESET) in the project using the MCU Config Tools.
However, I am facing an issue when modifying the freemaster_cfg.h file in CodeWarrior. Specifically, when I change the following line:
#define FMSTR_DISABLE 1 to #define FMSTR_DISABLE 0
I start getting multiple errors in other FreeMASTER source files during compilation.
The lines currently present in the freemaster_cfg.h file are:
#warning This freemaster_cfg.h file needs to be edited to configure low-level communication.
#define FMSTR_DISABLE 1 // TODO: set to 0 after this configuration is ready to be used
#define FMSTR_TRANSPORT FMSTR_SERIAL // TODO: select FMSTR_SERIAL or FMSTR_CAN transport interface
#define FMSTR_SERIAL_DRV // TODO: when using FMSTR_SERIAL: select Serial low-level communication driver
#define FMSTR_CAN_DRV // TODO: when using FMSTR_CAN: select CAN low-level communication driver
Could you please advise:
What additional changes or inclusions are required in the project to resolve the errors caused after enabling FreeMASTER?
In FreeMASTER under Project → Options → MAP Files, I have added the .elf file in the Default Symbol File section. However:
What should I select in the Plug-in Module section under Communication to properly connect to the controller using the P&E Micro Multilink?
What specific settings should be configured in the Connection Wizard to establish a successful link with the MC56F81666?
Also, in the P&E JTAG/BDM Communication settings, the default selection is P&E Cortex-M. Since the MC56F81666 is a DSC (not a Cortex-M device), I believe this setting needs to be changed. Could you confirm which option should be selected instead?
Your guidance on the correct configuration and steps needed to successfully connect FreeMASTER to the controller using the P&E debugger would be greatly appreciated.
Thank you.
解決済! 解決策の投稿を見る。
Yes, you can refer to the file fsl_adapter_uart.
I will be on leave for a few days and can only start replying after returning to the company on June 3. If you have further questions later, you can create a new post, which may get a faster response. Sorry for the inconvenience.
BRs,
Celeste
Hello @AJITH_KUMAR ,
Thanks for your post and sorry for the late response.
For the question 1 and 2, you can refer to our freemaster demo for MC56F81000 board SDK. Download link: Dashboard | MCUXpresso SDK Builder
And kindly note that it can only be imported in CodeWarrior 11.2.
Regarding how to import the demo in the SDK into CodeWarrior, please refer to the attached document "The steps to load example code in SDK package for DSC based on CodeWarrior for MCU".
Then you can import the fmstr_uart demo for reference.
You can refer to how the relevant parameters are defined in its freemaster_cfg.h.
In addition, you can also refer to AN4771, Integrating FreeMASTER-Time Debugging Tool with CodeWarrior for Microcontrollers v10.x Proje... and FreeMASTER Communication Driver. I believe they will be very helpful.
For question 3, I am not sure whether the P&E Multilink is supported in DSC FreeMASTER communication or not. You can confirm with the freemaster support team again.
You can post Question 3 on the FreeMASTER - NXP Community forum. They will provide more professional FreeMASTER support.
Hope it can help you. Let me know if there is something else that I could do to support you.
BRs,
Celeste
------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!
------------------------------------------------------------------------------------------------------------
Yes, you can refer to the file fsl_adapter_uart.
I will be on leave for a few days and can only start replying after returning to the company on June 3. If you have further questions later, you can create a new post, which may get a faster response. Sorry for the inconvenience.
BRs,
Celeste