In addition, make sure that the board itself is properly configured. If you're using a different dev kit, see the manufacturer's documentation. If your dev kit is compatible with the MT3620 reference development board (RDB), see the MT3620 development board user guide for details. Make sure that the real-time clock (RTC) is powered, by either the main 3V3 power supply or a coin cell battery. If the device appears "dead" or unresponsive, the problem could be a lack of power. Or Linux-specific problems to determine whether the problem might be unique to your platform. If none of these steps solves the problem, see Windows-specific problems This command power-cycles the FTDI ports of all attached devices and can sometimes help in connection problems. On Windows, run the azsphere device rescan-attached command. Wait ten seconds or so for the device to restart, and then try the failed command again. If the device is connected, press the Reset button on the device or disconnect and reconnect the USB cable. If OS update is progress, the device should again become responsive when the update completes. To diagnose and resolve the problem, start with these basic steps:Įnsure that the device is connected by USB to the host machine. During OS updates, the device may fail to respond. The device is currently busy applying an Azure Sphere OS update. The board is not connected by USB to the host machine.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |