Reach module not working - solid magenta LED

[mikhail.avkhimenia (Mikhail)]

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.

[vclor (Victor Lorentzen)]

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.

[igor.vereninov]

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

[vclor (Victor Lorentzen)]

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

[igor.vereninov]

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

[vclor (Victor Lorentzen)]

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

[vclor (Victor Lorentzen)]

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)

[egor.fedorov]

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

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.

[vclor (Victor Lorentzen)]

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.

[vclor (Victor Lorentzen)]

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

[egor.fedorov]

This really looks like a power issue, can you try changing cable and/or power source?

[vclor (Victor Lorentzen)]

Figured it out.
It was the onboard usb port that causes the problem.
When i use the RFD900+ with the reach, it seems that the port is pushing against the limit for what it can deliver. This causes the reach to not get enough power and probably damaged the onboard usb in some way.
When i supply the reach with through one of the DF13 ports it works fine. (Using 2.0A usb charger or 2.0A powerbank).

btw, I do not run the RFD900+ at full power, it is running at 10mW.

[vclor (Victor Lorentzen)]

It seems that the usb port was not properly mounted. It is twisted by almost 1mm. This might be the ansver to what causes my problems.

[igor.vereninov]

Victor, it certainly does not look right. Was it like that when it arrived?

[vclor (Victor Lorentzen)]

Yes, it has been like this since i got the card. And i have had problems with this card since I first powered it on.

[igor.vereninov]

Could you please send me your order number via PM? We will arrange a replacement.

[ploedoff]

I am having the exact same symptoms with one of my Reach modules, except the mal-placed USB socket:

1. it does not finish booting, same color sequence (blue → magenta for several minutes → repeat about 5 times, then blue)

2. I tried powering it from USB and the connector. both cases behave similarly.

3. the unit does not respond at all when trying to flash the firmware via macOS and linux, using the GUI.

4. dmesg on linux looks as follows, repeating connect - disconnnect over and over:

   Apr 4 17:47:24 loki kernel: [14369.905945] usb 3-2: new high-speed USB device number 15 using xhci_hcd
   Apr 4 17:47:24 loki kernel: [14369.937141] usb 3-2: New USB device found, idVendor=8086, idProduct=e005
   Apr 4 17:47:24 loki kernel: [14369.937150] usb 3-2: New USB device strings: Mfr=2, Product=1, SerialNumber=3
   Apr 4 17:47:24 loki kernel: [14369.937154] usb 3-2: Product: MERRIFIELD
   Apr 4 17:47:24 loki kernel: [14369.937158] usb 3-2: Manufacturer: INTEL
   Apr 4 17:47:24 loki kernel: [14369.937161] usb 3-2: SerialNumber: 83C01E72819A0E8471B8FA3354388C92
   Apr 4 17:47:29 loki kernel: [14374.890867] usb 3-2: USB disconnect, device number 15
   Apr 4 17:47:30 loki kernel: [14375.793795] usb 3-2: new high-speed USB device number 16 using xhci_hcd
   Apr 4 17:47:30 loki kernel: [14375.825122] usb 3-2: New USB device found, idVendor=8086, idProduct=e005
   Apr 4 17:47:30 loki kernel: [14375.825130] usb 3-2: New USB device strings: Mfr=2, Product=1, SerialNumber=3
   Apr 4 17:47:30 loki kernel: [14375.825134] usb 3-2: Product: MERRIFIELD
   Apr 4 17:47:30 loki kernel: [14375.825137] usb 3-2: Manufacturer: INTEL
   Apr 4 17:47:30 loki kernel: [14375.825140] usb 3-2: SerialNumber: 83C01E72819A0E8471B8FA3354388C92
   Apr 4 17:47:30 loki kernel: [14375.845813] usb 3-2: USB disconnect, device number 16

5. When connecting the serial UART RX/TX, I can see the same behavior as vclor:

https://pastebin.com/EDqtFu8A

I have not been using the unit for several months / close to a year, I only ever tested it on arrival back then, where it worked. I don’t know what could have changed that.

Please let me know if there is anything i can do to unbrick my device, @igor.vereninov or @egor.fedorov.

[igor.vereninov]

@ploedoff Does the unit create Wi-FI hotspot? If it does, are you able to connect to it?

[ploedoff]

No, it never seems to boot enough for any interaction to become possible, including no wifi hotspot, no (external) wifi connection.

[savvy0816]

I have the exact same symptoms on the boot sequence however I am able to reflash it ok. I’m afraid it’s bricked? This unit has been kept in a 3D printed case since Day 1.

Reach won't boot, LED always magenta

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 flash…