element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Azure Sphere Starter Kit
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Azure Sphere Starter Kit
  • More
  • Cancel
Azure Sphere Starter Kit
Blog Azure Sphere OS 19.09 - New Capabilities for your Starter Kit!
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Azure Sphere Starter Kit to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: peterfenn
  • Date Created: 11 Oct 2019 11:48 PM Date Created
  • Views 3550 views
  • Likes 10 likes
  • Comments 22 comments
  • azure sphere
  • azure sphere mt3620 starter kit
  • azure
  • sphere
  • 19.09
  • mt3620
Related
Recommended

Azure Sphere OS 19.09 - New Capabilities for your Starter Kit!

peterfenn
peterfenn
11 Oct 2019

*** Note! Updated Oct 19, 2019 ***

  • Enabled New Chip Features
  • Enhanced Wi-Fi capabilities
  • API changes
  • SDK Changes
  • Further Tips to Max-Out Your Starter Kit!

Azure Sphere OS 19.09 "major" release brings additional capabilities that are worth checking out.

  • Azure Sphere 19.09 Release Overview
  • Azure Sphere 19.09 Release Notes

image

Insights here on some of the new features you can take advantage of with your Starter Kit...

 

Enabled New Chip Features

ADC inputs and PWM output peripheral functions are now accessible from the high-level A7 user application. The Samples GitHub repository has been updated and now includes new applications that exercise these chip features.

Take a look at the following two examples:

  • ADC_HighLevelApp
  • PWM_HighLevelApp

Nine GPIOs with PWM functionality are accessible on the Avnet Starter Kit. See the table below.
eg. The utility and visual effectiveness of the five user-controlled LEDs (on GPIO4, GPIO5, GPIO8, GPIO9, GPIO10) can be enhanced by implementing PWM control of these GPIO outputs

image

Three GPIOs can be configured as ADC analog input pins on the Avnet Starter Kit:

image

ADC resolution is 12 bits. Maximum sample rate is 2 MHz.

 

Enhanced Wi-Fi capabilities

Good news is that the Wi-Fi capabilities have been enhanced in the 19.09 OS release to:

  1. Enable connection to hidden Wi-Fi networks and
  2. Provide better network discovery in congested Wi-Fi environments.

These features are supported both through the azsphere device wifi command and in the wificonfig API.

Notes!

  • When configuring Wi-Fi settings from the 19.09 command line, the --key parameter (abbreviated as -k) is now replaced by --psk (abbreviated as -p),
    eg.   azsphere device wifi add --ssid MyHotSpot --psk 12345678
  • To delete a Wi-Fi network from the stored Wi-Fi settings, the delete parameter has been replaced by forget
    eg. azsphere device wifi forget --id 0
  • A really important new feature is the availability of the optional --targeted-scan parameter (abbreviated as -t)
    eg.   azsphere device wifi add --ssid MyHotSpot --psk 12345678 -t
    This will force connection to an SSID even if this not among the SSIDs reported by a Wi-Fi scan, or if located in a crowded wireless network environment
    (Make sure to forget instances of the target SSID from list of WiFi networks currently configured, before adding an SSID with the -t targeted-scan parameter)
    More detail on this topic is available here: https://docs.microsoft.com/en-us/azure-sphere/network/wifi-including-ble#enable-targeted-scanning

 

API changes

The 19.09 Azure Sphere OS release includes several changes to the API set:

  1. Promotion of I2C and SPI Beta APIs to LTS APIs (Long Term Support)
  2. Changes to networking Beta APIs. Some previous Beta features have been replaced by new functionality. See Applibs networking.h for the networking API details.
  3. Changes to wificonfig API. See Applibs wificonfig.h for details.
  4. New event notification and event loops Beta APIs to monitor and dispatch events (High-level apps can use these APIs to request notification and defer updates)

 

SDK Changes

The 19.09 Azure Sphere SDK has also been updated, to work with the latest OS, - it now includes sysroots for four Target API Sets
In each Visual Studio project, the Target API Set (under Properties / Configuration / General) can now be set to 1, 2, 3 or 3+Beta1909

Beta APIs can change, so projects based on Beta APIs may need to be rebuilt  (with changed Target API Set) after an OS update

 

For help with command-line options or syntax, type-in the partially completed command followed by -? or --help to get context-relevant assistance

For verbose reporting in response to commands, add -v or --verbose to the end of the command entered

For documentation of the azsphere command-line tool go here

 

Further Tips to Max-Out Your Starter Kit!

 

Tips to max-out your Starter Kit hardware! (Part 1)

 

Tips to max-out your Starter Kit hardware! (Part 2)

image

  • Sign in to reply

Top Comments

  • peterfenn
    peterfenn over 5 years ago in reply to stevesmythe +3
    Steve This is because the RTApp was previously built using a Beta API set ( 2+Beta1905 ) that has now been deprecated and is not supported by the 19.09 OS To correct this requires the following: Two files…
  • peterfenn
    peterfenn over 5 years ago in reply to peterfenn +2
    PS: An alternative solution is to eliminate completely the M4 RTApp based sampling of the ADC inputs and instead move this function to the A7 HighLevelApp (from 19.09 onwards, the ADC can now be accessed…
  • agundrum1
    agundrum1 over 5 years ago +2
    I also found the updated documentation does not state that azsphere device wifi delete -id 0 has been changed to azsphere device wifi forget -id 0
  • skruglewicz
    skruglewicz over 5 years ago in reply to jgroman

    OK this sounds like a plan. I've been reading up on resistor Voltage dividers and it makes sense to me.

    Thanks so much for your guidance.

    Steve K.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • jgroman
    jgroman over 5 years ago in reply to skruglewicz

    skruglewicz
    Steve,
    connect red wire to 3.3V header. Looking at the sensor schematic I'd say maximum sensor output will be very close to 2.5V, but OTOH I am not really an opamp expert.

     

    Just to stay on a safe side, add a voltage divider: here is a short primer regarding voltage dividers for ADC. Let's say we have maximum of 3.3V and we want to "divide" it to safe maximum of 2.5V. Using an online voltage divider calculator we can work out possible resistor combination for example: R1=12 KOhm, R2=33 KOhm. Please note it is KILO Ohms. Using the same values in just Ohms would probably fry the sensor.

    You would connect R1 between sensor output and AN header and R2 between AN header and GND.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • skruglewicz
    skruglewicz over 5 years ago in reply to peterfenn

    Thanks Peter

     

    Does this seem like a viable connection?

    In collaboration with jgromanreply to my initial comment on the Heart Rate Sensor.

     

    I'm still not clear on the RED input the project calmed " RED: Input: +3V or +5V"

    I don't want to harm the the starter kit.

    So from your information I need to:

    1. Use the +5v header for the RED sensor wire.

    2. And place a simple resistor voltage divider between sensor output and AN input. (to cut the voltage to 2.5v)

     

    I will use the  A7 core to access the ADC and use "ADC_SetReferenceVoltage" Function to set the voltage to 2.5 v

     

    Thanks Steve K

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • skruglewicz
    skruglewicz over 5 years ago in reply to jgroman

    HI Jaroslav,

     

    Thanks for your help..

    I'm really new to electronics as you can probably tell (I'm a retired Software Engineer now hobbyist)

    I'm still not clear on the RED input the project calmed " RED: Input: +3V or +5V"

    I don't want to harm the the starter kit. 

    So from your information I need to:

    1. Use the +5v header for the RED sensor wire.

    2. And place a simple resistor voltage divider between sensor output and AN input. (to cut the voltage to 2.5v)

     

    I will use the  A7 core to access the ADC and use "ADC_SetReferenceVoltage" Function to set the voltage to 2.5 v

    Peter Fenn stated in a reply that (2.5V is the maximum voltage for ADC inputs)

     

    Does this This make seance?

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • jgroman
    jgroman over 5 years ago in reply to peterfenn

    Thank you!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
>
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube