Here is an interesting situation that we've seen pop up with about 5 devices -- all of these failures occurred in the last several weeks (since late January 2016).
I wondered if anyone had experienced something similar. The most obvious solution is to run the firmware update from DFU mode, which I'm assuming should work to recover these units.
But the main question: has anyone had these units stop working completely at random, and then hang at this place on boot? If so, any known causes?
These units had uptimes ranging from 38 days all the way to 170 days. We are running a mix of software, python, java, nodejs. I'm sure there could be memory leaks which could lead to crash, but I don't know how it would corrupt the image.
I also wondered if there was a recent time (1 second?) adjustment that might effect Yocto in some harmful way. But these failures didn't happen at the same moment. Or perhaps on this image version there were bugs that have been fixed since, and its reasonable to think this has already been solved?
Below is the console output, obviously it won't boot into yocto and is stuck until I restore the firmware ... thanks for the help!
microkernel built 11:24:08 Feb 5 2015
******* PSH loader *******
PCM page cache size = 192 KB
Cache Constraint = 0 Pages
Arming IPC driver ..
Adding page store pool ..
PagestoreAddr(IMR Start Address) = 0x04899000
pageStoreSize(IMR Size) = 0x00080000
*** Ready to receive application ***
U-Boot 2014.04 (Apr 29 2015 - 03:53:19)
DRAM: 980.6 MiB
MMC: tangier_sdhci: 0
Hit any key to stop autoboot: 0
Partitioning already done...
Flashing already done...
GADGET DRIVER: usb_dnl_dfu
5383904 bytes read in 133 ms (38.6 MiB/s)
Valid Boot Flag
Setup Size = 0x00003c00
Magic signature found
Using boot protocol version 2.0c
Linux kernel version 3.10.17-poky-edison+ (sys_dswci@tlsndgbuild004) #1 SMP PREEMPT Wed Apr 29 03:54:01 CEST 2015
Building boot_params at 0x00090000
Loading bzImage at address 00100000 (5368544 bytes)
Magic signature found
Kernel command line: "root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=fbfb587a17211b3cc3312b0c682ba577"
Starting kernel ...
[ 0.760318] pca953x 1-0020: failed reading register
[ 0.765532] pca953x 1-0021: failed reading register
[ 0.770630] pca953x 1-0022: failed reading register
[ 0.775747] pca953x 1-0023: failed reading register
[ 1.614815] snd_soc_sst_platform: Enter:sst_soc_probe
[ 2.018010] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[ 2.026390] pmic_ccsm pmic_ccsm: Battery Over heat exception
[ 2.026475] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary
[ 2.040372] pmic_ccsm pmic_ccsm: Battery temperature zone changed
[ 2.046552] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary