How to get the latest ubuntu image for Beaglebone Black (via MicroSD Card)?

Also as you are using a work computer at home, are you by any chance using a VPN to connect to your work ? If so, it could be that all IP traffic is being routed via VPN.

I think your issues are with your Windows computer. I have the same version of software on my BBB and there are no issues SSH’ing via ethernet or USB for me from my Linux laptop.

‘use’ to work, check what user (debian) that you are trying to login with…


Brilliant!!! That was it : if I stop the VPN, the BBB is back!

Here is what I did :

  1. Flash the Linux again, for a fresh start
  2. Remove the SD card
  3. Plug the ethernet cable from the router to the BBB
  4. Plug the BBB to the computer via USB

In this configuration, with the VPN on, the BBB appears as a new drive but no way to SSH it on
If I switch off the VPN, everything comes back: I can SSH (user: debian), ping Google, etc.

But now, I have another problem: when I try apt-get update I get

No space left on device

df -H says:

debian@BeagleBone:~$ df -H
Filesystem      Size  Used Avail Use% Mounted on
udev            222M     0  222M   0% /dev
tmpfs            51M  1.4M   50M   3% /run
/dev/mmcblk1p1  3.7G  3.5G     0 100% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M     0  5.3M   0% /run/lock
tmpfs            51M   21k   51M   1% /run/user/1000

What’s wrong with the memory? What is this mmcblk1p1 which takes so much space? Is it needed or can I remove it?

debian@BeagleBone:~$ ls -al /dev/mmcblk1p1
brw-rw---- 1 root disk 179, 1 Dec  1 15:55 /dev/mmcblk1p1
debian@BeagleBone:~$ lsblk
mmcblk1      179:0    0  3.6G  0 disk
`-mmcblk1p1  179:1    0  3.6G  0 part /
mmcblk1boot0 179:256  0    2M  1 disk
mmcblk1boot1 179:512  0    2M  1 disk
debian@BeagleBone:~$ lsblk -fs
NAME         FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINT
mmcblk1p1    ext4   1.0   rootfs 583bc30a-0c29-4258-ae99-aa4d1504cfa1       0    95% /

mmcblk1p1 is your root fs on the eMMC.
I have no idea how much space the XFCE image takes.
I only have old BBB’s with 2GB eMMC so I can’t fit the image on it anyway. I usually just use the minimal non desktop version.

This is the xfce snapshot, it takes most of the 4GB eMMC (3.2/3.3)…

If you really really need xfce use a microSD…


Then I need to disable the flasher, otherwise it will flash the eMMC each time I boot the board

Actually, I may not need xfce.
What I need (in the future, when everything is set) is to connect a 4.3" capacitive touch LCD cape (that I bought recently) and use it for interfacing with Python (using tk possibly). I thought this was only possible with xfce. But if xfce is not needed, then I can flash a smaller image.

After that, I’m planning to run some AI applications, so I also need memory.

What should I do?

Depends on how you build your interface. You don’t necessarily need a full desktop.
You could try LVGL, it is mostly C based though but does have bindings for micro python. They are probably others.

In the past I have used QT with a framebuffer backend and that was on a 2GB eMMC BBB.

Thanks, so I can try to flash a smaller image.
I see here 2 possible versions: minimal and IOT. What’s the difference, and which one do you suggest?

not sure of the difference. You can always start with the minimal and then install packages as required

I have found a thread somewhere saying that the IOT has everything but xfce, and the minimal has mostly netork and you need to install the rest (such as python).
I don’t feel comfortable with that right now, I’ll try the IOT version. They said it takes around 2GB.

It took 6 minutes to flash, and now I have some space left:

debian@BeagleBone:~$ df -H
Filesystem      Size  Used Avail Use% Mounted on
udev            225M     0  225M   0% /dev
tmpfs            51M  1.4M   50M   3% /run
/dev/mmcblk1p1  3.7G  2.2G  1.4G  62% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M     0  5.3M   0% /run/lock
tmpfs            51M     0   51M   0% /run/user/1000

apt-get update and upgrade did work.
All looks good now. Thanks again for your help everyone!

I have installed some of the packages I require (such as gnuplot, libopencv-dev) and there is now only a small space left for the rest. I may run out of memory.

debian@BeagleBone:~$ df -H
Filesystem      Size  Used Avail Use% Mounted on
udev            224M     0  224M   0% /dev
tmpfs            51M  1.4M   50M   3% /run
/dev/mmcblk1p1  3.7G  3.4G  170M  96% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M     0  5.3M   0% /run/lock
tmpfs            51M     0   51M   0% /run/user/1000

So I think I have 2 options:

  1. Start again but from the minimal version, as you suggested,
  2. Keep the IOT version but run it from a SD card.

As I said, I’m not comfortable with the first option, because I fear that I will miss some important packages or libraries.

In the second case, I have 2 questions:

  • Right now, the flasher is enabled, so each time I insert the SD card and boot, it flashes the eMMC, which is not what I need. How can I turn the flasher off?
  • If I boot from a SD card and install some packages, are they installed in the SD card as well or in the eMMC?

If they are installed in the SD card, then using a 64GB card should enable to install everything I need.

sounds like some of your packages are pulling in some hefty dependencies.

You could try doing an ‘apt-get clean’
This will remove the downloaded deb files from the apt cache - assuming apt is caching them. This will give you back some space depending on how much you have downloaded.

But it sounds like you will probably be better of running from SD.
If you boot from the SD card, then all installed packages are on the SD card only.

I don’t think the eMMC is mounted when booting from SD.

I think (not sure, Robert will hopefully tell you) that the flasher is a systemd service, that you can disable. There is a post on the forum somewhere mentioning the flasher.

If you are going to run from SD, just download the non-flasher version and put that on the SD card.

Found it!

Then 2 modes…
Basic user-mode…

sudo beagle-flasher

bootup “auto” flasher mode…

sudo enable-beagle-flasher

No, actually these are 2 ways of flashing from the SD card (manual and automatic).
Back to the question : how to disable auto flash from SD card?

I found this line at the end of /boot/uEnv.txt:

##enable Generic eMMC Flasher:

Should I uncomment it ?

I would have thought it should remain commented out. looks like the command to flash the eMMC

Your looking at /boot/ on the eMMC media…

mount your microSD, you’ll see it un-commented…


Why are you worried about this? Everything is in apt…

The minimal is small image for any of the boards, to at least get network up and running out of the box.


Yes you are right, but I’m very new to embedded linux and I fear that I might have difficulties.
The easiest, but far from elegant, would be to use a large SD card, put the xfce version in it and boot from it.

So if I write the xfce version on a new large SD card (I have a 64GB) and boot the BBB with the card inside, it will boot from the card (instead of flashing the eMMC from the card) ?