Community
cancel
Showing results for 
Search instead for 
Did you mean: 
aedwa2
New Contributor III
1,560 Views

Edison will not boot. How to recover data?

My Edison has been working in my product for a couple of years. It worked yesterday but might have had the power removed during shutdown. When I went to recover my data this morning it will not boot. No error messages. Is there any way to recover my data file? I logged about an hour of data and need to get it.

******************************

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 (Feb 11 2015 - 20:13:05)

Watchdog enabled

DRAM: 980.6 MiB

MMC: tangier_sdhci: 0

In: serial

Out: serial

Err: serial

Hit any key to stop autoboot: 0

Target:blank

Partitioning already done...

Flashing already done...

GADGET DRIVER: usb_dnl_dfu

reading vmlinuz

5280608 bytes read in 334 ms (15.1 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 (andrew@Compilefarm) # 1 SMP PREEMPT Wed Feb 11 22:21:05 CST 2015

Building boot_params at 0x00090000

Loading bzImage at address 00100000 (5265248 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=3a6af05b4217973936d6852d9dde7ee6 g_multi.dev_addr=02:00:86:de:7e:e6"

Starting kernel ...

0 Kudos
10 Replies
Andriy_S_Intel
Employee
24 Views

First of all, add ignore_loglevel to kernel command line (there is a special environment variable even for that, it has debug in the name, but I don't recall right now full name of it). Add it and see what kernel will write.

aedwa2
New Contributor III
24 Views

And how do I add anything to the kernel command line if it won't boot? I hope there is an answer because if I could write, I could probably read and that is what is important. I need the data that is on the Edison.

Andriy_S_Intel
Employee
24 Views

I'm too lazey to explain details, but you just simple need to interrupt U-Boot to get into its "shell" and modify environment variable. After that you have two options: just boot, or save and boot.

idata
Community Manager
24 Views

Hello allene,

 

 

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

 

 

I'm sorry to inform you that there isn't a way to retrieve the data from a board that doesn't boot.

 

 

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

 

 

Regards,

 

Andres V.
aedwa2
New Contributor III
24 Views

0andriy

Can you give me a link or a hint on how to get into U-Boot shell?

Allen

Andriy_S_Intel
Employee
24 Views

  • Connect your board via serial interface to the PC
  • Open terminal application on PC side (in Linux picocom, in Windows putty)
  • Reset or power on your Edison board
  • When it will starts countdown (for 1 second) you hit space to interrupt it
  • Now you are in U-Boot command line.
aedwa2
New Contributor III
24 Views

0andriy

I put the Edison in boot mode and have spent about an hour Googling trying to figure out how to put the append the "ignore_loglevel" parameter. I can find how to add it in the file system but not how to add it from the boot command line. I can't figure it out. I think it should not be this hard to figure it out. I am pretty sure I used to do it with RadHat 4 but that was 20 years ago. I would appreciate some help.

Andriy_S_Intel
Employee
24 Views

allene kirjoitti:

0andriy

I put the Edison in boot mode and have spent about an hour Googling trying to figure out how to put the append the "ignore_loglevel" parameter. I can find how to add it in the file system but not how to add it from the boot command line. I can't figure it out. I think it should not be this hard to figure it out. I am pretty sure I used to do it with RadHat 4 but that was 20 years ago. I would appreciate some help.

Hit any key to stop autoboot: 0

 

=> grep loglevel

 

bootargs_debug=loglevel=4

 

=> setenv bootargs_debug 'ignore_loglevel'

 

=> boot

 

 

aedwa2
New Contributor III
24 Views

Thank you 0andriy

This s what I get

boot > grep loglevel

bootargs_debug=loglevel=4

boot > setenv bootargs_debug 'ignore_loglevel'

boot > boot

Target:blank

Partitioning already done...

Flashing already done...

GADGET DRIVER: usb_dnl_dfu

reading vmlinuz

5280608 bytes read in 373 ms (13.5 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 (andrew@Compilefarm) # 1 SMP PREEMPT Wed Feb 11 22:21:05 CST 2015

Building boot_params at 0x00090000

Loading bzImage at address 00100000 (5265248 bytes)

Magic signature found

Kernel command line: "rootwait root=PARTUUID=012b3303-34ac-284d-99b4-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep ignore_loglevel g_multi.ethernet_config=rndis systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=3a6af05b4217973936d6852d9dde7ee6 g_multi.dev_addr=02:00:86:de:7e:e6"

Starting kernel ...

Then after a minute or so it starts over. Now what?

******************************

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 (Feb 11 2015 - 20:13:05)

Watchdog enabled

DRAM: 980.6 MiB

MMC: tangier_sdhci: 0

In: serial

Out: serial

Err: serial

Hit any key to stop autoboot: 0

Target:blank

Partitioning already done...

Flashing already done...

GADGET DRIVER: usb_dnl_dfu

reading vmlinuz

5280608 bytes read in 392 ms (12.8 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 (andrew@Compilefarm) # 1 SMP PREEMPT Wed Feb 11 22:21:05 CST 2015

Building boot_params at 0x00090000

Loading bzImage at address 00100000 (5265248 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=3a6af05b4217973936d6852d9dde7ee6 g_multi.dev_addr=02:00:86:de:7e:e6"

Starting kernel ...

Andriy_S_Intel
Employee
24 Views

Okay, it means you have quite corrupted boot partition. Depends on how valuable data is there (on eMMC) and how much time you have, you may try a hard way. I.e. update U-Boot, prepare an image with new kernel and initramfs on SD card, boot it and mount partitions on eMMC. Depending on the result it might be possible to retrieve valuable data.

Reply