Azure Sphere MT3620 enable development issue

René, Charles 36 Reputation points
2020-06-25T19:31:59.577+00:00

Hi!

I just received the Azure Sphere MT3620 starter kit. I've gone trought all the configurations steps. I've been able to upload my first blinking program and it works! My only problem is that I can't get the module in debug mode. In the configuration steps, after claiming the device, it is ask to enable app-development on the device by entering the following command:

"azsphere device enable-development"

What I get is an error saying: "Failed to install debugging server to device" and "Image package failed to transfer to the device. Check if the image is too large."

Attached you will find a screenshot of this error on the command prompt.

Do you have any ideas?
Tell me if you need more infos.

Thank you in advance!
Charles

10751-problem-debugging-server.jpg

Azure Sphere
Azure Sphere
An Azure internet of things security solution including hardware, operating system, and cloud components.
165 questions
0 comments No comments
{count} votes

Accepted answer
  1. Brian Willess 91 Reputation points
    2020-06-25T20:12:04.727+00:00

    I've never seen that issue before. Did you "recover" the device to make sure you're running the latest OS? If not, I would do that first. Note that if you've configured any wifi networks on your device they will be removed by the recover command.

    azsphere device recover

    <Let the device update the OS and reset>

    azsphere device enable-development

    1 person found this answer helpful.
    0 comments No comments

7 additional answers

Sort by: Most helpful
  1. René, Charles 36 Reputation points
    2020-07-02T21:39:06.93+00:00

    Hi everyone,

    Please be aware that my issue is solved... or at least it is working now ( I don't have an error message anymore). I don't know what was causing the problem. I have tried the same procedure on three different computers with no avail. Than I tried again on a brand new desktop computer and it worked the first time.
    Very strange on my opinion.

    Whatever,
    Thank you for your support guys!

    3 people found this answer helpful.

  2. René, Charles 36 Reputation points
    2020-06-25T22:31:40.26+00:00

    Hi Brian,

    First thank you for the reply. I have already done those steps earlier. I still tried again, but it doesn't work. I also tried to uninstall the Azure Sphere SDK and reinstall it. The file gdbserver.imagepackage is at the right place but somehow it can't be transfert to the device. By the way, I am using the SDK for windows 10.

    10729-device-recover.jpg

    0 comments No comments

  3. matsujirushi 636 Reputation points MVP
    2020-06-26T01:18:05.27+00:00

    Hi,
    Could you tell me some informations?

    1. azsphere -?
    2. azsphere device enable-development -v
    3. dir "c:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools\gdbserver.imagepackage"

    C:\>azsphere -?
    Azure Sphere Utility version 20.4.7.42974
    Copyright (C) Microsoft Corporation. All rights reserved.

    C:\>dir "c:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools\gdbserver.imagepackage"
    2019/11/14 07:35 352,468 gdbserver.imagepackage

    0 comments No comments

  4. René, Charles 36 Reputation points
    2020-06-26T02:01:47.38+00:00

    Hi and thank you for helping!

    Here are the infos you ask for:

    1.
    C:\WINDOWS\system32>azsphere -?
    Azure Sphere Utility version 20.4.10.9104
    Copyright (C) Microsoft Corporation. All rights reserved.

    2.
    C:\WINDOWS\system32>azsphere device enable-development -v
    Azure Sphere Utility version 20.4.10.9104
    Copyright (C) Microsoft Corporation. All rights reserved.

    Start time (UTC): Friday, 26 June 2020 01:58:40
    verbose: ==> Using Azure Active Directory tenant ID: '7d71c83c-ccdf-45b7-b3c9-9c41b94406d9'.
    verbose: ==> Using environment: 'prod'.
    verbose: ==> Using Azure Sphere tenant ID: 'ae2c84e0-7f1c-4b80-9133-799168e15c5a'.

    verbose: No SerialSlipToTunService port is set in the registry; defaulting to 48938.
    verbose: Using attached device ID 'B4C11C4897748C4AD8DBF7C317816BF13CD336E53868E8FBCC5A22DEF66B529E40895BA8626CE2EEC46958589D4661977243076C7D6EB0BEF45C15D509BBC04E'.
    Getting device group 'Development' for product 'prototype'.
    verbose: No SerialSlipToTunService port is set in the registry; defaulting to 48938.
    warn: The device already has the 'Enable App development' capability. No changes will be applied to its existing capabilities.
    Setting device group to 'Development' with ID '7d7c1883-46cb-4da9-bd42-ebde7ac0877f'.
    Successfully disabled application updates.
    Installing debugging server to device.
    verbose: > azsphere device sideload deploy --imagepackage "C:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools\gdbserver.imagepackage"
    Deploying 'C:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools\gdbserver.imagepackage' to the attached device.
    error: Image package failed to transfer to the device. Check if the image is too large.
    error: Failed to install debugging server to device.
    Command completed in 00:00:06.4647610.

    3.
    C:\WINDOWS\system32>dir "c:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools\gdbserver.imagepackage"
    Le volume dans le lecteur C s’appelle OS_Install
    Le numéro de série du volume est 6ED8-D3B0

    Répertoire de c:\Program Files (x86)\Microsoft Azure Sphere SDK\DebugTools

    2019-11-14 07:35 352 468 gdbserver.imagepackage
    1 fichier(s) 352 468 octets
    0 Rép(s) 7 671 906 304 octets libres

    Anything else just ask! Thank you for your time.
    Charles

    0 comments No comments