On Mon, 13 Jul 2020 23:24:06 +0530, in gmane.comp.hardware.beagleboard.user
Pankaj Rai <pamkajkumar64-re5jqeeqqe8avxtiumw...@public.gmane.org> wrote:
>Hi,
>I've enabled the port 22 on my pc and I'm not using sd card for flashing so
>I don't think i need to press the s2 button.
>And also i don't have any debugger and i tried pinging the BBB on that
>address but it shows all the sent packets are lost so i think I'm unable to
>ping.
>
>Is there any other way to work this out?
>
The surest is to NOT USE THE USB "network".
I presume your main computer is connected to some router.
Run an ethernet cable from the BBB to the same router. Connect a 5V
power supply to the barrel connector on the BBB. (If you must, you might be
able to use a 5V USB phone charger connected to the USB port -- but for
this debugging you do NOT want the USB port connected to the main
computer!)
Check the router configuration pages for what IP # it assigned to the
BBB (note: if the router is modern enough, it may do DNS and have assigned
the host name beaglebone.local to the BBB, in which case you can connect
using the host name instead of the router assigned IP #).
-=-=-=-
IP Allocation
IPv4 Address / Name MAC Address Status Allocation Action
192.168.1.68 / EPSONF4EF32 00:26:ab:f4:ef:32 on DHCP Allocation
192.168.1.65 / DIRECTV-HR54-C94828D7 18:16:c9:48:28:d9 on DHCP
Allocation
192.168.1.93 / unknown5ca39d084ab9 5c:a3:9d:08:4a:b9 on DHCP
Allocation
192.168.1.74 / unknown64c6670531d3 64:c6:67:05:31:d3 off DHCP
Allocation
192.168.1.70 / Galaxy-S9 8c:45:00:6d:1a:4c on DHCP Allocation
192.168.1.79 / pi-star-3b b8:27:eb:4b:0b:d5 on DHCP Allocation
192.168.1.252 / microdiversity b8:27:eb:ce:b1:eb on DHCP Allocation
192.168.1.66 / ElusiveUnicorn b8:ca:3a:79:0c:36 on DHCP Allocation
192.168.1.84 / HP7C548D c4:65:16:7c:54:8d on DHCP Allocation
192.168.1.69 / beaglebone d0:39:72:18:3e:e5 on DHCP Allocation
-=-=-=-
(my router does not show the .local, but access from Win10 works with or
without it)
Microsoft Windows [Version 10.0.19041.329]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\Wulfraed>ping 192.168.1.69
Pinging 192.168.1.69 with 32 bytes of data:
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.69:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\Wulfraed>
C:\Users\Wulfraed>ssh debian@192.168.1.69
The authenticity of host '192.168.1.69 (192.168.1.69)' can't be
established.
ECDSA key fingerprint is
SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '192.168.1.69' (ECDSA) to the list of known
hosts.
Debian GNU/Linux 10
BeagleBoard.org Debian Buster IoT Image 2020-04-06
Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
default username:password is [debian:temppwd]
debian@192.168.1.69's password:
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sun Jul 5 14:40:38 2020 from fe80::c932:bd85:577:9922%eth0
debian@beaglebone:~$
--
Dennis L Bieber
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/rgapgftlko8q86falvhiqtqdh5m90pktei%404ax.com.
