mier
commented
6 years ago Well after some investigations it clear that it is stuck in the upgrade mode. the dft-util state that -R (Reset)= shouldbe part of the command line. thus dfu-util -R -D firmware_X.dfu will update and reset back to normal mode.
So I have my pyTrack sheild back. Probably obvious for most people but for the rest like an update of the upgrade procedure for pytrack/pySense is in order. /ME
Please include the following information when submitting a bug report:
(Dev env on a ubuntu 16.04 machine. Using atom with pymakr plugin (latest available))
pyTrack with LoPy (Using it for a PoC that needs all power savings patches available...) (have 2 Lopy 1 pytrack and 1 pyExpboard)
Updated both LoPy to 1.7.9.b3 Updated pyTrack to 0.0.4 (using pytrack_0.0.4.dfu) All updates worked fine.
Both LoPY on pyExpBoard works (=connects to REPL in atom/pymaker) over serial (/dev/ttyUSB3) and on wifi.
But on pyTrack ....
Before shield update it turn up as /dev/ttyACM0 as expected (although I could for some reason not use that port (could be my env somehow) it complained about rst/dtr settings in dmesg..) wifi worked though which was enough for our purposes. (but really needed to get the new patches in to save power and some improvements on the LoRa layer (Counters - NVRAM helped.)
To issue started when I updated the sheild to 0.0.4. Then it will not come up as a serial device anymore... in dmesg: [158447.985265] usb 2-2: new full-speed USB device number 119 using xhci_hcd [158448.113748] usb 2-2: New USB device found, idVendor=04d8, idProduct=f014 [158448.113751] usb 2-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb-devices: T: Bus=02 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 76 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=fe(app. ) Sub=01 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=04d8 ProdID=f014 Rev=00.03 C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
No driver is found. (PIC16LF1459 say it should be ttyACMx)
WiFi is dead (comes to life if move to the pyExpboard)
and obviously installed program do not run....
so can't access it nor is anything starting ... bricked?
Is there any way of reverting the update via dfu-util of the pytrack shield? (or is there a other pytrack_0.0.X that works?)
Any ideas what went wrong?
/ME