Data Sheet

ManualsBrandsRealtek ManualsElectronics802.11a/b/g/n/ac RTL8822CE Combo Module

Project Santa Cruz Development Kit Overview 
Devkit Contents 
The Project Santa Cruz Development Kit contains the following major components: 
•  Carrier board with Wi-Fi antennas 
•  Azure Eye SoM 
•  Azure Ear SoM (includes microphone array) 
•  RBG camera (connects to Eye SoM) 
•  Required cables: MIPI, USB-C, USB Micro Type-B to USB-A, power cable. 
•  Welcome card with hex key 
•  Section of 80/20 1010 Series mounting rail 
For more detailed specs, please see the datasheets for the devkit, Eye SoM, and Ear SoM. 
Getting Started 
There are three main stages to getting started with your Project Santa Cruz Development Kit: 
1.  Onboarding 
2.  Devkit unboxing and set up 
3.  Out of Box Experience (OOBE) 
In the onboarding stage, you will assign an Azure subscription within your account to Project Santa 
Cruz. The onboarding tool will walk you through the process of creating an IoT Hub within your 
Azure subscription to use with Project Santa Cruz. You will have the option of enabling services, 
such as the Device Provisioning Service (DPS), Azure Device Update (ADU), and Automatic Import 
Updates, within your IoT Hub. 
After onboarding has been completed, follow the devkit unboxing and set up guide for guidance 
on connecting the various components of the kit and powering on your device. 
Once your devkit is powered on, work through the OOBE (out-of-box experience) to connect your 
devkit to a Wi-Fi network, set up an SSH login (optional), connect your devkit to your Azure 
account, and assign it to your Project Santa Cruz IoT Hub (created during onboarding). 
After the onboarding, devkit set up, and OOBE have been completed, you are ready to begin 
prototyping. 

Summary of content (22 pages)

PAGE 1
Project Santa Cruz Development Kit Overview Devkit Contents The Project Santa Cruz Development Kit contains the following major components: • Carrier board with Wi-Fi antennas • Azure Eye SoM • Azure Ear SoM (includes microphone array) • RBG camera (connects to Eye SoM) • Required cables: MIPI, USB-C, USB Micro Type-B to USB-A, power cable.
PAGE 2
Vision and Speech Experiences There are a number of no-code vision and audio solutions available for prototyping with your devkit. For more information on these experiences, please reference the prototyping documentation. Updating your Devkit Your devkit OS and firmware may be updated over-the-air (OTA) or via USB. For more information on updating your device, please see the update experience documentation.
PAGE 3
• Azure account with Azure Active Directory enabled and "owner" or "contributor" permissions Request access 1. Open a browser and enter https://projectsantacruz.microsoft.com/ in the address bar to open the onboarding portal. 2. Enter your account login details and click Next. [!IMPORTANT] To ensure you onboard the correct Azure subscription, you must log into the site with an Azure Active Directory-enabled account that is a member of the Azure subscription you wish to onboard.
PAGE 4
3. Click Request access. It may take up to 2 business days to process your request to access the onboarding portal. Create an IoT Hub and enable Azure services 1. Once your access request has been processed, return to the onboarding portal. Click Get Started on the welcome screen. 2. Select the Azure subscription you would like to use with Project Santa Cruz from the dropdown menu.
PAGE 5
3. Create an IoT Hub. i. Enter your IoT Hub name. It is recommended that you create a new IoT Hub for working solely with Project Santa Cruz. ii. Select your hub’s pricing tier from the drop-down menu. The S1 tier is recommended for use with Project Santa Cruz because other pricing tiers do not support IoT Edge, which is required. Note that Azure account credits may be used towards IoT Hub fees. iii. Select a resource group from the drop-down menu or create a new one. iv.
PAGE 6
vi. In some cases, you may receive the following error message after clicking Submit: The error message indicates that your Azure subscription is not registered to use the Microsoft.Devices namespace. To fix this, register your Azure subscription through the Azure portal by following the steps described here. There is no charge associated with the Microsoft.Devices namespace. Wait approximately 30 minutes after registering before trying to create your IoT Hub through the onboarding tool again.
PAGE 7
4. After creating your IoT Hub, you will see a new option at the bottom of the screen for enabling the Device Provisioning Service (DPS). Check the box and click Next to create your DPS instance and link it to your IoT Hub. This may take a few minutes to complete. When finished, you will see a new section for Device Management Services that lists your DPS status (ON) and your DPS name. 5. Next, you will see an option at the bottom of the screen for enabling Azure Device Update (ADU).
PAGE 8
Congratulations! You have successfully completed the onboarding tool and are ready to get started with Project Santa Cruz. Any changes to the settings you selected in the onboarding tool can now be made in your in your Azure account (this link allows you to access the Azure Device Update extension, which is a Private Preview service).
PAGE 9
o The devkit contains a carrier board, Azure Eye SoM, Azure Ear SoM, RGB camera, accessories box with antennas and required cables, a section of 80/20 1010 Series mounting rail, and a welcome card with a hex key. o The welcome card includes a sticker that has two passwords needed to access the dev kit's wifi access point. The first password is "santacruz" and is what should be used with the dev kit out of the box.
PAGE 10
vii. After plugging the power cable into a wall outlet, the device will automatically power on. The reset button on the left side of the carrier board will be illuminated, and the Ear SoM LEDs will turn green, indicating device authentication is in progress (specifically, the LED marked L01 will turn on and remain green, and LED L02 will flash green). Please allow some time for the device to boot up. [!NOTE] The reset button is for powering off or resetting the device while connected to a power outlet.
PAGE 11
What is SoftAP? SoftAP, or software-enabled access point, allows your devkit to act as a wireless access point/hotspot through its integrated Wi-Fi module. The devkit's SoftAP IP address is 10.1.1.1. We will be using the devkit's SoftAP for the initial setup. Connect to OOBE Warning: If completing OOBE via a mobile device, be aware that data rates from your mobile carrier may apply. 1. To get started, power on your devkit. 2.
PAGE 12
2. On the Network connection page, click Connect to a new WiFi network to connect your devkit to a Wi-Fi network. 3. Select your Wi-Fi network from the available connections.
PAGE 13
[!NOTE] The Wi-Fi network you connect to must currently have internet connectivity so we can communicate with Azure. EAP[PEAP/MSCHAP], captive portals, and Enterprise EAP-TLS connectivity is currently not supported. 4. Write down the IP address you are shown once a connection is established. You will want to use this IP address after OOBE completes for viewing the Preview Video Output instead of 10.1.1.1:3000. You can also use this IP address for SSH sessions and connecting to OOBE.
PAGE 14
5. On the Network connection page, click Access advanced network settings. 6. On the Advanced network settings page, click Define access point passphrase.
PAGE 15
7. On the Define access point passphrase page, enter a passphrase/password for your device's SoftAP hotspot and click Save. After changing your password, you will be disconnected from the SoftAP and will need to reconnect your device to proceed with the OOBE. Instead of reconnecting to the SoftAP with your new password, we recommend connecting to either your Wi-Fi network that was set up in a previous step or over Ethernet.
PAGE 16
9. If you would like to set up SSH for remote access to your devkit, enter your SSH username and password. To disable the root SSH login (username = root, password = p@ssw0rd), check the box next to SSH Root Login Disabled (Recommended). To prevent brute force security attacks, we recommend keeping SSH root login disabled. If you are an advanced user and choose to enable root login, please enable appropriate security measures for your deployment environment. Finally, click Save.
PAGE 17
10. On the next screen, click Connect with a new device to begin the process of linking your devkit to Azure. To check your Azure subscription status go to https://ms.portal.azure.com/#home, then tap Subscriptions. 11. Click Copy to copy your device code (this may take a few seconds to generate). Once you have copied your device code, click Login to Azure, which opens a new browser tab.
PAGE 18
i. On the new browser tab, paste the device code you copied in the previous step into the window and click Next. ii. Sign into your Azure account (the same account used during the onboarding process) and click Next. Navigate back to the OOBE window, which will show “Successfully Linked” once account sign-in is successful.
PAGE 19
12. Select the IoT Hub you created during the onboarding process to assign it to your devkit. If you are not sure which IoT Hub was created during onboarding, please check the onboarding website. 13. Enter a device name for your devkit, check the TPM enrollment box, and click Next.
PAGE 20
14. Congratulations! Your devkit has been successfully linked to your Azure account and Project Santa Cruz IoT Hub. You may now access your device within the Azure Portal. Before doing so, disconnect your computer from the devkit's SoftAP. [!NOTE] The Preview Video Output hyperlink on the final screen will no longer work once disconnected. Instead, use the IP address you wrote down in step 4 to preview the video output for the best streaming performance: http://:3000.
PAGE 21
Notes 1. To protect your security, after 30 minutes of inactivity, we stop the OOBE process (and we remove the port 80 allow rule). If this occurs, please restart the OOBE. 2. If at anytime during OOBE you see blue dots and then OOBE restarts, this is due to losing internet connectivity. Please verify you have a consistent internet connection. 3. During the WiFi connection, three blue dots will be shown. These will go away once the WiFi connection has been established. 4.
PAGE 22
2. You will be prompted to enter a new password, which must contain letters and numbers and be least 12 characters in length. Type your new password into the PuTTY terminal and hit Enter. 3. Write down your password in a safe place. 4. You are now free to close the PuTTY terminal. Provide Feedback After completing the OOBE, please provide feedback on your experience via this questionnaire. Your feedback will help us continue to fine-tune and improve the OOBE experience.