Unable to flash the edison

[EHube]

I am unable to flash the edison using any method I have found on the internet. This includes the flash tool and flashall.bat. I believe my problem has something to do with the USB0 interface being missing from my interfaces. It was there before. I have no idea how to enable it once again.

root@Edison:~# ifconfig

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:1837 errors:0 dropped:0 overruns:0 frame:0

TX packets:1837 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:133490 (130.3 KiB) TX bytes:133490 (130.3 KiB)

wlan0 Link encap:Ethernet HWaddr fc:c2:de:30:02:df

inet6 addr: fe80::fec2:deff:fe30:2df/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:3210 errors:0 dropped:0 overruns:0 frame:0

TX packets:385 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:163882 (160.0 KiB) TX bytes:54652 (53.3 KiB)

root@Edison:~# ifup usb0

ifup: can't open '/etc/network/interfaces': No such file or directory

This all started after I did a okpg update/okpg upgrade (or was it apt-get update/apt-get upgrade.)

How do I get my board to flash if I have already tried flashall.bat and the flash tool with no success?

[EHube]

I am able to sftp to the board to transfer files. Is there perhaps a way to transfer something to the board and flash the system? If so, on what partition do I put the files?

[Sergio_A_Intel]

Hi,

The command ifup won't work on the Edison. To configure and connect to a network you should use configure_edison –wifi. Try this approach to connect to a network. In what position do you have SW1? Make sure the switch is closest to the micro USB port and not to the USB port.

What was the issue with the flash tool lite method? Did you receive an error during the flashing process or did it never start? If you received an error what was the complete error log?

What about the flashall, what error did you receive? What image do you have right now and what image are you trying to flash to? What OS do you have on your computer?

Sergio

[EHube]

The USB network isn't up. I am able to connect via wifi

root@Edison:~# configure_edison --version

159

root@Edison:~# uname -a

Linux Edison 3.10.17-poky-edison+ # 1 SMP PREEMPT Fri Jun 19 12:06:40 CEST 2015 i686 GNU/Linux

root@Edison:~# ifconfig

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:26 errors:0 dropped:0 overruns:0 frame:0

TX packets:26 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:2138 (2.0 KiB) TX bytes:2138 (2.0 KiB)

wlan0 Link encap:Ethernet HWaddr fc:c2:de:30:02:df

inet addr:192.168.0.14 Bcast:192.168.0.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1612 errors:0 dropped:0 overruns:0 frame:0

TX packets:859 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:207216 (202.3 KiB) TX bytes:96225 (93.9 KiB)

sw1 is towards the smaller usb (micro usb)

I tried edison-iotdk-image-280915.zip and edison-image-ww25.5-15.zip

root@Edison:~# dmesg

[ 0.000000] Initializing cgroup subsys cpuset

[ 0.000000] Initializing cgroup subsys cpu

[ 0.000000] Initializing cgroup subsys cpuacct

[ 0.000000] Linux version 3.10.17-poky-edison+ (sys_dswci@tlsndgbuild004) (gcc version 4.9.1 (GCC) ) # 1 SMP PREEMPT Fri Jun 19 12:06:40 CEST 2015

[ 0.000000] e820: BIOS-provided physical RAM map:

[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000097fff] usable

[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable

[ 0.000000] BIOS-e820: [mem 0x0000000004000000-0x0000000005ffffff] reserved

[ 0.000000] BIOS-e820: [mem 0x0000000006000000-0x000000003f4fffff] usable

[ 0.000000] BIOS-e820: [mem 0x000000003f500000-0x000000003fffffff] reserved

[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved

[ 0.000000] BIOS-e820: [mem 0x00000000fec04000-0x00000000fec07fff] reserved

[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved

[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved

[ 0.000000] NX (Execute Disable) protection: active

[ 0.000000] SMBIOS 2.6 present.

[ 0.000000] DMI: Intel Corporation Merrifield/BODEGA BAY, BIOS 542 2015.01.21:18.19.48

[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved

[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable

[ 0.000000] e820: last_pfn = 0x3f500 max_arch_pfn = 0x1000000

[ 0.000000] MTRR default type: uncachable

[ 0.000000] MTRR fixed ranges enabled:

[ 0.000000] 00000-9FFFF write-back

[ 0.000000] A0000-BFFFF uncachable

[ 0.000000] C0000-FFFFF write-back

[ 0.000000] MTRR variable ranges enabled:

[ 0.000000] 0 base 000000000 mask FC0000000 write-back

[ 0.000000] 1 base 03F600000 mask FFFE00000 uncachable

[ 0.000000] 2 base 03F800000 mask FFF800000 uncachable

[ 0.000000] 3 base 004000000 mask FFE000000 uncachable

[ 0.000000] 4 disabled

[ 0.000000] 5 disabled

[ 0.000000] 6 disabled

[ 0.000000] 7 disabled

[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106

[ 0.000000] original variable MTRRs

[ 0.000000] reg 0, base: 0GB, range: 1GB, type WB

[ 0.000000] reg 1, base: 1014MB, range: 2MB, type UC

[ 0.000000] reg 2, base: 1016MB, range: 8MB, type UC

[ 0.000000] reg 3, base: 64MB, range: 32MB, type UC

[ 0.000000] total RAM covered: 982M

[ 0.000000] Found optimal setting for mtrr clean up

[ 0.000000] gran_size: 64K chunk_size: 512M num_reg: 5 lose cover RAM: 0G

[ 0.000000] New variable MTRRs

[ 0.000000] reg 0, base: 0GB, range: 512MB, type WB

[ 0.000000] reg 1, base: 64MB, range: 32MB, type UC

[ 0.000000] reg 2, base: 512MB, range: 512MB, type WB

[ 0.000000] reg 3, base: 1014MB, range: 2MB, type UC

[ 0.000000] reg 4, base: 1016MB, range: 8MB, type UC

[ 0.000000] e820: update [mem 0x04000000-0x05ffffff] usable ==> reserved

[ 0.000000] initial memory mapped: [mem 0x00000000-0x023fffff]

[ 0.000000] Base memory trampoline at [c0094000] 94000 size 16384

[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]

[ 0.000000] [mem 0x00000000-0x000fffff] page 4k

[ 0.000000] init_memory_mapping: [mem 0x37800000-0x379fffff]

[ 0.000000] [mem 0x37800000-0x379fffff] page 2M

[ 0.000000] init_memory_mapping: [mem 0x34000000-0x377fffff]

[ 0.000000] [mem 0x34000000-0x377fffff] page 2M

[ 0.000000] init_memory_mapping: [mem 0x00100000-0x03ffffff]

[ 0.000000] [mem 0x00100000-0x001fffff] page 4k

[ 0.000000] [mem 0x00200000-0x03ffffff] page 2M

[ 0.000000] init_memory_mapping: [mem 0x06000000-0x33ffffff]

[ 0.000000] [mem 0x06000000-0x33ffffff] page 2M

[ 0.000000] init_memory_mapping: [mem 0x37a00000-0x37bfdfff]

[ 0.000000] [mem 0x37a00000-0x37bfdfff] page 4k

[ 0.000000] BRK [0x01e27000, 0x01e27fff] PGTABLE

[ 0.000000] 121MB HIGHMEM available.

[ 0.000000] 891MB LOWMEM available.

[ 0.000000] mapped low ram: 0 - 37bfe000

[ 0.000000] low ram: 0 - 37bfe000

[ 0.000000] BRK [0x01e28000, 0x01e28fff] PGTABLE

[ 0.000000] Zone ranges:

[ 0.000000] DMA [mem 0x00001000-0x00ffffff]

[ 0.000000] Normal [mem 0x01000000-0x37bfdfff]

[ 0.000000] HighMem [mem 0x37bfe000-0x3f4fffff]

[ 0.000000] Movable zone start for each node

[ 0.000000] Early memory node ranges

[ 0.000000] node 0: [mem 0x00001000-0x00097fff]

[ 0.000000] node 0: [mem 0x00100000-0x03ffffff]

[ 0.000000] node 0: [mem 0x06000000-0x3f4fffff]

[ 0.000000] On node 0 totalpages: 251031

[ 0.000000] free_area_init_node: node 0, pgdat c1c59e40, node_mem_map f740e020

[ 0.000000] DMA zone: 32 pages used for memmap

[ 0.000000] DMA zone: 0 pages reserved

[ 0.000000] DMA zone: 3991 pages, LIFO batch:0

[ 0.000000] Normal zone: 1752 pages used for memmap

[ 0.000000] Normal zone: 216062 pages, LIFO ba...

[EHube]

root@Edison:~# systemctl status systemd-modules-load.service -l

● systemd-modules-load.service - Load Kernel Modules

Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static)

Active: failed (Result: exit-code) since Sat 2000-01-01 00:00:21 UTC; 15 years 10 months ago

Docs: man:systemd-modules-load.service(8)

man:modules-load.d(5)

Process: 103 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

Main PID: 103 (code=exited, status=1/FAILURE)

Jan 01 00:00:21 Edison systemd-modules-load[103]: Inserted module 'bcm4334x'

Jan 01 00:00:21 Edison systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE

Jan 01 00:00:21 Edison systemd[1]: Failed to start Load Kernel Modules.

Jan 01 00:00:21 Edison systemd[1]: Unit systemd-modules-load.service entered failed state.

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

All I care about is to wipe this edison and start from scratch.

[EHube]

I swear the problem is that the RNDIS over USB0 is not enabled. I neither know how to enable it nor how it became disabled. My project is rather stuck until we can get around this problem. Is there a flash method which does not use RNDIS to transfer files to the board? All I care about is to wipe this edison and start from scratch.

[Sergio_A_Intel]

Hi,

You can also see this thread Irakandjii let us know your results.

Sergio

[EHube]

@ Irakandjii Thanks for the suggestion. I had both usb 2 and 3 on here. It was plugged into the 3.0 ports. I switch both the console and otg ports to the 2.0 and no go. I was able to flash via the usb 3.0 ports before. Who knew if it would fix it. It was worth a try.

@ Intel_Alvarado

it used to flash and it used to show up as a drive. Now it is not. The USB0 RNDIS interface is now missing on the device (which I believe the RNDIS flash method uses). The only way to use the --recovery method from flashall.bat appears to be this fstk program which I am only able to find in unix flavor. Is there a windows version? Is there a way to get USB0 up so RNDIS will work and I may flash? Either of these appear to be a logical approach.

[EHube]

Are there any more ideas from Intel on this? Perhaps there is a windows version of the xfstk tools? This may flash the board using flashall --recovery. Thus far the only links I have found have been for unix.

[Sergio_A_Intel]

Hi,

The only available procedure to build the xfstk is for Linux. You can find it in this link . I'm not aware of anyone in the community building the xfstk in Windows. Have you tried to flash your Edison using another computer and with an external power supply?

Sergio

[RElli7]

Hi I had a heck of a time with this a few weeks ago. I solved the problem by ensuring I was using a USB 2.0 port on the PC .. buried in the intel Edison documentation it tells you this.

It was a real pain because I had no available USB 2.0's on the outside of the case. So I needed an adapter and bracket to run one from the motherboard to the case.

I was told that using a USB Hub with usb 2.0 ports would work, but that was not true in my case.

[Jose_N_Intel]

I still believe Intel's is making a huge mistake by not making sure normal configure_edison mechanism to flash and upgrade properly works on latest versions of the firmware. Or even the reboot ota method... what happened to backwards compatibility value???

A huge mistake.

[Sergio_A_Intel]

Thank you for your feedback. We have passed it to the appropriate team.

Sergio

[EHube]

I do not have a computer running Ubuntu. I made an attempt to use the only other thing at my disposal which was a raspberry pi but things did not install correctly. There must be an easier solution to this than to buy a new computer and install Ubuntu in order to flash an Edison one time.

[Sergio_A_Intel]

Please fill a form in http://www.intel.com/support/mailform/maker/edisonwarrantyemail.htm Intel Support . We'd like to take a closer look to your case.

Sergio

[EHube]

I finally got it to work. I uninstalled every single driver intel had on my system. Usb driver, Dnx driver, FTDI driver, iot kit, etc etc. I started over from scratch. I downloaded the 64 bit software and installed only the flash tool and drivers. I ran the flash tool and no problems at all. I have to assume something got corrupted somewhere in my driver stack. The odd thing is it worked on a different edison just a few days ago. I also did notice that for some reason every time I plugged in the edison windows said it was installing new hardware. I found this rather odd and possibly related to the issue.