FreeMASTER 3.0 Problem with the Recorder

cancel
Showing results for 
Search instead for 
Did you mean: 

FreeMASTER 3.0 Problem with the Recorder

Jump to solution
173 Views
Contributor I

Hi there,

I have installed FreeMASTER 3.0, I didn't change communication drivers on my project. After I connect with PDBDM Variable Watch and Oscilloscopes work with no issues.

But recorder is stuck in "Stopped, waiting for acknowledgement" state as shown below.

 pastedImage_1.png

HW instance is shown as 0: not found;

pastedImage_2.png

Then, instead of the old drivers, I tried to set up the new drivers and gave a shot. Found the communication buffer in my .map file;

pastedImage_4.png

But FreeMASTER doesn't find the buffer address. Manually typing the address will not result in making the connection.

Any help on finding the issue?

Thanks.

1 Solution
12 Views
NXP Employee
NXP Employee

Hello,

the FreeMASTER 3.0 should work well with old driver and old protocol implementation on all transports - including the PDBDM. It is normal that the Recorder settings shows the recorder 0 as "not found" - this is because the old driver version does not assign any name to that recorder instance. We should have probably called it "0:default", to avoid such confusion.

We have identified an issue with manual recorder stopping when the old driver is used - and this is probably what you are facing. The fix will appear in the upcoming release. The issue only affects manual stopping, recorder should still stop fine when a recorder is stopped by a trigger variable.

You can try a patched version of the communication DLL which should address this issue. Just copy DLL from this link to FreeMASTER installation folder..

Thanks,

Michal

View solution in original post

3 Replies
13 Views
NXP Employee
NXP Employee

Hello,

the FreeMASTER 3.0 should work well with old driver and old protocol implementation on all transports - including the PDBDM. It is normal that the Recorder settings shows the recorder 0 as "not found" - this is because the old driver version does not assign any name to that recorder instance. We should have probably called it "0:default", to avoid such confusion.

We have identified an issue with manual recorder stopping when the old driver is used - and this is probably what you are facing. The fix will appear in the upcoming release. The issue only affects manual stopping, recorder should still stop fine when a recorder is stopped by a trigger variable.

You can try a patched version of the communication DLL which should address this issue. Just copy DLL from this link to FreeMASTER installation folder..

Thanks,

Michal

View solution in original post

12 Views
Contributor I

Thank you for the response. The patched DLL fixed the issue as you've said. I can use Freemaster 3.0 with my old comm. drivers without any issues.

Thank you.

Burak

0 Kudos
12 Views
NXP Employee
NXP Employee

Thank you for your feedback. The fixed DLL will appear along with other fixes and updates in version 3.0.1 early February.

Regards,

Michal

0 Kudos