Community
cancel
Showing results for 
Search instead for 
Did you mean: 
KBoci
Beginner
1,488 Views

Edison hangs during booting after uploading a MCU program

I tried to upload a few simple programs to the MCU of the edison, and after a few working iterations, Edison started to fail during boot. On the serial console you can see it hang usually at "Starting Daemon to receive the wpa_supplicant event...". Once or twice it reached the redis server. At this point it isn't reachable by either serial or WiFi. It sometimes dies with some junk at the end of the serial console.

The program didn't do anything very interesting, it continuously flashed leds connected (via a logic shifter) to pins GP47, GP12, GP13 and read input on GP46. Every second it also writes with a The iteration that broken Edison was adding the read on GP46.

Cutting power to the Edison and restarting it doesn't help.

How can I unbrick my Edison and why has this happened in the first place - shouldn't the quark be separate from the Edison anyway?

Startup log follows:

0 Target:blank Partitioning already done... Flashing already done... GADGET DRIVER: usb_dnl_dfu reading vmlinuz 5461344 bytes read in 135 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.98-poky-edison+ (neck@flax) # 1 SMP PREEMPT Mon Jun 6 1 4:32:08 PDT 2016 Building boot_params at 0x00090000 Loading bzImage at address 00100000 (5445984 bytes) Magic signature found Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f 4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.et hernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSeria lNumber=695bd3388c207bec11732949aeb472a3 g_multi.dev_addr=02:00:86:b4:72:a3 plat form_mrfld_audio.audio_codec=dummy" Starting kernel ... [ 0.735841] pca953x 1-0020: failed reading register [ 0.740956] pca953x 1-0021: failed reading register [ 0.746083] pca953x 1-0022: failed reading register [ 0.751146] pca953x 1-0023: failed reading register [ 1.637291] snd_soc_sst_platform: Enter:sst_soc_probe [ 2.121198] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk [ 2.130050] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary ^[[18~ Welcome to Linux! [ 2.715113] systemd[1]: [/lib/systemd/system/wyliodrin-hypervisor.service:3] Failed to add dependency on redis, ignoring: [ 2.728107] systemd[1]: [/lib/systemd/system/wyliodrin-server.service:3] Failed to add dependency on redis, ignoring: Inva Expecting device dev-ttyMFD2.device... ^[ Expecting device sys-subsystem-net-devices-wlan0.device... [ OK ] Reached target Remote File Systems. Expecting device dev-disk-by\x2dpartlabel-factory.device... [ OK ] Reached target Paths. [ OK ] Reached target Swap. [ OK ] Set up automount boot.automount. [ OK ] Created slice Root Slice. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on udev Control Socket. [ OK ] Listening on udev Kernel Socket. [ OK ] Created slice User and Session Slice. [ OK ] Listening on Journal Socket. [ OK ] Created slice System Slice. Starting Remount Root and Kernel File Systems... Starting Apply Kernel Variables... Starting Create list of required static device nodes...rrent kernel... Mounting Debug File System... Starting Load Kernel Modules... Mounting POSIX Message Queue File System... Starting udev Coldplug all Devices... [ OK ] Created slice system-serial\x2dgetty.slice. [ OK ] Created slice system-getty.slice. Starting Journal Service... [ OK ] Started Journal Service. [ OK ] Reached target Slices. Mounting Temporary Directory... [ OK ] Set up automount home.automount. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Mounted Debug File System. [ OK ] Mounted Temporary Directory. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Apply Kernel Variables. [ OK ] Started Create list of required static device nodes ...current kernel. [ OK ] Started Load Kernel Modules. [ OK ] Started udev Coldplug all Devices. Mounting FUSE Control File System... Mounting Configuration File System... Starting Create Static Device Nodes in /dev... Starting Load/Save Random Seed... [ OK ] Mounted Configuration File System. [ OK ] Mounted FUSE Control File System. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started Load/Save Random Seed. Starting udev Kernel Device Manager... [ OK ] Reached target Local File Systems (Pre). Mounting /var/volatile... [ OK ] Started udev Kernel Device Manager. [ OK ] Mounted /var/volatile. [ OK ] Reached target Local File Systems. Starting Create Volatile Files and Directories... Starting Trigger Flushing of Journal to Persistent Storage... [ OK ] Started Create Volatile Files and Directories. [ OK ] Started Trigger Flushing of Journal to Persistent Storage. [ OK ] Found device /sys/subsystem/net/devices/wlan0. [ OK ] Found device /dev/disk/by-partlabel/factory. [ OK ] Found device /dev/ttyMFD2. Mounting Mount for factory... [ OK ] Created slice system-systemd\x2drfkill.slice. Starting Load/Save RF Kill Switch Status of rfkill2... Starting Load/Save RF Kill Switch Status of rfkill0... Starting Load/Save RF Kill Switch Status of rfkill1... Starting Network Time Synchronization... Starting Update UTMP about System Boot/Shutdown... [ OK ] Mounted Mount for factory. [ OK ] Started Network Time Synchronization. [ OK ] Started Load/Save RF Kill Switch Status of rfkill2. [ OK ] Started Load/Save RF Kill Switch Status of rfkill0. [ OK ] Started Load/Save RF Kill Switch Status of rfkill1. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Reached target Sound Card. [ OK ] Created slice system-systemd\x2dfsck.slice. Starting File System Check on /dev/disk/by-partlabel/home... [ OK ] Reached target System Initialization. [ OK ] Listening on RPCbind Server Activation Socket. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Timers. Starting Restore Sound Card State... Starting Console System Startup Logging... [ 8.036004] systemd-fsck[179]: /dev/mmcblk0p10: recovering journal [ OK ] Listening on sshd.socket. [ OK ] Started Console System Startup Logging. [ 8.058885] systemd-fsck[179]: /dev/mmcblk0p10: clean, 44/87120 files, 14223/348155 blocks [ OK ] Started File System Check on /dev/disk/by-partlabel/home. Mounting /home... [ OK ] Reached target Sockets. [ OK ] Reached target Basic System. Starting Edison PWR button handler... [ OK ] Started Edison PWR button handler. Starting Edison sketch check service... [ OK ] Started Edison sketch check service. Starting Wyliodrin server... Starting Telephony service... Starting OpenSSH Key Generation... Starting Daemon to handle arduino sketches... [ OK ] Started Daemon to handle arduino sketches. Starting Daemon to reset sketches... [ OK ] Started Daemon to reset sketches. Starting Start or stop WiFI AP Mode in Edison... [ OK ] Started Start or stop WiFI AP Mode in Edison. Starting Wyliodrin hypervisor... Starting Daemon to load edison mcu app binary... [ OK ] Started Daemon to load edison mcu app binary. Starting Bluetooth rf kill event daemon... [ OK ] Started Bluetooth rf kill eve▒P▒plication available at (physical) address 0x04819000 VRL mapped to 0xff217000 App size = 12340 bytes App Authentication feature is disabled! Resetting IPC *** Ready to receive application *** Starting WPA supplicant service... Starting D-Bus System Message Bus... [ OK ] Started D-Bus System Message Bus. [ OK ] Started Telephony service. Starting Network Service... Starting Login Service... Starting Cleanjournal service... [ OK ] Started Cleanjournal service. Starting Crashlog service... [ OK ] Started Crashlog service. Starting Watchdog sample daemon... [ OK ] Started Watchdog sample daemon. Starting Permit User Sessions... [ OK ] Mounted /home. [ OK ] Started OpenSSH Key Generation. [ OK ] Started Permit User Sessions. [ OK ] Started Restore Sound Card State. [ OK ] Started Login Service. Starting Bluetooth service... Starting PulseAudio Sound System... Starting Daemon to receive the wpa_supplicant event...
0 Kudos
5 Replies
KBoci
Beginner
29 Views

Pastebin link for the log for easier reading:

https://pastebin.com/DChjJLDz 0 Target:blank Partitioning already done... Flashing already done... GADGET - Pastebin.com

idata
Community Manager
29 Views

Hello kbociurko,

 

 

Thank you for your interest in the Intel® Edison Breakout Board.

 

 

If you have a bricked board, there are a three alternatives to try to recover it:

 

 

Using Flash Tool Lite

 

https://software.intel.com/en-us/using-flash-tool-lite

 

 

Flashing your firmware manually

 

https://software.intel.com/en-us/flashing-the-firmware-on-intel-edison-board

 

 

Building xFSTK on Ubuntu 14.04 (32-bit) for flashing Edison

 

https://communities.intel.com/thread/56121 https://communities.intel.com/thread/56121

 

 

If you want us to investigate more about why the issue happened, then you'll have to share the steps that you followed, the programs that you used, and, if possible, provide an image of your setup.

 

 

I'll be waiting for your response.

 

 

If you have any update or question, don't hesitate to contact us.

 

 

Have a nice day.

 

 

Regards,

 

Andres V.
idata
Community Manager
29 Views

Hello kbociurko,

 

 

I was wondering if you could check any of the methods to recover your board.

 

 

If you have any update or question, don't hesitate to contact us.

 

 

Regards,

 

Andres V.
KBoci
Beginner
29 Views

Sorry for the late reply, didn't get any notification on your answer.

After posting this issue, I have switched to another edison module to continue development. Now I have tried that then-broken module and somehow it works.

This was not an issue with connections as I tried with many boards, this also wasn't an issue of powering down as it was powered down for at least a few minutes between times when Edison had power.

I have no idea what has happened and why has it happened. Frankly, I'm afraid it can happen again, but not in a safe development environment, but in production where the module can't be easily replaced.

Do you have any reasons why this issue could have been triggered?

idata
Community Manager
29 Views

Hello kbociurko,

 

 

I'm glad to hear that your module is working again.

 

 

I understand your concern regarding the sudden, and seemly unpredictable behavior. Identifying what could have caused the issue is quite difficult from our side, at least without knowing what kind of software and hardware has been interacting with the module.

 

 

Since this seems like an isolated issue, my recommendation is to keep some kind of journal (you probably already have something similar), in order to identify the possible root of the issue in case it happens again.

 

 

If you have any other update or question, don't hesitate to contact us.

 

 

Have a nice day.

 

 

Regards,

 

Andres V.