Firefly Open Source Community

   Login   |   Register   |
New_Topic
Print Previous Topic Next Topic

Fireduino using linux.

38

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
38
Posted at 11/10/2016 01:42:50      1#
Thank you for the link to the board manager, I couldn't find that any where.  
First I don't know anything - this is just a few things I found.
I got a bunch of different errors when trying to upload a sketch form my linux machines - I think it's because it can't find the device.
So I did try it on a Windows box, just for the sake of trying.
The important driver is a ROCKUSB driver - I couldn't really find anything for linux thou (admittedly I only did a very quick search)
The biggest thing I learned however was I have to run the Arduino IDE as  ADMIN to get it too work at all in Windows.
The other thing was once the ROCKUSB driver was installed, and you exited out of the "upgrade" mode, Windows did see it as a serial device (normal serial) Windows didn't like the serial drivers that were included.
I was able to get my linux machines to finally see the device when in "upgrade" mode, but I could NOT get them to see it as a serial device when I reset the fireduino.  
I now wonder if I should run the Arduino as root on my linux machines.
*BTW the install and usage was not as straight forward as it should be even on a Windows Box - (Window 10, using the Win 8 drivers provided)
Have to disable the driver signature enforcement, reboot a couple of times, and no where did I find that you have to use the IDE as ADMIN (That maybe a Win 10 thing thou)

So it's frustration when things just don't work. I also think there is a language barrier in play here, which is also frustrating.
It looks to me like there are a lot of linux users thou, so hopefully someone smart will figure it out.
-LeRoy
Reply

Use props Report

38

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
38
Posted at 11/10/2016 02:52:04      2#
I was able to try linux again, running the Arduino IDE as root, And still no joy - I did see the serial port show up, and disappear this time however.
and I am getting a error -
/bin/sh: 0: Illegal option --  
That is the same error I got when trying this as a normal user.  I think the serial port disappears when the board is reset, and the board is reset by the compiler, but I'm not sure what the "Illegal option" is.
When you hold the reset button, then hold the upgrade button, release the reset button, then release the upgrade button
this shows up if you do a lsusb command;
lfmiller@Sherlock ~/Desktop $ lsusb
Bus 002 Device 004: ID 0c45:6494 Microdia
Bus 002 Device 003: ID 0596:0524 MicroTouch Systems, Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:e004 Atheros Communications, Inc.
Bus 001 Device 003: ID 1058:1021 Western Digital Technologies, Inc. Elements Desktop (WDBAAU)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2501 Dell Computer Corp.
Bus 003 Device 011: ID 2207:262d  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lfmiller@Sherlock ~/Desktop $

That changes if you exit  "upgrade mode" to:
lfmiller@Sherlock ~/Desktop $ lsusb
Bus 002 Device 004: ID 0c45:6494 Microdia
Bus 002 Device 003: ID 0596:0524 MicroTouch Systems, Inc.
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0cf3:e004 Atheros Communications, Inc.
Bus 001 Device 003: ID 1058:1021 Western Digital Technologies, Inc. Elements Desktop (WDBAAU)
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 413c:2501 Dell Computer Corp.
Bus 003 Device 012: ID 8888:0007  
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lfmiller@Sherlock ~/Desktop $

You'll notice a new ID: 8888:0007

The first device ID: 2207:262d looks like it is for some rockchip but so far I've not found which one, or what linux is looking for to make it work.

This looks like it might have some promise but I am not 100% sure.
http://www.cnx-software.com/2013 ... p-devices-in-linux/

when I searched for the device ID: 8888:0007 I didn't find anything at all.

Reply

Use props Report

38

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
38
Posted at 11/11/2016 10:28:29      3#
This error:
/bin/sh: 0: Illegal option --
has something to do with the default shell being dash, not bash in Ubuntu, and Ubuntu based systems.
I found a "fix" for that here -
https://wiki.ubuntu.com/DashAsBinSh

OK - So Here is the deal - I did get it this to work in linux, without any drivers, but it wasn't as straight forward as it should have been.
Quickly -
I followed the "hold reset", "push upgrade", "release reset", "release upgrade" - then I hit reset again and a serial port does show up (/dev/tyyACM0)
The IDE has to be run as admin (root), (Issue here is, it uses default sets, an you have to add the board back in the board manager)
Next, There are 3 files that need to have the permissions changed.
The easiest way is in the shell
su
cd /root/.arduino15/packages/Firefly/tools/fireduino_tools/1.0.0
chmod 744 rkImageMaker
chmod 744 upgrade_tool
chmod 744 update_tool

This seemed to work for me, I've been able to upload the audio_play_NET sketch, the blink sketch, and a couple others.
I'm using the Arduino 1.6.12 IDE - and this was done on a different linux box, than any of my above posts.
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list