meta-iot2050: Reboot problem

Hi,

When IOT works for a very long period (60 day) and I launch a reboot with cmd sudo reboot.

IOT can’t reboot, with software, I force to do an hard reset electrical. `======================= Board: IOT2050-ADVANCED Serial: xx MLFB: 6ES7647-0BA00-1YA2 UUID: 8069DFE5E3D14C05B9B8D6C4CAC1CEF0 A5E: A5E452229880AB08 MAC[0]: xx MAC[1]: xx SKU: SE Loading PK… ok PK count: 00 PK version: 00 SV: 00-00 Security ID 0x5125e53f-0x842e215d Security policy: soft Loading image atf… Loading image tee… Loading image spl… Loading image k3-am65-iot2050-spl.dtb… NOTICE: BL31: v2.5(release): NOTICE: BL31: Built : 14:41:24, May 17 2021 I/TC: I/TC: OP-TEE version: 3.12.0 (gcc version 10.2.1 20210110 (Debian 10.2.1-6)) #1 Wed Jan 20 17:48:48 UTC 2021 aarch64 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2021.04-V01.02.01.03-0-g7e29ca7 (Nov 04 2021 - 07:46:39 +0000) SYSFW ABI: 3.1 (firmware rev 0x0015 ‘21.5.0–v2021.05 (Terrific Llam’) Trying to boot from SPI QSPI: QSPI is still busy after poll for 10000 times. SF: Calibration failed (read) cadence_spi spi@47040000: Cannot set speed (err=-5) SPI probe failed. SPL: failed to boot from all boot devices

ERROR ### Please RESET the board

`

Thanks for your help.

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 51

Commits related to this issue

Most upvoted comments

Hello all, the firmware version V1.4.3 with the workaround for this issue was published today on our Downloads Page.

Further information can be found in our new forum entry.

Thanks

Hi @rFond ,

Thanks for your information.

We have been testing a debug firmware for over a month without any failures so far. We plan to release it early next month.

Details:

  • The original QSPI issue has been fixed with our workaround.
  • However, after resolving the QSPI issue, the device fails to boot with eMMC. We have added a potential workaround for the eMMC issue:
    • TI provided a workaround to enable the MMC reset function.
    • We added a workaround to reset the eMMC.

Example Scenario:

  1. The device runs for 2 months.
  2. The device fails to boot due to the QSPI issue. (If the device is running with the QSPI workaround, this issue will be bypassed and proceed to step 3.)
  3. The device fails to boot due to not being able to detect the eMMC. (The symptom is the same as the QSPI issue, where the device fails to boot and can only be recovered with a cold reset.)

We now have a potential workaround for step 3 (the eMMC issue). Our testing is not yet complete, but it should improve the situation.

Thanks.

Any advancement?