As for the power supply, you can take any 5V charger from an Android phone with a micro USB connector.<\/p>\n
2. The Operating System<\/h2>\n
I opted for the most recent Raspbian Jessie Lite version, as I wanted as little overhead as possible for the smooth operation of the camera (and maybe later a nextCloud service). Download the ZIP from this site and unzip the resulting image file to the hard disk of your local machine.<\/p>\n
2.1 Preparing the SDHC memory card<\/h2>\n
Then insert the microSDHC card into the card reader of your local machine and check if it has a single partition which is formatted to fat32. Normally these cards are shipped pre-formatted and you do not have to do anything. The features should look as follows:<\/p>\n Remember the path of the microSDHC card which is Before you copy the image, make sure that you unmount the card. Depending on your OS, the card may be mounted under [alert type=”warning” icon-size=”normal”]Keep in mind that the mount point and the path of the card are not identical. You must unmount the card from the mount point and not from its After unmounting copy the image file you unzipped to your card using the [alert type=”danger” icon-size=”normal”]Think twice before you apply Here is how my card gets flashed with Raspbian:<\/p>\n After a while, your card should be flashed.<\/p>\n Many of the tuorials on getting your Raspberry started recommend connecting your device to a monitor and a keyboard and setting up the remaining parameters. Apart from the fact that I newver liked fiddling around with cables on a Raspberry board which is intended to run as a standalone computer, this does not work for a Raspberry Zero. The reason is that there is only a micro USB plug while cable keyboards will have a “grown out” standard USB connector. The better way is to pre-edit the image before booting. The following description is based on David Maitland’s tutorial on the Pi Zero headless setup (no longer online, archived version) <\/a>.<\/p>\n Remount the SDHC card with the image flashed. After running the Then in the terminal window, Your [alert type=”warning” icon-size=”normal”]Raspbian is extremely picky with the syntax. Even a space before and after the equals sign can enough to derail the parsing of the wpa_supplicant.conf file at boot time.[\/alert]<\/p>\n [alert type=”info” icon-size=”normal”]Since Raspian Stretch static IPs are no longer set up in There is no need to edit\u00a0 Unless you are very good at setting up network discovery services, it is a good idea to configure your Raspberry device with a static IP so that you can always be sure about the address under which you can access the device on your network.<\/p>\n Setting the IP address and other related stuff is done by editing As the Raspbian image is already pre-configured to use the iconic Raspberry ships their Raspbian images with Now comes the moment where we have to work on the Your Pi is now ready for booting. Unmount the SDHC card and remove it from your workstation and plug it into your pi. Connect it to the power cable of an Android USB charger and wait ~ 45 sec until it has completely booted.<\/p>\n Then ssh into the Pi using the IP address you assigned it in the [alert type=”warning” icon-size=”normal”]Do not forget to change the password using the Instead of password authentication it is usually more convenient to set up a key based authentication. As the Pi0W will normally only be passively involved in remote log in procedures – i.e. the Pi0W will be the host on which someone remotely logs in but nobody will remotely log in from the Pi0W onto another host – we do not even need to create the key-pair but just set up the\u00a0 Copy the\u00a0 Set the access rights for the Log out from your Pi0W and check if relogging in from the client machine can be done by public key authentication. If this is the case, you may want to switch off password authentication completely by uncommenting the Reboot the Pi0w to activate the new configuration.<\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" I recently bought one of the new Raspberry Pi Zero W boards to build a wireless CCTV camera. This article shows how to get the Raspbian Operating System installed and![\"\"](\"http:\/\/hobbykeller.spdns.de\/wp-content\/uploads\/2017\/04\/gparted_shdc.png\")
\/dev\/mmcblk0p1<\/code>. You will need part of this path in the next step when you copy the image you downloaded to the memory card.<\/p>\n2.2 Copying the image to the card<\/h2>\n
\/media\/335-3432\/<\/code> (Ubuntu), \/media\/user_id\/335-3432\/<\/code> or \/run\/media\/user_id\/335-3432\/<\/code> (Manjaro). You can find this mount point by opening your file explorer, clicking on the link to the SDHC card and looking at the address bar in the top. The numbers at the end of the path may of course vary.<\/p>\n\/dev<\/code> path.[\/alert]<\/p>\ndd<\/code> command from the terminal. The of=<\/code> path should be the path of the card you retained at the end of section 2.1 without the partition indication<\/strong>. If the path was is \/dev\/mmcblk0p1<\/code>, the corresponding out file parameter in the dd command should be: of=\/dev\/mmcblk0<\/code>.<\/p>\ndd<\/code>. Make sure you have the right \/dev\/mmblk...<\/code> device in case you have more than one card connected to your machine. And – above all – do not confuse if<\/code> and of<\/code> parameters or you will risk fucking up your data or even your OS. dd<\/code> is nick named “disk destroyer” for a reason.[\/alert]<\/p>\n[ilek@nordic ~]$ sudo unmount \/dev\/mmcblk0p1\r\n[ilek@nordic ~]$ dd bs=4M if=2017-04-10-raspbian-jessie-lite.img of=\/dev\/mmcblk0<\/pre>\n
3. Preparing your image<\/h1>\n
3.1 Add network key<\/h2>\n
sync<\/code> command from your terminal you can just eject and reinsert the card to get it mounted. Open your file explorer and you should see two mount points referring to the card: one is labeled boot, the other one comes up as a 1.3 GB volume – which suggests that a cheaper 4 GB card probably would have been sufficient. Click on the “non-boot” partition and copy the path in the address field to your clipboard.<\/p>\n![\"\"](\"http:\/\/hobbykeller.spdns.de\/wp-content\/uploads\/2017\/04\/in_situ_edit_of_raspbian_image.png\")
cd<\/code> to that directory, and afterwards cd<\/code> to etc\/wpa_supplicant\/<\/code>. Use sudo vim<\/code> to edit the wpa_supplicant.conf<\/code> file:<\/p>\n[ilek@nordic ilek]$ cd \/run\/media\/ilek\/f2100b2f-ed84-4647-b5ae-089280112716\/\r\n[ilek@nordic f2100b2f-ed84-4647-b5ae-089280112716]$ cd etc\/wpa_supplicant\/\r\n[ilek@nordic wpa_supplicant]$ sudo vim wpa_supplicant.conf<\/pre>\n
wpa_supplicant.conf<\/code> should look as follows:<\/p>\ncountry=DE\r\nctrl_interface=DIR=\/var\/run\/wpa_supplicant GROUP=netdev\r\nupdate_config=1\r\n\r\nnetwork={\r\n\tssid=\"___Name_of_your_WIFI_network\"\r\n\tpsk=\"___your wifi password\"\r\n key_mgmt=WPA-PSK\r\n}\r\n<\/pre>\n3.2 Setup static IP<\/h2>\n
New Raspbian Stretch Lite Edition<\/h3>\n
\/etc\/network\/interfaces<\/code> but in \/etc\/dhcpcd.conf<\/code>[\/alert]<\/p>\n\/etc\/dhcpcd.conf<\/code> to set up name servers, either. The only file you need to edit is the\u00a0\/etc\/dhcpcd.conf<\/code> file as follows:<\/p>\n# Example static IP configuration:\r\n\r\n#interface eth0 \r\n#static ip_address=192.168.1.72\/24 \r\n#static routers=192.168.1.1 \r\n#static domain_name_servers=192.168.1.1 \r\n \r\ninterface wlan0 \r\nstatic ip_address=192.168.1.62\/24 \r\nstatic routers=192.168.1.1 \r\nstatic domain_name_servers=192.168.1.1 8.8.8.8 \r\n<\/pre>\n
PreVious Raspbian Jessie Lite Edition<\/h3>\n
etc\/network\/interfaces<\/code> with sudo vim<\/code>. At the end of your edit, your interfaces file should look like this (where the IP address and the gateway may of course differ depending on the setup of your network):<\/p>\n# Include files from \/etc\/network\/interfaces.d:\r\nsource-directory \/etc\/network\/interfaces.d\r\n\r\nauto lo\r\niface lo inet loopback\r\n\r\niface eth0 inet manual\r\n\r\nallow-hotplug wlan0\r\niface wlan0 inet\r\n address 192.168.1.8\r\n netmask 255.255.255.0\r\n gateway 192.168.1.1 \r\n wpa-conf \/etc\/wpa_supplicant\/wpa_supplicant.conf\r\n\r\nallow-hotplug wlan1\r\niface wlan1 inet manual\r\n wpa-conf \/etc\/wpa_supplicant\/wpa_supplicant.conf<\/pre>\n
8.8.8.8<\/code> and 8.8.8.4<\/code> DNS servers from Google, this step is rather optional. Skip it if you are fine with Google logging your DNS queries, or – if you are paranoid – edit etc\/resolv.conf<\/code> and replace the DNS IPs by a pair of servers you think you can trust more. You can choose such a server from here<\/a>.<\/p>\n3.3 Activate SSH<\/h2>\n
ssh<\/code> deactivated by default. This of course is bad news if you want to run a headless confiuration from scratch. You have to be sure that you can access your Pi zero by ssh<\/code> over the network.<\/p>\nboot<\/code> partition of the image. Again, the easiest way to find the address of boot is to open your file browser and click on the boot<\/code> partition of the SDHC card in the Devices section. Then copy the path to the clipboard as before und run cd<\/code> + paste in your terminal.<\/p>\n[ilek@nordic etc]$ cd \/run\/media\/ilek\/boot\/\r\n[ilek@nordic boot]$ touch ssh<\/pre>\n
4. Boot your Pi<\/h1>\n
etc\/network\/interfaces<\/code> of section 3.2. The default password for the Pi is.. guess what? Yes, it’s raspberry<\/strong>.<\/p>\npasswd<\/code> comand once you have logged into your pi.[\/alert]<\/p>\n5. Adding authorized keys<\/h1>\n
.ssh<\/code> directory:<\/p>\npi@pi0:~ $ mkdir .ssh\r\npi@pi0:~ $ chmod 700 .ssh\r\npi@pi0:~ $ vim .ssh\/authorized_keys\r\n<\/pre>\n
id_rsa.pub<\/code> public key of the client machine<\/strong> into the authorized_keys<\/code> file on the Pi0W.<\/p>\nauthorized_keys<\/code> file to 600:<\/p>\nchmod 600 .ssh\/authorized_keys<\/pre>\n
PasswordAuthentication<\/code>flag in the\u00a0\/etc\/ssh\/sshd_config<\/code> file and setting it to no<\/code> on the Pi0w:<\/p>\n# To disable tunneled clear text passwords, change to no here! \r\nPasswordAuthentication no \r\n#PermitEmptyPasswords no<\/pre>\n