Community gathering point for Google Coral dev board and dongle knowledge.
109
stars
14
forks
source link
It looks like you're trying to connect to a device that isn't connected to your workstation via USB and doesn't have the SSH key this MDT generated. Issue on Mac #91
It looks like you're trying to connect to a device that isn't connected
to your workstation via USB and doesn't have the SSH key this MDT generated.
To connect with mdt shell you will need to first connect to your device
ONLY via USB.
The mdt shell was working with eagle 5.0 after adding the public key to ~/.ssh/authorized_keys. I downgraded to mendel 4.0 Day 13 (which crashed during flashing). I reflahsed eagle mendel 5.0, and now it seems like it doesn't read the ~/.ssh/authorized_keys but everything else seems to be working (connects to wifi and gets the same ip address as before).
Is downgraded from eagle 5.0 to day 13 4.0 damaging?
Also, when I reflash the system with the same image (say eagle 5.0) it appears it doesn't erase the whole flash. Some of the data like /coral/pycoral seems stay even after reflashing??
What I ran
mdt shell
What the docs said should happen
Connect
What actually happened
It looks like you're trying to connect to a device that isn't connected to your workstation via USB and doesn't have the SSH key this MDT generated. To connect with
mdt shellyou will need to first connect to your device ONLY via USB.The mdt shell was working with eagle 5.0 after adding the public key to ~/.ssh/authorized_keys. I downgraded to mendel 4.0 Day 13 (which crashed during flashing). I reflahsed eagle mendel 5.0, and now it seems like it doesn't read the ~/.ssh/authorized_keys but everything else seems to be working (connects to wifi and gets the same ip address as before).
Is downgraded from eagle 5.0 to day 13 4.0 damaging?
Also, when I reflash the system with the same image (say eagle 5.0) it appears it doesn't erase the whole flash. Some of the data like /coral/pycoral seems stay even after reflashing??