Hello,
I have an application using a TCP over serial plugin, and it seems to be connecting to the desktop application.
Now, I need to implement some pytest cases with integration of FreeMASTER Lite. After multiple tries, I found that it was not possible to connect via this plug-in, and I found it's not supported yet.
Do you have any suggestions or feedback? thanks!
Kind regards,
Adnan
Hi @AELhammoudi,
Are you referring to Serial over TCP communication plugin ?
If so, it is supported by FreeMASTER Lite but has experimental status:
I just noticed that the connection string generated by the FreeMASTER tool when exporting service configuration has a wrong format (we will address this issue).
Could you check if your connection string is using the following format:
TCPCOM;{HOST_NAME};port={PORT_NUMBER};timeout={TIMEOUT_IN_MS}
example:
{
...
"connections": [
{
"name": "preset",
"description": "Default connection",
"connection_string": "TCPCOM;127.0.0.1;port=5001;timeout=2000"
}
]
...
}
Let us know if you are still facing issues using this feature so we can improve its stability.
Kind regards,
Iulian
Hi @iulian_stan ,
Thank you for your response!
I'm referring to this one, are they identical?
kind regards,
Adnan
Hi Adnan,
Yes, that's the one I was referring to.
Hi @iulian_stan
Thanks for your reply.
I've attempted to modify the string connection to TCPCOM before posting here, and today I tried again with no success.
The error I'm encountering after running the test case is "Cannot connect to the server." I will attach the logs for the error to provide more insight.
I also attempted to change the connection string to DAP. I'm flashing the board via a J-Link probe in DAP-CMSIS mode, and it was able to connect and detect the board. just to demonstrate if FreeMASTER Lite works.
Kind regards,
Adnan
Hi @AELhammoudi,
There's still one change required → the `addr=` part is redundant.
Instead of
TCPCOM;addr=localhost;port=9991;timeout=500
it should be
TCPCOM;localhost;port=9991;timeout=500
'It is intentionally done to match TCP/UDP plugin.
Hi @iulian_stan ,
I believe the modification in the configuration file was not implemented and needs to be changed manually.
However, after removing "addr=" from the string, I encountered a new error "This feature is only available on devices supporting protocol v4 and later". Despite this, the application can still connect via the desktop application.
Kind regards,
Adnan
Hi @AELhammoudi,
This plugin does require a newer version of the FreeMASTER Driver (that support protocol version 4). Could you provide more details about your setup:
Hi @iulian_stan
I am using a customized board for our customer based on iMXRT1075
freemaster_defcfg.h :
/* Define global version macro */
#define FMSTR_VERSION 0x00030004
#define FMSTR_VERSION_STR "3.0.4"
freemaster_cfg.h:
// Select communication interface
#define FMSTR_TRANSPORT FMSTR_SERIAL // Use serial transport layer
#define FMSTR_SERIAL_DRV FMSTR_SERIAL_BSP_COM // Use serial driver for UART
Hi @AELhammoudi,
I was able to reproduce your issue, it seems to be related to the used driver config (I will need to investigate it).
As a work around I could suggest using LPUART (if it is possible in your case):
//! Select communication interface
#define FMSTR_TRANSPORT FMSTR_SERIAL // Use serial transport layer */
#define FMSTR_SERIAL_DRV FMSTR_SERIAL_MCUX_LPUART // Use serial driver for LPUART */
Hi @iulian_stan
thank you for your response!
This is their driver implementation FMSTR_SERIAL_BSP_COM which is customized.
// Select communication interface
#define FMSTR_TRANSPORT FMSTR_SERIAL // Use serial transport layer
#define FMSTR_SERIAL_DRV FMSTR_SERIAL_BSP_COM // Use serial driver for UART
I don't think I can change it to a different driver configuration.
which driver configurations you were able to reproduce same issue with?
kind regards,
Adnan
I used USB CDC communication configuration:
#define FMSTR_TRANSPORT FMSTR_SERIAL
#define FMSTR_SERIAL_DRV FMSTR_SERIAL_MCUX_USB
and got the same "This feature is only available on devices supporting protocol v4 and later" error although Driver version 3.0.4 does support protocol v4.
I thought that you used a variation of USB CDC, I did not know that you had a custom implementation. Did you use an existing communication driver as code base or is it fully custom ?
Hi @iulian_stan
Our client uses a fully customized driver trying to process the serial stream passed through the CAN interface.
I am curious about this plugin and how it can be used in FreeMASTER Lite, should I report the issue or do I have to wait?
If you need further info, please let me know.
Kind regards,
Adnan
Hi @AELhammoudi,
Considering FreeMASTER desktop tool is working properly with the custom driver there is an issue on FreeMASTER Lite side. At this point I logged the USB CDC issue that I was able to reproduce. Hopefully, it has the same root cause as the one you are facing.
Unfortunately, there is no short solution but to use FreeMASTER desktop tool. I may come with updates on FreeMASTER Lite in a few weeks.
In case you or your client received assistance from NXP engineers for the custom driver implementation, I could follow up with them internally. In this case please mail me their contact info.
Kind regards,
Iulian
Hello @iulian_stan
I am not aware of that point of the implementation support, but I will notify the responsible to deliver this note, in case I received a useful info I will inform you for sure.
Also, I hope if something show up in the near feature please drop it here.
thanks for your support!
kind regards,
Adnan
Kin