AVNET Azure Sphere MT3620 Starter Kit

View table of contents ...  

image

Sign Up For the Webinar: IoT Skills: Learn How To Rapidly Secure Your IoT Design with Azure Sphere

 

 

{tabbedtable} Tab LabelTab Content
About

This RoadTest is an opportunity to test and experiment with an IoT microcontroller ecosystem from the device through connectivity to the cloud using the Avnet Azure Sphere MT3620 Starter Kit, the Azure Sphere O/S (based on open source Linux), and the Microsoft Azure IoT Hub.

 

Goals of this RoadTest

There are two goals for this Roadtest:

  • RoadTest the Device: RoadTesters will receive an Azure Sphere MT3620 Starter Kit to unbox, test, and build projects with. We want to you to test the device and put it through its paces.
  • RoadTest the Device to Cloud Connectivity: Roadtesters will take the Azure Sphere MT3620 and connect it to the Azure IoT Hub.  We want to test the cloud security and connectivity to gain insights into its use and capabilities from the point of view of an individual developer.

 

Kit Contents

RoadTesters will receive the AVNET Azure Sphere Starter kit which includes Carrier board with Azure Sphere MT3620 module, a USB Cable, and a Quick Start Card.

Avnet Azure Sphere MT3620 Starter Kit

The Avnet Azure Sphere MT3620 Starter Kit supports rapid prototyping of highly secure, end-to-end IoT implementations using Microsoft’s Azure Sphere--a solution for creating highly-secured, connected Microcontroller (MCU) devices,

 

The kit includes a small form-factor carrier board, featuring a production-ready MT3620 Sphere module, based on the MT3620 SoC, which has built-in Microsoft security, Wi-Fi connectivity, and the combined versatility and power of an Arm® Cortex™-A7 processor with the low overhead and real-time guarantees of two Arm Cortex-M4F microcontrollers.

image

 

The carrier board connects the Sphere module I/Os to two MikroE Click sockets, an I2C Grove connector, a connector supporting the addition of a 128 x 64 OLED graphical display, a 3D accelerometer, 3D Gyro, temperature sensor, and an ambient light sensor. Debugging is accomplished through a USB-to-UART interface, which also provides the necessary 5V power for the board.

 

User applications for the embedded Sphere controller are developed in C using Microsoft’s Visual Studio IDE and the Azure Sphere SDK. The combination of Visual Studio, the versatile carrier card, and the production ready Sphere module delivers a powerful starting point for IoT developers interested in learning, prototyping, and deploying Azure Sphere based solutions.

 

Additional Information

 

Azure Sphere MT3620 Modules

The Avnet Azure Sphere MT3620 Modules support Microsoft’s Azure Sphere end-to-end solution for highly-secured, WiFi connected Microcontroller (MCU) devices. The production-ready, certified modules come in two versions; an on-board chip antenna module for cost-optimized systems, and an external U.FL antenna module supporting two external antennas for applications requiring higher performance, external antennas. Both modules are pin and footprint compatible, allowing for easy design migration and end-product enhancements.

image

By integrating all the necessary support and RF front end circuitry onto the small 33 mm x 22 mm module, design time has been reduced for implementing Sphere-based solutions. More importantly, developers can leverage the modules wireless certifications (pending) for their end-product, saving considerable certification costs and testing time.

image

The Azure Sphere MT3620 modules are based on the MT3620AN SoC, which supports dual-band 802.11 a/b/g/n WiFi connectivity, a 500 MHz Arm® Cortex™-A7 core for user applications, and two general purpose 200MHz Arm Cortex-M4F I/O subsystem cores designed to support real-time requirements. The on-chip peripherals (GPIO, UART, I2C, SPI, PWM and ADC) can be mapped to dedicated I/O pins on the module for connection to external sensors, I/O connectors, or other user application circuits.

 

Additional Information

Important Dates

Enrollment Begin: June 4 2019

Enrollment Ends: June 30 2019

RoadTesters Selected: Aug 5 2019

Product Shipped: Aug 8 2019

RoadTesting Begins: Aug 15 2019

Reminder/Update Email: Sept 15 2019

Submit Reviews By: Oct 15 2019

*The element14 RoadTest Staff will send this reminder/update email.

**If a RoadTester is unable to meet the deadline, please notify the RoadTest Program Manager, , as soon as possible before the deadline.

RoadTesters

deadline Nov 10 2019

Terms and Conditions

Terms and Conditions: AVNET Azure Sphere MT3620 Starter Kit RoadTest

 

These are the terms and conditions which govern the AVNET Azure Sphere MT3620 Starter Kit RoadTest contest. This Contest requires participants to submit an application indicating their previous experience with this type of equipment/component, information on what they would do to test the equipment or component, and the applicant’s desire to post a thorough review of their experience with images, photos, or other supplemental materials. Participants will be required to meet the Conditions for Participation.  The winners of this RoadTest will receive the item(s) listed below. RoadTest Reviews are due no later than 45 days after the receipt of the item(s). No other prizes are offered.

The Principal terms of the Competition

The following words and phrases are used in these terms and conditions and have the meanings given to them below.

Key dates:

Applications Close: 9 PM (GMT) on June 30 2019

Announcement of Winner (estimated): July 8 2019

Prize: AVNET Azure Sphere MT3620 Starter Kit

Competition Site: https://www.element14.com/community/groups/roadtest?ICID=menubar_resources_roadtest

Site or element14 Community: www.element14.com/community

Judges: members of the element14 community team chosen at the Organiser’s discretion.

Judging Criteria, All of the following which will have equal weighting:

· Demonstrated competence with the technologies including links or descriptions of past projects

· Qualifications as indicated by current job role and/or schooling/vocational training;

· A thorough description of how the prize would be tested;

· Likelihood that the Applicant will blog about the prize and provide a review on element14.com;

· Originality;

· Innovation.

Organiser: Premier Farnell plc (registered in England and Wales under company number 876412) whose registered office is at Farnell House, Forge Lane, Leeds, UK

Conditions for Qualification: in addition to meeting the requirements of these terms, all persons applying to take part in the Contest (each one an Applicant) must:

· Provide a RoadTest application describing what he/she would do if awarded the Prize including similar previous projects, product experience and qualifications

Terms: these terms and conditions which govern the Competition and to which the Organiser reserves the right to make changes from time to time and the latest version of these Terms from time to time will be posted to the Site.

Eligibility

Applications:

Selecting Winners:

Liability:

General:

1.1 Save as set out in these Terms, the Contest is open to any natural or legal person, firm or company or group of natural persons or unincorporated body.

1.2 All Applicants must be aged at least 18 at the time of their application.

1.3 Applicants must not enter the RoadTest if doing so or taking part may:

1.3.1 cause the Organiser and/or themselves to be in breach of any agreement (including but not limited to any contract of employment) to which they are a party or in breach of any law, regulation or rule having the force of law to which the Organiser or the Applicant may be subject or any policy of the Organiser or the Sponsor;

1.3.2 Require the Organiser to obtain any licence, authorisation or permission to deal with the Applicant; or

1.3.3 Be in breach of any policy or practice of their employer. Some employers prohibit or restrict their employees from taking part in competitions such as these or receiving prizes under them and the Organiser respects those policies and practices.

The Organiser reserves the right to disqualify any Application made in breach of these Terms and to reject any Application which it reasonably believes may be or become in breach. The Organiser reserves the right to require evidence in such form as the Organiser may reasonably require of any Applicant’s compliance with any of these Terms and to disqualify any Applicant or Participant who cannot provide such evidence reasonably promptly.

1.4 Multiple applications are not permitted.

1.5 Applications may not be submitted by an agent whether acting on behalf of an undisclosed principal or otherwise.

1.6 The Contest is NOT open to:

1.6.1 Any person or entity who is a resident or national of any country which is subject to sanctions, embargoes or national trade restrictions of the United States of America, the European Union or the United Kingdom;

1.6.2 Any employee, director, member, shareholder (as appropriate) or any of their direct families (parents, siblings, spouse, partner, children) (“Direct Families”) of the Organiser and Sponsors; or

2.1 Each Applicant must fully complete and submit a RoadTest Application by the Application Close.

2.2 By submitting a Registration Form, each Applicant:

2.2.1 Authorises the Organiser to use his or her personal data (as defined in the Data Protection Act 1998) for the purposes of running and promoting the RoadTest;

2.2.2 Authorises the Organizer to copy, reproduce and publish their application should they be accepted as a Participant;

2.2.3 Will be deemed to have read, accepted and agree to be bound by these Terms. Applicants are advised to print and keep safe these Terms;

2.2.4 Authorises the Organiser to copy, reproduce and use the Application and/or Review for the purposes of the RoadTest and as otherwise contemplated by these Terms. The Organiser will not be responsible for any inaccuracy, error or omission contained in any reproduction or use of the Project Blogs.

2.2.5 Licenses the Organiser to use the intellectual property in the Project (IP) for the purposes of this Contest. As between the Applicant and the Organiser the IP remains owned by the Applicant.

2.2.6 Grants the Organiser the right to use his or her likeness, photographs, logos, trademarks, audio or video recordings without restriction for the purposes of Contest or the promotion of it or the Site;

2.2.7 Agrees to participate positively in all publicity surrounding the Contest;

2.2.8 Agrees to be responsible for all expenses and costs incurred by him or her in preparing for, entering and participating in the Contest (save for any expenses expressly agreed by the Organiser to be borne by it in these Terms);

2.2.9 Confirms that he or she owns all IP used in his or her application or Project or Blogs and indemnifies the Organiser from any claim by a third party that use of any material provided by an Applicant to the Organiser infringes the intellectual property rights of any third party;

2.2.10 Agrees not to act in any way or fail to act in any way or be associated with any cause or group which would have a negative impact on the reputation of the Organiser and/or the RoadTest.

2.3 All applications submitted to this RoadTest must meet the following criteria:

2.3.1 Applicants must be the author, creator and owner of the proposed review idea. Applicants must not submit someone else’s idea;

2.3.2 The proposed application must be reasonably achievable by the within the time constraints of the Contest;

2.3.3 Applications must not include or propose any of the following, the inclusion of which shall render any proposed application ineligible:

(a) Applications which relate to socially taboo topics, such as illicit drug use or sexual gratification;

(b) Applications that are or could reasonably be considered to be illegal, immoral, discriminatory or offensive as determined by the Organiser;

(c) Applications in relation to them which if accepted would infringe or breach any of the policies or terms of access or use of the Site.

2.4 No Application may contain any of the hazardous substances identified by Article 4 of Directive 2002/95/EC of the European Parliament on the Restrictions on the Use of Substances in Electronic and Electrical Equipment ("the Directive") or the use of such hazardous substances in the in any such Project must not exceed the maximum concentration values set out in the Directive.

3.1 Winners will be selected by the Organiser on the basis of the quality of his or her application and its adherence to these Terms.

3.2 The total number of Winners selected will be at least the minimum number set out above but the actual number is at the sole discretion of the Organizer and/or the Sponsor, if applicable.

3.3 The Organiser will use all reasonable efforts to announce the Winners via an update to the RoadTest page by the date listed above.

3.4 Winners agree to take part in all publicity which the Organiser or the Sponsor wishes to use to promote the RoadTest, the Products featured or other Contests with which the Organiser may be connected from time to time.

3.5 Details of the Winners may also be published in the media.

3.6 Winners are responsible for all applicable taxes, duties or other charges payable in relation to any prize.

3.7

4.1 The Organiser hereby excludes all and any Liability arising out of the Contest or the acceptance, use, quality, condition, suitability or performance of any Prize, even where that Liability may arise from the Organiser’s negligence.

4.2 Nothing in these Terms will affect any Liability of the Organiser for death or personal injury arising from its negligence, for breach of Part II of the Consumer Protection Act 1987 (in the event that any entrant is entitled to claim rights under the Consumer Protection Act 1987) or for any matter in relation to which it would be illegal for the Organiser to exclude or to attempt to exclude its Liability.

4.3 Subject to 4.2, neither the Organiser, any parent company nor any subsidiary of the Organiser or such parent company or any of their directors, officers and employees (together referred to in these terms and the ‘Associates’) makes any guarantee, warranty or representation of any kind, express or implied, with respect to this Competition or the Prizes potentially available under it. Neither the Organiser nor any of its Associates shall be responsible for any Liability that may arise out of or in connection with person’s participation in this Competition, the claiming, redemption or value of any prizes under it, the use or enjoyment of such prizes or any events or circumstances arising out of or in connection with any of them. Any implied warranties of condition, merchantability or suitability or fitness for purpose of any of them are hereby expressly excluded. Wherever used in these Terms, ‘Liability’ shall mean any and all costs, expenses, claims, damages, actions, proceedings, demands, losses and other liabilities (including legal fees and costs on a full indemnity basis) arising directly or indirectly out of or in connection with the matter concerned.

5.1 The RoadTest is organised and sponsored by the Organiser. The Organiser reserves the right to delegate all or any of its powers, rights and obligations arising in relation to the RoadTest to any Associate and certain such rights and powers are assumed by the Organiser on behalf of itself and each Associate. Reference to “Organiser” shall be deemed to include reference to each Associate.

5.2 The RoadTest may be terminated at any time if there are, in the sole opinion of the Organiser, an insufficient number of entries, or if the Applications are not of an appropriate standard for a competition of this nature. The Organiser has the right to cancel or suspend the RoadTest at any time due to circumstances outside its reasonable control.

5.3 The Organiser shall have the sole discretion to disqualify (without correspondence or right of appeal) any Applicant it considers to be adversely affecting the process or the operation of the RoadTest or to be in breach of these Terms or to be acting in a disruptive manner or with intent to annoy, abuse, threaten or harass any other Applicant or Participant.

5.4 The Organiser has the right to amend or add to these Terms from time to time. Revised Terms and Conditions will be posted on the Contest Site and it is a condition of entry to the RoadTest that Applicants agree to comply with these Terms and, if appropriate, such Terms as amended from time to time.

5.5 Headings are for convenience only and do not affect the interpretation or construction of these Terms and Conditions.

5.6 These Terms and the operation of the Contest shall be governed by and construed in accordance with English Law and any claim or matter arising under these Terms shall be subject to the exclusive jurisdiction of the English courts.

RoadTest Reviews
Comments
Anonymous
  • Yes, that is very helpful.  I was struggling with that exact same step.  Thanks!

  • Sure.  I set up a gmail account for kb5dhj.  In the AAD setup, my name was n5kzw and my User Name was n5kzw@kb5dhjgmail.onmicrosoft.com.  I hope this helps.

     

    Regards,

    Ed

  • Could you post or link the example of the properly formatted domain name input?  I have not gotten to that point yet (brand new to Azure, but well versed in AWS and Google Cloud). So far, this all looks extraordinarily complicated. image

  • Thanks to everyone that offered suggestions.  The key was that I did not know how to properly format the domain name input.  Once I found a real-life example, I was able to set up the AAD and claim my device.

  • One of the reasons I tried to get my road test in as early as possible is to try to help with this sort of problem. You should find the solution to that on my road test - it's to do with the need to create a user under Azure AD and log in with that account instead of your personal one.

  • The solution is to support a callback request informing the application that user doesn't exist in the tenant directory hence allow the calling application to support some custom message. This indicates a problem in the AAD. What AAD did you register with?

  • I sincerely hope that the road testers are making good progress.  I have not been able to get past the AADSTS50020 error when running azsphere login from the developers command line.  Sadly, it appears you can't even blink LEDs without getting past this point.

  • Also very excited to participate and contribute in this roadtest, and thank you to for selecting me as an E14 member with little previous activity in the community.

  • You only need the VS shell (which seems to be massive) you should not need to manually install C++ for Linux and Windows, that should be automatically pulled in as required by the Azure Sphere SDK

  • I finished installing the OVA. A few things:

    • The Visual Studio was incomplete, so I used the installer to update and then install both C++ for Linux and Windows.
    • Then installed the Azure Sphere Preview as per instructions
    • Continue for the registration et al.

    Got as far as logon and forgot password. Fell asleep until now. I will work later on this. In the meantime have another VM with code installed the hard way.

     

    Clem

  • Hello Edwin,

     

    I have not read the Eula. Unfortunately. As I started the finished VM, before registering it on Azure, I got the system message to update the license else it will expire in 15 days, not 60 sic. So I checked on the MS site how to upgrade the license for the specific version of W10 of the Virtual Machine, the enterprise edition and I found that the license on the original Microsoft site cots so few. And I got one. I also got one from the company where I work as they have W10 license for W10 enterprise.

     

    And here comes your helpful hint

     

    As I read the EULA, it appears to say that the license is for 60 days only and the product key cannot be updated.  To keep the confusion up to Microsoft's standards, it the EULA also says that Azure Sphere users are granted certain rights in perpetuity.

     

    Then I tried to install the license and in both cases (the one I bought and the one I got from the company, essentially both in theory compatible with the W10 version of this VM) it failed with the message that the license is not compatible. For now, I will use the VM anyway as it works; in the meantime, I should investigate on this issue as the VM is perfectly tailored for the development of the Azure environment and it is a pity I should use in the future another machine.

     

    Enrico

  • It's pretty straightforward, Clem.  Just download and unzip Oracle VirtualBox, and the evaluation image, the start VirtualBox and import the evaluation image.  I did have to go into my BIOS to turn on hardware acceleration.

     

    Regards,

    Ed

  • Enrico, thank you so very much for the link to the VirtualBox image.  The download took 20 hours, but everything installed fine after a minor BIOS tweek.  I am curious as to where you got the information about purchasing a license.  As I read the EULA, it appears to say that the license is for 60 days only and the product key cannot be updated.  To keep the confusion up to Microsoft's standards, it the EULA also says that Azure Sphere users are granted certain rights in perpetuity.

  • it says that if you don't register the key the license expires and you stop using the VM with Windows. I was worried for a while but then I discovered that the licenses cost about 10 euro. Not so expensive as I was expecting.

     

    Enrico

  • Congratulations to the selected road testers.  I opted for the free kit, and I will be interested to see if any of the testers encountered any problems setting up their Azure account.  I'm still working through issues in that area.

    Regards,

    Ed

  • The Microsoft web site says "This VM will expire on 08/21/19."  Any conjecture as to whether this means it the VM can only be downloaded before 8/21, or does the installation on you machine evaporate on 8/21?. 

     

    I would love to install this on my Linux desktop as it has a 1TB drive compared to the 250GB SSD on my Windows 10 laptop, but I'm not going to bother with a 20GB download if it is going to go away in 12 days.

    Regards,

    Ed

  • Are you 0x'Fred' Never would guessed. image

  • This RT and the Raspberry Pi 4 may applications mean Randy must be bleary eyed. Send over the Vi-zine.

    Clem

  •      Just installed Win 10 in Virtual box under Linux Mint. I was able to connect and use the Azure Sphere device. I will write up a HowTo if there are interested people. Just either like and/or mark this replay as helpful and I will know what folks wish this.

    Cheers,

    Clem

  • Thanks for choosing me in this road test and congratulations to the other road tester who got selected.  I am very excited to roadtest this product.