- ELO 2500UZ
- ELO 2701
ELO 2701 D68054 CTR-270100-IT-RSU-00P controller
Инструкция по установке сенсорного экрана SecureTouch и подключении его к контроллеру IT-RSU 2701 (интерфейс USB)
 |
 |
Elo Touch Screen Controller 2701
Leave a reply
Monthly Archives: August 2016
Grub + GPT partition / EFI / UEFI
Wikipedia
Unified Extensible Firmware Interface
EFI system partition
BIOS boot partition
Ubuntu
 |
 |
EFI Bootmanagement
EFI Grundlagen
EFI Installieren
EFI Nachbearbeitung
EFI Problembehebung
$ mount | grep efivars efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) $ sudo apt-get install efibootmgr $ sudo dmidecode -t 0 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.6 present. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Phoenix Technologies Ltd. Version: 02QA Release Date: 11/11/2011 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 2560 kB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) NEC PC-98 ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 0.1 $ sudo dmidecode -t 1 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.6 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 300E4A/300E5A/300E7A Version: 0.1 Serial Number: HN0J93FBC00446 UUID: 3B0E5E40-1DDD-11B2-8000-CD2AC832DD7D Wake-up Type: Power Switch SKU Number: System SKUNumber Family: HuronRiver System $ sudo efibootmgr -v BootCurrent: 0008 Timeout: 0 seconds BootOrder: 0008,0003,0005,0006,0007,0009 Boot0000 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0001 Boot Menu FvFile(86488440-41bb-42c7-93ac-450fbf7766bf) Boot0002 Recovery FvFile(ab4579c4-3bc5-4489-a88e-0f21e6cebf85) Boot0003* SATA CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354) Boot0004* CD-ROM: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,be9d0102e211f3489efa0b983c96839b) Boot0005* SATA HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600) Boot0006* USB CD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot0007* USB FDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot0008* USB HDD: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot0009* NETWORK: VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) $ sudo parted -l Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start End Size File system Name Flags 3 1049kB 269MB 268MB gpt-boot 4 269MB 286MB 16.8MB fat16 gpt-grub msftdata 1 108GB 119GB 10.5GB ext4 linux-root 2 119GB 120GB 1074MB linux-swap(v1) linux-swap Warning: The driver descriptor says the physical block size is 2048 bytes, but Linux says it is 512 bytes.
grub-efi-amd64-signed
# apt-get install shim-signed Reading package lists... Done Building dependency tree Reading state information... Done shim-signed is already the newest version (1.18~16.04.1+0.8-0ubuntu2). 0 upgraded, 0 newly installed, 0 to remove and 328 not upgraded. 2 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory) Setting up grub-efi-amd64-signed (1.66.2+2.02~beta2-36ubuntu3.2) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. dpkg: error processing package grub-efi-amd64-signed (--configure): subprocess installed post-installation script returned error exit status 1 Setting up shim-signed (1.18~16.04.1+0.8-0ubuntu2) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. <======= dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: grub-efi-amd64-signed shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1)
boot-repair
 |
Erich Styger (mcuoneclipse.com)
Teensy USB Development Board
Ultimaker Cura
MSYS2 / mingw-w64-x86_64
MSYS2 vs. MinGw64
MSYS vs. MinGW: internal environment variables
$ uname MSYS_NT-10.0 $ uname MINGW64_NT-10.0
Package Manager
$ pacman -Q <list all packages> $ pacman -Qi <package> <info about a single package> $ pacman -Ql <package> <files of a single package>
Pin to Taskbar
$ pacman -S msys2-launcher $ pacman -Qi msys2-launcher Name : msys2-launcher-git Version : 0.3.32.56c2ba7-2 Description : Helper for launching MSYS2 shells Architecture : x86_64 URL : None Licenses : MIT Groups : base Provides : msys2-launcher Depends On : mintty>=1~2.2.1 Optional Deps : None Required By : None Optional For : None Conflicts With : msys2-launcher Replaces : None Installed Size : 157.00 KiB Packager : Alexey Pavlov <alexpux@gmail.com> Build Date : Wed, Sep 7, 2016 7:59:07 PM Install Date : Thu, Apr 18, 2019 9:46:39 PM Install Reason : Explicitly installed Install Script : No Validated By : Signature $ pacman -Ql msys2-launcher msys2-launcher-git /mingw32.exe msys2-launcher-git /mingw32.ini msys2-launcher-git /mingw64.exe msys2-launcher-git /mingw64.ini msys2-launcher-git /msys2.exe msys2-launcher-git /msys2.ini
Update
MinGW coding under Windows (C, C++, OpenMP, MPI)
openFrameworks: msys2
$ pacman -Syu $ pacman -Su $ pacman -S base-devel $ pacman -S mingw-w64-x86_64-toolchain $ pacman -S git
fwrite()
fwrite() c function writing extra bytes
The difference in File access mode “w” and “wb”
// linux doesn't care... but windows does! FILE *fp = fopen(filename, "w"); // text mode // if streams includes 0x0A (\n) it prepends it with 0x0D (\r) FILE *fp = fopen(filename, "wb"); // binary mode
Keyring
Problem
$ pacman -Syu :: Synchronizing package databases... mingw32 mingw32.sig error: mingw32: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown error: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely error: failed to update mingw32 (invalid or corrupted database (PGP signature)) mingw64 mingw64.sig error: mingw64: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown error: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely error: failed to update mingw64 (invalid or corrupted database (PGP signature)) msys msys.sig error: msys: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" is unknown error: key "5F944B027F7FE2091985AA2EFA11531AA0AA7F57" could not be looked up remotely error: failed to update msys (invalid or corrupted database (PGP signature)) error: failed to synchronize all databases
Solution
# rm -r /etc/pacman.d/gnupg/ # pacman-key --init # pacman-key --populate msys2 $ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz $ curl -O http://repo.msys2.org/msys/x86_64/msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz.sig # pacman -U --config <(echo) msys2-keyring-r21.b39fb11-1-any.pkg.tar.xz $ pacman -Syu :: Synchronizing package databases... mingw32 is up to date mingw64 is up to date msys is up to date :: Starting core system upgrade... [...]
arm-none-eabi
mingw-w64-arm-none-eabi-newlib
MINGW-packages wiki
MSYS2-packages
$ git clone https://github.com/Alexpux/MINGW-packages.git
$ cd ~/MINGW-packages/mingw-w64-arm-none-eabi-binutils/
$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf
$ pacman -U mingw-w64-x86_64-arm-none-eabi-binutils-2.24-1-any.pkg.tar.xz
$ cd ~/MINGW-packages/mingw-w64-arm-none-eabi-gcc/
$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf
==> Making package: mingw-w64-gcc 4.8.4-1 (Sun, Mar 5, 2017 9:50:40 AM)
==> Checking runtime dependencies...
==> Installing missing dependencies...
error: target not found: mingw-w64-x86_64-arm-none-eabi-newlib
==> ERROR: 'pacman' failed to install missing dependencies.
$ cd ~/MINGW-packages/mingw-w64-arm-none-eabi-newlib/
$ MINGW_INSTALLS=mingw64 makepkg-mingw -sLf
==> Making package: mingw-w64-newlib 2.1.0-1 (Sun, Mar 5, 2017 9:51:25 AM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
[...]
/bin/sh ../../gcc/gcc/../move-if-change tmp-mlib.h multilib.h
echo timestamp > s-mlib
rm cpp.pod gcov.pod fsf-funding.pod gfdl.pod
make[1]: Leaving directory '/home/bachman0/MINGW-packages/mingw-w64-arm-none-eabi-newlib/src/build-gcc-x86_64-w64-mingw32/gcc'
make: *** [Makefile:3892: all-gcc] Error 2
==> ERROR: A failure occurred in prepare().
Aborting...
List of files installed by a package
$ pacman -Ql mingw-w64-x86_64-arm-none-eabi-binutils [...] mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-addr2line.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-ar.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-as.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-ld.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-objcopy.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-objdump.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-readelf.exe mingw-w64-x86_64-arm-none-eabi-binutils /mingw64/bin/arm-none-eabi-strip.exe [...]
MSYS2 consists of three subsystems and their corresponding package repositories, msys2, mingw32, and mingw64.
The mingw subsystems provide native Windows programs and are the main focus of the project. These programs are built to co-operate well with other Windows programs, independently of the other subsystems.
The msys2 subsystem provides an emulated mostly-POSIX-compliant environment for building software, package management, and shell scripting. These programs live in a virtual single-root filesystem (the root is the MSYS2 installation directory). Some effort is made to have the programs work well with native Windows programs, but it’s not seamless.
Each of the subsystems provides its own native (i.e. target=host) compiler toolchain, in msys2-devel, mingw-w64-i686-toolchain, and mingw-w64-x86_64-toolchain. There are also cross compiler toolchains with host={i686,x86_64}-pc-msys and target={i686,x86_64}-w64-mingw32 in mingw-w64-cross-toolchain, but these are of limited use because there are no library packages for them.
Every subsystem has an associated “shell”, which is essentially a set of environment variables that allow the subsystems to co-operate properly. These shells can be invoked using scripts in the MSYS2 installation directory or shortcuts in the Start menu. The scripts set the MSYSTEM variable and start a terminal emulator with bash. Bash in turn sources /etc/profile which sets the environment depending on the value of MSYSTEM.
Update MSYS2
ssh not finding ssh config or IdentityFile
$ pacman -Sy
:: Synchronisiere Paketdatenbanken...
mingw32 291,3 KiB 867K/s 00:00 [#####################] 100%
mingw32.sig 96,0 B 0,00B/s 00:00 [#####################] 100%
mingw64 290,9 KiB 1672K/s 00:00 [#####################] 100%
mingw64.sig 96,0 B 0,00B/s 00:00 [#####################] 100%
msys 135,6 KiB 11,0M/s 00:00 [#####################] 100%
msys.sig 96,0 B 0,00B/s 00:00 [#####################] 100%
$ pacman --needed -S bash pacman msys2-runtime
(1/3) Aktualisiere msys2-runtime [#####################] 100%
(2/3) Aktualisiere bash [#####################] 100%
(3/3) Aktualisiere pacman [#####################] 100%
$ exit
$ pacman -Su
:: Starting core system upgrade...
[...]
WARNING: the shell starting scripts have been unified. Please update your
shortcuts to the following targets, otherwise they will STOP WORKING:
* MSYS2_ROOT\msys2_shell.cmd -mingw32
* MSYS2_ROOT\msys2_shell.cmd -mingw64
* MSYS2_ROOT\msys2_shell.cmd -msys
[...]
$ exit
Update Links => .bat to .cmd
$ pacman -S openssh
$ pacman -S git
$ pacman -h -S
Verwendung: pacman {-S --sync} [Optionen] [Paket(e)]
Optionen:
-b, --dbpath <Pfad> Setzt einen anderen Ort für die Datenbank
-c, --clean Entfernt alte Pakete aus dem Paketpuffer (-cc für alle)
-d, --nodeps Überspringt die Versionsüberprüfungen für Abhängigkeiten (-dd um alle Überprüfungen zu überspringen)
-g, --groups Zeigt alle Mitglieder einer Paket-Gruppe an
(-gg um alle Gruppen samt Mitgliedern anzuzeigen)
-i, --info Zeigt Paketinformationen an (-ii für erweiterte Informationen)
-l, --list <repo> Zeigt eine Liste aller Pakete eines Repositoriums an
-p, --print Zeigt die Ziele an, statt die Operation auszuführen
-q, --quiet Zeigt weniger Information bei Abfragen und Suche an
-r, --root <Pfad> Setzt ein alternatives Wurzelverzeichnis zur Installation
-s, --search <regex> Durchsucht entfernte Repositorien nach einem Wort
-u, --sysupgrade Aktualisiert installierte Pakete (-uu ermöglicht Downgrades)
-v, --verbose Sei gesprächig
-w, --downloadonly Lädt Pakete herunter, ohne etwas zu installieren oder aktualisieren
-y, --refresh Lädt aktuelle Paketdatenbanken vom Server herunter
(-yy um eine Aktualisierung auch bei aktuellen Datenbanken durchzuführen)
--arch <arch> Setzt eine alternative Architektur
--asdeps Installiert Pakete als nicht-ausdrücklich installiert
--asexplicit Installiert Pakete als ausdrücklich installiert
--assume-installed <package=version>
Fügt ein virtuelles Paket hinzu, um Abhängigkeiten zu erfüllen
--cachedir <Verzeichnis> Setzt einen anderen Ort für den Paketpuffer
--color <wann> Ausgabe farbig darstellen
--config <Pfad> Setzt eine alternative Konfigurationsdatei
--confirm Immer nach einer Bestätigung fragen
--dbonly Verändert nur Datenbank-Einträge, keine Paketdateien
--debug Zeigt Debug-Meldungen an
--force Installation erzwingen, Dateikonflikte überschreiben
--gpgdir <path> Setzt alternatives Konfigurationsverzeichnis für GnuPG
--hookdir <dir> setze ein anderes Hook-Verzeichnis
--ignore <pkg> Ignoriert ein neues Paket (kann mehrfach genutzt werden)
--ignoregroup <grp>
Ignoriert Upgrade einer Gruppe (kann mehrfach genutzt werden)
--logfile <Pfad> Setzt eine alternative Log-Datei
--needed Installiert aktuelle Pakete nicht erneut
--noconfirm Niemals nach einer Bestätigung fragen
--noprogressbar Keine Fortschrittsanzeige anzeigen, wenn Dateien heruntergeladen werden
--noscriptlet Installationsskript nicht ausführen, falls vorhanden
--print-format <string>
Legt fest, wie die Ziele ausgegeben werden sollen
C:\msys64\msys2_shell.bat’ is not recognized as an internal or external command
Current installer/installation instructions are broken
==> update links. Don’t use msys2_shell.bat but msys2_shell.cmd
Install Python NumPy
Practical Computing for Biologists – Setting up Windows and Linux
# download MSYS2 (Arch Linux)
https://msys2.github.io/
# Choose the version that says x86_64, not i686
# Update system
pacman --needed -Sy bash pacman pacman-mirrors msys2-runtime
# Restart MSYS
# (Close all windows and reopen from start menu)
# All Programs > MSYS2 64-bit > MSYS Shell
pacman -Su
# You might get some errors. If so, just run the command again and it should pick up the slack.
#install python and other utilities
# REQUIRED
pacman --noconfirm -S gcc python2 man nano sqlite vim git bc tar
# This can take a while to download
# Note: To search for other package locations, use
pacman -Ss <package_name>
Then to install, copy the name (before the version number) after a pacman -Sy command...
# issues: sudo and screen not there in default pacman...
# NEXT you should do these commands:
cd /usr/bin
ln -sf python2 python
cd
# Then install pip using these steps:
mkdir ~/scripts
cd ~/scripts
curl -O 'https://bootstrap.pypa.io/get-pip.py'
./get-pip.py
# If that succeeds (which pip should now find something)
then..
rm get-pip.py
# Now to use the installer for grabbing python packages like numpy, Biopython, and beautifulSoup:
pip install numpy
##########################
Working in MSYS2
Your home directory, as we refer to it in the book, will be /home/lucy in the terminal window, but it lives in the c:\msys32 (or msys64) folder. You could make a shortcut from the folder here with our username to the Windows desktop for easy cross-platform access.
# MSYS2 starts with an annoying multi-line prompt, so edit your .bash_profile using this command
nano ~/.bash_profile
# Note that <ctrl>C will not work for copying in the terminal, because it has another function.
# Right click to copy/paste from the pop-up menu
# Add the following four lines to your .bash_profile
PS1='\[\e[1;32m\]\u:\[\e[1;36m\]\w \$ \e[0m'
export PATH=$PATH:$HOME/scripts
export EDITOR=/usr/bin/nano
set -o noclobber
################################
Next, in Windows, install the GUI
Install <a href="http://www.sublimetext.com/3">Sublime Text 3</a>
After installation, Change color scheme to iPlastic
To get the command-line option (so you can edit files from the terminal by typing 'subl' google the page about changing your System Path to work with Sublime Text 3.
##############################
Difference between native python and mingw-w64 python.
Numpy Mingw w64 FAQ
Anaconda – open data science platform
Conda – open source package management system
Install mingw-w64-x86_64 packages
$ pacman -S mingw-w64-x86_64-python3 [...] (24/24) checking for file conflicts [####################################################################] 100% error: failed to commit transaction (conflicting files) mingw-w64-x86_64-gmp: /mingw64 exists in filesystem [...]
Msys2 + Windows 10 + pacman errors
$ mkdir /mingw64
Change language
$ export LC_ALL=en_US.UTF-8
No C Compiler installed
$ python3 setup.py install
running install
running build
running build_py
creating build
creating build/lib.mingw-3.5
creating build/lib.mingw-3.5/bigfloat
copying bigfloat/context.py -> build/lib.mingw-3.5/bigfloat
copying bigfloat/core.py -> build/lib.mingw-3.5/bigfloat
copying bigfloat/ieee.py -> build/lib.mingw-3.5/bigfloat
copying bigfloat/rounding_mode.py -> build/lib.mingw-3.5/bigfloat
copying bigfloat/__init__.py -> build/lib.mingw-3.5/bigfloat
creating build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/test_bigfloat.py -> build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/test_context.py -> build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/test_mpfr.py -> build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/test_rounding_mode.py -> build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/test___all__.py -> build/lib.mingw-3.5/bigfloat/test
copying bigfloat/test/__init__.py -> build/lib.mingw-3.5/bigfloat/test
running build_ext
Traceback (most recent call last):
File "setup.py", line 267, in <module>
'bigfloat.test',
File "C:/msys64/mingw64/lib/python3.5\distutils\core.py", line 148, in setup
dist.run_commands()
[...]
File "C:/msys64/mingw64/lib/python3.5\distutils\ccompiler.py", line 1033, in new_compiler
return klass(None, dry_run, force)
File "C:/msys64/mingw64/lib/python3.5\distutils\cygwinccompiler.py", line 288, in __init__
CygwinCCompiler.__init__ (self, verbose, dry_run, force)
File "C:/msys64/mingw64/lib/python3.5\distutils\cygwinccompiler.py", line 127, in __init__
if self.ld_version >= "2.10.90":
TypeError: unorderable types: NoneType() >= str()
$ pacman -S mingw-w64-x86_64-gcc
$ python3 setup.py install
running install
running build
running build_py
running build_ext
building 'mpfr' extension
creating build/temp.mingw-3.5
C:\msys64\mingw64\bin/x86_64-w64-mingw32-gcc.exe -Wno-unused-result -Wsign-compare -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fwrapv -D__USE_MINGW_ANSI_STDIO=1 -DNDEBUG -IC:/msys64/mingw64/include/python3.5m -c mpfr.c -o build/temp.mingw-3.5/mpfr.o
[...]
Writing C:/msys64/mingw64/lib/python3.5/site-packages/bigfloat-0.3.0-py3.5.egg-info
pacman install build system for mingw-w64-x86_64
$ pacman -S mingw-w64-x86_64-gcc $ pacman -S mingw-w64-x86_64-gdb
pacman query
How can I show the list of all installed packages in Arch Linux (pacman packet manager)?
-Q, --query
Query the package database.
This operation allows you to view installed packages
and their files, as well as meta-information about
individual packages
-i, --info
Display information on a given package.
-s, --search <regexp>
Search each locally-installed package for names or
descriptions that match regexp.
$ pacman -Qi mingw-w64-x86_64-python3
Name : mingw-w64-x86_64-python3
Version : 3.5.2-2
$ pacman -Qs python
local/mingw-w64-x86_64-python3 3.5.2-2
A high-level scripting language (mingw-w64)
local/mingw-w64-x86_64-python3-cairo 1.10.0-5
Python2 bindings for the cairo graphics library (mingw-w64)
local/mingw-w64-x86_64-python3-cycler 0.9.0-1
Composable style cycles
[...]
$ pacman -Ss xpdf
mingw32/mingw-w64-i686-poppler 0.76.1-1
PDF rendering library based on xpdf 3.0 (mingw-w64)
mingw32/mingw-w64-i686-xpdf 4.00-1
Utilities for PDF files (mingw-w64)
mingw64/mingw-w64-x86_64-poppler 0.76.1-1
PDF rendering library based on xpdf 3.0 (mingw-w64)
mingw64/mingw-w64-x86_64-xpdf 4.00-1
Utilities for PDF files (mingw-w64)
[...]
$ pacsearch python2
$ pacman -R mingw-w64-x86_64-arm-none-eabi-binutils
MSYS2 Shell vs MinGW-w64 Shell
MSYS2 Shell or MinGW-w64 Shell
MSYS2-Introduction
How does MSYS2 differ from Cygwin?
MSYS2
MSYS2 is based on Cygwin and knows how to understand POSIX conventions like paths (/usr/bin/, /etc) as well as special devices like /dev/null, /dev/clipboard, etc and many other things. MSYS2 comes with a GCC toolchain who will produce native binaries that are always tied to msys-2.0.dll. It’s that DLL that does all the magic of interoperability between POSIX conventions and Windows. It’s because of it that it’s possible to use a Unix like path /home/joe/ and pass it to a Windows and it still works.
Indeed, (I’m not sure of the exact details) but when when msys-2.0.dll
sees you are calling a native Windows executables (one that does not
depends on msys-2.0.dll), it will convert the path /home/joe/ to a
Windows path like C:\Users\joe that the native Windows program receives
and knows how to understand. Without this translation, the Windows program
would receive /home/joe/ and wouldn’t understand how to treat it
correctly. All this paths translations applies also to environment
variables.
This process (and all the POSIX emulation layer) incurs a performance
penalty that can be significant for heavy file-centric software. Git is a
good example and that’s why the MSYS2 git package (msys/git) is slower
than a native git client like the one provided by Git For Windows
(git-for-windows/mingw-w64-x86_64-git). That’s why a native program (read
a MINGW one) is usually “better” than an MSYS2 one. Don’t be afraid of
using pure MSYS2 program, in most cases (I would say 90%), the difference
is not significant because bottleneck is not the filesystem (CPU, network,
other).
That’s why you will often read that MSYS2 is only a way to make it easier
to build and deploy MINGW native executables. In my personal opinion and
the way I use it, it’s much much more than that as I use and build little
MINGW tools. MSYS2 is a full subsystem dealing with way more than just a
toolchain as it deals with filesystem, users, permissions (to an extent)
and much more. I use it mainly because it has the same toolset as the one
I’m used on Linux (console-based of course :)).
Because MSYS2 understands POSIX and has a pretty good emulation layer, it
is often very easy to port a package originally built on Linux to it,
because almost no code work is needed.
MINGW
MINGW (either 32 or 64) is a set of toolchain to build native Windows
program. Those program do not depends on msys-2.0.dll and depends rather
on MSVC runtime. Those don’t understand POSIX paths, so if you pass
/home/joe outside of an MSYS2 shells (from pure cmd for example), it will
not understand it. Indeed, in pure cmd (and via many interactions from
other programs), no translation of paths is performed.
MINGW toolchains are based on mingw-w64 which
provides the ground work to compile them. They are available in pacman for
installation and they also contains GCC et related tools (binutils, ld).
When invoked, GCC produces pure native executable. So, when working with a
MINGW program, remember that it’s like a native Window program that knows
nothing about MSYS2.
MSYS2 happens to actual provides those toolchains directly to you
pre-compiled via pacman. Note however, that it’s possible to download the
mingw-w64 toolchains in standalone, put them somewhere and invoke them
afterward in MSYS2 (by proprely configuring PATH and other variables
yourself). They can also be invoked via cmd directly because they do not
depend on MSYS2 at all.
Shells
When you start any of the MSYS2 shells, they all start an MSYS2 bash
program. Since it’s a MSYS2 bash, it understands Unix paths and will do
translation when calling native Windows executables.
That being said, what is the difference between all the shells? It all
about the tweaking some environment variables to change default programs
picked when calling them. It’s mainly about the PATH environment variable
but it also involves MSYSTEM PKG_CONFIG_PATH ACLOCAL_PATH MANPATH like Ray
said earlier. Checkout /etc/profile around line 28 to see the conditional
that sets all this.
Let’s assume you have installed three toolchains:
* MSYS2 (package group msys2-devel) to compile MSYS2 tools which
installs gcc in /usr/bin.
* MINGW32 (package group mingw-w64-i686-toolchain) to compile Windows
native 32 bits executable which installs gcc in /mingw32/bin.
* MINGW64 (package group mingw-w64-x86_64-toolchain) to compile
Windows native 64 bits executable which installs gcc in /mingw64/bin.
For msys2_shell, PATH is roughly only /usr/local/bin:/usr/bin:/bin. This
means that when running gcc, you will get /usr/bin/gcc.
For mingw32_shell, PATH is roughly
/mingw32/bin:/usr/local/bin:/usr/bin:/bin. This means that now, running
gcc you will get instead /mingw32/bin/gcc.
For mingw64_shell, PATH is roughly
/mingw64/bin:/usr/local/bin:/usr/bin:/bin and as you have guessed,
running gcc you will get instead /mingw64/bin/gcc.
This means that all three shells have the same capabilities, but because of
the different orders, tools that will be picked are different. So, if you
want to compile something, use the appropriate shell for what you want to
do (MSYS2 program, Windows native 32 bits or Windows native 64 bits).
If you are not compiling anything, then it depends. Usually, msys2_shell is
recommended. However, on a bare installation, /mingw64/bin is not added
anywhere when using msys2_shell, problem it can causes is that if you had
installed mingw64 packages, they are not available in the shell. In my
case, I have tweaked by .bash_profile to correctly add /mingw64/bin
after PATH (like /usr/local/bin:/usr/bin:/bin:/mingw64/bin). This
always favor MSYS2 tools but will pick /mingw64/bin when they don’t exist
in MSYS2 /usr/bin.
LoRa Gateway IMST iC880A
Internet of Things (IoT) Protocols & Standards
IMST LoRa Products
ttn-zh/ic880a-gateway/wiki
iC880A-SPI QuickStart Guide
Raspbian Jessie Lite
NiceRF
Blog Posts and Tutorials
absolutelyautomation.com
instructables.com: Arduino Internet Of Things (IoT) Using NiceRf LoRa1276
Internet Of Things (IoT) Using NiceRf LoRa1276
INTERNET OF THINGS USING NICERF LORA1276 (PDF)
YouTube: Internet Of Things IoT Using NiceRf LoRa1276 (Video)
Jordi Binefa’s blog
Arduino library for SX1276 using LoRA and PyQt
ESP8266 and Arduino using LoRa and AES encryption
Adding AES encryption to LoRa at SX1276 on Arduino
IoT Blog
Hands on with LoRa in North America. #1
Hands on with LoRa in North America. #2
Hands on with LoRa in North America. #3
Connect Conduit to TTN LoRaWan via Poly Packet Fwd
IoT Gateways Review
Air Quality Index – Part 1
Air Quality Index – Part 2; LoRaWan Sensor
Hands On with RM7201 & RM7601 LoRa modules by Dapu Telecom
LoRa Hybrid Mode and FCC regulations
Marketing in the Era of the Internet of Things
Race for the IoT connectivity standard
Arduino Libraries
Dapu Telecom dptel.com
RM-7200/RM-7201
RM-7600/RM-7601
CeBIT: Dapu Telecom Technology
CeBIT: RM-7200/7201
github: Lora-net
Lora-net/lora_gateway
Lora-net/packet_forwarder
Lora-net/LoRaMac-node
github: TheThingsNetwork
TheThingsNetwork/packet_forwarder
github: cheristi
Downlink
Problem with LoRaWAN Downlink
Example of how to call the LoRaMacPayloadDecrypt function ?
Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: *** Poly Packet Forwarder for Lora Gateway *** Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: Version: 2.1.0 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: *** Lora concentrator HAL library version info *** Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: Version: 3.1.0; Options: native; Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: *** Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Little endian host Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: found global configuration file global_conf.json, parsing it Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: lorawan_public 1, clksrc 1 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Configuring TX LUT with 16 indexes Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: radio 0 enabled (type SX1257), center frequency 867500000, RSSI offset -166.000000, tx enabled 1 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: radio 1 enabled (type SX1257), center frequency 868500000, RSSI offset -166.000000, tx enabled 0 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 0> radio 1, IF -400000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 1> radio 1, IF -200000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 2> radio 1, IF 0 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 3> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 4> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:54 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 5> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 6> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Lora multi-SF channel 7> radio 0, IF 400000 Hz, 125 kHz bw, SF 7 to 12 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: gateway MAC address is configured to AA555A0000000000 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Found 2 servers in array. Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Server 0 configured to "127.0.0.1", with port up "1680" and port down "1681" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Server 1 configured to "iot.semtech.com", with port up "1680" and port down "1680" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Found 5 system calls in array. Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: System command 0: "df -m" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: System command 1: "free -h" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: System command 2: "uptime" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: System command 3: "who -a" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: System command 4: "uname -a" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: monitor hostname or IP address is configured to "127.0.0.1" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: monitor port is configured to "2008" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: ghost hostname or IP address is configured to "127.0.0.1" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: ghost port is configured to "1918" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: downstream keep-alive interval is configured to 10 seconds Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: statistics display interval is configured to 30 seconds Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: upstream PUSH_DATA time-out is configured to 100 ms Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with a valid CRC will be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with a CRC error will NOT be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with no CRC will NOT be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: GPS serial port path is configured to "/dev/ttyAMA0" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: SSH path is configured to "/usr/bin/ssh" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: SSH port is configured to 22 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: HTTP port is configured to 80 Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: NGROK path is configured to "/usr/bin/ngrok" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Reference latitude is configured to 10.000000 deg Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Reference longitude is configured to 20.000000 deg Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Reference altitude is configured to -1 meters Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: GPS is enabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Using fake GPS coordinates instead of real. Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Upstream data is enabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Downstream data is enabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Ghoststream data is disabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Radiostream data is enabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Statusstream data is enabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Beacon is disabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Monitor is disabled Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Platform configured to "IMST + Rpi" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Contact email configured to "operator@gateway.tst" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Description configured to "Update me" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: found local configuration file local_conf.json, parsing it Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: redefined parameters will overwrite global parameters Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: local_conf.json does not contain a JSON object named SX1301_conf Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: gateway MAC address is configured to B827EBFFFE4CECFD Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Found 1 servers in array. Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Server 0 configured to "router.eu.thethings.network", with port up "1700" and port down "1700" Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with a valid CRC will be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with a CRC error will NOT be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: packets received with no CRC will NOT be forwarded Feb 19 17:50:55 ttn-gateway ttn-gateway[324]: INFO: Reference latitude is configured to 47.490301 deg Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Reference longitude is configured to 8.752050 deg Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Reference altitude is configured to 500 meters Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: GPS is enabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Upstream data is enabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Downstream data is enabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Ghoststream data is disabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Radiostream data is enabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Statusstream data is enabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Beacon is disabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Monitor is disabled Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Contact email configured to "bachi@te-clan.ch" Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Description configured to "ttn-ic880a" Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: Successfully contacted server router.eu.thethings.network Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [main] Starting the concentrator Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [main] concentrator started, radio packets can now be received. Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] Thread activated for all server router.eu.thethings.network Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [up] Thread activated for all servers. Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### 2017-02-19 16:51:28 GMT ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [UPSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets received by concentrator: 1 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets forwarded: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA datagrams sent: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA acknowledged: 0.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [DOWNSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_DATA sent: 3 (100.00% acknowledged) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_RESP(onse) datagrams received: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets sent to concentrator: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # TX errors: 0 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [GPS] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Invalid gps time reference (age: 1487523088 sec) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Manual GPS coordinates: latitude 47.49030, longitude 8.75205, altitude 500 m Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### END ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 47 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### 2017-02-19 16:51:58 GMT ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [UPSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets received by concentrator: 0 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets forwarded: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA datagrams sent: 1 (219 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA acknowledged: 100.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [DOWNSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_DATA sent: 3 (100.00% acknowledged) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_RESP(onse) datagrams received: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets sent to concentrator: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # TX errors: 0 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [GPS] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Invalid gps time reference (age: 1487523118 sec) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Manual GPS coordinates: latitude 47.49030, longitude 8.75205, altitude 500 m Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### END ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 49 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### 2017-02-19 16:52:28 GMT ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [UPSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets received by concentrator: 2 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # CRC_OK: 0.00%, CRC_FAIL: 100.00%, NO_CRC: 0.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets forwarded: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA datagrams sent: 1 (221 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA acknowledged: 100.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [DOWNSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_DATA sent: 3 (100.00% acknowledged) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_RESP(onse) datagrams received: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets sent to concentrator: 0 (0 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # TX errors: 0 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [GPS] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Invalid gps time reference (age: 1487523148 sec) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # Manual GPS coordinates: latitude 47.49030, longitude 8.75205, altitude 500 m Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### END ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ##### 2017-02-19 16:52:58 GMT ##### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [UPSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets received by concentrator: 1 Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # RF packets forwarded: 1 (23 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA datagrams sent: 2 (463 bytes) Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PUSH_DATA acknowledged: 100.00% Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: ### [DOWNSTREAM] ### Feb 19 17:52:58 ttn-gateway ttn-gateway[324]: # PULL_DATA sent: 3 (100.00% acknowledged) Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: # PULL_RESP(onse) datagrams received: 0 (0 bytes) Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: # RF packets sent to concentrator: 0 (0 bytes) Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: # TX errors: 0 Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: ### [GPS] ### Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: # Invalid gps time reference (age: 1487523178 sec) Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: # Manual GPS coordinates: latitude 47.49030, longitude 8.75205, altitude 500 m Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: ##### END ##### Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network serv_addr[ic]PULL_RESP received :) Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [down] a packet will be sent on timestamp value 125951067 Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:39 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: ##### 2017-02-19 16:53:28 GMT ##### Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: ### [UPSTREAM] ### Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # RF packets received by concentrator: 23 Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # CRC_OK: 100.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00% Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # RF packets forwarded: 23 (322 bytes) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # PUSH_DATA datagrams sent: 24 (5511 bytes) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # PUSH_DATA acknowledged: 100.00% Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: ### [DOWNSTREAM] ### Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # PULL_DATA sent: 3 (100.00% acknowledged) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # PULL_RESP(onse) datagrams received: 1 (197 bytes) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # RF packets sent to concentrator: 1 (33 bytes) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # TX errors: 0 Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: ### [GPS] ### Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # Invalid gps time reference (age: 1487523208 sec) Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: # Manual GPS coordinates: latitude 47.49030, longitude 8.75205, altitude 500 m Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: ##### END ##### Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:53:40 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [down] for server router.eu.thethings.network PULL_ACK received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 46 ms Feb 19 17:54:28 ttn-gateway ttn-gateway[324]: INFO: [up] PUSH_ACK for server router.eu.thethings.network received in 47 ms
Kieferorthopädie
Fuchsia / Magenta OS
Fuchsia is Google’s latest operating system
- Pink + Purple == Fuchsia
- LittleKernel (LK)
- Magenta
- FreeRTOS
- ThreadX
FreeRTOS
ThreadX
googlesource: Fuchsia
googlesource: Magenta and LK
github: Fuchsia
github: LittleKernel (LK)
Hex-Rays IDA Pro
Current Version: IDA v6.9 (21.12.2015)
Current Version: IDA v7.0.1 (18.09.2018)
Currently IDA Pro is a 32-bit application. One year later (in the first quarter of 2017) we will switch to 64-bit. Please note that this means that IDA Pro will not run on 32-bit systems after the transition.
News (like current version)
Executive Summary: IDA Pro – at the cornerstone of IT security
What is IDA Pro?
- IDA Pro is a disassembler
- IDA Pro is a debugger
- IDA Pro is interactive
- IDA Pro is programmable
How is IDA Pro useful?
- Hostile Code analysis
- Vulnerability research
- COTS validation
- Privacy protection
Debugger
Host:
- Windows
- Linux
- Mac OS X
Target:
- Windows
- Linux
- Mac OS X
Debugger
- Remote GDB debuggger
- Remote Linux debugger
Remote Linux debugger:
Remote debugging with IDA PRO 7.0
C:\Program Files\IDA 7.0\dbgsrv
Decompiler (Binary => C Code)
- x86 decompiler (32-bit code)
- x64 decompiler (64-bit code)
- ARM decompiler (32-bit code)
- ARM64 decompiler (64-bit code)
IDA Pro Book, 2nd Edition, No Starch Press
Hex-Rays IDA
Hex-Rays IDA Order
Documents
Digital Genome Mapping – Advanced Binary Malware Analysis, PDF
Books
- Practical Malware Analysis, 2012, Michael Sikorski, Andrew Honig
- The IDA Pro book, 2008, Chris Eagle
- Reverse Engineering Code with IDA Pro, Justin Ferguson, Jason Larsen, Luis Miras, Walter Pearce
Blog
Installing IDA 6.9 on Linux
Decompilation gets real
Developers
- Ilfak Guilfanov (Wikipedia)
- Igor Skochinsky
- Arnaud Diederen
Keyboard Shortcuts
Enter = Jump to operand Ctrl-X = List Cross-Reference
Contest
Plug-Ins
Unicorn – The ultimate CPU emulator
Unicorn & QEMU
github.com/cseagle/sk3wldbg, Debugger plugin for IDA Pro backed by the Unicorn Engine
github.com/alexhude/uEmu, Tiny cute emulator plugin for IDA based on unicorn
github.com/unicorn-engine/unicorn/tree/master/qemu
CPU Emulators
- Unicorn, Next Generation CPU Emulator (fork of QEMU)
- QEMU
- libemu
- PyEmu
- IDA-x86emu
- libCPU
Re-Assembler
Recompile the asm file IDA pro created
generate_nasm.idc
IDA pro asm instructions change
Why there are not any disassemblers that can generate re-assemblable asm code?
Modifying and Saving in IDA
- OllyDBG (Wikipedia)
- LordPE
- GNU Binutils objdump
- objconv
Modify Assembler
Applied IDA Pro: Part 1 – Applied Cracking & Byte Patching with IDA Pro
Applied IDA Pro: Part 2 – Applied Reverse Engineering with IDA Pro
OllyDBG
Other debuggers
Is there any disassembler to rival IDA Pro?
best alternatives to IDA, Immunity and Ollydbg
x64dbg (Github)
radare2 (Github)
Bokken (GUI for Radare2)
Snowman (Github)
Vdb / Vivisect (Github)