My experience with Intel Edison. Part I (preparatory)
Finally, he gathered his will into a fist, pushed all urgent matters aside and sat down to write about his impressions about the thing that Intel Corporation showed the world last year. I’ll try to talk about the Edison platform in several articles. More precisely, about my attempts to work with this platform. I am a learned physicist, so everything related to the subject matter of this series of publications is my hobby. I ask you in advance for condescension if something is wrong ...
Since November last year, "Edison" has been living with me. This happened after the hackathon that Intel conducted as part of promoting its vision of the Internet of Things (IoT) concept and the Galileo and Edison platforms. Herereview of this event. I note right away that working with Edison gives me much more pleasure than, for example, with Galileo, and that's why. In order for the board to come to life, you need to perform a few simple manipulations that are intelligibly described on the Intel website (there sufferers will find a lot of interesting information, including how to start Edison). You can also refer to this publication for advice.on Habré. I, following the instructions in the style of "do so," managed to start Edison the first time. But many of those who tried to use the Galileo board at the aforementioned hackathon in November, without third-party help from the expert Matthias Khan (one of the developers of the Intel IoT Dev Kit), failed to launch it, following only the instructions. Around Galileo you have to dance with a tambourine (although now the situation may have changed).
So, after the hackathon (on which I worked with Galileo) I tried to do the simplest things already with Edison. I tried it and left it for several months due to the appearance of more important cases. But this year I decided to resume experiments and periodically sit down to tinker with the board. So, I played with Edison, played, while in a couple of weeks he take it, and “break” ...
First, the libmraa library needed to use ports has stopped working. I decided to reflash the board and fill it with the latest version of the Yocto operating system (standard OS for Edison). But it was not there! The second problem turned out to be more serious - the desktop computer flatly refused to perceive Edison as an external USB drive, which has never happened before. It already seemed so serious that I was ready to throw away the old board and buy a new one.
The thing is that when you connect Edison to a computer via USB, the computer should automatically recognize Edison as an external USB drive. Files from the archive are uploaded to this drive for installing / updating the operating system, and then through the Edison console it is rebooted with a tricky command, which starts the OS installation process from the section into which the files from the archive were copied. In fact, there is a possible way to install "via USB cable" from a directory with files located on the desktop computer to which Edison is connected. The whole process, again, is described in detail on the Intel website . However, none of the suggestions worked for me.
Here I am and droop. Using the fsck command, it was possible to find out that on its flash memory, which Edison uses under the OS, there is a FAT32 partition, which, obviously, throws the OS image.
Since Edison runs on a Linux system, you just won’t get to a partition, you need to mount it first, after which you will get access to this partition as a simple folder. Since Edison is a new platform, there is not much information on the Internet on it, and the team did not give out a specific pointer to the FAT32 section. I had to search until I saw the treasured lines on this page, from which it followed that the FAT32 partition is located at / dev / disk / by-partlabel / update . Further, a technical matter: mount the partition (for this I first created the fat directory in / mnt that I will mount to),
root @ edison: ~ # mkdir / mnt / fat
root @ edison: ~ # mount / dev / disk / by-partlabel / update / mnt / fat
If you now look at the mounted partitions, it turns out that the cherished target was located at the address / dev / mmcblk0p9 , and / dev / disk / by-partlabel / update , apparently, the folder associated with it. If I knew this before, I could mount the partition file ( mount / dev / mmcblk0p9 / mnt / fat ) directly instead of the folder ( mount / dev / disk / by-partlabel / update / mnt / fat ).
Now we overload Edison in system installation mode.
root @ edison: ~ # reboot ota It
worked! After updating the system, Edison was again recognized by the stationary computer as an external USB drive. Only now, since the system was reflashed, it needs to be reconfigured (root password, wifi, etc.) with the commandconfigure_edison --setup (at this stage, you can safely return to the manuals on the official Intel website).
In the next article, I will describe my ordeal when creating web access to Edison ports.
Since November last year, "Edison" has been living with me. This happened after the hackathon that Intel conducted as part of promoting its vision of the Internet of Things (IoT) concept and the Galileo and Edison platforms. Herereview of this event. I note right away that working with Edison gives me much more pleasure than, for example, with Galileo, and that's why. In order for the board to come to life, you need to perform a few simple manipulations that are intelligibly described on the Intel website (there sufferers will find a lot of interesting information, including how to start Edison). You can also refer to this publication for advice.on Habré. I, following the instructions in the style of "do so," managed to start Edison the first time. But many of those who tried to use the Galileo board at the aforementioned hackathon in November, without third-party help from the expert Matthias Khan (one of the developers of the Intel IoT Dev Kit), failed to launch it, following only the instructions. Around Galileo you have to dance with a tambourine (although now the situation may have changed).
So, after the hackathon (on which I worked with Galileo) I tried to do the simplest things already with Edison. I tried it and left it for several months due to the appearance of more important cases. But this year I decided to resume experiments and periodically sit down to tinker with the board. So, I played with Edison, played, while in a couple of weeks he take it, and “break” ...
First, the libmraa library needed to use ports has stopped working. I decided to reflash the board and fill it with the latest version of the Yocto operating system (standard OS for Edison). But it was not there! The second problem turned out to be more serious - the desktop computer flatly refused to perceive Edison as an external USB drive, which has never happened before. It already seemed so serious that I was ready to throw away the old board and buy a new one.
The thing is that when you connect Edison to a computer via USB, the computer should automatically recognize Edison as an external USB drive. Files from the archive are uploaded to this drive for installing / updating the operating system, and then through the Edison console it is rebooted with a tricky command, which starts the OS installation process from the section into which the files from the archive were copied. In fact, there is a possible way to install "via USB cable" from a directory with files located on the desktop computer to which Edison is connected. The whole process, again, is described in detail on the Intel website . However, none of the suggestions worked for me.
Here I am and droop. Using the fsck command, it was possible to find out that on its flash memory, which Edison uses under the OS, there is a FAT32 partition, which, obviously, throws the OS image.
What the fsck command issues
root @ edison: ~ # fsck
fsck from util-linux 2.24.1
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/ dev / mmcblk0p7: 5 files, 2700/2931 clusters
e2fsck 1.42.9 (28-Dec-2013)
/ dev / mmcblk0p10 is mounted.
e2fsck: Cannot continue, aborting.
fsck from util-linux 2.24.1
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/ dev / mmcblk0p7: 5 files, 2700/2931 clusters
e2fsck 1.42.9 (28-Dec-2013)
/ dev / mmcblk0p10 is mounted.
e2fsck: Cannot continue, aborting.
Since Edison runs on a Linux system, you just won’t get to a partition, you need to mount it first, after which you will get access to this partition as a simple folder. Since Edison is a new platform, there is not much information on the Internet on it, and the team did not give out a specific pointer to the FAT32 section. I had to search until I saw the treasured lines on this page, from which it followed that the FAT32 partition is located at / dev / disk / by-partlabel / update . Further, a technical matter: mount the partition (for this I first created the fat directory in / mnt that I will mount to),
root @ edison: ~ # mkdir / mnt / fat
root @ edison: ~ # mount / dev / disk / by-partlabel / update / mnt / fat
If you now look at the mounted partitions, it turns out that the cherished target was located at the address / dev / mmcblk0p9 , and / dev / disk / by-partlabel / update , apparently, the folder associated with it. If I knew this before, I could mount the partition file ( mount / dev / mmcblk0p9 / mnt / fat ) directly instead of the folder ( mount / dev / disk / by-partlabel / update / mnt / fat ).
Now we overload Edison in system installation mode.
root @ edison: ~ # reboot ota It
worked! After updating the system, Edison was again recognized by the stationary computer as an external USB drive. Only now, since the system was reflashed, it needs to be reconfigured (root password, wifi, etc.) with the commandconfigure_edison --setup (at this stage, you can safely return to the manuals on the official Intel website).
In the next article, I will describe my ordeal when creating web access to Edison ports.