Not able to detect AVNET MT3620 (AVNET AES-MS-MT3620-M-G-3) Custom Board.

Question

Hi,

We have developed a custom board with AVNET AES-MS-MT3620-M-G-3 module. Currently this device is not getting detected when connected to the PC. We are using a Windows 11 PC to communicate with the device. The device is not claimed. While trying to create the tenant we are facing connection issue with the device.

Please see the output when we run the command "azsphere device show-attached"

Response while performing rescan-attached:

When connected the Debug port of the device, these logs were obtained when reset button was pressed.

As we have the connection issue , we have verified the configurations that are already addressed in the window

Azure Sphere SDK is installed.

Azure Sphere Device communication service is running.

Windows TAP-adapter is configured properly.

Before having the custom board we have developed a custom application for the same with the help of AVNET MT3620 Dev Kit. We haven't faced this issue while working with the dev kit. We were able to claim and run the application.

Any other configurations need to be checked for detecting the device. What are all the steps involved when a device is connected PC?

Answer 1

Hi @Georgin Jacob I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer .

Error Message:

Could not connect to an Azure sphere device. Please check the device is correctly connected. Please run "azsphere device list-attached" to see the attached devices.

Solution:

The EEPROM with FTDI was blank when we got the custom board.

Programming the EEPROM according to the steps provided in this link : FTDI FT_PROG programming tool

enabled the system to get detected using the device using the command "azsphere device rescan-attached".

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

I hope this helps!

If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.

Answer 2

Hi @LeelaRajeshSayana-MSFT , Thank you for attending my question. We were able to figure out the issue and solve it.

The EEPROM with FTDI was blank when we got the custom board.

We programmed the EEPROM according to the steps provided in this link : https://learn.microsoft.com/en-us/azure-sphere/hardware/mt3620-mcu-program-debug-interface?view=azure-sphere-legacy#ftdi-ft_prog-programming-tool .

After that system is able to detect the device using the command "azsphere device rescan-attached".