Freemaster communication plugin development

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Freemaster communication plugin development

Jump to solution
926 Views
agostinofacotti
Contributor III

Hi all,

is there any resources about Freemaster communication plugins?

I just need a translation from serial to a similar protocol and would be great to write a small plugin to do the job but i cannot find any documentation...

Thanks for your support,

best regards,

agostino

1 Solution
798 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

Unfortunately, there is no publicly available documentation describing the development of FreeMASTER communication plug-ins. The necessary header files are available in the installation though.

 

In general, the plug-in is a 32bit COM+ object supporting the IMcbCommPlugin and IMcbCommPluginInfo interfaces as defined in the mcbcom_i.idl file (see in FreeMASTER installation). The FreeMASTER 2.5 supports a new communication protocol (internally numbered as v4) so there is also a new interface called IMcbCommPluginV4. The key function is called “SendRecvPacket” whose goal is to deliver the command and receive a response from target microcontroller using an arbitrary transport interface.

 

One  information missing in the mcbcom_i.idl file is that the COM+ plugin object should be registered in category with CATID identifier 48A185C0-FFDB-11d3-80E3-00C04F176153 so it becomes discoverable by the FreeMASTER application.

 

When using a completely different transport protocol, the SendRecvPacket must “emulate” the behavior of the FreeMASTER protocol. It should decode the command passed by caller and use a custom protocol to do a desired action. The response received by custom protocol should then be returned to caller again in the way defined by FreeMASTER protocol.

 

The command and response format used by SendRecvPacket must be compatible with selected version of protocol as defined in file mcbcom.h. The new V4 protocol uses commands 0x20…0x34, older protocols use commands 0x01..0x15 and “fast” commands 0xc0..0xf1. The old protocol is documented in mcbcom.chm file distributed with FreeMASTER 2.0 installation. Protocol V4 specification is not yet public, we can send you a draft if you choose to use this version.

regards,

Peter

View solution in original post

2 Replies
799 Views
petervlna
NXP TechSupport
NXP TechSupport

Hello,

Unfortunately, there is no publicly available documentation describing the development of FreeMASTER communication plug-ins. The necessary header files are available in the installation though.

 

In general, the plug-in is a 32bit COM+ object supporting the IMcbCommPlugin and IMcbCommPluginInfo interfaces as defined in the mcbcom_i.idl file (see in FreeMASTER installation). The FreeMASTER 2.5 supports a new communication protocol (internally numbered as v4) so there is also a new interface called IMcbCommPluginV4. The key function is called “SendRecvPacket” whose goal is to deliver the command and receive a response from target microcontroller using an arbitrary transport interface.

 

One  information missing in the mcbcom_i.idl file is that the COM+ plugin object should be registered in category with CATID identifier 48A185C0-FFDB-11d3-80E3-00C04F176153 so it becomes discoverable by the FreeMASTER application.

 

When using a completely different transport protocol, the SendRecvPacket must “emulate” the behavior of the FreeMASTER protocol. It should decode the command passed by caller and use a custom protocol to do a desired action. The response received by custom protocol should then be returned to caller again in the way defined by FreeMASTER protocol.

 

The command and response format used by SendRecvPacket must be compatible with selected version of protocol as defined in file mcbcom.h. The new V4 protocol uses commands 0x20…0x34, older protocols use commands 0x01..0x15 and “fast” commands 0xc0..0xf1. The old protocol is documented in mcbcom.chm file distributed with FreeMASTER 2.0 installation. Protocol V4 specification is not yet public, we can send you a draft if you choose to use this version.

regards,

Peter

798 Views
agostinofacotti
Contributor III

Hi Peter,

thank for your kind suggestions: you've provided me enough informations to start;

about the V4 protocol I think is not necessary to have the documentation right now, I'll begin to study the previous version and make it work first :-)

Regards,

agostino

0 Kudos