Member #127179

Member Since: March 28, 2010

Country: United States

  • From the description above: "With a simple upload of new firmware, the Arduino core has been ported to the PSoC5LP..."

  • I don't see anything recent with regard to comments, so thought I'd chime in:

    This board is for those with just a little more experience under their belt than needed for the basic Arduino, and who need the extra power. The Edison is, of course, way faster than the Arduino, if you need that, and has much more program and RAM memory space to work with. It accepts most shields. It works with most existing example programs, and has its own libraries for implementing them.

    So why an Edison instead of an Arduino? My reason is because I'm loading large matrices with LIDAR-Lite range data, and using large arrays in an occupancy grid for navigation and localization. Crunching big arrays to garner navigation data is very processor intensive, and speed counts. And the Arduino is useless when it comes to large arrays; memory is very limited.

    Why the Edison instead of a Pi 2, or similar? The Edison is perfectly happy running without monitor, keyboard or mouse. All similar products I've looked at take a lot of fiddling (which is difficult to figure out for relative newbies) to get them to run bare. And getting other boards like this to run applications on boot-up can be problematic, while the Edison, loaded with an Arduino sketch via the IDE, runs on reboot automatically.

    As for there not being a lot of documentation, there is plenty of that but it takes a lot of searching to find. However, when using the Intel in the Arduino mode (using the Arduino IDE), there's little to learn beyond what one already has to know to use the Arduino.

    If you don't need the speed or the memory for large amounts of data, then just stick with the Arduino Uno. But if you need an Arduino-like board that is massive by comparison, the Edison gets my vote for being the easiest overall to use.

  • Their is a serial buffer that takes in data whenever it is sent. Once it overflows, then you loose data, but it shouldn't go any farther than that. The serial buffer isn't very big, so it should overflow very quickly.

    The only thing I'm aware of that might cause a reboot is excess current draw. Checking what you might have drawing a bunch of current all at once (like one of the large Sharp IR sensors), or something that might suddenly put a big voltage spike on the line, such as a large servo or a DC motor.

  • By updating the MRAA and UPM libraries in the Eclipse IDE #include folders, the "blink" example provided in the Eclipse sample programs runs without the Segmentation Fault. For the life of me, why Intel doesn't update all their stuff is beyond me. Hate to be negative, but they must be short-handed over there. On the bright side, with everyone pitching in from the user community, the linux issues seem to be getting sorted out.

  • It appears the integers are 32 bit on the Edison Arduino IDE. Good news!

  • Yes. I just updated to the latest Yocto. Simply follow the instructions. The inner of the two MicroB ports is used for programming with the Arduino IDE. Get the latest software from here: https://communities.intel.com/docs/DOC-23242.

  • It's hard to wait for the bugs to get worked out. But it's a brand new system, and I expect it to be worth the wait.

  • If anyone finds they are able to use SPI, please explain how. I have the latest Yakto flashed, and am running the latest libraries, etc. To see the issue, just #include "SPI.h" and watch the fun!

    Update: the trick is to delete the "Robot_Control" file out of the libraries folder in the sketch folder. Then sketches which include "SPI.h" will compile. The issue is that the noted file also contains "SPI.h", probably of a different flavor. In my case, the compiler dug down to get the SPI library in "Robot_Control" instead of using the one it should have, which is up a level...

  • I answered my own question. "Serial" and "Serial1" are both supported. A simple sketch that initialized Serial1 compiled without compliant. And then there's this: https://communities.intel.com/message/258157

    My Edison is being employed on a rover bot along with a Mega. The Mega is dedicated to basic robot management and control, and sensor data gathering, while the Edison will be the high level executive taking care of a large occupancy grid for localizing and mapping, etc. The Mega is severely limited when it comes to large arrays, hence the Edison (which is also WAY faster).

  • To address TX and RX pins (pin1 and pin0 on the Uno) using the Edison-flavor Arduino IDE for serial communications, the Internet says to use Serial1. Has anyone tried communicating through serial with other devices yet?

No public wish lists :(