I have owned two Reach units for the past couple years. I have gone through all the upgrades for ReachView, etc with minimal issue. I had stability problems since the most recent upgrade and decided to reflash (one of the units). I reflashed with image 2.3, 2.4, and even tried 1.2. The flash appears to complete 100% successfully per the terminal output. I’ve done flashing in the past and periodically had to reflash but always ultimately succeeded. I flash from an Ubuntu terminal with flashall.sh and tried the GUI. Both approaches shows 100% successful flash. This time, my Reach device is “stuck” in the magenta signal state and never proceeds past it. I get no wifi hotspot. I tried different USB cables including the one that ships with Reach. I separated the Edison from Reach and remounted, no difference.
So, when you plug Reach into your Ubuntu box, does syslog report anything? Does is create a USB over ethernet interface appearing as usb0 or enxXXXXXXX ? tail -f /var/log/syslog CTRL-C when done sudo ifconfig -a
I’ve been at this point before, and I’ve found it was easier to flash again than troubleshoot.
But if you’ve already flashed 2 or three times and it still behaves the same, then I would be wondering about the integrity of the downloaded image. I just downloaded a fresh copy and this is my checksum:
Reflashed 2.3 using the flashall.bat method once again. Now I can no longer access the normal application . It always goes directly to the update application.
I tried to do 192.168.2.15:80 it goes directly to the updater
@igor.vereninov, @egor.fedorov Do you have any recommendations? I’m disappointed if my Reach is bricked as it’s been used in an indoor environment as a base station always inside its case.
