This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 35%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
I am working on a project involving a client device that spits out serial data over a USB port. The client device will talk to any FTDI interface that is plugged in. Neither I nor my team are hardware developers so I was wondering if anyone has any experience using the Avnet MT3620 dev kit and getting the FTDI chipset to start listening via the USB power/data connector on the dev kit? The current examples are a little generic and cryptic. Any assistance from the community would be appreciated. Thank you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Mark Scott Can you please share what examples have you referred earlier? I am enquiring at the moment and update you with my findings. Appreciate your time and patience.
@AshokPeddakotla-MSFT I've looked at the following resources
The team is looking for something more specific to making use of the using the FTDI chip reading serial data via the MT3620 dev kit usb/power port.
Thanks.
-Mark
@AshokPeddakotla-MSFT Additionally, this example https://learn.microsoft.com/en-us/samples/azure-samples/azure-rtos-on-azure-sphere-mediatek-mt3620/azure-rtos-on-azure-sphere-mediatek-mt3620/ says to add a USB to Serial adapter to the dev kit. It's confusing as to why this is required. My understanding is that the Avnet MT3620 already has an FTDI chipset onboard. Why would another one be required? If you could please clarify this, it would be helpful. Thank you.
@Mark Scott Could you please confirm, have you referred the Tutorial: Build a real-time capable application?
We have confirmation that the Avnet MT3620 dev kit can't use the onboard FTDI chipset to listen to USB serial data. This would explain why the existing demos say to use FTDI friend or other board.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 72%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
@Mark Scott - You are right. MT3620 comes with an in-built FTDI chipset. This FTDI is used for USB power/data connectivity and other built-in functions. For custom applications to use the UART, MT3620 requires an additional USB to serial adapter which is what the documentation refers to.
What documentation? Could you please include a link to some documentation that mentions this? I haven't seen any documentation that specifically calls this out. Thank you.
The documentation reference was to the samples using additional FTDI friend for displaying output.
UART Sample - https://github.com/Azure/azure-sphere-samples/tree/master/Samples/UART/UART_HighLevelApp
MT3620 real-time capability application using Azure RTOS - https://learn.microsoft.com/en-us/samples/azure-samples/azure-rtos-on-azure-sphere-mediatek-mt3620/azure-rtos-on-azure-sphere-mediatek-mt3620/
Thank you for the additional info. fwiw - for non-hardware developers, seeing that the Azure Sphere MT3620 dev kit has an FTDI chip onboard is a little misleading in this use case. Trying to ramp up very quickly, our initial impression was that we could use it for reading serial data via the USB port. Having to add another board to accomplish this task is very confusing.
Thanks for your feedback, Mark! I will forward your feedback to our documentation team.