## 树莓派国内源

 Asia China Tsinghua University Network Administrators http://mirrors.tuna.tsinghua.edu.cn/raspbian/raspbian/ Unreachable as of 15-may-2015 Asia China Dalian Neusoft University of Information http://mirrors.neusoft.edu.cn/raspbian/raspbian Asia China Cohesion Network Security Studio (CNSS) http://raspbian.cnssuestc.org/raspbian/  rsync://raspbian.cnssuestc.org/raspbian Asia China Unique Studio of Huazhong University of Science and Technology (http|rsync)://mirrors.hustunique.com/raspbian/raspbian Asia China University of Science and Technology of China (http|rsync)://mirrors.ustc.edu.cn/raspbian/raspbian/ Asia China SUN YAT-SEN University http://mirror.sysu.edu.cn/raspbian/ Asia China Zhejiang University http://mirrors.zju.edu.cn/raspbian/raspbian/ Asia China Open Source Software Association of Chinese Academy of Sciences http://mirrors.opencas.cn/raspbian/raspbian/ Asia China Chongqing University http://mirrors.cqu.edu.cn/Raspbian/raspbian/

## 树莓派OS历史版本下载

 2012-07-15-wheezy-raspbian 2012-08-16-wheezy-raspbian 2012-09-18-wheezy-raspbian 2012-10-28-wheezy-raspbian 2012-12-15-wheezy-raspbian 2012-12-16-wheezy-raspbian 2013-02-09-wheezy-raspbian 2013-05-25-wheezy-raspbian-shrunk 2013-05-25-wheezy-raspbian 2013-07-26-wheezy-raspbian raspbian-2013-09-16 raspbian-2013-09-27 raspbian-2013-10-07 raspbian-2013-12-24 raspbian-2014-01-09 raspbian-2014-06-22 raspbian-2014-09-12 raspbian-2014-12-25 raspbian-2015-02-02 raspbian-2015-02-17 raspbian-2015-05-07 Debian 7(Wheezy) raspbian-2015-09-28 raspbian-2015-11-24 raspbian-2016-02-08 raspbian-2016-02-09 raspbian-2016-02-29 raspbian-2016-03-18 raspbian-2016-05-13 raspbian-2016-05-31 raspbian-2016-09-28 raspbian-2016-11-29 raspbian-2017-01-10 raspbian-2017-02-27 raspbian-2017-03-03 raspbian-2017-04-10 raspbian-2017-06-23 raspbian-2017-07-05 Debian 8 (Jessie) raspbian-2017-08-17 raspbian-2017-09-08 raspbian-2017-12-01 raspbian-2018-03-14 raspbian-2018-04-19 raspbian-2018-06-29 raspbian-2018-10-11 raspbian-2018-11-15 raspbian-2019-04-09 Debian 9 (Stretch) raspbian-2019-06-24 raspbian-2019-07-12 Debian 10(Buster)

## Using QEMU to emulate a Raspberry Pi

If you're building software for the Raspberry Pi (like I sometimes do), it can be a pain to have to constantly keep Pi hardware around and spotting Pi-specific problems can be difficult until too late.

One option (and the one I most like) is to emulate a Raspberry Pi locally before ever hitting the device. Why?

• Works anywhere you can install QEMU
• No hardware setup needed (no more scratching around for a power supply)
• Faster feedback cycle compared to hardware
• I can use Pi software (like Raspbian) in a virtual context
• I can prep my "virtual Pi" with all the tools I need regardless of my physical Pi's use case

Given I'm next-to-useless at Python, that last one is pretty important as it allows me to install every Python debugging and testing tool known to man on my virtual Pi while my end-product hardware stays comparatively pristine.

### Getting started

First, you'll need a few prerequisites:

#### QEMU (more specifically qemu-system-arm)

You can find all the packages for your chosen platform on the QEMU website and is installable across Linux, macOS and even Windows.

#### Raspbian

Simply download the copy of Raspbian you need from the official site. Personally, I used the 2018-11-13 version of Raspbian Lite, since I don't need an X server.

#### Kernel

Since the standard RPi kernel can't be booted out of the box on QEMU, we'll need a custom kernel. We'll cover that in the next step.

### Preparing

First, you'll need to download a kernel. Personally, I (along with most people) use the dhruvvyas90/qemu-rpi-kernel repository's kernels. Either clone the repo:

For the rest of these steps I'm going to be using the kernel-qemu-4.4.34-jessiekernel, so update the commands as needed if you're using another version.

#### Filesystem image

This step is optional, but recommended

When you download the Raspbian image it will be in the raw format, a plain disk image (generally with an .img extension).

A more efficient option is to convert this to a qcow2 image first. Use the qemu-imgcommand to do this:

Now we can also easily expand the image:

You can check on your image using the qemu-img info command

### Starting

You've got everything you need now: a kernel, a disk image, and QEMU!

Actually running the virtual Pi is done using the qemu-system-arm command and it can be quite complicated. The full command is this (don't worry it's explained below):

So, in order:

• sudo qemu-system-arm: you need to run QEMU as root
• -kernel: this is the path to the QEMU kernel we downloaded in the previous step
• -append: here we are providing the boot args direct to the kernel, telling it where to find it's root filesytem and what type it is
• -hda: here we're attaching the disk image itself
• -cpu/-m: this sets the CPU type and RAM limit to match a Raspberry Pi
• -M: this sets the machine we are emulating. versatilepb is the 'ARM Versatile/PB' machine
• -no-reboot: just tells QEMU to exit rather than rebooting the machine
• -serial: redirects the machine's virtual serial port to our host's stdio
• -net: this configures the machine's network stack to attach a NIC, use the user-mode stack, connect the host's vnet0 TAP device to the new NIC and don't use config scripts.

If it's all gone well, you should now have a QEMU window pop up and you should see the familiar Raspberry Pi boot screen show up.

Now, go get yourself a drink to celebrate, because it might take a little while.

### Networking

Now, that's all well and good, but without networking, we may as well be back on hardware. When the machine started, it will have attached a NIC and connected it to the host's vnet0 TAP device. If we configure that device with an IP and add it to a bridge on our host, you should be able to reliably access it like any other virtual machine.

#### (on host) Find a bridge and address

This will vary by host, but on my Fedora machine, for example, there is a pre-configured virbr0 bridge interface with an address in the 192.168.122.0/24 space:

I'm going to use this bridge and just pick a static address for my Pi: 192.168.122.200

Reusing an existing (pre-configured) bridge means you won't need to sort your own routing

#### (in guest) Configure interface

NOTE: I'm assuming Stretch here.

Open /etc/dhcpcd.conf in your new virtual Pi and configure the eth0 interface with a static address in your bridge's subnet. For example, for my bridge:

You may need to reboot for this to take effect

#### (in host) Add TAP to bridge

Finally, add the machine's TAP interface to your chosen bridge with the brctl command:

Now, on your host, you should be able to ping 192.168.122.200 (or your Pi's address).

#### Set up SSH

Now, in your machine, you can run sudo raspi-config and enable the SSH server (in the "Interfacing Options" menu at time of writing).

Make sure you change the password from default while you're there!

Finally, on your host, run ssh-copy-id pi@192.168.122.200 to copy your SSH key into the Pi's pi user and you can now SSH directly into your Pi without a password prompt.

#### 参考链接

Using QEMU to emulate a Raspberry Pi

## usbip--ubuntu 16.04(USB局域网共享)

usbip的目的是为了开发一个在局域网内共享的USB设备，也就是说你可以直接访问局域网内其他计算机的USB设备。

ubuntu 16.04

## 解决Raspberry Pi安装libgtk2.0-dev出错的问题

#### 参考链接

Unable to install libgtk2.0-dev on Raspberry Pi 2