Avnet Azure Sphere Starter Kit does not work with the Ethernet examples (new hardware configuration build required) RRS feed

  • Question

  • The Issue


    The current Ethernet implementation requires that the user side load a special hardware imagepackage to the device as documented here.  This package configures the Sphere Hardware and OS to use the ENC28J60 Ethernet device on interface ISU0 with GPIO 5 to expose eth0 on the board.  This hardware configuration works fine with the Seeed board, since these interfaces are available on the header pins and are not being used for other development kit features.


    On the Avnet Starter Kit the desired Ethernet hardware solution is to use a ETH Click board.  The ETH Click board uses the same ENC28J60 device, and using the click sockets makes for a clean solution.  The problem is that the Click Sockets do not use the same interfaces (ISU0 and GPIO 5) as the existing hardware configuration.  The click sockets use ISU1 and GPIO 2.


    Because of these differences the current hardware configuration file, will not work with the Starter Kit.


    The Solution


    The solution to this issue is for have another hardware configuration that uses ISU1 and GPIO 2.  This should be an easy change, but we don’t have access to this source.  Microsoft needs to make these changes and supply the new hardware configuration file.

    Wednesday, July 3, 2019 6:32 PM

All replies

  • Hi,

    Thank you so much for the detailed description of the issue. Appreciate for sharing the resolution, this would certainly benefit other community members.

    We will investigate this and update as earliest. The best way to address this feedback is to create an issue under the same azure sphere documentation so that it can be assigned to the respective team to make changes to the repo.

    Thursday, July 4, 2019 7:07 AM
  • Can you offer any insight as to when we may see a SPI ethernet hardware configuration build that's compatible with the Avnet Starter Kit?  We've got lots of fresh engineering minds using the kit and not being able to use ethernet will surly be a blocker for some.

    The original request was posted on the documentation page as suggested, but it was closed after it was passed on to the development team.

    Thanks for any update you can offer!

    Friday, August 2, 2019 3:01 PM
  • Tuesday, August 6, 2019 8:14 PM
  • Any update on this issue ? I have a really big client which really liked the Azure Sphere solution. This issue is open for more than a month and Client have asked me to explore other options and move away. I have spent lot of effort in development. Please suggest any rough ETA so I can plan accordingly. 
    Thursday, August 15, 2019 9:41 PM
  • @RohitSin

    If it helps, please note that other Azure Sphere dev kits support hard-wired Ethernet. In particular, the Seeed MT3620 dev kit has an Ethernet shield available.

    Reference: https://github.com/MicrosoftDocs/azure-sphere-issues/issues/114

    Tuesday, October 29, 2019 12:46 PM
  • For future reference this is the current suggestion from Azure Sphere team: 

    "Our recommendation is to attach an Ethernet port using the configuration spelled out on this pagehttps://docs.microsoft.com/en-us/azure-sphere/network/connect-ethernet

    Specifically, this page enumerates that Ethernet should be connected to SPI via ISU0 with interrupts on GPIO5."

    Thursday, November 14, 2019 7:52 PM