LoPy does not start any more (crash or dead?)
-
I used to see /dev/cu.usbmodemPy343431 and everything was working fine.
Then I disconnected my pycom (I think a program was running from Atom in the REPL).
When I plug it again, I don't see /dev/cu.usbmodemPy343431 any more. The led light is also not blinking anymore and Atom fails to connect as well.I tried with another laptop and it is the same problem (nothign in /dev/)
It is my pycom already dead or is it rather a boot problem?
I hope it is only a boot problem.
Any help is welcome.ps: I'm using a macbook pro.
-
@jmarcelino Thank you!!! you saved my day, it works!
-
@pschaus
It may be worth at least trying to do a firmware upgrade on your PyTrack: https://docs.pycom.io/chapter/pytrackpysense/installation/firmware.html
-
Thank you for your help @jmarcelino I see nothing with the PyTrack only. It thus seems to be defective. Disappointing, it only worked for a couple of hours ... Thank you for your help
-
@pschaus
You can try connecting just the PyTrack board without the LoPy mounted on it.The /dev/tty.usbmodemPy* device should still appear that way. If not and you've tried different cables etc then your PyTrack may be damaged/defective.
-
@jmarcelino Unfortunately it is not a USB problem. Yes I tried another cable, another laptop as well. I'm using the pytrack
-
@pschaus
Sounds more like a USB problem (the USB device appearing in /dev/ and the LoPy itself working are mostly independent things)I'd suggest trying another microUSB cable first.
Also what are you using to communicate with the LoPy, is it the PySense or PyTrack?