![]() Once connected, the nRF52 displays a JLINK removable drive in Windows. Connect the nRF52 developer board to your computer using USB.Refer to the following graphic for details.Ĭlone the Azure Sphere samples repository and find the ExternalMcuUpdate sample in the ExternalMcuUpdate folder or download the zip file from the Microsoft samples browser. NRF52 Ground: GND to MT3620 GND: Header 2 (lower left) Pin 2 NRF52 DFU: P0.16 to MT3620 GPIO44: Header 2 (lower left) Pin 14 NRF52 Reset: P0.21 to MT3620 GPIO5: Header 2 (lower left) Pin 4 NRF52 RTS: P0.22 to MT3620 UART0 CTS: Header 2 (lower left) Pin 5 NRF52 CTS: P0.23 to MT3620 UART0 RTS: Header 2 (lower left) Pin 7 NRF52 TX: P0.12 to MT3620 UART0 RX: Header 2 (lower left) Pin 1 NRF52 RX: P0.11 to MT3620 UART0 TX: Header 2 (lower left) Pin 3 Make the following connections between the Nordic nRF52 and Azure Sphere MT3620 dev boards using the jumper wires: For detailed instructions, see the Hardware Definitions README file. To build the sample for different Azure Sphere hardware, change the value of the TARGET_HARDWARE variable in the CMakeLists.txt file. Note: By default, the sample targets the Reference Development Board design, which is implemented by the Seeed Studios MT3620 Development Board. The setup procedures describe how to choose and install an SDK.Īn Azure Sphere development board that supports the Sample Appliance hardware requirements. Download and install the latest SDK as needed. At the command prompt, run azsphere show-version to check. This reference solution requires the following items:Īzure Sphere SDK version 22.11 or above. hex bootloader files.įolder containing the configuration files, source code files, and other files needed for building your own bootloader. Manages communication with the Nordic nRF52 Development Kit.įolder containing the configuration files, source code files, hardware definitions, and other files needed for the high-level application.įolder containing the. Manages the buttons and LEDs on the device.ĭisplays messages in the Device Output window during debugging. The sample uses the following Azure Sphere libraries. This application can itself be updated remotely via over-the-air updates, ensuring that the software versions of this application and the MCU firmware are always in sync. This solution contains an Azure Sphere application that deploys firmware to the Nordic nRF52 Development Kit over UART. This reference solution demonstrates how you might use an Azure Sphere device to deploy an update to an external MCU device. Assuming the other MCUs permit updates to be loaded over the connection you establish with the Azure Sphere device, for example over UART, you can use the Azure Sphere device to securely deliver those updates. Your product may incorporate other MCUs with your Azure Sphere device, and those other MCUs may require updates.
0 Comments
Leave a Reply. |