Search Project: *:*

 
<< < 1 .. 350 351 352 353 354 .. 3647 > >> (Page 352 of 3647)

retro-games: Artifact 5f48f89ee0677b001536b2a1 Retro Games tickets (Bin)
Last updated: 2020-08-28

code Discussion I/O Drivers code (Discussion)
Forum for code comments
Last updated: 2018-01-24

tickets Discussion I/O Drivers tickets (Discussion)
Forum for tickets comments
Last updated: 2018-01-24

doc Discussion I/O Drivers doc (Discussion)
Forum for doc comments
Last updated: 2018-01-24

database Discussion I/O Drivers database (Discussion)
Forum for database comments
Last updated: 2018-01-24

code Discussion Wharfie code (Discussion)
Forum for code comments
Last updated: 2018-02-14

wiki Discussion Wharfie wiki (Discussion)
Forum for wiki comments
Last updated: 2018-02-14

tickets Discussion Wharfie tickets (Discussion)
Forum for tickets comments
Last updated: 2018-02-24

Wharfie SVN repository Wharfie code (SVN Repository)
Last updated: 2020-08-04

Home Wharfie wiki (WikiPage)
Download debian package codesuccessful Build Embedded Linux Automate Building of Image Role out up-to-date images Get Cross-Toolchains Legal concerns Install Debian Other distributions Documentation Commands Tutorials Quickstart CODESYS Raspberry Pi Build Embedded Linux Wharfie is a modern build system for embedded devices. The concept is very similar to "docker". Both, "docker" and "wharfie", are using a simple format to describe custom linux system configurations and rebuild those easily. Wharfie uses basically the same syntax, while it is not fully compatible. While "docker" is focusing on scalable web services, "wharfie" is focusing on embedded linux systems. With "wharfie" you can easily build a root filesystem, based on the Debian distribution from scratch. To configure the system for your needs, you just write all necessary configuration steps into a configuration file. You don't do this configuration at the live system. Those configuration files are called Dockerfile in the docker eco-system. It's pendent in the world of wharfie is called Wharfile. Automate Building of Image When you install linux on an embedded target, it is very common, that you are first faced with a preconfigured system, which you have to configure manually. Doing this multiple times can become really anoying. Wharfie helps you in this process, as it can repeat all the configuration steps for you. ... # Set the locale RUN locale-gen en_US.UTF-8 RUN git clone https://github.com/pyload/pyload.git /opt/pyload \ && cd /opt/pyload \ && git checkout stable \ && echo "/opt/pyload/pyload-config" > /opt/pyload/module/config/configdir ADD pyload-config/ /opt/pyload/pyload-config ADD ../common/files/pyload.service /etc/systemd/system/pyload.service ... Role out up-to-date images Because the building process can be highly automated, you can easily just rebuild the images on a regular basis, and keep the images which you role out to new targets always up-to-date. # rebuild $ wharfie --clean $ wharfie Get Cross-Toolchains Wharfie supports armhf, armel, i386 and amd64 from debian. At least for ARM it is always difficult to get cross-toolchains, which can be easily archived and reused on different hosts. But also for x86 it makes fully sense to archive a cross toolchain for the systems, which you are roling out somewhere. Otherwise it can become difficult to rebuild programs for your systems in a few years. FROM debian_armhf_stretch TOOLCHAIN toolchain_debian_armhf_stretch.tar Legal concerns When using the linux OS for embeddded systems, a lot of legal issues have to be respected. Wharfie contains two additional commands to face these issues: LICENSE <filename></filename> SOURCE <filename></filename> These commands are creating tarballs, containing all the source packages, or all the licenses of your system, which were installed through debian packages. This feature makes it very easy to prepare yourself for distributing such an image. You will need to be able to provide such packages when you plan to distribute the image as part of a product, as well as when you share it with others in form of a download on the internet. When you publish anything, which contains code that was released under a third party license, you are usually forced to provide at least a list of all those licenses, containing the license text. Install Debian Click on the download link at the top of the package. Install the package on the terminal, using dpkg: sudo dpkg -i wharfie.deb Other distributions Use SVN to checkout the repository: svn checkout https://forge.codesys.com/svn/tol,wharfie,code/trunk wharfie-code Enter the directory and install the files under /usr/local/ cd wharfie ./install.sh
Last updated: 2020-02-07

Quickstart Tutorial Wharfie wiki (WikiPage)
Step 1: Debian Base System Step 2: Bootable debian with systemd Step 3: Username and password Step 4: Wireless network Step 5: Make a bootable image Final: The resulting file [[include IndexMain (already included)] This tutorial guides you on a basic setup of a debian based root filesystem. Without knowing anything about "wharfie", we can define what we want: Bootable debian with systemd Our desired username and password Wireless network SSH access To make everything a bit more specific, we configure the system for the Raspberry Pi Zero W. Step 1: Debian Base System With the simple Statement "FROM", we can decide which debian version and which architecture we want to use. The exact syntax is: FROM debian_<architecture>_<version> When doing anything with the Raspberry Pi, you have to know which CPU version you have, as you will need to select the correct architecture. Don't think, that this is not necessary, as Raspbian can serve all variants with a single image. They can do this, as they selected a compromise between the two major architecture variants, which debian is using. But no worries, the rule is easy: Single Core: armel Multi Core: armhf As the Raspberry Pi Zero hosts a single core CPU, we are using "armel". FROM debian_armel_stretch TO rpi.tar Step 2: Bootable debian with systemd We are installing the following pakets: systemd-sysv: This paket installs systemd, as well as the compatibility wrapper generator for system V. It is actually still a good idea, as some pakets (like dhcpcd5) still uses system V init scripts. dhcpcd5: This will enable the configuration of the IP address, using DHCP. wpa_supplicant: This will enable us to connect to a WPA secured access point. openssh: This will enable SSH access to the device. We will install everything with the following two flags: -y to answer all questions during installation with "yes" *-no-install-recommends to install only fix dependencies and keep the system small RUN apt-get update && apt-get install -y -no-install-recommends systemd-sysv dhcpcd5 wpa_supplicant openssh Now we just need the following actions, to add a proper /etc/fstab file. ADD files/fstab /etc/fstab Step 3: Username and password It should be rather selfexplainatory. This concept is widely used in docker images to add specific users and change their passwords. RUN useradd -ms /bin/bash wharfie; echo "wharfie:wharfie" | chpasswd; echo "root:root" | chpasswd; Step 4: Wireless network To load the network driver and to start wpa_supplicant for connecting to our access point, we use the following actions. ADD files/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-wlan0.conf ADD files/wireless.conf /etc/modules-load.d/wireless.conf RUN sed -i 's,^Requires,#Requires,' /lib/systemd/system/wpa_supplicant@.service; \ systemctl enable wpa_supplicant@wlan0.service; We are starting wpa_supplicant for our interface wlan0. Dhcpcd is by default configured to assign IP addresses to every available network interface. So /etc/network/interfaces is not used at all. Step 5: Make a bootable image The result of the build would currently be a simple tar archive. To bring this root filesystem onto a bootable SD card image, containing a bootloader, a kernel, kernel modules and all necessary firmware files, we can use a script from the folder "examples/bootstrategy/raspberrypi.sh". This is downloading the most current raspian image and is exchanging the rootfilesystem. RUN HOST \ ../../bootstrategy/raspberrypi.sh rpi.img Note, that RUN HOST is executed from a subfolder of your current working directory, which contains the full root filesystem. Therefore a relative path needs to contain an additional "../". Final: The resulting file All the steps above, need to be written into a file named "Wharfile". You should create a new folder for your image, where you can place this file. The additional files which are needed can be placed where you like, but it's recommended to use a subfolder (e.g. "files/" or "root/") to collect all files which are added using the ADD command. Here is the listing of the file. You file find a slighly changed version of it in the "examples" folder of wharfie. FROM debian_armel_stretch TO rpi.tar RUN apt-get update && apt-get install -y -no-install-recommends systemd-sysv dhcpcd5 wpa_supplicant openssh ADD files/fstab /etc/fstab RUN useradd -ms /bin/bash wharfie; echo "wharfie:wharfie" | chpasswd; echo "root:root" | chpasswd; ADD files/wpa_supplicant.conf /etc/wpa_supplicant/wpa_supplicant-wlan0.conf ADD files/wireless.conf /etc/modules-load.d/wireless.conf RUN sed -i 's,^Requires,#Requires,' /lib/systemd/system/wpa_supplicant@.service; \ systemctl enable wpa_supplicant@wlan0.service; RUN HOST \ ../../bootstrategy/raspberrypi.sh rpi.img To build the image, just change into the newly created folder, containing the "Wharfile" and type the command "wharfie". You will be asked to enter your password, as some of the actions during build need root access. After the image is created, it can be used on the target. In case of the Raspberry Pi from this example, the file "rpi.img" can be written on an SD card using the tool "dd". Have fun!
Last updated: 2019-11-30

CODESYS Wharfie wiki (WikiPage)
What it is Why to use it How to get it Use it on Linux [[include IndexMain (already included)] What it is CODESYS is an independent programming tool for PLCs. It consists of a programming tool, which is running under Windows, and a runtime, which can run on a real PLC or an open Linux Device, like the Raspberry Pi. Why to use it The glue for hobbyists is, that the programming system is free and the runtime is available as a 2h demo. There are generally a few major advantaes of using CODESYS over using C, python or s.th. similar: It is by far easier to access I/Os The graphical languages are easier to understand You can use an easy to use WebVisu You can easily use secure OPCUA communication to exchange variables through the internet For me, the easy I/O access and connectivity is key. How to get it To get CODESYS, you need to register yourself for free at http://store.codesys.com. After the registration you can download the programming system. Use it on Linux With some minor limitations, the programming system is running in Wine. But, as SVN and therefore cforge are not working, it has only few use cases at the moment, where it makes sense. For example, you place your project additionally on a network share to work on Linux and Windows in parallel. Then you can uae Linux for debugging and Windows to commit it in the end. For those of you, who don't have a Windows system available, you can use a trail VM from microsoft here: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ hints Please make sure that you save your projects and stuff outside of the VM when using the trail version. If you use "bridged" networking, you can easily scan your devices. Otherwhise you might need to enter the IP address in the "communication" dialog.
Last updated: 2018-12-23

<< < 1 .. 350 351 352 353 354 .. 3647 > >> (Page 352 of 3647)

Showing results of 91159

Sort by relevance or date