Reach module not working - solid magenta LED

Hello all,

I unboxed my reach module today, expecting to do some field tests but I am unable to get the reach module to work. I am a geologist/GIS analyst, so I’m no stranger to this sort of technical work, but I am at a tough spot here.

Before I put power to the unit, I was careful to read all of the quick start instructions so I wouldn’t screw anything up. Sure enough, halfway through trying to disable the wifi on the module/add it to my wireless network, my network connection failed - causing the setup to be incomplete. I spent some time trying to get reconnected to the reach’s wireless network to start over, but it was already disabled. At this point, I thought the best course of action was to reflash the unit so I could basically start over.

I followed the directions on the “firmware reflashing” documents page, being careful to make sure all drivers were installed correctly (I am using Windows 7). Unfortunately, during the reflash, it only made it to about 27% and it had an error and stopped. At this point, I tried again several times with the same results. I unistalled then reinstalled all of the drivers/programs to perform the reflash, and gave it another go. When I tried to plug the unit back into my computer, I noticed a solid magenta light (where it was flashing blue and red earlier in the day) that presisted for about 30 min. I tried to run the reflash procedure again on the freshly reinstalled drivers/programs and the reach unit was not recognized by my computer, so the procedure couldn’t be started. When I plug the unit into my power supply, I only get the solid magenta LED (turned it off after 5 minutes).

I was under the impression that the magenta LED was a sign of the unit booting? The first time I fired it up, it showed magenta for a few seconds then went through some other colors…

Where should I go from here if I can’t communicate with the reach unit being plugged into my computer and I can’t communicate with it over wireless?

PS I have a single Reach module and the supplied Tallysman antenna with the intention of post correcting collected survey points in RTKLIB - my goal is to be able to survey ground control points for UAV surveys, so real time accuracy isn’t a huge concern at this point.

Thanks for your help,
Chad

Hello, Chad!

Could you try using a different usb cable? Also, do you have a different computer available to try reflashing?
Unfortunately, we have some problems reflashing with Windows 7.

I’ve read about the issues with reflashing using Windows 7 - unfortunately, I don’t have access to a computer with a different operating system. I did, however try a different USB cable on a different (albeit Windows 7) machine, and could not communicate with the unit, and still had the persistent magenta LED.

Any ideas? I would really like to use this unit for surveying.

Thanks!

Could you try flashing via command line?

It might work better.

Solid magenta wasn’t bad in my experience (I don’t know exactly what it means). I simply waited long enough and it passed through on its own.

Solid red, however, was bad and didn’t pass on its own.

Are there instructions on how to flash via command line? I’m not really familiar with how to do that, I apologize for my lack of skills.

No need to apologize, it’s our fault.

Here is the full description, including the command line routine.

I was able to reflash the module using a different (windows 7) computer, without having to use the command line routine. I am not tracking satellites in Single mode (no base module). Looking forward to getting my settings correct so I can post correct points in rtklib!

Great! Don’t hesitate to share your results or report any problems.

Hi,

I am experiencing the same problem with one of my reach modules,
Here is what i managed to read on the uart output.
The reach stops for a little while, then tries to read the registers again, but gets the same error message.
I have tried to reflash the module with success 3-4 times, but the error persists.


PSH KERNEL VERSION: b0182b2b
WR: 20104000


SCU IPC: 0x800000d0 0xfffce92c

PSH miaHOB version: TNG.B0.VVBD.0000000c

microkernel built 11:24:08 Feb 5 2015

******* PSH loader *******
PCM page cache size = 192 KB
Cache Constraint = 0 Pages
Arming IPC driver …
Adding page store pool …
PagestoreAddr(IMR Start Address) = 0x04899000
pageStoreSize(IMR Size) = 0x00080000

*** Ready to receive application ***
[ 0.766271] pca953x 1-0020: failed reading register
[ 0.791379] pca953x 1-0021: failed reading register
[ 0.816441] pca953x 1-0022: failed reading register
[ 0.841557] pca953x 1-0023: failed reading register

Is the reach module done for or is there something i could do?

Regards,

This pca953x error message is irrelevant as it is related to Intel Edison dev board hardware.
We do not use this chip on Reach, so this message is displayed because there is no chip but the driver expects it.
Will be removed in the next version of image.

The chip never boots past this message, it is stuck with the magenta color on the LED and goes into a “reeboot” state.
That message is the only thing showing up, it will not set up wifi or boot past the initial sequence.

The UART output on boot is disabled after a few messages so that it does not disturb radios. Does it constantly reboot itself?

Yes, it boots itself 6-7 times, then it is stuck on the blue LED and will not go past that.

How is it powered? Which OS/method did you use to reflash it?

It is powered with 2A usb charger. Win 8.1 pro, reflashed with intel edison gui and terminal. Both flash methods aparantly works.

Flash log:

04/11/16 14:00:56.070 INFO : [Port 2/12] XFSTK-STATUS–Detecting Intel Device - Attempt #0
04/11/16 14:00:56.070 INFO : [Port 2/12] Qt: Untested Windows version 6.3 detected!
04/11/16 14:00:57.202 INFO : [Port 2/12] …XFSTK-LOG–virtual bool MerrifieldDownloader::SetDevice(IGenericDevice*)
04/11/16 14:00:57.202 INFO : [Port 2/12] Initiating download…
04/11/16 14:00:57.203 INFO : [Port 2/12] XFSTK-STATUS–FW(Miscdnx) download is in progress …
04/11/16 14:00:57.203 INFO : [Port 2/12] XFSTK-STATUS–FW: Sending DnX DCFI00 …
04/11/16 14:01:00.026 INFO : [Port 2/12] XFSTK-STATUS–Error Code: 0 - Success
04/11/16 14:01:00.026 INFO : [Port 2/12] XFSTK-STATUS–Firmware download completed. Continuing to OS…
04/11/16 14:01:10.387 INFO : [Port 2/12] XFSTK-STATUS–Reconnecting to device - Attempt #1
04/11/16 14:01:11.075 INFO : [Port 2/12] XFSTK-STATUS–POS download is in progress …
04/11/16 14:01:14.288 INFO : [Port 2/12] XFSTK-STATUS–Error Code: 0 - Success
04/11/16 14:01:14.288 INFO : [Port 2/12] XFSTK-STATUS–Firmware and OS download completed.
04/11/16 14:01:14.288 INFO : [Port 2/12] XFSTK: Transfer Completed Successfully.
04/11/16 14:01:14.288 INFO : [Port 2/12] Success: Download of FW Completed.
04/11/16 14:01:14.288 INFO : [Port 2/12] xfstkFlashTool exited with success
04/11/16 14:01:14.288 INFO : [Port 2/12] Command "xfstkFlashTool.exe" "-1" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison_dnx_fwr.bin" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison_ifwi-dbg-00.bin" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison_dnx_osr.bin" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-edison.img" "0x80000007" "none" "none" "0" succeed
04/11/16 14:01:14.288 INFO : [Port 2/12] Running Wait for device with status pos on port 2/12 command
04/11/16 14:01:28.721 INFO : [Port 2/12] Command Wait for device with status pos on port 2/12 succeed
04/11/16 14:01:28.721 INFO : [Port 2/12] Running "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot0" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-edison.bin" "-t" "4096" "-d" "8087:0a99" command
04/11/16 14:01:29.815 INFO : [Port 2/12] Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot0" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-edison.bin" "-t" "4096" "-d" "8087:0a99" succeed
04/11/16 14:01:29.815 INFO : [Port 2/12] Running "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env0" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-d" "8087:0a99" command
04/11/16 14:01:30.862 INFO : [Port 2/12] Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env0" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-d" "8087:0a99" succeed
04/11/16 14:01:30.862 INFO : [Port 2/12] Running "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env1" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-R" "-d" "8087:0a99" command
04/11/16 14:01:31.956 INFO : [Port 2/12] Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "u-boot-env1" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\u-boot-envs\edison-blankrndis.bin" "-t" "4096" "-R" "-d" "8087:0a99" succeed
04/11/16 14:01:31.956 INFO : [Port 2/12] Running Sleeping for 6 seconds command
04/11/16 14:01:37.957 INFO : [Port 2/12] Command Sleeping for 6 seconds succeed
04/11/16 14:01:37.957 INFO : [Port 2/12] Running Wait for device with status pos on port 2/12 command
04/11/16 14:01:46.227 INFO : [Port 2/12] Command Wait for device with status pos on port 2/12 succeed
04/11/16 14:01:46.227 INFO : [Port 2/12] Running "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "boot" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison-image-edison.hddimg" "-t" "4096" "-d" "8087:0a99" command
04/11/16 14:01:48.477 INFO : [Port 2/12] Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "boot" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison-image-edison.hddimg" "-t" "4096" "-d" "8087:0a99" succeed
04/11/16 14:01:48.477 INFO : [Port 2/12] Running "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "rootfs" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison-image-edison.ext4" "-t" "4096" "-R" "-d" "8087:0a99" command
04/11/16 14:04:58.620 INFO : [Port 2/12] Command "C:\Program Files (x86)\Intel\Platform Flash Tool Lite\dfu-util.exe" "--alt" "rootfs" "-D" "C:\Users\Victor Lorentzen\Downloads\ReachImage_v1.2\reach_image\reach_image\edison-image-edison.ext4" "-t" "4096" "-R" "-d" "8087:0a99" succeed
04/11/16 14:04:58.620 INFO : [Port 2/12] Running Notify command
04/11/16 14:04:58.656 INFO : Displaying notification during 60000 ms
04/11/16 14:04:58.674 INFO : [Port 2/12] Command Notify succeed
04/11/16 14:04:58.674 INFO : [Port 2/12] Flash success (duration=00:04:11.551)

Hi!

What exactly do you mean by 6-7 times? Also, could you please post here the LED color sequence during boot?

Should be magenta during boot, then off for a second, white for a second, yellow blinking while looking for networks, then the normal sequence.

Boot sequence:
Blue -> off -> blue -> magenta flashes two times -> solid magenta for 5-10 min -> repeat

The reason i believe it boots several times is because i listened to the UART output, the message was repeating itself 6-7 times before UART was disabled.

After a while it goes into a state where the LED is solid blue.