13 Replies Latest reply on May 11, 2017 1:35 AM by Umesh@pro3

    Problem with booting from the eMMC after image flashing

    rosek

      Hi,

       

      I'm trying to setup Intel Joule with the newest Reference Linux OS for IoT image. I completed all steps described here:

      IoT - Flashing the development platform with the latest version of Reference Linux* OS for IoT | Intel® Software

       

      but the OS doesn't boot. I'm using SD card, it looks like image is transfered from the SD Card to eMMC but then boot procedure fails with the following error:

      [    4.958163] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [    4.971142] mmc1: tuning execution failed

      [    4.975643] mmc1: error -5 whilst initialising MMC card

      starting version 230

      [    5.086176] random: udevd urandom read with 9 bits of entropy available

      [    5.120292] mmc1: new HS400 MMC card at address 0001

      [    5.127469] mmcblk0: mmc1:0001 016G32 14.7 GiB

      [    5.132850] mmcblk0boot0: mmc1:0001 016G32 partition 1 4.00 MiB

      [    5.139615] mmcblk0boot1: mmc1:0001 016G32 partition 2 4.00 MiB

      [    5.148917] mmcblk0gp0: mmc1:0001 016G32 partition 4 4.00 MiB

      [    5.158975] mmcblk0gp3: mmc1:0001 016G32 partition 7 4.00 MiB

      [    5.165895] mmcblk0rpmb: mmc1:0001 016G32 partition 3 4.00 MiB

      [    5.316223]  mmcblk0: p1 p2 p3

      [    6.412141] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [    6.425090] mmc1: tuning execution failed

      [    6.435731] blk_update_request: I/O error, dev mmcblk0, sector 63490

      [    6.442898] EXT4-fs (mmcblk0p3): unable to read superblock

      mount: mounting /dev/disk/by-partuuid/12345678-9abc-def0-0fed-cba987654320 on /rootfs failed: Invalid argument

      umount: can't unmount /rootfs: Invalid argument

      [    7.624326] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [    7.645434] blk_update_request: I/O error, dev mmcblk0, sector 63490

      [    7.652562] EXT4-fs (mmcblk0p3): unable to read superblock

      mount: mounting /dev/disk/by-partuuid/12345678-9abc-def0-0fed-cba987654320 on /rootfs failed: Invalid argument

      umount: can't unmount /rootfs: Invalid argument

      [    8.832238] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [    8.853397] blk_update_request: I/O error, dev mmcblk0, sector 63490

      [    8.860528] EXT4-fs (mmcblk0p3): unable to read superblock

      mount: mounting /dev/disk/by-partuuid/12345678-9abc-def0-0fed-cb[    8.867533] mmc1: unexpected status 0x800900 after switch

      a987654320 on /rootfs failed: Invalid argument

      umount: can't unmount /rootfs: Invalid argument

      [   10.051362] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [   20.089297] mmc1: Timeout waiting for hardware interrupt.

      [   20.097365] ------------[ cut here ]------------

      [   20.102528] WARNING: CPU: 1 PID: 0 at /var/lib/jenkins/workspace/builder-slot-3/build/tmp-glibc/work-shared/intel-corei7-64/kernel-source/drivers/mmc/host/sdhci.c:1017 sdhci_send_command+0x739/0xbd0()

      [   20.122448] Modules linked in:

      [   20.125862] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.15-yocto-standard #1

      [   20.133933] Hardware name: Intel Corp. Broxton M/SDS, BIOS GTPPA16A.X64.0143.B30.1608112014 08/11/2016

      [   20.144333]  0000000000000086 1ad54f83858803bb ffff88017fc83d28 ffffffffa81edbbb

      [   20.152615]  0000000000000000 ffffffffa8946568 ffff88017fc83d60 ffffffffa7e758d2

      [   20.160892]  ffff88007a147500 ffff88017b31f2d8 0000000000000246 ffff88017b31f318

      [   20.169172] Call Trace:

      [   20.171900]  <IRQ>  [<ffffffffa81edbbb>] dump_stack+0x4d/0x72

      [   20.178328]  [<ffffffffa7e758d2>] warn_slowpath_common+0x82/0xc0

      [   20.185037]  [<ffffffffa7e75a1a>] warn_slowpath_null+0x1a/0x20

      [   20.191551]  [<ffffffffa84fc049>] sdhci_send_command+0x739/0xbd0

      [   20.198261]  [<ffffffffa81fa937>] ? __const_udelay+0x27/0x30

      [   20.204580]  [<ffffffffa84f96b9>] ? sdhci_reset+0x59/0xc0

      [   20.210608]  [<ffffffffa84fc5b8>] sdhci_finish_data+0xd8/0x3a0

      [   20.217123]  [<ffffffffa84fc880>] ? sdhci_finish_data+0x3a0/0x3a0

      [   20.223926]  [<ffffffffa84fc8fb>] sdhci_timeout_timer+0x7b/0xc0

      [   20.230538]  [<ffffffffa7eca43e>] call_timer_fn+0x3e/0x170

      [   20.236662]  [<ffffffffa84fc880>] ? sdhci_finish_data+0x3a0/0x3a0

      [   20.243465]  [<ffffffffa7ecabf6>] run_timer_softirq+0x226/0x2c0

      [   20.250076]  [<ffffffffa7e7a1df>] __do_softirq+0x9f/0x2e0

      [   20.256103]  [<ffffffffa7e7a56d>] irq_exit+0x9d/0xa0

      [   20.261647]  [<ffffffffa86f0e12>] smp_apic_timer_interrupt+0x42/0x50

      [   20.268743]  [<ffffffffa86ef4cf>] apic_timer_interrupt+0x7f/0x90

      [   20.275449]  <EOI>  [<ffffffffa84e2853>] ? cpuidle_enter_state+0x123/0x2f0

      [   20.283132]  [<ffffffffa84e283d>] ? cpuidle_enter_state+0x10d/0x2f0

      [   20.290128]  [<ffffffffa84e2a57>] cpuidle_enter+0x17/0x20

      [   20.296155]  [<ffffffffa7eb0ef2>] call_cpuidle+0x32/0x60

      [   20.302084]  [<ffffffffa84e2a33>] ? cpuidle_select+0x13/0x20

      [   20.308400]  [<ffffffffa7eb11ce>] cpu_startup_entry+0x2ae/0x370

      [   20.315010]  [<ffffffffa7e371d2>] start_secondary+0x142/0x160

      [   20.321423] ---[ end trace bf8cfdb8dcfffd48 ]---

      [   20.326639] mmc1: Got data interrupt 0x00000002 even though no data operation was in progress.

      [   20.340344] mmcblk0: error -110 sending status command, retrying

      [   20.349139] mmcblk0: error -110 sending status command, retrying

      [   20.357898] mmcblk0: error -110 sending status command, aborting

      [   20.372740] mmc1: cache flush error -110

      [   20.507326] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

      [   20.520285] mmc1: tuning execution failed

      [   20.524769] mmc1: tried to reset card, got error -5

      [   20.530219] blk_update_request: I/O error, dev mmcblk0, sector 63490

      [   20.537380] EXT4-fs (mmcblk0p3): unable to read superblock

      mount: mounting /dev/disk/by-partuuid/12345678-9abc-def0-0fed-cba987654320 on /rootfs failed: Invalid argument

      I've updated BIOS to the newest version and then tried to flash using SD card, no luck. I've tried to use USB stick instead of the SD card but this failed too. Please find attached file which contains linux output while flashing using USB stick.

       

      Regards,

      Krzysztof

        • 1. Re: Problem with booting from the eMMC after image flashing
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          Hi Krzysztof,

          Thanks for reaching out.

          That's a weird issue. I followed the guide without problems using an SD Card and USB Drive, make sure that your SD Card is formatted before flashing the image in it (FAT file system). I recommend you start the process from the beginning again.

          Let us know if you still have issues.

          Regards,
          -Leonardo

          • 2. Re: Problem with booting from the eMMC after image flashing
            rosek

            Hi Leonardo,

             

            Thanks for a prompt reply.

             

            I found out that the image was actually flashed to the eMMC, however I'm not able to run from internal flash when the SD card is removed. Is this an expected behaviour?

             

            In order to flash image I follow exactly steps described in IoT - Flashing the development platform with the latest version of Reference Linux* OS for IoT | Intel® Software, but in a step when the guide says "You can now remove your bootable device from the development platform." I power off the system format SD card to FAT file system, insert SD card again and then it boots correctly. If the SD card is not inserted I get errors as posted in my previous message.

             

            This is my fdisk output:

            root@intel-corei7-64:~# fdisk -l | grep mmcblk

            Disk /dev/mmcblk0: 14.4 GiB, 15489564672 bytes, 30253056 sectors

            /dev/mmcblk0p1       8192 30253055 30244864 14.4G  c W95 FAT32 (LBA)

            Disk /dev/mmcblk1: 14.7 GiB, 15749611520 bytes, 30760960 sectors

            /dev/mmcblk1p1  2048    32767    30720   15M EFI System

            /dev/mmcblk1p2 32768    63487    30720   15M Windows recovery environment

            /dev/mmcblk1p3 63488 30760925 30697438 14.7G Linux filesystem

            Disk /dev/mmcblk1gp3: 4 MiB, 4194304 bytes, 8192 sectors

            Disk /dev/mmcblk1gp0: 4 MiB, 4194304 bytes, 8192 sectors

            Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors

            Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors

             

            When I remove the SD card while the OS is running I start to get these erros:

            [  626.927214] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

            [  626.940277] mmc1: tuning execution failed

            [  626.944816] mmcblk1: unknown error -5 sending read/write command, card status 0x800900

            [  626.953761] mmc1: Got data interrupt 0x00600000 even though no data operation was in progress.

            [  627.091210] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock

            [  627.106892] mmc1: tuning execution failed

            [  627.112708] mmc1: tried to reset card, got error -5

            [  627.119484] blk_update_request: I/O error, dev mmcblk1, sector 12918768

            [  627.128249] blk_update_request: I/O error, dev mmcblk1, sector 12918776

            [  627.136970] blk_update_request: I/O error, dev mmcblk1, sector 12918784

            [  627.145654] blk_update_request: I/O error, dev mmcblk1, sector 12918792

            [  627.154326] blk_update_request: I/O error, dev mmcblk1, sector 12918800

            [  627.163080] blk_update_request: I/O error, dev mmcblk1, sector 12918808

            [  627.171765] blk_update_request: I/O error, dev mmcblk1, sector 12918816

            [  627.180395] blk_update_request: I/O error, dev mmcblk1, sector 12918824

            [  627.189022] blk_update_request: I/O error, dev mmcblk1, sector 12918832

            [  627.197750] Aborting journal on device mmcblk1p3-8.

            [  637.226182] mmc1: Timeout waiting for hardware interrupt.

            [  637.235437] ------------[ cut here ]------------

            [  637.241760] WARNING: CPU: 1 PID: 0 at /var/lib/jenkins/workspace/builder-slot-3/build/tmp-glibc/work-shared/intel-corei7-64/kernel-source/drivers/mmc/host/sdhci.c:1017 sdhci_send_command+0x739/0xbd0()

            [  637.264137] Modules linked in: drbg ctr ccm xt_connmark bnep iptable_nat nf_nat_ipv4 nf_nat iptable_mangle spidev mei_spd gpio_keys intel_rapl x86_pkg_temp_thermal coretemp efivars typec_wcove gpio_wcove intel_pmic_thermal arc4 pwm_lpss_pci pwm_lpss iwlmvm(O) mac80211(O) spi_pxa2xx_platform iwlwifi(O) btusb btrtl btbcm snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_hda_codec_hdmi snd_soc_core cfg80211(O) i915 processor_thermal_device snd_hda_intel compat(O) snd_hda_codec intel_soc_dts_iosf mei_me iosf_mbi i2c_designware_platform mei dwc3_pci snd_hda_core i2c_designware_core hci_uart btintel video int3403_thermal int340x_thermal_zone int3400_thermal soc_button_array acpi_thermal_rel nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_conntrack nf_conntrack iptable_filter uio iio_trig_sysfs industrialio efivarfs ip_tables x_tables

            [  637.368401] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O    4.4.15-yocto-standard #1

            [  637.379383] Hardware name: Intel Corp. Broxton M/SDS, BIOS GTPP131A.X64.0143.B30.1609232056 09/23/2016

            [  637.391373]  0000000000000086 507c628edb167a88 ffff88017fc83d28 ffffffffb29edbbb

            [  637.401251]  0000000000000000 ffffffffb3146568 ffff88017fc83d60 ffffffffb26758d2

            [  637.411140]  ffff88017a188500 ffff88017a17a2d8 0000000000000246 ffff88017a17a318

            [  637.421029] Call Trace:

            [  637.425344]  <IRQ>  [<ffffffffb29edbbb>] dump_stack+0x4d/0x72

            [  637.433389]  [<ffffffffb26758d2>] warn_slowpath_common+0x82/0xc0

            [  637.441708]  [<ffffffffb2675a1a>] warn_slowpath_null+0x1a/0x20

            [  637.449829]  [<ffffffffb2cfc049>] sdhci_send_command+0x739/0xbd0

            [  637.458142]  [<ffffffffb29fa937>] ? __const_udelay+0x27/0x30

            [  637.466079]  [<ffffffffb2cf96b9>] ? sdhci_reset+0x59/0xc0

            [  637.473713]  [<ffffffffb2cfc5b8>] sdhci_finish_data+0xd8/0x3a0

            [  637.481825]  [<ffffffffb2cfc880>] ? sdhci_finish_data+0x3a0/0x3a0

            [  637.490216]  [<ffffffffb2cfc8fb>] sdhci_timeout_timer+0x7b/0xc0

            [  637.498402]  [<ffffffffb26ca43e>] call_timer_fn+0x3e/0x170

            [  637.506075]  [<ffffffffb2cfc880>] ? sdhci_finish_data+0x3a0/0x3a0

            [  637.514396]  [<ffffffffb26cabf6>] run_timer_softirq+0x226/0x2c0

            [  637.522487]  [<ffffffffb267a1df>] __do_softirq+0x9f/0x2e0

            [  637.529988]  [<ffffffffb267a56d>] irq_exit+0x9d/0xa0

            [  637.536983]  [<ffffffffb2ef0e12>] smp_apic_timer_interrupt+0x42/0x50

            [  637.545522]  [<ffffffffb2eef4cf>] apic_timer_interrupt+0x7f/0x90

            [  637.553634]  <EOI>  [<ffffffffb2ce2853>] ? cpuidle_enter_state+0x123/0x2f0

            [  637.562705]  [<ffffffffb2ce283d>] ? cpuidle_enter_state+0x10d/0x2f0

            [  637.571096]  [<ffffffffb2ce2a57>] cpuidle_enter+0x17/0x20

            [  637.578512]  [<ffffffffb26b0ef2>] call_cpuidle+0x32/0x60

            [  637.585815]  [<ffffffffb2ce2a33>] ? cpuidle_select+0x13/0x20

            [  637.593524]  [<ffffffffb26b11ce>] cpu_startup_entry+0x2ae/0x370

            [  637.601540]  [<ffffffffb26371d2>] start_secondary+0x142/0x160

            [  637.609375] ---[ end trace 2e8c191e1a2b7c3f ]---

            [  637.620177] mmcblk1: error -110 sending status command, retrying

            [  637.628518] mmcblk1: error -110 sending stop command, original cmd response 0x0, card status 0xc00900

            [  637.640306] mmcblk1: error -110 transferring data, sector 12916048, nr 8, cmd response 0x0, card status 0x0

            [  637.652708] blk_update_request: I/O error, dev mmcblk1, sector 12916048

            [  637.661628] Buffer I/O error on dev mmcblk1p3, logical block 1606570, lost sync page write

            [  637.672592] JBD2: Error -5 detected when updating journal superblock for mmcblk1p3-8.

            Do you have any idea why this happens?

            • 3. Re: Problem with booting from the eMMC after image flashing
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              Hi Krzysztof,

              I'm not sure why this is happening to you, did you successfully install the OS onto the eMMC? 

              After you remove the SD Card, you have to change the boot order again and set eMMC first again. I think that if you keep the SD Card, it will continue using the image in the SD Card.

              I will be waiting for your reply.

              Regards,
              -Leonardo

              • 4. Re: Problem with booting from the eMMC after image flashing
                rosek

                Hi Leonardo,

                 

                I believe that the image was flashed to eMMC,- the fdisk output I posted above shows that the SD card is formatted to FAT file system (mmcblk0p1) and that there is a bunch of partitions on the eMMC (mmcblk1). The partition which is mounted on a root folder is mmcblk1p3 which is on the eMMC. However I get these errors as posted above which seems to be related to mmc1 (eMMC?).

                 

                I'm starting to think that there is an hardware issue with either my development platform or Joule module itself. Is there a simple test which I can run to test all parts of these system? There must be a test script which is run in the production process?

                 

                FYI. I was checking boot order each time I restarted the module, definitely got this right. The development platform is powered from a high quality bench power supply with current limit set to 4A so I think power supply is not a problem here.

                 

                We need to decide soon if we would use Joule in our next product, so I wonder how to handle this problem. I ordered this kit in order to check that Joule has everything we need to develop a product but it is not possible to test it. I could order another platform module but then it would be a waste of money if Joule doesn't meet our requirements.

                 

                Please advice.

                 

                Regards.

                • 5. Re: Problem with booting from the eMMC after image flashing
                  Intel Corporation
                  This message was posted on behalf of Intel Corporation

                  Hi Krzysztof,

                  Let us investigate more about this issue, we will let you know when we have updates.

                  I appreciate your patience.

                  Regards,
                  -Leonardo

                  • 6. Re: Problem with booting from the eMMC after image flashing
                    Intel Corporation
                    This message was posted on behalf of Intel Corporation

                    Hi Krzysztof,

                    When I ran the command fdisk -l | grep mmcblk, I got a different output, take a look:

                    root@intel-corei7-64:~# fdisk -l | grep mmcblk
                    GPT PMBR size mismatch (7651327 != 30253055) will be corrected by w(rite).
                    Disk /dev/mmcblk0: 14.4 GiB, 15489564672 bytes, 30253056 sectors
                    /dev/mmcblk0p1  6144   36863   30720   15M EFI System
                    /dev/mmcblk0p2 36864   67583   30720   15M Windows recovery environment
                    /dev/mmcblk0p3 67584 7645183 7577600  3.6G Linux filesystem
                    Disk /dev/mmcblk1: 14.7 GiB, 15749611520 bytes, 30760960 sectors
                    /dev/mmcblk1p1  2048    32767    30720   15M EFI System
                    /dev/mmcblk1p2 32768    63487    30720   15M Windows recovery environment
                    /dev/mmcblk1p3 63488 30760925 30697438 14.7G Linux filesystem
                    Disk /dev/mmcblk1gp3: 4 MiB, 4194304 bytes, 8192 sectors
                    Disk /dev/mmcblk1gp0: 4 MiB, 4194304 bytes, 8192 sectors
                    Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
                    Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors

                    The difference between the outputs is in the Disk /dev/mmcblk0 section. It seems that the SD card is formatted in a different way. That might be the root cause of the issue since I don't find anything else different. 

                    So, I have the following recommendations for you:

                    1. Run the configuration tool without formatting the SD Card previously. Make sure the correct file is downloaded. The file is available in this site: https://download.ostroproject.org/releases/ostro-os-xt/milestone/, under v1.0.0/images/intel-corei7-64/ostro-xt-image-swupd-intel-corei7-64.dsk.xz

                    2. Run the configuration tool in another OS, maybe Linux OS if customer is using Windows.

                    3. Use a different 16GB SD Card

                    Please let us know if any of these recommendations worked.

                    Regards,
                    -Leonardo

                    • 7. Re: Problem with booting from the eMMC after image flashing
                      rosek

                      Hi Leonardo,

                       

                      Can you also pass output of 'mount | grep mmcblk' from yours system, please? It shows which partition is mounted on a root directory. Can you remove the SD card and boot Intel Joule? Does it boot correctly from eMMC?

                       

                      Looking on the fdisk output you provided, we have exactly the same partitions setup on the internal eMMC (Please have a look on the mmcblk1 disk). The mmcblk0 is the SD card, I formatted mine to FAT file system to make sure that the OS is running from internal eMMC flash memory, not from the SD card.

                       

                      It shouldn't matter that we have different partitions setup on the mmcblk0, the Joule should work correctly even without SD card inserted. Correct?

                       

                      1. I was using v1.0.0/images/intel-corei7-64/ostro-xt-image-swupd-intel-corei7-64.dsk.xz image and also the newest development release from Ostro project. I tried Ubuntu too, I can boot ubuntu from the USB stick but then when I flash it to the eMMC it doesn't boot at all.

                       

                      2./3. I was using two different PCs, using both Linux and Windows. I tried two different SD cards and two different USB memory sticks without success.

                       

                      Best regards,

                      Krzysztof

                      • 8. Re: Problem with booting from the eMMC after image flashing
                        Intel Corporation
                        This message was posted on behalf of Intel Corporation

                        Hi Krzysztof,

                        This is the output that you requested:

                        /dev/mmcblk1p3 on / type ext4 (rw,relatime,data=ordered)

                        The Joule boot from the eMMC without issues, with or without the SD Card.

                        Let me research more about your issue, and I'm going to reply ou when we got something helpful.

                        Have a nice weekend.

                        Regards,
                        -Leonardo

                        • 9. Re: Problem with booting from the eMMC after image flashing
                          rosek

                          Thanks Leonardo, enjoy the weekend too.

                           

                          Regards,

                          Krzysztof

                          • 10. Re: Problem with booting from the eMMC after image flashing
                            Intel Corporation
                            This message was posted on behalf of Intel Corporation

                            Hi Krzysztof,

                            We were checking your issue, and we found that you are using firmware 131 which was released on September 23rd. Please try to update it to the latest firmware 161 released November 15th. Check this guide: https://software.intel.com/en-us/flashing-the-bios-on-joule

                            And this is the file:https://downloadmirror.intel.com/26206/eng/Joule_BIOS_2016-11-15-161-Public.zip

                            Let us know if you still have issues.

                            Regards,
                            -Leonardo

                            • 11. Re: Problem with booting from the eMMC after image flashing
                              rosek

                              Hi Leonardo,

                               

                              Please find attached putty log which shows exactly the same errors when Joule is flashed with the newest 161 firmware. Clearly something must be wrong with this particular module or development kit. For your information, we'd like to return the development kit and replace it with the new one. We have contacted Mouser here in Poland but it looks like they have to contact with Intel first. Hopefully it wouldn't take much time and we could get an replacement module very soon to continue our work.

                               

                              Thank you for your support and Best Wishes for the Holiday Season and a Happy New year.

                               

                              Kind regards,

                              Krzysztof

                              • 12. Re: Problem with booting from the eMMC after image flashing
                                Intel Corporation
                                This message was posted on behalf of Intel Corporation

                                Hi Krzysztof,

                                That's great, let's hope you will receive it soon.

                                Let us know if you have issues with it to assist you.

                                Happy holidays too.

                                Regards,
                                -Leonardo

                                • 13. Re: Problem with booting from the eMMC after image flashing
                                  Umesh@pro3

                                  hello rosek ,

                                                 im also facing the same issue with one intel joule board ,are you resolve that  issue??

                                                 i have posted query here Re: read only files