Not working in different hardware

[YashasDG]

I used the same FreeRTOS+TCP library which is modified with raw socket but while using even TCP socket is also not working, unable to ping also.

[embeddedcrab]

Hello Yasha, I believe you have tested the FreeRTOS+TCP official stack with your hardware and a particular Ethernet or Wifi port is available for it. If that is confirmed, I do not see any problem in this repo updates that you will not even get pings.
I have also provided the RAW Sockets .pcap[named as IPPROTO_RAW and RAW_Sockets] output for confirmation.

If the problem is because of different hw platform then please check your Network Interface Port Files [in portable/NetworkInterface].

I am not sure of latest changes in FreeRTOS+Plus stack but this should work if port is correct.

Good Luck & Keep Going!

[YashasDG]

Hi Hemant, Thanks for the response. Actually in our hardware with the normal FreeRTOS+TCP it is working fine, but when we replaced this normal TCP also not working and also ping. Can you please guide me on this.

…

________________________________ From: Hemant Sharma ***@***.***> Sent: Wednesday, February 1, 2023 12:33:15 AM To: embeddedcrab/FreeRTOS_RAW_Sockets ***@***.***> Cc: Yashas D G ***@***.***>; Author ***@***.***> Subject: Re: [embeddedcrab/FreeRTOS_RAW_Sockets] Not working in different hardware (Issue #1) CAUTION: This email comes from outside of Utthunga. Make sure you verify the sender before clicking any links or downloading/opening attachments. If this email looks suspicious, Forward it and raise a ticket on IThelpdesk/CyberSquad team. Hello Yasha, I believe you have tested the FreeRTOS+TCP official stack with your hardware and a particular Ethernet or Wifi port is available for it. If that is confirmed, I do not see any problem in this repo updates that you will not even get pings. I have also provided the RAW Sockets .pcap[named as IPPROTO_RAW and RAW_Sockets] output for confirmation. If the problem is because of different hw platform then please check your Network Interface Port Files [in portable/NetworkInterface]. I am not sure of latest changes in FreeRTOS+Plus stack but this should work if port is correct. Good Luck & Keep Going! — Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUXSRJCRJY5QDEKWPPW2XV3WVFOXHANCNFSM6AAAAAAUL7LPZE>. You are receiving this because you authored the thread.Message ID: ***@***.***> DISCLAIMER: This email and any files transmitted with it are confidential, intended solely for the use of the individual or entity to whom they are addressed. If you are not the named addressee, copying, dissemination, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Any views or opinions presented in this email are solely those of the author and do not necessarily represent the organization. Computer viruses can be transmitted via email. Utthunga accepts no liability for any damage caused by any virus transmitted by this email or otherwise.

[embeddedcrab]

I need some information to diagnose your problem:

1. Which HW you are using, Board Information and network interface port (given by FreeRTOS-Plus?)
2. Using latest FreeRTOS-Plus stack?

Now you need to compare the source code a bit if you are using latest stack from (https://github.com/FreeRTOS/FreeRTOS-Plus-TCP), I have not gone through latest changes, if significant!

And you also mentioned that even ping is not working with TCP on this repo stack, did you check Network Capture for that run to check what is happening on Network.. and try to add some break points in your Network Interface port files so that you could know the data transfer from/to HW and other System.

Good Luck and Keep Going!

[YashasDG]

I need some information to diagnose your problem:

1. Which HW you are using, Board Information and network interface port (given by FreeRTOS-Plus?)
2. Using latest FreeRTOS-Plus stack?

Now you need to compare the source code a bit if you are using latest stack from (https://github.com/FreeRTOS/FreeRTOS-Plus-TCP), I have not gone through latest changes, if significant!

And you also mentioned that even ping is not working with TCP on this repo stack, did you check Network Capture for that run to check what is happening on Network.. and try to add some break points in your Network Interface port files so that you could know the data transfer from/to HW and other System.

Good Luck and Keep Going!

I need one information, for example if the FreeRTOS+TCP stack is already available in our environment and it is linked to our source codes.
Can we just replace only the FreeRTOS+TCP folders source files, or any other files also needs to be replaced.
And also on the networkinterface source file whether anything needs to be modified in that file or the default source code will work with this.

Observations:

1. Once after FreeTOS_IP_Init API is executed ethernet driver is getting up and even its blinking
2. But after that creating a TCP socket and other functions required for the server code is enabled and then when we are trying to ping it is unable to ping

[embeddedcrab]

Directly replacing all files related to FreeRTOS TCP/IP would not be a better way, because there might be multiple changes but can be tried, iff port files are working fine. There is a port layer which connects your stack with actual hardware/ethernet.

If your communication with latest stack is working fine then your port files are Ok. If you particularly want to try for RAW Sockets then there are multiple files which has been changed and you need to compare b/w them to exactly get the changes.

Solution for you: You can take your port files with this repo stack and make sure that interfacing functions are same as present in this stack (if there are some changes w.r.t. latest one), this should work out.

Good Luck & Keep Going!