mchelper does not detect make controller in linux

OK, I'm clearly over my head, but  I'm committed to getting this project done all open-source,  I've got finally Linux running (ubuntu gutsy gibbon -  Linux kernel 2.6.22 i think) on an old machine (P3 era) but I cannot get mchelper to detect the make controller board. 

Any help much appreciated.

should have added:

mchelper 2.2.0

also, I've followed the linux tutorial and loaded sam7utils-0.2.1 and gnuarm-3.4.3.   All works until I try to make the firmware (tiny or Heavy) then I get the following :

make: arm-elf-gcc: Command not found

Thanks

In order to build the firmware yourself, you'll need to install the arm-elf-gcc toolchain. Check gnuarm.org for a recent package for linux. When you upload the pre-compiled heavy.bin, are you still not seeing anything? How are you connecting to the board - through your LAN or directly to your computer?

Thanks for the reply.

I have installed the toolchain (gnuarm-3.4.3) on usr/local and there appears to be a arm-elf-gcc file in there, but it does not seem to find it when building Heavy.  I will try the current gnuarm (4.0.2) next.

I did upload heavy.bin and tried moving it  various places but no luck getting mchelper to detect the controller. 

I am connecting the controller through a USB port to the computer.  When I connect a different USB external (a USB floppy drive), the computer detects it and it shows up in the "computer:///" screen.  When I connect the controller board it does not show up.  Is this an Unbuntu USB issue  Do I need to put the sam7 driver somewhere else (it's currently in a file on /Desktop)?

One of the known issues for mchelper on Linux is that there is not USB support. It sounds like arm-elf-gcc is not on your path...is /usr/local already on your path, or have you otherwise adjusted it?

Thanks!! got heavy to compile and load.

Just a couple of dont-know-much-bout-linux questions left:

I know that I'm supposed to put something in the .bashrc file
to put gnuarm on "the path" but what exactly to I add?  this is what I entered  from a terminal:
export PATH=$PATH:/usr/local/gnuarm-3.4.3/bin

is that what goes in the .bashrc ?
 and is it the .bashrc in my home directory or the one in the /etc directory?

also, the tutorial says i need to copy something into modprobe.conf so that the driver will load next time I boot.  What exactly goes in there?

Thanks

I'm running Linux as well, how did you get around the lack of usb in mchelper?

Previously Chris Bruner wrote:

I'm running Linux as well, how did you get around the lack of usb in mchelper?

It works over Ethernet.  I suppose folks just use that while waiting for USB support; assuming they aren't sufficiently motivated and able to create USB support themselves.

At one point I had an experimental version of the OSC/USB support semi-working under Linux. It had *lots* of problems, but would work about 1/5'th of the time. I started by copying most of the stuff for OSX since many of the underlying API's support POSIX/ANSI interfaces, etc. Anyway, the USB support is something that I was hoping to get back to but I doubt that I really have the time in the foreseeable future... EBo --

In the mchelper svn tree in the v25 branch, the support for Linux USB open/close/read/write is all there. The only thing that needs to be done is to do the enumeration of connected devices. Sample code for this using libusb is in there but I still don't have a Linux machine to test on.

Whereabouts are you located Liam? I'm currently back in Albuquerque New Mexico. If there was some way we could get together I would be glad to set you up with dual boot, etc. I'll try to break away some more time to take another look at v25b and the whole thumb/cross-dev support issues. I'm not sure how far I will get with all that though. EBo --

Oh. I remember what sidetracked me last time I picked this up... v25 requires Qt4.4+ which provides QPlainTextEdit and possibly others. My canonical system only provides Qt4.3. I'll poke around again and see what the current integration of Qt4.4 into the Gentoo distribution is, but is it possible to remove the Qt4.4'isms? I started hacking QPlainTextEdit down to QTextEdit which IIRC is supported by Qt4.3. Liam, what do you see as the pro's and con's of writing to Qt4.3 instead of 4.4? EBo --

The main benefit is QPlainTextEdit, unfortunately When there are LOTS of messages streaming through the mchelper dialog, QTextEdit just cannot handle it - QPlainTextEdit is WAY faster. This is an issue particularly when using mchelper as an XML interface to Flash, for example, when the message sending is more automated. Otherwise, there are no major issues that I'm aware of.

How about this then... I'll ifdef the section of the code so we can turn on/off Qt4.3/4.4 support... Hmmm, that might not work. Does anyone know how to set up suck a switch in the Layout and qmake files? EBo --