Hi,
First thing to note when working with FreeMASTER BDM Plugin is that there are 2 modes:
- Direct access to target microcontroller memory - the "traditional" or non-intrusive debug mode. In this mode you don't need FreeMASTER support to be enabled on the target as it relies on the hardware debug mechanism, however you won't have access to FreeMASTER specific features such as TSA, Recorder or Pipes.
- PD or Packed-Driven BDM that uses the debug register to exchange data frames just like UART or CAN protocols. This mode requires FreeMASTER Driver enablement, which, as far as I know is not supported by the MatLAB Toolbox. You'd need to go into freemaster_cfg.h file and enable it:
No need to disable other options explicitly - if an option is not present it is considered disabled (0). I just included other options as an example of what you should pay attention to depending on the MatLAB generated code.
To make sure you don't confuse these 2 modes, I suggest using Connection Wizard:
In the next step it is configured just like Marius did.
Hope this helps,
Iulian
Hello sparkee,
Well, constantinrazvan.chivu is right, the issue regarding the Recorder error will be investigated.
But, I understand from your post that there are actually two issues:
1. the connection through the multilink probe when the FreeMaster block is in the model.
How do you perform the settings for the Multilink probe in FreeMaster?
I tried going in the Options to the Comm options and selected in the Plug-In module the first option "FreeMASTER BDM Communication Plug-In"
Now, by pressing the Configure button, the following Window appears. Here I selected the P&E CortexM and selected the connection to USB Multilink. The only speed required here is the JTAG Clock Speed.
Using this setup, I was able to connect to the board even if the FreeMaster Config block is in the model so no changes had to be made in the model.
Instead of USB Multilink, you can select also the OpenSDA which comes directly on the S32K144 EVB but, if you are using the PEMicro, I suggest to power up the board externally in order to disconnect the OpenSDA from the circuit ( cheange the J107 to other position and unplug the USB cable). If not, then there will be two debuggers (Multilink and OpenSDA on the same JTAG link to the controller).
2. The problem with the recorder. Well, you have a compile issue but I tried to use the recorder using this setup and I got the following message error: Recorder could not be initialised. Error 0x80000081 (Invalid command.)
Once again, I will ask our friend iulianstan to help us answer this question: Is the FreeMaster Recoder available over the Jtag connection?
Hope this helps,
Marius
Hi,
First thing to note when working with FreeMASTER BDM Plugin is that there are 2 modes:
- Direct access to target microcontroller memory - the "traditional" or non-intrusive debug mode. In this mode you don't need FreeMASTER support to be enabled on the target as it relies on the hardware debug mechanism, however you won't have access to FreeMASTER specific features such as TSA, Recorder or Pipes.
- PD or Packed-Driven BDM that uses the debug register to exchange data frames just like UART or CAN protocols. This mode requires FreeMASTER Driver enablement, which, as far as I know is not supported by the MatLAB Toolbox. You'd need to go into freemaster_cfg.h file and enable it:
No need to disable other options explicitly - if an option is not present it is considered disabled (0). I just included other options as an example of what you should pay attention to depending on the MatLAB generated code.
To make sure you don't confuse these 2 modes, I suggest using Connection Wizard:
In the next step it is configured just like Marius did.
Hope this helps,
Iulian
Thank you all for your input.
There was a little confusion as to what the problem was due to me citing multiple issues and not being as thorough and clear as I should have. We've definitely taken a big step towards clearing up the issue though.
I have no issues using FreeMaster when connected over SDA to the Dev Board. It works great. Scope is a little slower than I'd like but not a problem because I can use the Recorder when I need higher fidelity.
Where I ran into the problem was trying to use the Recorder with the MultiLink Universal. My problem stemmed from using the direct access mode instead of PD-BDM mode.
When I go into the PD-BDM configure window, the S32K does not appear in the dropdown box:
If I go into Configure and Test Connection:
It looks like all is good? But when I go pack to the main configuration screen and Test Connection I get this:
You are almost there, the missing piece is the communication buffer address. You can either specify:
- its exact address or
- a range to scan
You could get the exact address from the map file. The line would look like this:
.bss.pcm_bdm_pCommBuffer 0x20004c64 0x44 ./FreeMASTER/src_common/freemaster_bdm.o
Or specify the range. Considering you cannot predict the exact location where that buffer will be stored you'd need to specify the entire RAM range.
Thank you for the reply but that does not exist in my freemaster_bdm.o file nor can I search and find it.
