Segmentation fault Using example 3_c_onboard_LED_blink

[Mike_M_3]

I opened the example "3_c_onboard_LED_blink" in eclipse, changed nothing to it. Built it and executed it.

In the console window i received the following. Not sure what a Segmentation fault is.

root@edison:~#
echo $PWD'>'
/home/root>
root@edison:~#
root@edison:~# chmod 755 /tmp/3_c_onboard_LED_blink;/tmp/3_c_onboard_LED_blink;e
xit
Welcome to libmraa
 Version: v0.5.0-12-g3898182
 Running on Some weird devboard that isn't recognised...
Segmentation fault

[David_B_7]

My bad, I thought you were using Python as that is what I tried to the same effect.  Oh well, we shall wait.

Mike M. wrote:

If your not using the Arduino board, And try to access the GPIO using libmraa It will compile just fine, but when you try to run it you will get a "Segmentation fault" in the terminal window and it just stops. So for now we have to wait until they fix it.

[Matthias_H_Intel]

David B. wrote:

 Oh well, we shall wait.

That's one option - another option would be to contribute. Libmraa is an open source project and everyone is welcome to contribute at https://github.com/intel-iot-devkit/mraa ;

[Mike_M_3]

matthias-hahn (Intel) wrote:

That's one option - another option would be to contribute. Libmraa is an open source project and everyone is welcome to contribute at https://github.com/intel-iot-devkit/mraa 

I don't want to sound like a jerk here, however this is not some community project for all to help. They are selling a product to which they are responsible for providing accurate documentation and working software. If its not ready then they should have not released it. It's just that simple.

Why should i spend my valuable time to write a working driver just so i can evaluate their product. They do not even have a document for Atom's register set so that one can write a low level drivers for the I/O.

I have wasted many hours of my time trying to accomplish a simple task only to find out in the end that I cant because its not supported. Here is the kicker of it, they don't support their own board!  Tell me that does not blow your mind. It just like when Microsoft started selling Vista, people bought it and it flat out sucked. Why? Because someone at the top said something like "I don't care its not ready yet. Our Shareholders need profit this quarter".  I fear that Edison will become branded with a bad name just like Vista. After all I would have though they would have learned from their mistakes from that flop the GALILEO.

If they had done their homework, and showed more responsibility to the customer then my attitude would be different and I most likely would be more willing to help. At this point they have put a very bad taste in my mouth. The Edison is a VERY nice product in fact its better than the RPI CM, yet in it's software's present state it could not hold a candle to what RPI has done and can do.

This is not directed toward you matthias-hahn. Its to hopefully shake Intel to wake up and smell the coffee, and do what is right before its to late.

.

[Tage_B_]

I would like to know how I can write a simple Python program that toggles one pin. One single pin. On the mini breakout board that I bought from Intel? Just so I know it is working. Is that too much to ask?

Please.

I did opkg update and upgrade and the error message Segmentation Fault went away. But the pin is not toggling.

[Matthias_H_Intel]

Tage B. wrote:

I would like to know how I can write a simple Python program that toggles one pin. One single pin. On the mini breakout board that I bought from Intel? Just so I know it is working. Is that too much to ask?

Please.

I did opkg update and upgrade and the error message Segmentation Fault went away. But the pin is not toggling.

Unfortunately, as mentioned the mini breakout board is not yet supported from libmraa (as you might have spotted on log messages at https://github.com/intel-iot-devkit/mraa it's work in progress). AND: the IoT devkit IDE is Beta right now.  

Due to the fact that it is pretty easy to build an own proprietary breakout board I guess there will soon be various breakout boards which might be not (yet) supported. Having libmraa / UPM open source projects everyone can contribute to support more breakout boards and to support more sensors.

[David_B_7]

It's nice to know that the library is open-source.  However, the amount of time it would take for me to get comfortable enough with the Atom/Quark architecture and the existing libmraa code in order to make a contribution is way more than I have available right now.  It's also not apparent to me why the basic GPIO code has to be board dependent as most of the module pins connect directly to the mini breakout board's headers.  To me, it would have made more sense to release a basic library first that handles I/O at the module pins and then later develop support (with the community's help) for different breakout boards.

[Brendan_L_Intel]

David B. wrote:

It's nice to know that the library is open-source.  However, the amount of time it would take for me to get comfortable enough with the Atom/Quark architecture and the existing libmraa code in order to make a contribution is way more than I have available right now.  It's also not apparent to me why the basic GPIO code has to be board dependent as most of the module pins connect directly to the mini breakout board's headers.  To me, it would have made more sense to release a basic library first that handles I/O at the module pins and then later develop support (with the community's help) for different breakout boards.

Hi please update libmraa, miniboard is now supported. Board doc is here: http://iotdk.intel.com/docs/master/mraa/edison.html

Oh if only hardware was so simple ;-). Sadly there's many ways to wire boards and the kernel pinctrl driver don't understand the way your board is layed out.

[Francis_C_]

Hi Mike .M,

I am having the same issue. I am running the arduino breakout board with edison on win7 64.

sad, do you have any other solution ?

with thanks,

Francis

[Francis_C_]

root@edison:~#
echo $PWD'>'
/home/root>
root@edison:~#
root@edison:~# chmod 755 /tmp/3_c_onboard_LED_blink;/tmp/3_c_onboard_LED_blink;e
xit
Failed to write to export
Intel Edison Failed to initialise Arduino board TriState,                         check i2c devices! FATAL
Welcome to libmraa
 Version: v0.4.4
 Running on Some weird devboard that isn't recognised...
Segmentation fault

[Matthias_H_Intel]

you do have a pretty old version of libmraa. Pls update and check again

[Francis_C_]

Thanks, Matthias-hahn.

I got it working after updating the libmraa, my edison is shipped with the older version of libmraa, after update it works fine.

I followed the instruction from

https://software.intel.com/en-us/forums/topic/534501 - post #2

[Dmitri_M_]

Hi all, I have the latest version of libmraa (0.5.2.4). It worked yesterday, now I keep getting the segmentation fault error. It is so buggy that it is almost unusable. As is the javascript used to format this message. Keeping in mind it's 2014.

root@edison:~# echo $PWD'>' /home/root> root@edison:~# root@edison:~# chmod 755 /tmp/5_cpp_mraa_analog_input;/tmp/5_cpp_mraa_analog_inp ut;exit Segmentation fault

[ksam_]

Hi all, today I bought the board, and it was having the 0.4.4 version, with that the LED blinking was getting segmentation fault error. I have update with the libmraa and upm libraries, using "opkg update" and "opkg upgrade" command. Now it is showing v0.5.3 version and the blinking is working just fine.