Announcement

Collapse
No announcement yet.

Backdoor / recovery

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Backdoor / recovery

    Device: XPP1002000-02R (Evolution OS).
    Update process with ftp client.


    We have a small number of devices that bite the dust after a firmware update. The update process via ftp was normal (regarding the syslog output). But the device did not manage to reboot after the image has been transferred to the flash.

    These devices do not send any ethernet frames (e.g. DHCP discover) and no serial char. Recovery with DeviceInstaller fails (does not discover the XPP within the timeout). The backdoor mechanism does not work, too (no response to '!' at 9600 8N1).

    The green LED is on for a period of about 4 seconds and then off for about 1 or 2 seconds. This behaviour repeats while the device is powered. We checked the power supply and the serial lines.

    These small number of devices got exactly the same firmware like all the other devices that work after the firmware update process.

    Is there another way to recover these devices (tomc wrote, that the boot code is always available: http://forums.lantronix.com/showpost...70&postcount=3)?

  • #2
    Originally posted by TESK View Post
    Device: XPP1002000-02R (Evolution OS).
    Update process with ftp client.


    We have a small number of devices that bite the dust after a firmware update. The update process via ftp was normal (regarding the syslog output). But the device did not manage to reboot after the image has been transferred to the flash.

    These devices do not send any ethernet frames (e.g. DHCP discover) and no serial char. Recovery with DeviceInstaller fails (does not discover the XPP within the timeout). The backdoor mechanism does not work, too (no response to '!' at 9600 8N1).

    The green LED is on for a period of about 4 seconds and then off for about 1 or 2 seconds. This behaviour repeats while the device is powered. We checked the power supply and the serial lines.

    These small number of devices got exactly the same firmware like all the other devices that work after the firmware update process.

    Is there another way to recover these devices (tomc wrote, that the boot code is always available: http://forums.lantronix.com/showpost...70&postcount=3)?
    I have had this bootloop problem with failed firmware updates also. It is concerning to say the least, and I haven't found a pattern. However, in my cases, using the serial recovery has worked in the past. Are you sure you have it connected properly, and are using a NULL modem cable? I found that to be the trick for the serial recover to work from Device Installer.

    Comment


    • #3
      There are two different "bootloop problems" for the devices. I checked the connection several times and also measured the signals at the pins of the XPP.

      For the one "bootloop problem", the XPP can be recovered with DeviceInstaller. So it is also possible to do the trick with the backdoor mechanism ('!'). I think, the period of time to the next reboot is longer and therefore sufficient for the backdoor mechanism.

      But there seems to be another "bootloop problem". We have about 10 devices that cannot be recovered. The period of time from reset to reset is about 5 to 6 seconds. I am interested in the cause of this problem and how to fix these devices. Has anybody seen this problem? Is there another possibility to read and check the bootloader?

      Comment


      • #4
        I just had a device come back from the field that was recently shipped to the client. It "bootloops" and I can't recover it. The green LED comes on for maybe 2 seconds, then off, in a perpetual cycle. Sounds like this one is completely dead.

        Comment


        • #5
          Are these new devices? XPP I assume?
          Where are you physically located? Might need your FAE involved on this one; because devices should always be recoverable from Device Installer.

          Comment


          • #6
            Originally posted by garry0427 View Post
            Are these new devices? XPP I assume?
            Where are you physically located? Might need your FAE involved on this one; because devices should always be recoverable from Device Installer.
            It is an XPP. It is a new device that worked when it left our office. Upon receipt, the client attempted to commission it, and reported that they could not get ethernet connectivity and that the green LED kept turning on/off. I RMA'd the equipment.

            I received the product back. I have seen "bootloops" before, but in most cases the bootoop cycle is 6-10 seconds, and is recoverable via DeviceInstaller. For this one I can't get to recover via DI at all. I have removed it from our product and also tried using the DEV board with the same result.

            In fairness, I'm not sure how this product was handled, perhaps it was static, etc that damaged it, but I have not seen this failure mode before. It was out of a batch of 50 units which two units were completely DOA from the factory packaging, so I am getting a little concerned.

            We are in Ontario, Canada.

            Comment


            • #7
              If you have non-working units that are under warranty, please contact the distributor through which you bought them to arrange an RMA.

              Comment

              Working...
              X