Error in MACT

fanlikang · ‎03-06-2023

In the process of using MACT, there was an error that could not be solved at present. Please ask for help

1.The starting MACT interface is as follows

2. Start communication configuration. The configuration process is as follows

It seems that the configuration is normal, and the light with normal communication can also be on

3.However, it finally failed. The following prompt appears, and MACT cannot be used normally

Software currently used: Freemaster 3.0 Codewheel 11.0

RadekS · ‎03-09-2023

Hi fanlikang,

Please ensure that you exected the right version of FreeMASTER. Go to menu -> Help -> About FreeMASTER

The new FM version will not rewrite the old one and the search at the start menu shows you only one of executable files.

In my case, the list of communication plug-ins looks different:

Just Idea: If you download and install PEmicro Multilink Resource package you may execute the c:\PEMicro\Multilink_Resources\PEFirmwareConfig.exe and check whether your Mutilink probe contains the right firmware for S12Z.

Note: The Mutilink firmware should be updated automatically during flashing code into MCU in CodeWarrior for MCU IDE. The PEFirmwareConfig.exe is way how to do it manualy.

Idea2: You may try install the FreeMASTER Communication driver 2.0 from FM web page

This installation shouldn't be necessary, since driver is already part of example code.
BTW: which S12ZVM motor control software project did you upload into MCU?

BR

RadekS

View solution in original post

lama · ‎03-07-2023

Hi,

it looks like something wrong in BDM connection.

In the picture 3 you selected HCS12 but you use HCS12Z device. Could you try to change it?

Do you use own board. If yes may I see schematic?

There is an report in Chinese. I am sorry I am not able to translate to English it from this image.

Best regards,

Ladislav

fanlikang · ‎03-08-2023

Thank you very much for your patience. Yes, we use our own control board. I have tried to switch HCS12 to HCS12S, but the situation has not improved. It is worth noting that after the change, freemaster does show that the connection is successful, but the variables in the interface have not changed at all. I beg your help.

RadekS · ‎03-09-2023

Hello fanlikang,

Thank you very much for these pictures. It seems that the connection works - according to CPU register values.

I would like to join my colleague (your FreeMASTER Community thread) in recommending to use newer FreeMASTER version e.g version 3.2.

https://www.nxp.com/freemaster

In this version, it is possible to select a clock for the BDM connection.

Typically the BDM runs on bus clock speed. However, when bus clock is set close to maximum frequency, sometimes there might be some unstability of BDM clock (especially during PLL frequency change). Therefore I would like to recomend to configure BDM clock to fix internal 1MHz oscilator. The BDM connection will be slower, but more reliable. This feature was added also into newest FreeMASTER

According to description, you should uncheck the highlighted checkbox.

I think that settings 300rpms in the Scalar Control is quite high. I would like to recommend to start rather with 50 or 100rpms and slowly increase the V_rpm factor. Typically, the motor at kits starts moving around value in range 100 ~ 150.

I hope it helps you.

Best regards

Radek

fanlikang · ‎03-09-2023

Thank you very much for your patience. Now Freemaster's version number is 3.2. I tried to debug BDM using the method you taught, but unfortunately, this version still does not have the interface you said. I don't know where the problem is.

I have listed my debugging steps in the new version. Please see what is wrong.

Thank you very much for your patient guidance.