Reach Module - Don't detected

davidrf · July 8, 2024, 6:03pm

I’m having problems with my reach module to connect to wifi. I accessed to the device with SSH and I saw that the /data filesystem was full, I also saw som errors with bluetooth, so I decided to reflash the device.

I installed the last versión of the reach firmware flash tool (1.11.1) and upgraded to the las version the tool offered to me, sorry I can’t remember what version was.

After install the new firmware, I lost all access to my device, I’m can’t detect the reach:xx:xx wifi.

I’m trying to reflash again and windows 11 is saying that don’t know the usb device.
This is the sequence of booting:

Plug the usb in the computer
4 seconds, leds off, error on windows “Don’t know device”
1 second, led white a few milleseconds
blue a few millseconds
purple and red 7 seconds (aprox)
blue a few milliseconds, error on windows “Don’t know device”
purple and red 7 seconds
leds off aprox 80 seconds
The sequence begins again

How can I revive the device?

inkar.madikyzy · July 9, 2024, 1:30pm

Hi @davidrf,

Let’s try powering up your Reach Module without reflashing it. What is the LED’s behavior? Do all the LEDs turn off again?

Please check if the LED blinks again after waiting a little longer, around 30-45 seconds after all the LEDs turn off.

davidrf · July 14, 2024, 5:58pm

I can’t reflash, the module isn’t detected.

The leds behavior are what I described in the first message, except, that after a long time, the led remain blue.

inkar.madikyzy · July 15, 2024, 8:25am

Hi @davidrf,

Blue LED means your Reach Module is connected to a known Wi-Fi network. Let’s try connecting to the Reach Module in Emlid Flow.

Since the device has no battery, you should connect the Raech Module to any USB power source to get power. It can be a power bank, wall adapter, or computer port.
Please wait until the LED turns blue once more. Then, connect your mobile phone to the same Wi-Fi network as the Reach module. This network might be from a nearby Wi-Fi router.
Open the Emlid Flow on your phone and check if the Reach Module will appear.

Thank you, and let me know how it goes.

davidrf · September 25, 2024, 8:50am

Hi. I tried what yo proposed, but I had no luck. I tried connecting the device to a linux debian and it’s keeps connecting and disconnecting. There’s the log on the dmesg:

[Sep25 10:42] usb 1-1: new high-speed USB device number 30 using xhci_hcd
[ +0.161439] usb 1-1: New USB device found, idVendor=8086, idProduct=e005, bcdDevice= 0.a0
[ +0.000014] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ +0.000007] usb 1-1: Product: MERRIFIELD
[ +0.000006] usb 1-1: Manufacturer: INTEL
[ +0.000004] usb 1-1: SerialNumber: 8B1745565F3F7_______4EDEE4__1831
[ +8.909813] usb 1-1: USB disconnect, device number 30
[ +0.936606] usb 1-1: new high-speed USB device number 31 using xhci_hcd
[ +0.165417] usb 1-1: New USB device found, idVendor=8086, idProduct=e005, bcdDevice= 0.a0
[ +0.000014] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ +0.000007] usb 1-1: Product: MERRIFIELD
[ +0.000005] usb 1-1: Manufacturer: INTEL
[ +0.000005] usb 1-1: SerialNumber: 8B1745565F3F7________4EDEE4__1831
[ +0.008651] usb 1-1: USB disconnect, device number 31
[ +2.045853] usb 1-1: new high-speed USB device number 32 using xhci_hcd
[ +0.149207] usb 1-1: New USB device found, idVendor=8087, idProduct=0a99, bcdDevice= 2.23
[ +0.000015] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000007] usb 1-1: Product: USB download gadget
[ +0.000005] usb 1-1: Manufacturer: Intel
[ +0.000005] usb 1-1: SerialNumber: c447679176e28_______ca6d851__b8d
[ +2.482598] usb 1-1: USB disconnect, device number 32

[Sep25 10:44] usb 1-1: new high-speed USB device number 33 using xhci_hcd
[ +0.161521] usb 1-1: New USB device found, idVendor=8086, idProduct=e005, bcdDevice= 0.a0
[ +0.000005] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ +0.000002] usb 1-1: Product: MERRIFIELD
[ +0.000002] usb 1-1: Manufacturer: INTEL
[ +0.000001] usb 1-1: SerialNumber: 8B1745565F3F7_______4EDEE4__1831
[ +8.909765] usb 1-1: USB disconnect, device number 33
[ +0.936724] usb 1-1: new high-speed USB device number 34 using xhci_hcd
[ +0.161346] usb 1-1: New USB device found, idVendor=8086, idProduct=e005, bcdDevice= 0.a0
[ +0.000015] usb 1-1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ +0.000007] usb 1-1: Product: MERRIFIELD
[ +0.000005] usb 1-1: Manufacturer: INTEL
[ +0.000005] usb 1-1: SerialNumber: 8B1745565F3F7_______4EDEE4__1831
[ +0.008819] usb 1-1: USB disconnect, device number 34
[ +2.041674] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[ +0.148951] usb 1-1: New USB device found, idVendor=8087, idProduct=0a99, bcdDevice= 2.23
[ +0.000014] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000007] usb 1-1: Product: USB download gadget
[ +0.000005] usb 1-1: Manufacturer: Intel
[ +0.000005] usb 1-1: SerialNumber: c447679176e28_______ca6d851__b8d
[ +2.488671] usb 1-1: USB disconnect, device number 35

davidrf · September 26, 2024, 6:11am

After a lot of tries, I have completed the firmware upgrade with a mac. Now I have access to the AP of the device but I can’t access to web interface. I’m able to log in by ssh and I can see that the filesystem / is filling:

Reach:~$ df -h
Filesystem      Size  Used Avail Use% Mounted on
none            473M  4.0K  473M   1% /dev
/dev/mmcblk0p6  704M  613M   38M  95% /
tmpfs           479M     0  479M   0% /dev/shm
tmpfs           479M  620K  478M   1% /run
tmpfs           479M     0  479M   0% /sys/fs/cgroup
tmpfs           479M  4.0K  479M   1% /tmp
tmpfs           479M     0  479M   0% /var/volatile
/dev/mmcblk0p5 1003K   19K  913K   3% /factory
/dev/mmcblk0p8  2.1G   59M  2.0G   3% /data
tmpfs            96M     0   96M   0% /run/user/1000

I can’t connect to my home wifi, I have this error:

[ WARNING] --- Wi-Fi interface is broken in runtime. Wireless interface available: True; MMC debugfs exists: False; Try to run quirk (monitor.py:405)

and a lot of kernel critical errors:

Dec  8 09:32:01 localhost user.crit kernel: [  565.327788] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #10724: comm python3: deleted inode referenced: 32779
Dec  8 09:32:01 localhost user.crit kernel: [  565.330478] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #10724: comm python3: deleted inode referenced: 32779
Dec  8 09:32:01 localhost user.crit kernel: [  565.616071] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #10724: comm python3: deleted inode referenced: 32779
Dec  8 09:32:01 localhost user.crit kernel: [  565.768079] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #10724: comm python3: deleted inode referenced: 32779
Dec  8 09:32:01 localhost user.crit kernel: [  565.771556] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #10724: comm python3: deleted inode referenced: 32779
Dec  8 09:32:02 localhost user.crit kernel: [  567.248377] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5392: comm python3: deleted inode referenced: 2268
Dec  8 09:32:03 localhost user.crit kernel: [  567.328787] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5392: comm python3: deleted inode referenced: 2268
Dec  8 09:32:03 localhost user.crit kernel: [  567.382661] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27653
Dec  8 09:32:03 localhost user.crit kernel: [  567.445578] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27653
Dec  8 09:32:03 localhost user.crit kernel: [  567.455921] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27654
Dec  8 09:32:06 localhost user.crit kernel: [  570.462081] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.465752] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.563160] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.565469] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.615334] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.617855] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.676309] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.678319] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.723686] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:06 localhost user.crit kernel: [  570.731724] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #2252: comm (imesyncd): deleted inode referenced: 27655
Dec  8 09:32:11 localhost user.crit kernel: [  575.492228] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27657
Dec  8 09:32:11 localhost user.crit kernel: [  575.570737] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27660
Dec  8 09:32:11 localhost user.crit kernel: [  575.613204] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 27660
Dec  8 09:32:11 localhost user.crit kernel: [  575.642394] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 2762
Dec  8 09:32:11 localhost user.crit kernel: [  575.725034] EXT4-fs error (device mmcblk0p6): ext4_lookup:1578: inode #5798: comm python3: deleted inode referenced: 2762

There is something I can do to restore the device in normal operation?

inkar.madikyzy · September 26, 2024, 9:37am

Hi David,

I received your email and have replied here. Could you please check it? From what you mentioned, the Reach module can connect to a mobile hotspot but not to the Wi-Fi network.

Let’s continue our conversation via email to keep everything in one place. Thank you!