-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device unable to start(10) #19
Comments
@adithya003 , can your Duo enter Safe Mode? Please have it a try and then upload a known valid user application via Particle Build or Arduino IDE. After that if it works, then the factory reset application may be broken, you have to update it using dfu-util: |
My device is not being listed in the PORT of the arduino IDE. |
How did you make your Duo enter Safe Mode? It should be:
In Safe Mode, your Duo will try to connect to the Particle cloud, but if you haven't stored any WiFi credentials, it will enter Listen Mode (i.e. RGB blinking blue) first to allow you configure an credential. Regarding to the driver issue, the driver files may be broken. You can download the origin files here (the .cat and .inf): |
This is the result which i am getting when i try to enter into the safe mode. |
I see. Please follow the following link (Back to factory default state) to recover your Duo: http://discuss.redbear.cc/t/general-recovery-of-the-duo-from-stuck-state/216 |
Under the first step of the factory reset which was mentioned in the given link i downloaded the STM32 ST-LINK util application and followed all the steps when i click connect it says me not detected. |
I did factory reset to the device. I released the setup button when the green light was blinking after that i the device is constantly blinking white light for every 5 seconds and i cannot see the device in any port under my laptop.
I tried to install driver again using the DFU mode but still i am getting the same issue how to fix this problem
Is my device broken?? else is their any solution
Thanks in advance
The text was updated successfully, but these errors were encountered: