7 Replies Latest reply on Nov 16, 2015 3:35 AM by LorenWest

    Intel Edison not recognized

    Evotis

      Hi !

      I come to you after having tried to flash my edison with the flashtool, the flashtool told me then that the flash failed part away and then, after having rebooted my edison, she is not recognised anywhere.

      She does not appear any more on windows (or on mac, or linux, for that matter (yes, i tried ) ).

      I have read many posts on the subject and every one of them ended with "try the flash tool" or "run do_ota".

      We also tried the flashall.sh and the flashall.bat, wich does nothing and end with a timeout

       

      the flashtool does not find the edison, and end with a timeout.

       

      the run do_ota does that :

       

      boot > run do_ota

      ** Unrecognized filesystem type **

      Saving Environment to MMC...

      Writing to MMC(0)... done

      resetting ...

       

      and then, when rebooting :

       

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

      PSH KERNEL VERSION: b0182b2b

                      WR: 20104000

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

       

      SCU IPC: 0x800000d0  0xfffce92c

       

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

       

      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 ***

       

       

      GADGET DRIVER: usb_dnl_dfu

      reading vmlinuz

      5434848 bytes read in 134 ms (38.7 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 Fri Jun 19 12:06:40 CEST 2015

      Building boot_params at 0x00090000

      Loading bzImage at address 00100000 (5419488 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=258a14998452d5552f21fae850663c69 g_multi.dev_addr=02:00:86:66:3c:69 platform_mrfld_audio.audio_codec=dummy"

       

      Starting kernel ...

       

      [    1.602328] snd_soc_sst_platform: Enter:sst_soc_probe

      [    2.006372] pmic_ccsm pmic_ccsm: Error reading battery profile from battid frmwrk

      [    2.024547] pmic_ccsm pmic_ccsm: Battery Over heat exception

      [    2.024615] pmic_ccsm pmic_ccsm: Battery0 temperature inside boundary

      [    2.190056] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.195406] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.205138] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.205942] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.206743] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.207909] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.208709] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.209507] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.210307] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.211103] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.212000] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.212801] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.213591] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.214387] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.215252] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.216124] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.216919] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.217726] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.218527] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      [    2.219325] EXT4-fs error (device mmcblk0p8): __ext4_ext_check_block:477: inode #4193: comm init: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)

      /sbin/init: error while loading shared libraries: libkmod.so.2: cannot open shared object file: No such file or directory

       

      I'm quite desesperate, if anyone have an idea, I will be very happy to try it.

      Thanks !

        • 1. Re: Intel Edison not recognized
          KurtE

          When you said you did the flashall.sh  did you run it using: sudo?

          That is what fixed some of these issues for me in the past.

           

          Good Luck

          • 2. Re: Intel Edison not recognized
            Evotis

            Yep, I did it using sudo.

            • 3. Re: Intel Edison not recognized
              KurtE

              Hopefully someone from Intel or the like can answer this better than I can.

               

              Again if it were me, I would try again using the sudo ./flashall.sh from a linux box.

              If this fails, it might help if you post what messages were printed in the terminal window you ran it from the flashall from.  It might help others help diagnose the issue.  Like did it find the necessary tools.

               

              Also which carrier board are you using? (Mini or Arduino, or ...)

              Once you start the flashall, did you then apply power to the Edison?  On Minis, I unplug the USB connection closest to the center and then plug it back in.

               

              If Arduino board, make sure the usb switch is going toward the small usb connector and not the larger one...  Again on these boards I unplug the USB from the appropriate connector and plug it back in.

               

              If you have the debug terminal USB plugged in, with a terminal window open on it, you should see it go through a boot process after you start the flashall...

               

              Earlier I had better luck on having the flashall complete if I then also applied external power to the Edison.  If I remember correctly this was more with the Arduino carrier board where maybe I had a shield or two plugged in.  But again you still need to make sure that the board reboot after you start the flashall...  Unfortunately I can no longer verify this with an Arduino board as my board fried itself yesterday when I plugged in the power connector...

               

              I hope that helps

              • 4. Re: Intel Edison not recognized
                Intel_Alvarado

                Hi,

                 

                The recommended methods for flashing are the flash tool lite and the flashall script.

                Flashall script guide: How to Run the Flashall Script

                 

                If you believe that you may have damaged your board you can fill a form in Intel Support so the Warranty Team can take a closer look at your board.

                 

                Sergio

                • 5. Re: Intel Edison not recognized
                  rageberry

                  Hi Intel_Alvarado,

                   

                  Is that an automatic response ? Did you read the original question ? You just recommend to do what he has done...


                  I have the same problem. I tried both flashall script from your website and from the usb key given in intel edison hackaton in Paris this month. I also tried the GUI software Phone Flash Tool (again from your website and the one given in the hackaton).

                  It does not work. I have the same output than him.

                   

                  Do you have more informations about this problem ?

                   

                  Thanks

                  • 6. Re: Intel Edison not recognized
                    Evotis

                    Hi Kurte,

                     

                    Sorry for the delay, I have an arduino expention board.

                    When I run the flashall, it simply does nothing until it times out.

                    The power switch is going toward the usb (well... otherwise it will not even output anything ).

                    The Edison goes through a boot process, the one i've attached to the original post.

                     

                    @Alvarado : Yep... did that, doesn't work... well, thanks anyway... I guess.

                    • 7. Re: Intel Edison not recognized
                      LorenWest

                      I'm having the exact same issue with the exact same output.  Evotis, did you ever find a resolution, or is your Edison still a brick?