(06-28-2021, 02:30 AM)danielt Wrote:(06-25-2021, 06:55 PM)Mpoint Wrote: Ok on line 2 https://pastebin.cl/6 You can see the PineTime that ends in MAC Address :CC which happens to be an unsealed unit, I have no problem with upload or pull command it works fine but as soon as I switch to sealed PineTime that ends in MAC Address :9B (line 15) then I am unable issue command` ./tools/wasptool --eval 'wasp.system.app.debug = True` (line 94) without errors. So the upload or pull command does not work for seal PineTime by default is it ?
Upload and pull work on all my sealed units OK. I can't actually think of any way that wasptool could distinguish between sealed and unsealed units.
The --device options need to be combined with the actions in the *same* command line. For example: ./tools/wasptool --device F5:E2:9C:A2:B0:9B --upload README.rst
Note that if you have been experimenting with tools like GadgetBridge or connecting to the sealed watch from any other device you may need to disable bluetooth on those devices to prevent them from connecting first. Rebooting the watch is also a good idea if you are having connectivity problems.
Mpoint:
I may have Isolated the problem It seems that my hcitool is either malfunctioning or there seem to be a ghost device with the same MAC address as my PineTime https://pastebin.cl/11 Is there a fix to this problem ?
Messages In This Thread |
Switching between two PineTime in Wasp-os - by Mpoint - 06-24-2021, 02:58 AM
RE: Switching between two PineTime in Wasp-os - by danielt - 06-24-2021, 03:07 AM
RE: Switching between two PineTime in Wasp-os - by Mpoint - 06-25-2021, 06:55 PM
RE: Switching between two PineTime in Wasp-os - by danielt - 06-28-2021, 02:30 AM
RE: Switching between two PineTime in Wasp-os - by Mpoint - 06-28-2021, 07:39 AM
|
Users browsing this thread: 2 Guest(s)