Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
2,226 Views

I210 controller is not working, if we set other than Auto-negotiation in the controller side

Jump to solution

Hi,

I have observed that the driver is not working, if we set something other1than Auto-Negotiation in the board side (I.e. 100-Half, 10-Full etc.).

I am working with I210's internal PHY.

The sequence for setting some speed/duplexity in PHY is mentioned in section 4.3.1.4 PHY Reset of the data sheet.

 

I have found that all other steps are OK, but setp 7"Wait for the CFG_DONE bit (EEMNGCTL.CFG_DONE0)." not OK. This bit is never getting set.

 

I have tried to perform some delay(around 100ms) instead of step 7, and rest of the sequence as sequence 4.3.1.4 PHY Reset. In that case, the driver worked properly in 100/Full case.

Could anyone help in this matter.

Please note I have checked this with another different board(that means another type of target board,not the another copy of same type board). And have not faced this problem.

Thanks and Regards,

Sumit Kumar Paul

0 Kudos

Accepted Solutions
Highlighted
Moderator
18 Views

Hello, SumitGemini :

Thank you for contacting Intel Embedded Community.

In order to be on the same page, we would like to address the following questions:

Could you please tell us if the design related to this situation has been developed by you or by a third party company? In case that it is a third-party product, could you please give us all the information related to it? If it has been developed by you, how many units show this behavior? could you please let us where are stated the guidelines to develop it?

Could you please attach screenshots related to this condition?

Please let us know all the information that may answer the previous questions.

We really appreciate your cooperation.

Best regards,

Carlos_A .

View solution in original post

0 Kudos
9 Replies
Highlighted
Moderator
19 Views

Hello, SumitGemini :

Thank you for contacting Intel Embedded Community.

In order to be on the same page, we would like to address the following questions:

Could you please tell us if the design related to this situation has been developed by you or by a third party company? In case that it is a third-party product, could you please give us all the information related to it? If it has been developed by you, how many units show this behavior? could you please let us where are stated the guidelines to develop it?

Could you please attach screenshots related to this condition?

Please let us know all the information that may answer the previous questions.

We really appreciate your cooperation.

Best regards,

Carlos_A .

View solution in original post

0 Kudos
Highlighted
Beginner
18 Views

Hi Carlos,

Thank you for your prompt reply.

>Could you please tell us if the design related to this situation has been developed by you or by a third party company?

The driver software is developed by me.This driver is to be worked with some RTOS (not Linux). The hardware board is developed by some third party.

>In case that it is a third-party product, could you please give us all the information related to it?

Currently I cannot disclose those information for confidentiality reasons. Please wait, let me check if I can share some information with you.

>Could you please attach screenshots related to this condition?

There is no such screen shots.

I want to share one information. I am getting this problem with two different hardware boards. Each one of them is manufactured by different H/W vendors.

Please let me know if you have any further queries.

Thank you very much for your kind co-operation.

0 Kudos
Highlighted
Moderator
18 Views

Hello, sumitkumarpaul:

Thanks for your reply.

Based on your previous communication, could you please give us all the details and information related to the mentioned third party hardware board?

We really appreciate your collaboration to find the best way possible to help you.

Best regards,

Carlos_A.

0 Kudos
Highlighted
Beginner
18 Views

Hi Carlos A,

Thank you for your reply.

Following are the details,

i) Hardware board name and version. SOM-6867 (do not know the detail version) ii)H/W manufacturer of the board. Advantech iii)Details of the board http://support.advantech.co.jp/support/SearchResult.aspx?keyword=SOM-6867&searchtabs=Datasheet http://support.advantech.co.jp/support/SearchResult.aspx?keyword=SOM-6867&searchtabs=Datasheet

Please let me know if any further information is needed?

0 Kudos
Highlighted
Moderator
18 Views

Hello, sumitkumarpaul:

Thanks for your reply.

Based on the provided information, we would like to help you but the information of the affected design should be provided by its manufacturer.

Due to this fact, please address your consultations related to it as a reference at the http://iotforum.advantech.com/ Advantech IoT Developer Forum, https://server.iad.liveperson.net/hc/68676965/?cmd=file&file=visitorWantsToChat&site=68676965&SESSIO... Advantech Chat Window, and/or by filling out the http://www.advantech.com/contact/inquiryrequestform?type=Embedded%2bComputing&subject=Price%2band%2b... Advantech Service Request form.

We hope that this information is useful to you.

Best regards,

Carlos_A.

0 Kudos
Highlighted
Beginner
18 Views

Hi Carlos,

Thank you for your reply.

As you mentioned, I have posted the question in http://iotforum.advantech.com/ Advantech IoT Developer Forum.

In the mean time, I have done the same experiment with another hardware board(Justice board). And found that, the problem is same in that board also.

So, I suspect this may not be a problem of the target board. But I think this maybe a problem of I210 controller(or may be the specification document).

Could you please look into this matter?

Thanks and Regards,

Sumit Kumar Paul

0 Kudos
Highlighted
Moderator
18 Views

Hello, sumitkumarpaul:

Thanks for your reply.

We suggest you use the https://downloadcenter.intel.com/download/13663/Intel-Network-Adapter-Driver-for-82575-6-82580-I350-... Intel(R) Network Adapter Driver for I210/211-Based Gigabit Network Connections for Linux*. This is the raw files that has comments throughout explaining what the function is for. You would take those files and compile it for the cited third-party system, or use the comments to help build their own. Please let us know the outcomes of these changes.

We hope that this information may help you.

Best regards,

Carlos_A.

0 Kudos
Highlighted
Beginner
18 Views

Hi Carlos,

Thank you for your suggestion.

According to your suggestion, I have checked the Linux driver. I have some doubts. I have found that in some places, the Linux driver is not implemented

as per the specification.

For example,

1. The address of EEMNGCTL register is mentioned in the datasheet is 0x12030. But the Linux code use the address 0x01010.

2. There are some delay in the code, which are not mentioned in the specification.(Delay before H/W semaphore release)

etc.

It would be very helpful, if you can share your idea about these differences.

Please note, as I mentioned earlier our main problem is

"EEMNGCTL.CFG_DONE0 is never getting set after PHY reset operation".

We have tried the register address 0x01010(as per the Linux code). But have not found any differences in the result.

Thanks and Regards,

Sumit Kumar Paul

0 Kudos
Highlighted
Moderator
18 Views

Hello, sumitkumarpaul:

Thanks for your reply.

We suggest you address your consultations to develop your own driver to the Operating System (OS) developer because they have clear what is supported. As a reference, feel free to use the following website:

https://askubuntu.com/questions Newest Questions - Ask Ubuntu

Please keep in mind that the information to support third-party projects should be provided by their developers, so please contact them.

We hope that this information may help you.

Best regards,

Carlos_A.

0 Kudos