Debian C/C++ Cross-Compilation for Embedded Linux using Eclipse (Luna), CDT, RSE & Remote Debug
ฝัง
- เผยแพร่เมื่อ 9 ก.ย. 2024
- This video introduces C/C++ cross-compilation on the BeagleBone platform, and is applicable to any embedded Linux development. I show the steps that are necessary to set up a toolchain, the Eclipse CDT environment and use the Target Management RSE (Remote System Environment) plugin to communicate with the BeagleBone. Finally, I demonstrate how you can set up a cross-platform debugging environment within Eclipse, where you can use gdbserver on the ARM device and gdb-multiarch on the client device to establish a full debugging environment.
This video supports Chapter 7 in the book "Exploring BeagleBone" -- please see more at www.exploringbeaglebone.com
01:37 Installing a cross-compilation toolchain
15:25 Installing the Eclipse IDE with CDT
20:30 Using the Remote System Explorer(RSE)
25:41 Automatically Deploying the Executable
30:30 Cross-platform debugging
I'm using Eclipse 3.8 (Indego) and at the 22:00 mark, I needed to check ~3 boxes related to "Remote System Explorer user Actions" before any choices appeared in the "Remote Systems" tab (one was under the Mobile Development folder, not sure if that one helped but...)
Thanks for the great book and videos Derek! This stuff is crypic as is, your material is immensely helpful and helps me to stay motivated!
Man your video has been so helpful it`s beyond words. I got the BB wireless but managed to get everything working start to finish. God bless you good man.
Thank you. While some items are a bit out of date, determining the modifications helped me learn the system better.
As always, you have outdone yourself! Thank you for these informative videos. Just bought the Kindle edition of our book and enjoying it immensely.
VERY helpful. Managed to get remote debugging on Ubuntu 16.04 and Eclipse Oxygen with just a few minor changes!
Could you please tell what changes did you do? I would like to do this in Ubunto 16.04 as well.Also will the above steps work with a 32 bit Ubuntu installation?
THANK YOU THANK YOU THANK YOU! That was pretty painless and it would have probably taken me a month to figure all of that stuff out on my own. I think as mentioned in another comment, if you install Eclipse Mars, you'll now have to separately install the terminal as it's no longer a default part of the remote tools. That was the only real gotcha that I ran into. Also... if anyone else is wondering about running this under Debian sid/unstable and experimental... I just took delivery of a Dell XPS-13 with the new Skylake processor. It's not a real happy camper running under Jessie so I had to point my sources.list to unstable and do an apt-get dist-upgrade to Debian unstable. That still wasn't quite good enough to get everything working so I also needed to add in the experimental so I could grab linux kernel 4.3 which adds support for Skylake (sort of... it's mostly there). Anyhow, with all that I didn't encounter any problems and I now have a nice, compact (and sweet) little development environment for the BeagleBone Black. Thanks again! :)
This is fantastic. Makes me want to ditch OS X and install Linux on my desktop. I'll try this with a Pi. Thank you
Hi from Brazil Derek!!! Thanks a lot for this video.
Jesus, you are a God Mr.Derek!!! Thank you for this!!!!
Thank you so much, every sentence of this video is gold.
Great video. I used it to configure my RPI B environmente. In my case, I needed the ARMEL architecture, and I have used the gnueabi instead of gnueabihf.
Very well done! Just what I needed.
Tip: use the `file` command on the binary. It will give you some nice info on the file including the architecture it was build for.
Very useful video, also for Rpi projects :) Thanks.
This video is gold. Thank you!
I found that these days I need to add
"set sysroot"
before
"set architecure arm"
in the .gdbinit file. otherwise GDB is not starting properly.
I don't know why this is needed now and it was not needed when Derrek made this video but anyway... if you got problems with debugging, try my solution.
Thank you derrek for your excellent video's!!
Thanks for such a Great tutorial
Thank you for this.
My interest was how to do remote gdbserver debugging on just amd64, the cross compiling info was an interesting extra!
Great video and book. I am running Ubuntu 14.04 on my desktop and Debian on the BBB. I could not get the debugger working per the video instructions. I had to add the following command to the debugger Main setup below the remote absolute file path for C++ applications. The command is chmod 777 /home/beagle/BBBProgram/TestARM. Your path will be whatever your absolute file path is for your setup. I am not sure why I needed to add this since I am not Linux expert but it did solve my problem. Without the command I was getting an IO Error message when I tried to run the debugger.
FYI you need the TM Terminal add-on in Eclipse (from Install New Software menu)
Incredible !!! I thanks you so much
THANK YOU Dr. Molloy. Your video saved me many, many hours.
Thanks Derek for this helpful video!
And for all of you (including me) who runs Ubuntu and got stuck at 7:49 ( with sudo apt-get update failing), here I found a solution:
Modify existing sources, restricting to appropriate architectures (i.e. all i386 and amd64 package sources are prefixed as "deb [arch=i386,amd64]")
sudo sed 's~\(\(deb\(-src\)*\) \([^\[]\)\)~\2 [arch=i386,amd64] \4~' /etc/apt/sources.list | sudo tee /etc/apt/sources.list
#Manually configure third party sources
sudo sed 's~\(\(deb\(-src\)*\) \([^\[]\)\)~\2 [arch=i386,amd64] \4~' /etc/apt/sources.list.d/*.list
Create source list for the port architecture(s) (this adds the armhf port sources to apt)
sudo bash -c 'cat > /etc/apt/sources.list.d/armhf-ports.list
Thank you from 2022
This is a great video. First, way to go. Second, using a deployed, remote system environment is a great way to use the BBB and other MCUs for that matter. Good on you and Geaux Cajuns...
I need to get emacs on my BBB and I am having trouble getting emacs to use instead of nano. What gives?
Awesome - thank you
Great video Derek. Very helpful, as always. I just installed Deb8.xfce, and this video helped me to get Eclipse configured for the RPi I've been working with.
With regards to starting Eclipse from the command line--you can certainly do that. However if anyone would like to have an icon for Eclipse appear in their Applications Menu under the "Development" category, it's very simple and takes three steps:
1) Copy the contents of the file I have uploaded to Pastebin
pastebin.com/T4Y73YkU
2) Assuming that you put eclipse into your "/home//" directory like Derek showed in the video here, simply change the path to the eclipse executable and icon.xpm files. Just edit the contents of the file I uploaded to replace the part with your username in lines 3 and 6. For me those lines would be...
Exec=/home/tb/Programs/eclipse/eclipse
Icon=/home/tb/Programs/eclipse/icon.xpm
3) Finally, save the file to the full path as shown in the title of my upload. So for me it would be...
/home/tb/.local/share/applications/eclipse.desktop
Note that this works in Debian and Ubuntu, and should basically work in any version of those two. Just note the dot (.) in the "~/.local/" directory--it's a hidden directory. There should be other .desktop files in that directory as well, and you can simply create this one and drop it right in there. You will probably have to click the "show hidden files" option in your text editor--or just navigate there in the console and use vim or nano to create the file directly. But once the file is in place, you should have a menu entry for "Eclipse Luna" in your Applications Menu.
*NOTE: For those not too familiar with Linux, you do this with user privileges, NOT as root or with the "sudo..." command. You want the eclipse.desktop file to be owned by user (ie; you)...not root.*
Enjoy!
Tom B Thanks Tom -- very useful!
Derek Molloy I'd say it is the *least* I could do after all the instruction you've given me. Any more time watching your videos or reading your book, and my wife will buy me a ticket to Ireland, and tell me not to come back without the degree!
Tom B Thanks!
Thank you very much for this excellent tutorial. I was able to complete this project using Linux Mint Cindy (LMDE) and Eclipse 2019-03 which, for some reason, didn't show SSH Terminals, but I worked around that. I had Jessie on my BBB release A6A. By the way, the gcc-4.9-arm-linux-gnueabihf and g++-4.9-arm-linux-gnueabihf are no longer available for Jessie on emdebian.org. However, they are available in Stretch.main
which apt source you used?
I did search on google. no old version sources found.
still works
Please make a video about exploring Logi-Bone. :)
Very nice video (as usual). Debian Jessie is on the PC not on the BBB. Does this work on Ubuntu on the PC?
Derek,
Excellent video! I was able to follow this setup using Ubuntu 16.04.1 LTS running on a VM in my Mac. I also used the current latest version of Eclipse (neon) without issue. The hardware I'm using is a stock BeagleBone Green Wireless.
I did however have one problem in regard to remote debugging. I'm able to step through program execution, but GDB is having trouble watching variables. From my research it appears this is caused by a version mismatch between GCC and GDB. Do you have any thoughts or advice?
Thanks for taking the time to put together this video :D
Dear Derek, I bought your book and for the first time in months I actually now feel confident to start developing knowing I can finish what I start. Is there any chance of a book on "Brexit" as after several years I still don't really get it.
nice
thanks
Hi Derek,
Awesome video. Cant tell you how much time this has saved. Is there a way to tell that the g++/gcc/library versions that are used to compile the code in eclipse will run on the beaglebone. Another way to put this is how do I check which version of g++-X.X-arm-linux-gnueabi should I install on the eclispe dev environment to match the beaglebone.
When I run "uname -a" on the beaglebone I am running Linux beaglebone 3.8.13 and I don't have any needs at the moment to upgrade the beaglebone.
Hello Derek! I'm learning a lot with you about Beaglebone, watching your videos, however I'm stuck at 10:43. After you use sftp command, you have to put a password. I've tried all the passwords I know but it didn't permitted... Do you know if have some way that I could discover this password? If not, could you give me a solution for this problem? Thank you
Great video, very helpful. As a 3rd year Electronics Engineering student, I'm involved in a project where we utilize a beagle board-xm and a webcam to track motion and point a water gun at it. I tried to follow your instructions but can't work out some parts due to me working on a Ubuntu 14.04 LTS and you on Debian 8. I tried installing debian on the laptop that I'm working the project by cannot make even install it because it does not recognize the ethernet and wlan. I have the exact same problem with almost every linux distort except ubuntu. The main problem is that when I add the armhf architecture at dpkg and hit update, it fails to find the packages. I suspect they are not available at the ubuntu repositories. After that when i try to install crossbuild-essential-armhf i get the message "the package you are trying to install has unmet dependencies" and cannot find (obviously) the packages that should have been installed with the update command but did not because it can't find them.
Great Video. It helped me alot.
I wonder how i can send a "command line" argument to the application on the beaglebone before starting to debug it with GDB?
Greetings Derek,
Kudos on the top-notch material in your videos and your companion website for Exploring BeagleBone. My copy of the book should be arriving soon! I hope that it is not too outdated. I'm trying to get set up to cross-debug using Eclipse Neon. Everything went well until I got to setting up the remote debug configuration. The "Connection" drop-down menu only contains "Local". In this video, it appears you did nothing special to make BeagleBone appear in this selection. Should I need to create a "New" connection at this point or is something else borked that I missed? Like I said, everything has worked up to this point including automatic deployment of the executable to the BBB, using the remote terminal, etc. I was going to ask this on "Exploring..." but could see no way to comment. Regards.
**EDIT** -- I went ahead and added a new connection to the debug configuration and everything seems to be working as expected.
Make "New.." connection with desired configuration.
This video is incredibly helpful but... The current version of Eclipse is Mars. All worked the same as Luna until at 23:05 when you create the remote connection. The options stop after selecting the ssh shell, there is no option for setting up an ssh terminal. In addition, there did not appear to be any other way to create a terminal connection. I tried using the Remote Shell view but it does not behave like the terminal. Any suggestions?
JoAnn M I had the exact same problem. Here's how I got it to work in Mars today.
You have to install the Terminal package(s) since they don't come with Mars by default for some reason.
I went to Help -> Install New Software -> Work with: Mars
then in "type filter text" type "terminal".
I installed both "TM Terminal via Remote API..." & "TM Terminal View Remote System...".
THEN I was able to right-click Beaglebone in Remote Systems tab -> Open Terminal...
Host: 192.168.7.2
then your login details (however you have your account set up on BBB)
defaults for everything else and OK.
Should work!
SorlacChannel Thanks for your update -- it is very useful. I found that I had to install "TM Terminal" and the "TM Terminal View RSE add-in" but I did not need to install the API version.
+SorlacChannel Wow! You have no idea how long I've been looking for a solution to this! Since I learned about Eclipse Mars, obviously. Anyway, I'm going to tell the world, as the message is not getting out effectively. Thanks a lot!
Spencer Williams Glad to be of help.
This tutorial is out of date. whatever, thank you very much!
what can be done better now? or do you have an other newer tutorial?
The video uses emdebian.org at 5:28 (and elsewhere), but as of July 2016, the web site says that all distributions were stopped on July 2014, and that there will never be another update. Basically, the project has been shut down and deprecated. The 2014 snapshot seems to do the job, but is there an alternative method which avoid abandonware?
Just use the regular GNU C compiler from the official repositories. ---> sudo apt-get install gcc-arm-linux-gnueabihf or g++-arm-linux....
NOMAD: You need to do more than that. If you just do that you'll get a segmentation fault as soon as you try to run on ARM hardware.
Debian recommends the following: wiki.debian.org/CrossToolchains
I'm just now getting a chance to look through it, so I don't know how easy it'll be to set up, but I definitely won't use emdebian. They say their signing key was compromised too.
Is there any update/upgrade, since the video came out 2 years ago.
Very good as ever!, should it be possible for you to update cross compiling Qt, as I 'm stuck trying to find how to qmake2 in beaglebone Debian
for some reason when I run ssh-copy-id root@192.168.7.2 it gets stuck here. However, ssh root@... works fine.
Does anyone know the reason?
I am using virtualbox and the network attached to NAT and I have the ports forwarded 2222 and 22
Hi, Derek. Are you using virtual machine to build these develop environment? I fond that my pc freeze up all the time while running debian and eclipse in virtual machine.
Hi,
I have bean fallowing along with a newly installed debian
machine.
The eclipse requires java 8 while the debian comes with 7.
I tried to fallow some tutorials on how to install jre 8 on
debian, but without success.
Links are out of date, the java8-installer can't be found.
Can you please point me in the right direction?
I am installing Debian 9.4.0 Stretch. @7:55, after letting go of: "sudo apt-get update" and it reports several problems, like "Repository doesn't have Release file" or "failed to fetch ...../binary-i386/Packages 404 Not Found"? Any suggestions?
I’ve watched this video and duplicates the steps many times but now it’s 6 years old and I’m wondering how relevant this information is. Is this still a reasonable starting point or should I look somewhere else? I just ordered the latest addition of the book. I wish these little computers got more traction. They went out of style long before I got good with them. Now my grandma can build AI with an Arduino and a library with functions like do_ai(), solve_hard_problem() or identify_enemy_deploy_countermeasures(). They don’t even need to open the ARM reference manual.
I'm getting an error when I try to run the debugger, I get the following message
"Cannot access memory at adress 0x0"
Hi Derek,
I followed your tutorial, and I managed to perform remote debugging on my Ubuntu 20.04 ARM platform (ODROID-XU4). The problem is that when I use gdb-multiarch, the debugging is very slow it takes a lot of time to reach main, do you have any idea of how to resolve this issue ?
Video was helpful, successfully installed once on a macine, new installation, running on Debian Stretch 9.7. When I go to run apt-get update, I get an error indicating an unsigned package.
Any ideas?
can you recreate this using cmake. Seems a little easier than setting up from eclipse? Can you setup specific settings for eclipse from cmake?
Great video.
I have a question. I have installed ubuntu 15.10 in my laptop. Will It work for me? or just work for debian8? Thx
I've tried successfully with Debian stretch and Luna.
I wonder why Derek have chosen Debian not Ubuntu.
Tonight I will try to repeat all steps with Ubuntu 18.04 and Luna.
I've tried. Luna failed to run on Ubuntu 18.04 (after ./eclipse bunch of errors) :(
Hi Derek, first of all thank you for the great instructions! Your videos are really helpful. However I ran into a problem and cannot google a way to fix it:
At minute 22:54 while adding the BeagleBone as a Remote System to Eclipse, you choose "processes.shell.linux" in the configuration. I am using Eclipse Mars and there this configuration does not show up, only dstore.processes can be selected. Do you have any idea how to get that fixed?
Thanks a lot!
The problem does also exist with Eclipse Luna...
Mr. Molloy - I can't thank you enough for these videos. They are extremely helpful. I'm somewhat of a novice, but I'm making progress!
I have a specific problem/question. I've followed everything in the video with success, right up to running gdb. Unfortunately, I've run into a problem there. When I try to "debug", the console says "readchar: Got EOF" and "Remote side has terminated connection. GDBServer will reopen the connection."
And finally, it gets stuck at "listening on port 12345".
If I look on the beaglebone, I see the BBBTest and gdpserver processes running.
However, Eclipse does not proceed.
Any guidance would be greatly appreciated!
And thank you again for your wonderful videos!
Once this is working, I'm on to creating some image processing with OpenCV!
Adam Weiss - I read online that gdb could have problems if the versions on the server and client weren't the same. The version on my VM is 7.7.1 and the one on the beaglebone black is 7.4.1. I thought this might be the problem, but both are the latest versions, and I can see in your video that you're using 7.7.1 on your VM as well. If anyone has any ideas, I'd sure appreciate it. Debugging by "cout" is not ideal ;-)
I'm off to a bad start.
E: Package 'sudo' has no installation candidate.
Well, I'll just use root then.
E: Package 'build-essential' has no installation candidate.
Now I'm stuck.
SorlacChannel The solution was to add these lines to /etc/apt/sources.list
deb httpredir.debian.org/debian jessie main
deb-src httpredir.debian.org/debian jessie main
then, as root, type: apt-get update
then type: apt-get install sudo
then type: apt-get install build-essential
#1 What should the /etc/apt/sources.list file look like on the beaglebone? I get an error when trying to install gdbserver:
"
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package gdbserver is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'gdbserver' has no installation candidate
"
Similarly, what should the sources.list file look like on the virtual machine, since even things like apt-get install chromium don''t install/run.
#2: Does the newer versions of Eclipse (Mars / Remote System Explorer User Action) not have the Shell Terminal (24min mark)? It lists 'Ssh shells' but not 'Ssh terminals'.
#3: Executing ssh-copy-id (26min mark) the terminal window just hangs.. no output of the command is entered. As if the SSH is in use, but there's nothing else running. How can I find what's hanging this up? Is there another way to copy the key to the bbb?
#4 What are your thoughts on other IDEs.. would it reduce some of the above setup issues? ex. visualgdb, coocox, atollic truestudio, etc
Some questions answered here:
blog.embeddedcoding.com/2015/05/beaglebone-black-development-part-6.html
Hey Derek,
Good Tutorial...
I think you forgot to mention about the addition in source list in this video.
Because of that in Debian 8 or 8.1 I am not able to intall crossbuild-essential-armhf.
I go to various tutorial of yours and found it on
exploringbeaglebone.com/chapter7/
where you explained about Debian 7 Toolchain Installation
sudo nano sources.list
add below line to source list
deb ftp.us.debian.org/debian unstable main contrib non-free
sudo apt-get update
Is these steps are right or wrong?
The other thing is that
sudo apt-get install screenfetch
is not working in 8.1. Don't know the reason.
sudo apt-get install crossbuild-essential-armhf
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
crossbuild-essential-armhf : Depends: libc6-dev:armhf but it is not going to be installed
Depends: gcc-arm-linux-gnueabihf (>= 4.9.1-1) but it is not going to be installed
Depends: g++-arm-linux-gnueabihf (>= 4.9.1-1) but it is not going to be installed
Depends: dpkg-cross but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Why did I got this result DEBIAN 8.5(amd64) get a result like this?
after double check the video,I found your cross client host is arm64...
can u teach me how to do this at Intel Amd architecture?
after add
deb ftp.cn.debian.org/debian/ jessie main contrib non-free
deb-src ftp.cn.debian.org/debian/ jessie main contrib non-free
everything is done.thanks 4 video
I got the same error as you on Debian 8.5 (Jessie). But I fixed it by commenting out two lines in sources.list that I had and, for some reason, were messing up with dependency versions:
#deb security.debian.org/ jessie/updates main
#deb-src security.debian.org/ jessie/updates main
IHi, I have completed all the steps using Raspberry Pi and everything is working fine. Now the only problem for me how to create new project in athe quicker way. As the whole process is a bit lengthy. I want to make the process a bit faster for creating new projects in eclipse. Is there any way?
Thanks
do it once and then just copy the project and rename it?
nice video SIR can you help me I m using Window 7 and how to cross compile in WINDOW need HELP anyone
Hi, Derek. Thank you for your tutorials.
I followed all your steps, but when remote debugging i get an error "Segmentation fault".
When i'm debugging on target device with GDB everything is OK.
I'm using the latest Eclipse Neon v2.
Could you please help me with that?
Add a following lines to .gdbinit file:
set debug-file-directory /opt/gnueabihf_rootfs/usr/lib/debug
set sysroot /opt/gnueabihf_rootfs
Hi Derek,
I've followed your guidelines to install Eclipse. In my case, the Eclipse version was Mars and not Luna (apparently the latest version). One issue I have with this: when configuring the RSE plugin, I do see that in your video the last screen in the New Connection setup for the BeagleBone is Ssh Terminals. In my case, the last screen prior to pressing the Finish button, is Shells. I don't see a next screen with the Ssh Terminals in it.
As a result, I also don't have the item Ssh Terminals under the BeagleBone item.
Is this due to a modified RSE plugin or due to the Mars version of Eclipse instead of the Luna version?
How to eventually get the Ssh Terminals item, you have an idea?
Geert Vancompernolle Oops... I just saw that @MartinHeyn has the same issue...
Duplicat. :-(
Geert Vancompernolle I've followed the guidelines given by +SorlacChannel and indeed, when installing the two extra packages I do see the item "Open Terminal..." when right-clicking on the BeagleBone item. However, there's no reaction afterwards, I don't see any terminal opening...
Geert Vancompernolle You are right, here is the solution: You can install terminal from help - > software install, and then open it from view - >show - >other (search terminal keyword). In mars, terminal is not part of the remote systems but a different tool.
Gökhan Özdoğan Thanks for your input, but how can I reach "help > show > other' from Eclipse? There is no such search sequence I can see from within the Help menu item. Could you clarify?
Geert Vancompernolle Ok, here's what I did to get it working:
1. Installed Eclipse as per the directions given by Derek Molloy
2. Started up Eclipse
3. Went to this web site, marketplace.eclipse.org/content/tm-terminal, and drag'n'dropped the install onto my running Eclipse
4. I then could get a terminal tab by pressing Ctrl-Alt-T
5. I then installed the RSE plugin: still no Ssh Terminals in the BeagleBone RSE setup
6. Still no "Open Terminal" when right-clicking on the BeagleBone connection in the RSE
7. I then again installed the two (other?) TM plugins according +SorlacChannel's explanation and I got the Open Terminal... item back when right-clicking on the BeagleBone. Apparently, those two plugins are additions to the TM Terminal plugin I installed before???
8. When I now select the Open Terminal... item in the popup menu of the BeagleBone, I do get a dialogue box asking for SSH connection details, so IT SEEMS TO WORK!!! :-)
I'm not sure this is the most nice, most short, most efficient, most elegant, most whatever way to get it working, but it works...
Still a pity it doesn't work straight from within the RSE plugin, though...
When I do:
sudo apt-get update
it failed
I got:
Ign cdrom://[Debian GNU/Linux....
....
W: Failed to fetch cdrom://[Debian GNU/Linux 8.0.0 _Jessie......
...
I don't know why it is looking to cdrom.
Bing H It's probably set that way by default, for folks that have some repos on the CD-Rom. I think you can simply edit /etc/apt/sources.list and comment-out that line (as root) and it should work. Seems to me I've done this in the past.
Tom B you are right.
You may also need to un-comment in /etc/apt/sources.list
deb ftp.debian.org/debian/ jessie-updates main contrib
deb-src ftp.debian.org/debian/ jessie-updates main contrib
I'm an idiot. Spent like 15 minutes wondering why the project setup in Eclipse gives me some error about the compiler not being in PATH just to come here and find out that I used the wrong prefix since I'm working with the BCM2708 toolchain for the Raspberry Pi, which has the prefix "arm-bcm2708-linux-gnueabi". *facepalm*
ssh does not work for me.
just some things:
aptitude, as well as apt-get, is deprecated. You should now use apt itself, e.g. apt update, apt upgrade, apt install sudo, etc...
don't include your user to the sudoers, but instead add your user to the sudo group (usermod -aG sudo molloyd), then logout and login again to apply the settings
don't use sftp... that's weird. Just use scp (scp yourLocalFile molloyd@192.168.7.2: )
All in call I think linux isn't your daily operating system, is it? ;)
Hello Derek;
I'm from Argentina and is very difficult write and talk english for mi, but i will try to explain mi problem as best as possible. Sorry.
I'm using Ubuntu 14.04.02 now, and this tutorial not works with Ubuntu. I have been working a lot for for it work, but i haven't been able to do it. I remember, that you have a similar tutorial with Ubuntu. ¿Could you give me this tutorial?. Please.
Thanks.
Cordials regards.
Bruno.
Bruno Gervasoni I don't believe that Ubuntu support cross-platform development (on ARM, for instance) as well as the Debian folks do now...especially with the new Debian 8 (Jessie) version. Maybe you can install Oracle VirtualBox in Ubuntu 14.04, and then install Jessie inside that as a guest, and then follow the tutorial? It would be a way to safely try to get this working. I've done that in the past with Ubuntu 12.04, and it works perfectly...
Derek, This is video is very helpful. However I am at a roadblock and need some assistance when I type sudo apt-get update, it results in the following:
Ign us.archive.ubuntu.com trusty InRelease
Ign security.ubuntu.com trusty-security InRelease
Ign us.archive.ubuntu.com trusty-updates InRelease
Hit security.ubuntu.com trusty-security Release.gpg
Ign us.archive.ubuntu.com trusty-backports InRelease
Hit security.ubuntu.com trusty-security Release
Hit us.archive.ubuntu.com trusty Release.gpg
Get:1 us.archive.ubuntu.com trusty-updates Release.gpg [933 B]
Hit security.ubuntu.com trusty-security/main Sources
Hit emdebian.org jessie InRelease
Ign extras.ubuntu.com trusty InRelease
Get:2 us.archive.ubuntu.com trusty-backports Release.gpg [933 B]
Hit security.ubuntu.com trusty-security/restricted Sources
Hit us.archive.ubuntu.com trusty Release
Hit security.ubuntu.com trusty-security/universe Sources
Get:3 us.archive.ubuntu.com trusty-updates Release [63.5 kB]
Hit security.ubuntu.com trusty-security/multiverse Sources
Hit security.ubuntu.com trusty-security/main amd64 Packages
Hit extras.ubuntu.com trusty Release.gpg
Hit security.ubuntu.com trusty-security/restricted amd64 Packages
Hit emdebian.org jessie/main amd64 Packages
Get:4 us.archive.ubuntu.com trusty-backports Release [63.5 kB]
Hit security.ubuntu.com trusty-security/universe amd64 Packages
Hit security.ubuntu.com trusty-security/multiverse amd64 Packages
Hit extras.ubuntu.com trusty Release
Hit us.archive.ubuntu.com trusty/main Sources
Hit emdebian.org jessie/main armhf Packages
Hit us.archive.ubuntu.com trusty/restricted Sources
Hit us.archive.ubuntu.com trusty/universe Sources
Hit us.archive.ubuntu.com trusty/multiverse Sources
Hit extras.ubuntu.com trusty/main Sources
Hit security.ubuntu.com trusty-security/main i386 Packages
Hit us.archive.ubuntu.com trusty/main amd64 Packages
Hit emdebian.org jessie/main i386 Packages
Hit security.ubuntu.com trusty-security/restricted i386 Packages
Hit us.archive.ubuntu.com trusty/restricted amd64 Packages
Hit security.ubuntu.com trusty-security/universe i386 Packages
Hit us.archive.ubuntu.com trusty/universe amd64 Packages
Hit security.ubuntu.com trusty-security/multiverse i386 Packages
Hit extras.ubuntu.com trusty/main amd64 Packages
Hit us.archive.ubuntu.com trusty/multiverse amd64 Packages
Hit extras.ubuntu.com trusty/main i386 Packages
Hit us.archive.ubuntu.com trusty/main i386 Packages
Hit us.archive.ubuntu.com trusty/restricted i386 Packages
Hit us.archive.ubuntu.com trusty/universe i386 Packages
Hit us.archive.ubuntu.com trusty/multiverse i386 Packages
Hit security.ubuntu.com trusty-security/main Translation-en
Hit us.archive.ubuntu.com trusty/main Translation-en
Hit security.ubuntu.com trusty-security/multiverse Translation-en
Hit security.ubuntu.com trusty-security/restricted Translation-en
Hit us.archive.ubuntu.com trusty/multiverse Translation-en
Hit security.ubuntu.com trusty-security/universe Translation-en
Hit us.archive.ubuntu.com trusty/restricted Translation-en
Hit us.archive.ubuntu.com trusty/universe Translation-en
Get:5 us.archive.ubuntu.com trusty-updates/main Sources [206 kB]
Err security.ubuntu.com trusty-security/main armhf Packages
404 Not Found [IP: 91.189.91.13 80]
Err security.ubuntu.com trusty-security/restricted armhf Packages
404 Not Found [IP: 91.189.91.13 80]
Err security.ubuntu.com trusty-security/universe armhf Packages
404 Not Found [IP: 91.189.91.13 80]
Err security.ubuntu.com trusty-security/multiverse armhf Packages
404 Not Found [IP: 91.189.91.13 80]
Get:6 us.archive.ubuntu.com trusty-updates/restricted Sources [3,433 B]
Get:7 us.archive.ubuntu.com trusty-updates/universe Sources [117 kB]
Get:8 us.archive.ubuntu.com trusty-updates/multiverse Sources [5,152 B]
Get:9 us.archive.ubuntu.com trusty-updates/main amd64 Packages [525 kB]
Err extras.ubuntu.com trusty/main armhf Packages
404 Not Found [IP: 91.189.92.152 80]
Ign emdebian.org jessie/main Translation-en_US
Ign emdebian.org jessie/main Translation-en
Get:10 us.archive.ubuntu.com trusty-updates/restricted amd64 Packages [11.8 kB]
Ign extras.ubuntu.com trusty/main Translation-en_US
Get:11 us.archive.ubuntu.com trusty-updates/universe amd64 Packages [281 kB]
Ign extras.ubuntu.com trusty/main Translation-en
Get:12 us.archive.ubuntu.com trusty-updates/multiverse amd64 Packages [11.9 kB]
Get:13 us.archive.ubuntu.com trusty-updates/main i386 Packages [512 kB]
Get:14 us.archive.ubuntu.com trusty-updates/restricted i386 Packages [11.8 kB]
Get:15 us.archive.ubuntu.com trusty-updates/universe i386 Packages [281 kB]
Get:16 us.archive.ubuntu.com trusty-updates/multiverse i386 Packages [12.1 kB]
Hit us.archive.ubuntu.com trusty-updates/main Translation-en
Hit us.archive.ubuntu.com trusty-updates/multiverse Translation-en
Hit us.archive.ubuntu.com trusty-updates/restricted Translation-en
Hit us.archive.ubuntu.com trusty-updates/universe Translation-en
Get:17 us.archive.ubuntu.com trusty-backports/main Sources [5,851 B]
Get:18 us.archive.ubuntu.com trusty-backports/restricted Sources [28 B]
Get:19 us.archive.ubuntu.com trusty-backports/universe Sources [26.2 kB]
Get:20 us.archive.ubuntu.com trusty-backports/multiverse Sources [1,898 B]
Get:21 us.archive.ubuntu.com trusty-backports/main amd64 Packages [6,256 B]
Get:22 us.archive.ubuntu.com trusty-backports/restricted amd64 Packages [28 B]
Get:23 us.archive.ubuntu.com trusty-backports/universe amd64 Packages [29.9 kB]
Get:24 us.archive.ubuntu.com trusty-backports/multiverse amd64 Packages [1,245 B]
Get:25 us.archive.ubuntu.com trusty-backports/main i386 Packages [6,285 B]
Get:26 us.archive.ubuntu.com trusty-backports/restricted i386 Packages [28 B]
Get:27 us.archive.ubuntu.com trusty-backports/universe i386 Packages [29.9 kB]
Get:28 us.archive.ubuntu.com trusty-backports/multiverse i386 Packages [1,249 B]
Hit us.archive.ubuntu.com trusty-backports/main Translation-en
Hit us.archive.ubuntu.com trusty-backports/multiverse Translation-en
Hit us.archive.ubuntu.com trusty-backports/restricted Translation-en
Hit us.archive.ubuntu.com trusty-backports/universe Translation-en
Err us.archive.ubuntu.com trusty/main armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty/restricted armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty/universe armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty/multiverse armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-updates/main armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-updates/restricted armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-updates/universe armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-updates/multiverse armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-backports/main armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-backports/restricted armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-backports/universe armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Err us.archive.ubuntu.com trusty-backports/multiverse armhf Packages
404 Not Found [IP: 91.189.91.14 80]
Ign us.archive.ubuntu.com trusty/main Translation-en_US
Ign us.archive.ubuntu.com trusty/multiverse Translation-en_US
Ign us.archive.ubuntu.com trusty/restricted Translation-en_US
Ign us.archive.ubuntu.com trusty/universe Translation-en_US
Fetched 2,216 kB in 7s (313 kB/s)
W: Failed to fetch security.ubuntu.com/ubuntu/dists/trusty-security/main/binary-armhf/Packages 404 Not Found [IP: 91.189.91.13 80]
W: Failed to fetch security.ubuntu.com/ubuntu/dists/trusty-security/restricted/binary-armhf/Packages 404 Not Found [IP: 91.189.91.13 80]
W: Failed to fetch security.ubuntu.com/ubuntu/dists/trusty-security/universe/binary-armhf/Packages 404 Not Found [IP: 91.189.91.13 80]
W: Failed to fetch security.ubuntu.com/ubuntu/dists/trusty-security/multiverse/binary-armhf/Packages 404 Not Found [IP: 91.189.91.13 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty/main/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty/restricted/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty/universe/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty/multiverse/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-updates/restricted/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-updates/multiverse/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch extras.ubuntu.com/ubuntu/dists/trusty/main/binary-armhf/Packages 404 Not Found [IP: 91.189.92.152 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-backports/main/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-backports/restricted/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-backports/universe/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
W: Failed to fetch us.archive.ubuntu.com/ubuntu/dists/trusty-backports/multiverse/binary-armhf/Packages 404 Not Found [IP: 91.189.91.14 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am unable to get updates for armhf architecture...
ANY HELP WILL BE APPRECIATED
Thank You.