Impossible de faire clignoter l'image IoT Android pour Pico Pro Maker Kit

Question

J'ai obtenu un kit Pico Pro Maker et j'utilise un PC Windows 10. J'ai suivi les instructions clignotantes here. Gestionnaire de périphériques détecte le kit de cette façon: Android ADB interface

L'appareil est en mode fatboot, mais quand j'exécute le flash-tout scénario, un message d'erreur est renvoyée (ne peut pas charger « u-boot.imx »):

Microsoft Windows [Version 10.0.15063] 

(c) 2017 Microsoft Corporation. Minden jog fenntartva.

C: \ Android \ sdk \ plate-forme-tools> Appareils adb

Liste des périphériques connectés

C: \ Android \ sdk \ plate-forme-tools> Appareils fastboot

000000e5f4439b02 fastboot

C: \ applications \ SDK \ plate-outils> C: \ F_Android_Things_NXPPico \ flash all.bat

erreur: ne peut pas charger 'u-boot.imx'

Est-ce que quelqu'un a une idée de ce qui ne va pas?

Answer 1

Enfin je suis venu à travers. Int flash-all.bat regardé le script qui dit:

The fastboot executable must be in your path to run this script

J'imitée dans toute l'image Chose Android, générée par le AndroidThingsConsole dans le répertoire C:\Android\sdk\platform-tools\ sous, et exécutez à nouveau le script flash-all.bat.

Le résultat est ici:

C:\Android\sdk\platform-tools>flash-all.bat 

target reported max download size of 209715200 bytes 

sending 'bootloader' (479 KB)... 

OKAY [ 0.017s] 
writing 'bootloader'... 
OKAY [ 0.397s] 
rebooting into bootloader... 
OKAY [ 0.009s] 

finished. total time: 0.457s 

< waiting for any device > 

target reported max download size of 209715200 bytes 

sending 'gpt' (33 KB)... 
OKAY [ 0.006s] 
writing 'gpt'... 
OKAY [ 28.856s] 

rebooting into bootloader... 

OKAY [ 0.006s] 

finished. total time: 28.876s 

target reported max download size of 209715200 bytes 

Creating filesystem with parameters: 

    Size: 2009071616 
    Block size: 4096 
    Blocks per group: 32768 
    Inodes per group: 8176 
    Inode size: 256 
    Journal blocks: 7664 
    Label: 
    Blocks: 490496 
    Block groups: 15 
    Reserved block group size: 119 
Created filesystem with 11/122640 inodes and 16088/490496 blocks 

sending 'boot_a' (32768 KB)... 

OKAY [ 0.886s] 
writing 'boot_a'... 
OKAY [ 1.222s] 
sending 'boot_b' (32768 KB)... 
OKAY [ 0.883s] 
writing 'boot_b'... 
OKAY [ 1.235s] 
erasing 'system_a'... 
OKAY [ 7.114s] 
sending sparse 'system_a' 1/2 (203704 KB)... 
OKAY [ 5.909s] 
writing 'system_a' 1/2... 
OKAY [ 8.516s] 
sending sparse 'system_a' 2/2 (204764 KB)... 
OKAY [ 6.189s] 
writing 'system_a' 2/2... 
OKAY [ 11.602s] 
erasing 'system_b'... 
OKAY [ 6.999s] 
sending sparse 'system_b' 1/2 (203704 KB)... 
OKAY [ 5.993s] 
writing 'system_b' 1/2... 
OKAY [ 8.500s] 
sending sparse 'system_b' 2/2 (204764 KB)... 
OKAY [ 5.818s] 
writing 'system_b' 2/2... 
OKAY [ 11.603s] 
erasing 'userdata'... 
OKAY [ 26.163s] 
sending 'userdata' (33356 KB)... 
OKAY [ 0.903s] 
writing 'userdata'... 
OKAY [ 1.252s] 
Setting current slot to 'a'... 
OKAY [ 0.030s] 
finished. total time: 110.864s 
target reported max download size of 209715200 bytes 
sending 'gapps_a' (72040 KB)... 
OKAY [ 1.929s] 
writing 'gapps_a'... 
OKAY [ 2.570s] 
sending 'gapps_b' (72040 KB)... 
OKAY [ 1.938s] 
writing 'gapps_b'... 
OKAY [ 2.467s] 
finished. total time: 8.917s 
target reported max download size of 209715200 bytes 
sending 'oem_a' (1096 KB)... 
OKAY [ 0.036s] 
writing 'oem_a'... 
OKAY [ 0.139s] 
sending 'oem_b' (1096 KB)... 
OKAY [ 0.036s] 
writing 'oem_b'... 
OKAY [ 0.123s] 
finished. total time: 0.344s 

Successfully flashed your imx7d. 
rebooting... 

finished. total time: 0.001s 

C:\Android\sdk\platform-tools>