Firmware flash tool does not find reach module

[Charlie_Robinson]

I am trying to get my old reach modules up to date after sitting unused for a pretty long time.

Running windows 10, reach module on reachview v2.20.8, reach firmware flash tool v 1.4.1

When I run the tool, after selecting Reach Module, then connecting the Reach via USB, the tool sits at ‘Looking for Reach Module’ and never finds the device.

Thererfore I am unable to flash the latest firmware. Any advice would be great!

System report follows:

Simple system report

app version: 2.20.8-r0
'wifi_status, interface: wlan0':
- wifi_mode: wpa_supplicant
- ip: 192.168.8.110
  is_connected: true
  mac_address: 78:4b:87:ac:87:dd
  ssid: Beiwei
base mode:
  base coordinates:
    accumulation: '2'
    antenna offset:
      east: '0'
      north: '0'
      up: '0'
    coordinates:
    - '0'
    - '0'
    - '0'
    format: llh
    mode: single-and-hold
  output:
    enabled: true
    format: rtcm3
    path: serial://ttyMFD2:57600:8:n:1:off#rtcm3
    type: serial
  rtcm3 messages:
    '1002':
      enabled: true
      frequency: '1'
    '1006':
      enabled: true
      frequency: '0.1'
    '1008':
      enabled: false
      frequency: '1'
    '1010':
      enabled: true
      frequency: '1'
    '1019':
      enabled: false
      frequency: '1'
    '1020':
      enabled: false
      frequency: '1'
    '1097':
      enabled: false
      frequency: '1'
    '1107':
      enabled: false
      frequency: '1'
    '1117':
      enabled: false
      frequency: '1'
    '1127':
      enabled: false
      frequency: '1'
bluetooth:
  discoverable: false
  enabled: false
  pin: '***'
camera:
  duty cycle: 20
  enable: false
  period: 2
  polarity: true
correction input:
  input2:
    enabled: true
    format: rtcm3
    path: ttyMFD2:38400:8:n:1:off
    send position to base: 'off'
    type: serial
  input3:
    enabled: false
    format: rtcm3
    path: :9028
    type: tcpsvr
logging:
  base:
    format: RTCM3
    started: true
    version: null
  correction:
    format: RTCM3
    started: true
    version: null
  interval: 24
  overwrite: true
  raw:
    format: UBX
    started: true
    version: null
  solution:
    format: LLH
    started: true
    version: null
position output:
  output1:
    enabled: true
    format: erb
    path: ttyMFD2:38400:8:n:1:off
    type: serial
  output2:
    enabled: true
    format: llh
    path: :2013
    type: tcpsvr
  output3:
    enabled: true
    format: llh
    path: :2014
    type: tcpsvr
  output4:
    enabled: true
    format: llh
    path: :2015
    type: tcpsvr
rtk settings:
  elevation mask angle: '15'
  glonass ar mode: 'off'
  gps ar mode: fix-and-hold
  max horizontal acceleration: '1'
  max vertical acceleration: '1'
  positioning mode: kinematic
  positioning systems:
    compass: false
    galileo: true
    glonass: true
    gps: true
    qzs: true
    qzss: true
    sbas: true
  snr mask: '35'
  update rate: '1'

[timd1971]

I think you have to install the old Edison drivers first. Emlid DOCS seemed to have removed that information which leaves users with older Reach products with no longer supported Emlid chips at a loss.

You can search the community for Edison drivers to get them.

EDIT: Download Intel® Edison Configuration Tool

[polina.buriak]

Hey guys,

I just wanted to mention that we removed the drivers from the docs because you don’t need to additionally install them. Reach Flash Tool is capable of handling them.

Charlie @Charlie_Robinson, would it be possible to share the screenshot of the Device Manager with us? It’ll help us to see how your computer recognize the connected Reach Module.

[Charlie_Robinson]

Thanks - I tried both with and without the edison drivers, it didn’t make a difference.

[timd1971]

More reading. Only way I was successful to get flashed to firmware 26. USB-to-PC still does not work though.

Flashing Emlid Reach RS? (Intel Edison chip)

Hi @timd1971, We’ve just tested Reach Modules USB-to-PC connection on Windows, and it worked fine. So, the issues you experience are rather unexpected. Could you please email us at support@emlid.com with the Flasher logs? To access flasher logs, follow these steps: Press Win + R The Run window should appear Paste this string into the Run window: AppData\Local\Emlid\Reach Firmware Flash Tool\logs It should open the folder with flasher logs. Please zip the folder and send it in. Al…

M2 UsbtoPC

Hi wondering if someone can shed some light on a problem. Trying to connect my M2 usbtopc , when i goto windows settings to get the port number i can see reach M2 other a section “other devices” if i try to update the driver , just says it can’t find one. anyone got any ideas?

[ewen.mck]

Hi @Charlie_Robinson, I have just been through the process of flashing my old reach modules to firmware 26 on a win10 machine. To get USB-to-PC connection I needed to disable driver signatures and then install EdisonDriverSetup1.2.1 as per this thread Flashing Reach RS - Win10
The flashing tool then found the module and completed the update without issue.

[Charlie_Robinson]

HI Ewen, thanks very much. Unfortunately this doesn’t seem to work in my case. I sucessfully used the workaround to install the Edison drivers but the flash tool still doesn’t find the Reach module.

[timd1971]

Glad it worked for you. Yes, it is quite difficult, but only way I could find to do it.

[timd1971]

Maybe try a different USB port? Or if laptop, an external powered USB port? Or another PC?

[ewen.mck]

Hi Charlie, Sorry to hear you have not yet had success.
A couple more observations from my experience, note this is my first time using Reach modules so apologies if I am stating the obvious;

1. Installing Edisondrivers - Disabling driver signatures is a must per the previous post, I also then ran the setup in administrator mode to ensure the software had full access. during this setup you will get some warnings as windows detects the signature issues.
   If the install is successful, once you reboot the p.c and plug the reach module into a usb port, the device will be recognised and shown as an Edison device in device manager, if you still have RNDIS with exclamation mark then Edison drivers has not installed correctly.

2)I found that the flashtool must be started and be looking for a reach module before the module is plugged into the usb port, otherwise it will not be detected.

[timd1971]

@polina.buriak

I just wanted to mention that we removed the drivers from the docs because you don’t need to additionally install them. Reach Flash Tool is capable of handling them.

That would be great, but if the Reach Flash Tool cannot detect the device, then the problem persists. : /

[polina.buriak]

Hi Charlie,

Would it be possible to share the screenshot of the Ports section of the Device Manager as well?

We’re currently checking what can be triggering this issue.

[Charlie_Robinson]

device manager screenshot attached. Thanks very much!

[Charlie_Robinson]

Thanks Guido - I tried version 1.5.0 but unfortunately it still doesn’t work, I now get the message ‘launch failed. Try reinstalling the app’ when I try to connect the reach. Tried both with and without the edison drivers installed.

[timd1971]

Quite a mystery.

Especially trying to get a COM port created for USB-to-PC after finally getting it detected. Reach RS (non-plus Edison).

[polina.buriak]

Hi Charlie,

Thanks for the screenshot! Just to be sure, have you checked all USB ports of your PC?

[guido_sanchez]

Sad to hear that!

Have you tried another USB port or USB cable? I was able to update both of my Reach Modules to firmware version 26 following the steps I detailed on the forum post I created here

[Charlie_Robinson]

I have checked a few of the usb ports but not all, tried USB 2, usb 3/3.1 ports and a variety of cables. Can’t rule out usb port or cable issue I suppose, but nothing I have so far tried has worked. Thanks for the assistance!

[Charlie_Robinson]

Happy to report that uninstalling all the edison drivers, uninstalling the flash tool and rebooting then reinstalling worked! I’m not sure what exactly changed as I’m pretty sure that’s the process I followed on the first installation attempt, but all seems ok. Now to reflash my other modules Cheers!