Difference between revisions of "BBB New Debian Image"

(Created page with '==Installing a new official Debian image on a SD card== Download from the [http://beagleboard.org/latest-images BeagleBoard.org] site or elsewhere a fresh image suitable for the …')

Download from the [http://beagleboard.org/latest-images BeagleBoard.org] site or elsewhere a fresh image suitable for the BBB.

Download from the [http://beagleboard.org/latest-images BeagleBoard.org] site or elsewhere a fresh image suitable for the BBB.

+

+

'''NOTE''': ''There are different ways of handling the IO in newer distributions. In earlier versions, pre version 8.x, a Capemanager was used to control the IO. In later versions this is done in a different way - and in an easier way.''

You will typically get a file named like this

You will typically get a file named like this

Line 15:

Line 17:

===Locate your SD card===

===Locate your SD card===

+

If you use a USB SD-card reader you can route the device to your virtual Centos, where the instructions below will fit.

+

Have a 4GB SD ready and inserted into your computer. Execute

Have a 4GB SD ready and inserted into your computer. Execute

<source lang=bash>

<source lang=bash>

Line 34:

Line 38:

Removing the SD card and rerunning the command will give you the final evidence to what the name is, since it is now missing in the list.

Removing the SD card and rerunning the command will give you the final evidence to what the name is, since it is now missing in the list.

If the SD card i preformatted, which most are, you will see two - or more - devices like this

If the SD card i preformatted, which most are, you will see two - or more - devices like this

Line 45:

Line 51:

The '''mmcblk0''' is the main block device and the '''mmcblk0p1''' is the first partition on the disk.

The '''mmcblk0''' is the main block device and the '''mmcblk0p1''' is the first partition on the disk.

+

+

Be careful to locate your SD card, since transferring data could accidentally ruin you permanent hard disk if you write to that instead of the SD card.

===Transferring the image to the SD card===

===Transferring the image to the SD card===

−

In order to transfer the disk image to the SD card first ensure that it is not mounted, e.g. by removing the card and re-insert it into the reader slot or by running a '''umount''' command (RTFM umount).

+

In order to transfer the disk image to the SD card first ensure that it is not mounted, e.g. by removing the card and re-insert it into the reader slot or by running a '''umount''' command (man umount).

Next issue this command

Next issue this command

Line 65:

Line 73:

Remove the SD card from your computer and insert it into the BBB.

Remove the SD card from your computer and insert it into the BBB.

−

Find the user button located just above the SD card slot.

+

On newer BBB the system boots on a SD card if inserted, but some may not boot. If the system does not boot from the SD card find the ''user button'' located just above the SD card slot. Press and hold the button while applying power to the device. When the device starts to boot (blinking LED's) release the ''user button''.

−

+

−

Press and hold the button while applying power to the device. When the device starts to boot (blinking leds) release the user button.

+

If you have previously connected your BBB using the

If you have previously connected your BBB using the

Line 88:

Line 94:

ECDSA host key for 192.168.7.2 has changed and you have requested strict checking.

ECDSA host key for 192.168.7.2 has changed and you have requested strict checking.

Host key verification failed.

Host key verification failed.

−

which tells us that in the ~/.ssh/known_hosts file we keep a fingerprint of hosts that we have previously accepted to be legal computers to connect to. You have to edit the ~/.ssh/known_hosts file and remode the line(s) beginning with 192.168.7.2 and then try to connect once again.

+

which tells us that in the ~/.ssh/known_hosts file we keep a fingerprint of hosts that we have previously accepted to be legal computers to connect to. You have to edit the ~/.ssh/known_hosts file and remove the line(s) beginning with 192.168.7.2 and then try to connect once again.

−

First time you connect to your new image you will be prompted to verify the fingerprint of the connecion. Do that by typing yes.

+

First time you connect to your new image you will be prompted to verify the fingerprint of the connection. Do that by typing yes.

Determine the version of your new image by issuing this command

Determine the version of your new image by issuing this command

Line 99:

Line 105:

</source>

</source>

−

This is at the time of wirting the latest official supported image, but not necessarily the newest - you may find newer images floating around the Internet. The following device driver development will take outspring in the version.

+

This is at the time of writing the latest official supported image, but not necessarily the newest - you may find newer images floating around the Internet.

Latest revision as of 10:00, 21 June 2018

Contents

Installing a new official Debian image on a SD card

Download from the BeagleBoard.org site or elsewhere a fresh image suitable for the BBB.

NOTE: There are different ways of handling the IO in newer distributions. In earlier versions, pre version 8.x, a Capemanager was used to control the IO. In later versions this is done in a different way - and in an easier way.

You will typically get a file named like this

bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz

Date and version number may vary.

In your download directory execute this command

]$ xz -dk bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz

this will unpack the image into a file like this

bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img

Locate your SD card

If you use a USB SD-card reader you can route the device to your virtual Centos, where the instructions below will fit.

Have a 4GB SD ready and inserted into your computer. Execute

]$ ll /dev/sd*

or

]$ ll /dev/mmcblk*

the way your computer interface to the SD card will either see it as a disk drive and name it /dev/sdN, where N is the next free letter - e.g. you have one disk already installed in your computer it is most likely sda[09], the next disk the system recognises will be sdb.

On my laptop when I use the SD slot directly in the laptop the system sees the SD card as a new mmc block device, hence the mmcblk name.

Another way to determine the name of the freshly inserted SD card is to execute

]$ ls-lart/dev

this will list the content of /dev in reverse order with the newest at the end of the list, i.e. at the bottom of your console.

Removing the SD card and rerunning the command will give you the final evidence to what the name is, since it is now missing in the list.

The dd command is a versatile utility that takes an input file (if) and an output file (of) and copies the input file to the output file (/dev/mmcblk0) in 1 mega bytes blocks (BS=1M). Expect 10 to 20 minutes before the command returns depending on the speed of your card reader and the SD card. Note here, that we use the main block interface file mmcblk0 not the mmcblk0p1 or the sdb not the sdb1.

Starting the new image on BBB

Remove the SD card from your computer and insert it into the BBB.

On newer BBB the system boots on a SD card if inserted, but some may not boot. If the system does not boot from the SD card find the user button located just above the SD card slot. Press and hold the button while applying power to the device. When the device starts to boot (blinking LED's) release the user button.

If you have previously connected your BBB using the

]$ ssh root@192.168.7.2

you will probably get a message like this

]$ ssh root@192.168.7.2
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
80:98:39:60:af:8e:db:14:47:9f:76:6a:88:89:12:e3.
Please contact your system administrator.
Add correct host key in /home/klaus/.ssh/known_hosts to get rid of this message.
Offending RSA key in /home/klaus/.ssh/known_hosts:49
ECDSA host key for 192.168.7.2 has changed and you have requested strict checking.
Host key verification failed.

which tells us that in the ~/.ssh/known_hosts file we keep a fingerprint of hosts that we have previously accepted to be legal computers to connect to. You have to edit the ~/.ssh/known_hosts file and remove the line(s) beginning with 192.168.7.2 and then try to connect once again.

First time you connect to your new image you will be prompted to verify the fingerprint of the connection. Do that by typing yes.