Edison not showing up on Dashboard


#1

I am a bit of a noob here, so bear with me.

After flashing my Edison, the device does not show up on the Dashboard after 15 minutes.

So I had flashed my Edison three times, both through the batch file and Phone flash Tool Lite. I have also re-downloaded the OS.
The flashing process gives no error, but there is no blinking after it finishes, perhaps indicating that it does not boot. Indeed it seemed not to. It gave this output:

Starting Hold until boot process finishes up...

So I stopped the autoboot and did:

run do_flash

Thinking this would put me into Device Firmware Upgrade mode.

The computer now did not recognize the Edison and I re-flashed it.

After re-flashing, when I re-started the Edison I got:

▒

******************************
PSH KERNEL VERSION: b0182929
                WR: 20104000
******************************

SCU IPC: 0x800000d0  0xfffce92c

PSH miaHOB version: TNG.B0.VVBD.0000000c

microkernel built 10:14:01 Jan 13 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 (Mar 29 2016 - 15:15:39)

       Watchdog enabled
DRAM:  980.6 MiB
MMC:   tangier_sdhci: 0, tangier_sdhci: 1
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Target:blank
Partitioning already done...
Flashing already done...
Probing DFU...
Saving Environment to MMC...
Writing to MMC(0)... done
GADGET DRIVER: usb_dnl_dfu
reading vmlinuz
5829408 bytes read in 142 ms (39.2 MiB/s)
Valid Boot Flag
Setup Size = 0x00003c00
Magic signature found
Using boot protocol version 2.0c
Linux kernel version 3.10.17-yocto-standard (jenkins@build4) #1 SMP PREEMPT Mon Apr 4 18:17:35 CEST 2016
Building boot_params at 0x00090000
Loading bzImage at address 00100000 (5814048 bytes)
Magic signature found
Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=6bf4d2b430a216a68a3b4eafd4afebe8 g_multi.dev_addr=02:00:86:af:eb:e8 platform_mrfld_audio.audio_codec=dummy"

Starting kernel ...

[    2.809068] snd_intel_sst: request fw failed
[    2.864513] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[    2.873307] pmic_ccsm pmic_ccsm: Battery Over heat exception

Welcome to Resin OS 1.1.1!

[  OK  ] Reached target Swap.
[  OK  ] Created slice Root Slice.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Listening on Journal Socket.
         Mounting POSIX Message Queue File System...
         Starting Create list of required st... nodes for the current kernel...
         Mounting Temporary Directory...
[  OK  ] Created slice User and Session Slice.
         Starting udev Coldplug all Devices...
         Mounting Debug File System...
[  OK  ] Reached target Slices.
         Starting Load Kernel Modules...
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Reached target Login Prompts.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on Journal Socket (/dev/log).
         Starting Journal Service...
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Temporary Directory.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Started Journal Service.
[  OK  ] Started Load Kernel Modules.
         Starting Apply Kernel Variables...
         Mounting Configuration File System...
         Mounting FUSE Control File System...
         Starting Flush Journal to Persistent Storage...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting RCE tmp mountpoint...
         Mounting /var/volatile...
[  OK  ] Mounted RCE tmp mountpoint.
[  OK  ] Mounted /var/volatile.
[  OK  ] Started udev Kernel Device Manager.
         Starting Load/Save Random Seed...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Found device /dev/disk/by-label/resin-conf.
[  OK  ] Found device /dev/disk/by-label/resin-boot.
[  OK  ] Found device /dev/mmcblk0p5.
[  OK  ] Found device /dev/disk/by-label/resin-data.
         Mounting /factory...
         Mounting Resin boot partition mountpoint...
[  OK  ] Mounted Resin boot partition mountpoint.
[  OK  ] Mounted /factory.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Show Plymouth Boot Screen...
[  OK  ] Started Create Volatile Files and Directories.
Application available at (physical) address 0x04819000
        VRL mapped to 0xff213000
        App size = 11508 bytes

        App Authentication feature is disabled!
        Resetting IPC

*** Ready to receive application ***

But it does not give me a prompt or show up on my Dashboard.

I think the problem is at:

    Starting kernel ...

[    2.809068] snd_intel_sst: request fw failed
[    2.864513] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[    2.873307] pmic_ccsm pmic_ccsm: Battery Over heat exception

If I’m not misstaken snd_intel_sst is a driver. Did I mess up the firmware?
Any ideas?


#2

Hello,
Looking at you kernel log I cannot see any fatal errors and the fact that your board resets (probably continuously) makes me think this is a power a issue. I have seen this before, when the edison does not get enough power. Could you please re-check your power connection? Maybe try an USB that is externally powered?
Best regards,
Theodor


#3

Hi @telphan, thanks for your reply!

I am externally powering my Edison, the same power unit I use for my other Edisons, so I’m sure it’s fine. Was thinking that it was some problems with the wifi antenna or something, but then I remembered that when I had another OS on it, I used the wifi. So I’m still lost. It gives the same output and stopps at " *** Ready to receive application *** ", and then nothing.

▒

******************************
PSH KERNEL VERSION: b0182929
                WR: 20104000
******************************

SCU IPC: 0x800000d0  0xfffce92c

PSH miaHOB version: TNG.B0.VVBD.0000000c

microkernel built 10:14:01 Jan 13 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 (Mar 29 2016 - 15:15:39)

       Watchdog enabled
DRAM:  980.6 MiB
MMC:   tangier_sdhci: 0, tangier_sdhci: 1
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Target:blank
Partitioning already done...
Flashing already done...
Probing DFU...
Saving Environment to MMC...
Writing to redundant MMC(0)... done
GADGET DRIVER: usb_dnl_dfu
reading vmlinuz
5829408 bytes read in 142 ms (39.2 MiB/s)
Valid Boot Flag
Setup Size = 0x00003c00
Magic signature found
Using boot protocol version 2.0c
Linux kernel version 3.10.17-yocto-standard (jenkins@build4) #1 SMP PREEMPT Mon Apr 4 18:17:35 CEST 2016
Building boot_params at 0x00090000
Loading bzImage at address 00100000 (5814048 bytes)
Magic signature found
Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=6bf4d2b430a216a68a3b4eafd4afebe8 g_multi.dev_addr=02:00:86:af:eb:e8 platform_mrfld_audio.audio_codec=dummy"

Starting kernel ...

[    2.808456] snd_intel_sst: request fw failed
[    2.864892] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk
[    2.871187] pmic_ccsm pmic_ccsm: Battery Over heat exception

Welcome to Resin OS 1.1.1!

[  OK  ] Created slice Root Slice.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Created slice System Slice.
[  OK  ] Listening on Journal Socket.
         Mounting Debug File System...
         Starting Create list of required st... nodes for the current kernel...
         Starting Remount Root and Kernel File Systems...
         Starting Journal Service...
         Starting Load Kernel Modules...
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
         Mounting POSIX Message Queue File System...
[  OK  ] Reached target Login Prompts.
         Mounting Temporary Directory...
[  OK  ] Listening on udev Kernel Socket.
         Starting udev Coldplug all Devices...
[  OK  ] Created slice User and Session Slice.
[  OK  ] Reached target Slices.
[  OK  ] Reached target Swap.
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Temporary Directory.
[  OK  ] Started Journal Service.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started udev Coldplug all Devices.
         Starting Create Static Device Nodes in /dev...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting RCE tmp mountpoint...
         Mounting /var/volatile...
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Mounting Configuration File System...
[  OK  ] Mounted RCE tmp mountpoint.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Mounted Configuration File System.
[  OK  ] Mounted /var/volatile.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Found device /dev/mmcblk0p5.
[  OK  ] Found device /dev/disk/by-label/resin-conf.
[  OK  ] Found device /dev/disk/by-label/resin-boot.
[  OK  ] Found device /dev/disk/by-label/resin-data.
         Mounting Resin boot partition mountpoint...
         Mounting /factory...
         Starting Load/Save Random Seed...
[  OK  ] Mounted Resin boot partition mountpoint.
[  OK  ] Mounted /factory.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Created slice system-systemd\x2drfkill.slice.
         Starting Load/Save RF Kill Switch Status of rfkill0...
         Starting Load/Save RF Kill Switch Status of rfkill1...
         Starting Load/Save RF Kill Switch Status of rfkill2...
[  OK  ] Reached target Sound Card.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Tell Plymouth To Write Out Runtime Data...
         Starting Show Plymouth Boot Screen...
Application available at (physical) address 0x04819000
        VRL mapped to 0xff213000
        App size = 11508 bytes

        App Authentication feature is disabled!
        Resetting IPC

*** Ready to receive application ***

#4

Ok, so the log stops there, I apologize I thought at that point the board resets in your case.
That is natural, where the log stops, at this point seeing that your services started without failures I am thinking about network issues. I would recommend that you check the config.json file (found in the config.img in your downloaded image before flashing the device) for valid wifi credentials. Also check if this specific wifi has network access.
This is not much help but it is really hard to grasp what is happening there.

Best regards,
Theodor


#5

Ok, so I’m not supposed to get a prompt, that was one of the things I was confused about, thanks!
It was a typo in the wifi! Stupid mistake I probably made when re-downloading the image.
Thanks for all your help!


#6

Glad I could help. Have fun with you project.

Best regards,
Theodor