Hi! I’m having trouble with a reach module. It boots and sets up a hotspot, and i can hook it up with my wifi using http://reach.local:5000, and I can get the IP and ping it.
I can see the wifi config via IP:5000 and I can also login via ssh.
- The reachView app doesn’t load (I know the correct IP and its up)
- I tried reflashing (using Intel Phone Flash tool, under win and Linux), but the devices not found.
With a second reach I have everything is working fine.
Boot led is:
short blue,
long magenta,
short off, white,
green
Chip is NEO-M8T-0-01,
firmware I don’t know, but outdated I assume
Hope there is some way to flash it anyway? Maybe not using Intel phone tool?
Thank you,
Johannes
Hi!
What happens if you go to the IP address?
Some browsers need to have http:// before the IP address to load it properly
Hi Egor,
thanks for the quick reply. I tested in Chrome and Firefox and also put the http:// mannualy.
I stillg et ERR_CONNECTION_REFUSED, while the wifi connection is up (IP:5000 gives device info)
I’m even more troubled by the fact that I can’t flash the reach… I’ll try the recovery option, but first need to compile xfstk for my linux version…
What exactly happens when you flash via command line? Do you follow the routine from the docs?
Yes I follow the docs.
I get a timeout after starting flashall, and pluggingin the device.
here the output from windows:
D:\landmapp\resources\ReachImage_v1.2\reach_image\reach_image>flashall.bat -v
Using U-boot target: edison-blankrndis
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Dfu device not found Timeout
Did you plug and reboot your board?
If yes, please try a recovery by calling this script with the --recovery option
I cannot reboot from the config, since ReachView doesn’t work, but the LED status indicates a booting sequence.
In intel tool, the devices don’t show up
It worked once before with a reach running an old firmware. now also this reach doen’t show up any more.
That’s a weird issue. The image should not affect device visibility?
What is your Windows version? Did you install the drivers? Does Edison show up as an external drive?
Can you try it using Linux?
On Linux similar. Output:
$ ./flashall.sh -v
Using U-Boot target: edison-blankcdc
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Timed out while waiting for dfu device 8087:0a99
DEBUG: lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 005: ID 04f2:b2ea Chicony Electronics Co., Ltd Integrated Camera [ThinkPad]
Bus 003 Device 004: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad]
Bus 003 Device 003: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode)
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
DEBUG: dfu-util -l
dfu-util 0.8
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org
Found Runtime: [0a5c:21e6] ver=0112, devnum=4, cfg=1, intf=3, alt=0, name="UNKNOWN", serial="C01885DD3C84"
Did you plug and reboot your board?
If yes, please try a recovery by calling this script with the --recovery option
and here the output from intel tool under linux:
04/13/16 15:22:19.255 INFO : Flash file ReachImage_v1.2/reach_image/reach_image/FlashEdison.json [RNDIS] loaded
04/13/16 15:22:20.614 INFO : Flash file ReachImage_v1.2/reach_image/reach_image/FlashEdison.json [CDC] loaded
04/13/16 15:22:20.615 INFO : Ready to flash!
04/13/16 15:22:25.088 INFO : [Port -1] Starting flash ...
04/13/16 15:22:25.088 INFO : [Port -1] Running `Notify` command
04/13/16 15:22:25.521 INFO : Displaying notification during 42000 ms
04/13/16 15:22:25.523 INFO : [Port -1] Command `Notify` succeed
04/13/16 15:22:25.523 INFO : [Port -1] Running `Wait for device with status dnx_fw on port -1` command
04/13/16 15:23:07.524 ERROR : [Port -1] Command `Wait for device with status dnx_fw on port -1` failed
04/13/16 15:23:07.524 ERROR : [Port -1] Flash failed (Command type: Device enumeration)
I see no reason why a Linux computer would not see Edison. Do you connect it via the USB cable with nothing on the DF13 connector?
Maybe, try switching the cable, or USB port? There also might be a chance USB 3.0(with a blue contact pad) does not work.
1 Like
Wow, ok, seems the USB cable was no good…
I connected to one of the devices succesfully (the one with the config page issue, but ReachView app accesabile… )
Flashing now… then i will test the device with no ReachView access…
Good. I was already getting worried 
Second reach also flashing… wow, just a stupid cable… (not the one you supplied btw)
Thanks!
