このページの2つのバージョン間の差分を表示します。
両方とも前のリビジョン前のリビジョン次のリビジョン | 前のリビジョン | ||
mas1xx_ope:update_firmware:start [2020/08/25 09:51] – admin | mas1xx_ope:update_firmware:start [2024/06/27 11:33] (現在) – [SDカードブート から本体ファームウェアの更新] サポート | ||
---|---|---|---|
行 32: | 行 32: | ||
Succeeded. | Succeeded. | ||
</ | </ | ||
+ | \\ | ||
+ | ==== SDカードブート から本体ファームウェアの更新 ==== | ||
+ | 本体ファームで起動出来なくなった際、SDカードブートで起動してから、本体ファームを再書き込みする事で復旧する場合があります。 | ||
+ | |||
+ | === 1.SDカードブート === | ||
+ | |||
+ | 下記URLを参考に、SDカードイメージを作成し、SDカードブートで起動させます。\\ | ||
+ | [[max3xx_tips: | ||
+ | [[mas1xx_ope: | ||
+ | |||
+ | |||
+ | === 2./ | ||
+ | |||
+ | ディレクトリ /ro/.host を作成し、/ | ||
+ | < | ||
+ | root@metis: | ||
+ | root@metis: | ||
+ | root@metis: | ||
+ | </ | ||
+ | |||
+ | === 3.firmupコマンドの実行 === | ||
+ | |||
+ | USBメモリやsftp などでファームウェアを実機に転送し、root 権限で " | ||
+ | < | ||
+ | root@metis: | ||
+ | ### MA-X3xx series firmware update utility (for 2-area firmware). | ||
+ | * checking firmware file integrity... OK. | ||
+ | * custom firmup-pre script found. | ||
+ | * device type: GP | ||
+ | * u-boot (1st stage) file found. | ||
+ | writing " | ||
+ | * u-boot (2nd stage) file found. | ||
+ | writing " | ||
+ | MSP430 is not need to update firmware. | ||
+ | * Update XIO MSP430(1) firmware. | ||
+ | MSP430 firmware updater | ||
+ | * Load firmware from file: / | ||
+ | * Invoke MSP430 BSL...done. | ||
+ | * Wait for BSL booting...done. | ||
+ | * Mass-erase device...done. | ||
+ | * Unlock device succeeded. | ||
+ | * Writing segment No. 1 ............................ OK. | ||
+ | * Writing segment No. 2 . OK. | ||
+ | * Writing segment No. 3 . OK. | ||
+ | * Writing segment No. 4 . OK. | ||
+ | * Writing segment No. 5 . OK. | ||
+ | * Verify segment No. 1 ... OK. | ||
+ | * Verify segment No. 2 ... OK. | ||
+ | * Verify segment No. 3 ... OK. | ||
+ | * Verify segment No. 4 ... OK. | ||
+ | * Verify segment No. 5 ... OK. | ||
+ | * Update XIO MSP430(2) firmware. | ||
+ | MSP430 firmware updater | ||
+ | * Load firmware from file: / | ||
+ | * Invoke MSP430 BSL...done. | ||
+ | * Wait for BSL booting...done. | ||
+ | * Mass-erase device...done. | ||
+ | * Unlock device succeeded. | ||
+ | * Writing segment No. 1 ......................... OK. | ||
+ | * Writing segment No. 2 . OK. | ||
+ | * Writing segment No. 3 . OK. | ||
+ | * Writing segment No. 4 . OK. | ||
+ | * Writing segment No. 5 . OK. | ||
+ | * Verify segment No. 1 ... OK. | ||
+ | * Verify segment No. 2 ... OK. | ||
+ | * Verify segment No. 3 ... OK. | ||
+ | * Verify segment No. 4 ... OK. | ||
+ | * Verify segment No. 5 ... OK. | ||
+ | Updating Area: 1 ... | ||
+ | * image file for kernel found, writing... succeeded. | ||
+ | * image file for kmod found, writing... succeeded. | ||
+ | * image file for initramfs found, writing... succeeded. | ||
+ | * image file for rootfs found, writing... succeeded. | ||
+ | * DTB file(s) found. | ||
+ | writing k3-am642-centurysys-metis-00.dtb... succeeded. | ||
+ | writing k3-am642-centurysys-metis-01.dtb... succeeded. | ||
+ | writing k3-am642-centurysys-metis-02.dtb... succeeded. | ||
+ | writing k3-am642-centurysys-metis-03.dtb... succeeded. | ||
+ | writing k3-am642-centurysys-metis-20.dtb... succeeded. | ||
+ | writing k3-am642-centurysys-metis-ext-01.dtbo... succeeded. | ||
+ | writing k3-am642-centurysys-metis-ext-02.dtbo... succeeded. | ||
+ | writing k3-am642-centurysys-metis-mod-01.dtbo... succeeded. | ||
+ | writing k3-am642-centurysys-metis-mod-02.dtbo... succeeded. | ||
+ | writing k3-am642-centurysys-metis-mod-03.dtbo... succeeded. | ||
+ | * Bootloader file found. | ||
+ | writing " | ||
+ | * Bootloader script found. | ||
+ | writing " | ||
+ | * custom firmup-post script found. | ||
+ | * generating SUM file... | ||
+ | MD5: f29ef9a970f0b257030130900f91f63c | ||
+ | SHA1: 0f90dbd8ecef12fdd56e72bff5a4129d5b98b1ef | ||
+ | done. | ||
+ | * updating default firmware area: 1 | ||
+ | Succeeded. | ||
+ | </ |