Reach module not working - solid magenta LED

Reach Module / M+ / M2 Getting started
21

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

22

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.

23

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.

DSC_0524.JPG3840×2160 2.58 MB

24

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

25

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.

26

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

27

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.

28

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

29

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

30

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.