I cannot seem to SSH into my Beaglebone from my Windows (Windows 10 Business)
machine. I try open an ssh sessioon with host ip address 192.168.7.2
but nothing happens. The putty session eventually times out with this error, “Network error: Connection timed out”.
Don’t know what else to try.
The 192.168.7.2 range is setup for the usb-Ethernet gadget… How do you have the device connected to the network/pc? Is it directly connected via usb between the board and pc, or using an Ethernet cable?
When using the usb cable between the board and pc, make sure from the windows network connection manager, that it’s connected and has a valid ip…
Regards,
Hi Nelson,
I’m connecting directly from the PC to the beaglebone black via USB .
Where do I find the Windows Network connection manager to check ?
Also, what does the Beaglebone enumerate as so I can check to see if it is properly enumerated in the device manager? I see something that I think is it, something like “…NDIS”, but I’m not sure.
Thank you
Ignore the “BeagleY-AI” at the top left, this is just a board i had on hand… Same usb gadget script loading the stack…
Two common drivers, Remote NDIS (192.168.7.2) and UsbNcm (192.168.6.2)
As windows 10 goes eol, we wil move to Ncm…
Regards,
Hello and thank you for your response. How ever, I don’t know what to do with this information. I still can’t ssh into my Besglebone.
Am I missing a driver or something? Is this stack guaranteed to be in my Beaglebone?
Thanks,
Jorge
First step would be to verify what shows up in your network connections window.
Then click on details to see what settings are set.
I’m not a SW guy, so I’m not sure I understand how this works exactly.
These “gadgets” are in the beaglebone in Flash (or ROM)?
Can you give me (or point me to something I can read) a little background on this?
Thank you!
It’s purely software controlled thru a Linux driver on bootup.
This gets deep into the weeds… Linux USB gadget configured through configfs — The Linux Kernel documentation
But the first section ‘overview’ does a good job of the theory.
But please feel free to share any screenshots of what I’ve asked to confirm what’s happening on your board.
This windows application will help show what driver was loaded thru USB… USB Device Tree Viewer
Here’s what I see:
notice that it is disabled. I can’t seem to be able to enable it… seems it is looking for an ethernet connection and not USB (USB is how it is connected and how it shows up).
It looks good (windows 10 doesn’t like the ncm driver this is known), but we see Remote NDIS Compatible Device (RNDIS aka usb-ethernet)
and driver is loaded:
It wants to load, as it’s right here:
Try Right click, enable/disable…
Regards,
as soon as I enable it, the red x appears on the icon…
typing 192.168.7.2 on Chrome (and Firefox) with the Beaglebone connected via USB (through the USB mini connector) eventually times out…
Here’s some additional data.
Exploring the USB Device Tree, I noticed that the Remote NDIS compatible device was showing an error code 22. I was able to reenable it, but I still cannot reach ip address 192.168.7.2. (and the ethernet 4 icon remains x’d out.
When I look at the details of the Remote NDIS Compatible Device driver, I see this:
Is something not yet installed or failing to install properly? I had to disable the SIgned Driver Enforcement policy to install the drivers from here:
http://beagleboard.org/static/Drivers/Windows/BONE_D64.exe
Did I not have to install these ? (I did it when it first couldn’t ssh into the Beaglebone --but it siill fails “the same way” with these drivers installed. It kind of feels like I have some sort of driver conflict
no don’t use that driver… it was for Win XP/etc…
Can you use putty to login into com 7? putty or: https://mobaxterm.mobatek.net/
then we can get, the ‘firmware’ version…
For example, “Xfce 2024-06-12” from above ^
Regards,
I tried login in with username “root” and leaving the password blank, but that didn’t work…
Ah there we go, Debian 10.x (Buster) built on 2019-09-01… (root password should be root)
Just grab the Debian 11.x (Bullseye) image from here: Debian 11.x (Bullseye) - Monthly Snapshot - 2023-10-07
Minimal or IoT… unless you really want a slow desktop…
Personally I’d go with this one: https://rcn-ee.com/rootfs/release/2023-10-07/bullseye-iot-armhf/am335x-eMMC-flasher-debian-11.8-iot-armhf-2023-10-07-4gb.img.xz
Use etcher.io to flash it to a microSD
Regards,
wait…I see that it should be debian and temppwd, let me try that…
that one also says “login incorrect”
doing (trying) it now…question, does the bootloader in the beaglebone then copy this image from the SD card into its flash, or will I need the SD card always installed going forward?
the image i linked to: am335x-eMMC-flasher-debian-11.8-iot-armhf-2023-10-07-4gb.img.xz is setup to automatically copy/flash the microSD → eMMC… (keyword flasher in file name)
Just make sure you hold the boot button, insert power, wait for led, lift up on boot button… within a minute you should see the cylon led/led chasser/etc <>>>>>><<<<<<>>>>><<<> pattern, that means it’s coping the microSD to eMMC… It should shutdown within 5-7 minutes…
Regards,
writing the SD card fails to verify. I’m trying uncompressing the file prior to flashing it.
shout the SD card be formatted as NTFS or FAT32?
by the way, I don’t think my beaglebone has a boot (reset) button populated. I’ll have to install one…
Yeah try un-compressing the xz… i’m using etcher 1.18.12 i think the default is now 1.19.x
Don’t worry about the SD card, the *.img will contain the low level partition information when writing…
Maybe ‘usr’ button, i forgot what label was on it… digs around for a board… “S2” near the microSD cage…
Regards,
