14 Replies Latest reply on Aug 18, 2016 1:27 PM by Intel Corporation

    Installing latest yocto image - renders board unusable

    pixelsitter

      Recently purchased Edison board with Arduino.  I don't know if it matters but my board's serial is: FZEDA543D00UHS501

       

      I'm running the tools on Ubuntu 14.04 from this url: IoT - Intel® Edison Board Download | Intel® Software

       

      1. When I first booted up the edison board, it came up and mounted an "Edison" drive.

      2. Ran install_GUI.sh and followed to flash to the latest release.  Rebooted and the edison board is hosed, No "Edison" drive mounted.  install_GUI.sh no longer recognizes theres any edison board.

      3. Reflashed it manually, using flashall.sh and it said it flashed successfully.  Edison board still hosed after reboot.

      4. So I downloaded the Previous Yocto* Poky image for Edison", flashed it manually, rebooted and "Edison" drive mounted.  Uploaded and and ran Blink test app.

       

      So, my question is why does Latest Yocto* Poky image for Edison  not work on my board?

        • 1. Re: Installing latest yocto image - renders board unusable
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hello pixelsitter,
           
          I have seen a behavior similar to this one where the board would behave unexpectedly after flashing the latest image. The workaround that I found to be useful was to flash the previous image (version 3.0) and then flash again the image 3.5 with the flashall.sh method. After this the board should behave as expected.
           
          Please try this and let me know how it goes.
          -Peter.

          • 2. Re: Installing latest yocto image - renders board unusable
            pixelsitter

            Hi Peter,

             

            Tried it a few times but no joy.  Anything else I can try?

            • 3. Re: Installing latest yocto image - renders board unusable
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              When you flash the latest image, do you have access to the Linux console? If so, do you see anything strange on its output? I mean, is there something different from when you flash the 3.0 image?
               
              Also, you could try the recovery method of flashall.sh and pre-built xFSTK (https://communities.intel.com/thread/56133). Let me know if it makes any difference?
               
              -Peter.

              • 4. Re: Installing latest yocto image - renders board unusable
                Intel Corporation
                This message was posted on behalf of Intel Corporation

                Hi pixelsitter,

                Do you still need help on this? Were you able to run additional tests?

                Regards,
                -Diego

                • 5. Re: Installing latest yocto image - renders board unusable
                  pixelsitter

                  Hi Diego,

                   

                  Yes, I still your help on this.  Got pulled away for a bit.  I will run the test this afternoon and report my finding.

                   

                  Thanks,

                  Robert

                  • 6. Re: Installing latest yocto image - renders board unusable
                    pixelsitter

                    Intel Corporation wrote:

                     

                    When you flash the latest image, do you have access to the Linux console? If so, do you see anything strange on its output? I mean, is there something different from when you flash the 3.0 image?

                    Also, you could try the recovery method of flashall.sh and pre-built xFSTK (https://communities.intel.com/thread/56133). Let me know if it makes any difference?

                    -Peter.

                    Here's my output starting from 3.0:

                     

                    ------- previous image

                    Poky (Yocto Project Referen1.7.2 edison ttyMFD2

                     

                    edison login: root

                    root@edison:~# uname -r

                    3.10.17-poky-edison+

                    root@edison:~#

                     

                    ----3.5 Image: Flashall log ----------------

                     

                    robert@edison1:~/Downloads/iot-devkit-prof-dev-image-edison-20160606$ sudo ./flashall.sh

                    Using U-Boot target: edison-blankcdc

                    Now waiting for dfu device 8087:0a99

                    Please plug and reboot the board

                    Flashing IFWI

                    ##################################################] finished!

                    ##################################################] finished!

                    Flashing U-Boot

                    ##################################################] finished!

                    Flashing U-Boot Environment

                    ##################################################] finished!

                    Flashing U-Boot Environment Backup

                    ##################################################] finished!

                    Rebooting to apply partition changes

                    Now waiting for dfu device 8087:0a99

                    Flashing boot partition (kernel)

                    ##################################################] finished!

                    Flashing rootfs, (it can take up to 5 minutes... Please be patient)

                    Rebooting

                    U-boot & Kernel System Flash Success...

                    Your board needs to reboot to complete the flashing procedure, please do not unplug it for 2 minutes.

                    robert@edison1:~/Downloads/iot-devkit-prof-dev-image-edison-20160606$

                     

                     

                    ------- Console after update to 3.5 --------------------------

                    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 14: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-34e03a2335f4 rootfstype=ext4 console=ttyMFD2 earlyprintk=ttyMFD2,keep loglevel=4 g_multi.ethernet_config=cdc systemd.unit=multi-user.target hardware_id=00 g_multi.iSerialNumber=8166d9bfa286147e96692b6142af3bbd g_multi.dev_addr=02:00:86:af:3b:bd platform_mrfld_audio.audio_codec=dummy"

                     

                     

                    Starting kernel ...

                     

                     

                    --------- Board pretty much dead -----------------------------

                    After waiting more than half hour...

                     

                    --------- Unplugged/replugged cables to reboot -------------------------

                    No "Edison" drive mounted....

                     

                    -------- Logged in through serial ------------------

                    Poky (Yocto Project Reference Distro) 1.7.2 edison ttyMFD2

                     

                    edison login: root

                    root@edison:~# uname -r

                    3.10.98-poky-edison+

                    root@edison:~#

                     

                    ---------------- No response from any IDE's, etc. -----------------

                    install_GUI.sh - doesn't see the board even after multiple reboots

                     

                    --------------- Reflashed with 3.0 --------------------------------

                    Works as designed.

                     

                    Any idea from the logs above?  I'll try the xFSTK next to see if that works.

                    • 7. Re: Installing latest yocto image - renders board unusable
                      Intel Corporation
                      This message was posted on behalf of Intel Corporation

                      Right now the only option left would be to try the xFSTK method. Please try that and let us know. If it doesn't work, I'd suggest you to submit an email to http://www.intel.com/support/mailform/maker/emailsupport.htm, we should be able to help you more accurately there.

                      -Peter.

                      • 8. Re: Installing latest yocto image - renders board unusable
                        pixelsitter

                        Hi Peter,

                         

                        xFSTK didn't work for me.  Also, I went back to reflashing with the latest and flashall since I missed a FAILED warning.  I'm not sure if it helps you narrowing down the issue.  I don't see that line on the previous image that works.

                         

                        Welcome to Linux!

                         

                         

                                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  ] Created slice User and Session 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  ] Listening on Journal Socket.

                        [  OK  ] Created slice System Slice.

                                Mounting Temporary Directory...

                        [  OK  ] Created slice system-serial\x2dgetty.slice.

                        [  OK  ] Created slice system-getty.slice.

                                Starting Load Kernel Modules...

                                Starting udev Coldplug all Devices...

                                Starting Create Static Device Nodes in /dev...

                                Mounting Debug File System...

                                Mounting POSIX Message Queue File System...

                                Starting Apply Kernel Variables...

                                Starting Journal Service...

                        [  OK  ] Started Journal Service.

                        [  OK  ] Reached target Slices.

                                Starting Remount Root and Kernel File Systems...

                        [  OK  ] Set up automount home.automount.

                        [  OK  ] Mounted POSIX Message Queue File System.

                        [  OK  ] Mounted Debug File System.

                        [  OK  ] Mounted Temporary Directory.

                        [FAILED] Failed to start Load Kernel Modules.

                        See 'systemctl status systemd-modules-load.service' for details.

                        [  OK  ] Started Create Static Device Nodes in /dev.

                        [  OK  ] Started Apply Kernel Variables.

                        [  OK  ] Started Remount Root and Kernel File Systems.

                        [  OK  ] Started udev Coldplug all Devices.

                                Starting Load/Save Random Seed...

                                Starting udev Kernel Device Manager...

                        [  OK  ] Reached target Local File Systems (Pre).

                                Mounting /var/volatile...

                                Mounting Configuration File System...

                                Mounting FUSE Control File System...

                        [  OK  ] Mounted FUSE Control File System.

                        [  OK  ] Mounted Configuration File System.

                        [  OK  ] Mounted /var/volatile.

                        [  OK  ] Started udev Kernel Device Manager.

                        [  OK  ] Started Load/Save Random Seed.

                        [  OK  ] Reached target Local File Systems.

                                Starting Trigger Flushing of Journal to Persistent Storage...

                                Starting Create Volatile Files and Directories...

                        [  OK  ] Started Create Volatile Files and Directories.

                        [  OK  ] Found device /dev/ttyMFD2.

                        [  OK  ] Found device /dev/disk/by-partlabel/factory.

                        • 9. Re: Installing latest yocto image - renders board unusable
                          pixelsitter

                          Hi Peter,

                           

                          It looks like I'm getting the same error as this user on this thread Failing to Flash Edison breakout board

                           

                          The only difference between him and I is that I have the Arduino board.

                          • 10. Re: Installing latest yocto image - renders board unusable
                            Intel Corporation
                            This message was posted on behalf of Intel Corporation

                            Hi pixelsister,

                            In that case, please submit an email to https://customercare.intel.com/?lang=en-US. We should be able to provide you a more accurate support there.

                            -Peter.

                            • 11. Re: Installing latest yocto image - renders board unusable
                              TGunthorpe

                              To Intel

                               

                              I've been using Edison now for about 6 months. It's a moving target ....

                              Recently I changed from using tools such at Phone Flash Tool (deprecated) to the Intel Edison Board Configuration Tool. Nice to have all of the configuration in one place.

                              Yesterday I ran the tool, Flashed several Edisons to edison-image-20160606 and spent the rest of the night trying to figure out what I had done wrong. The AP mode doesn't work anymore (haven't tested other functions).

                               

                              The answer is to re-Flash back to the previous image edison-image-20160315

                               

                              Any news on an image that works ?

                               

                              -T

                              • 12. Re: Installing latest yocto image - renders board unusable
                                Intel Corporation
                                This message was posted on behalf of Intel Corporation

                                I've seen this behavior you mention a couple of times. The workaround I have used so far is to flash the previous image (3.0) and then use the flashall.sh method (https://communities.intel.com/docs/DOC-25154) to flash the latest image (3.5). Please try this and let me know how it goes.

                                 

                                -Peter.

                                • 13. Re: Installing latest yocto image - renders board unusable
                                  TGunthorpe

                                  Hi Peter,

                                  I did what you suggested with the Flashing. Just mildly better results, - the AP was discoverable - however I could never get the page to load at http://192.168.42.1

                                  I re-flashed back to edison-image-20160315 and it's works fine.

                                   

                                  -Tom

                                  • 14. Re: Installing latest yocto image - renders board unusable
                                    Intel Corporation
                                    This message was posted on behalf of Intel Corporation

                                    I just noted that the issues with web server is a known issue with the latest image. This issue has been reported and we are currently working on find a way to solve it. However, there's no ETA for a fix.
                                     
                                    -Peter.