regarding KontrollerLab

Go To Last Post
19 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

While searching for some avr related material I came to know about KontrollerLab IDE for developing software for avr
I downloaded this IDE from following link and installed..

http://sourceforge.net/project/s...

Is there anybody who is using this one and let me know is it good for avr micro programming or not.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What do you want to hear? Why don't you form an own opinion?

I didn't like it when I tried it. But why should you care about my taste? Try it for yourself and form an own opinion.

Stealing Proteus doesn't make you an engineer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, I use it for programming my uCs, and it works all right. I think, it's great, but as it has already been pointed out, it's probably a question of taste.
Zoltan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

when I compile , build project and build all using (KcontrollerLab) its successful but when I click on erase device its giving error...

avrdude -p m16 -u -e
avrdude: no programmer has been specified on the command line or the confing file

Now, I know I have to specify -c stk500v2 but I am unable to find out the option. One more thing what is this command line and about confing file I saw its already there in /usr/local/etc and path is provided from configure programmer

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello,

After a month , today I was again trying my hands with this Kontrollerlab. But I was stuck again at the same position

I am waiting for this response for a long time. If anybody is having the solution , try to give some reply (or better to say hint).

Thanks !!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is it not the case that for programming that KontrollerLab is simply issuing "make program" and the definition of the programmer in use (-c stk500v2) is something that would therefore need to appear in the Makefile you are using?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

But where is this makefile in kontrollerlab?
How can I find this one. Any suggestion !!

Thanks for quick reply of yours.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Isn't there a screen something like this:

(the avrdude, not uisp tab though)

I downloaded the package but it's not much use on Windows and seems to have woefully inadequate documenation (it all seems to consist of "need to fill in this bit later")

I just remembered I've got a Linux computer (my EEE PC) which has kde so I might try it on there and see what happens.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Go to Project -> Configure programmer -> AVR-Dude -> Specify programmer type -> STK-500, whatever. That should do.
As for the make file, by default, kontrollerlab uses its own build system. In order to change it to "make", you should go to
Project -> Configure project -> Common, and uncheck the "built-in build system" box.
Zoltan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello clawson,

even I was playing around the screen and tried all the relevant options but in vain. Moreover, It's short of documentation so, unable to get it completely. I have a query is it complete or yet in developement phase.

Hello zoltanvoros,

First thanks for reply. I tried the same with all options of programmer type. About my hardware I am using STK500v2 and JTAGICE mkII now my connections are as follows, (both are communicating using STK500 JTAG adapter) Serial programming cable connected to JTAG and and usb for power supply . please let me know what options may I try?

About makefile option when I uncheck the box and compiling my program Its crashing again and again (otherwise it was OK) and when I backtrace it the output is like this give below :-

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7fd96c0 (LWP 3450)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x007b5467 in execvp () from /lib/tls/libc.so.6
#5  0x076fbd97 in QProcess::start () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6  0x080db688 in KLProcess::start ()
#7  0x080db342 in KLProcessManager::addProcess ()
#8  0x080cc9bd in KLAVRGCCCompiler::compile ()
#9  0x0806b059 in KLProject::compile ()
#10 0x08061b8e in KontrollerLab::qt_invoke ()
#11 0x07763450 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x07763b2a in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x07cf8f49 in KAction::activated () from /usr/lib/libkdeui.so.4
#14 0x07cf8f6d in KAction::slotActivated () from /usr/lib/libkdeui.so.4
#15 0x07cf901c in KAction::qt_invoke () from /usr/lib/libkdeui.so.4
#16 0x077633d9 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x07763b2a in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x07a9b590 in QButton::clicked () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x077f30a7 in QButton::mouseReleaseEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x077993aa in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x077048f9 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x07704b39 in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x002703b8 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0x076a3a2e in QETWidget::translateMouseEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x076a22c8 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x076b46d6 in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x07719f25 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x07719e7e in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x07703afb in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x0805d633 in main ()
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When I am compiling the program using make enabled its giving this error-

make clean
make: ***No rule to make target 'clean'. Stop.
Error(s) occured: The exit status was 2.
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think the makefile is their I am attaching the same . Have a look. (Sorry how to attach a file their no option found) But still pasing the same file ....



  
    
  
  
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  
  
    
    
    
    
    
    
    
    
  
  
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
  

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

anmol2701 wrote:
I think the makefile is their I am attaching the same . Have a look. (Sorry how to attach a file their no option found) But still pasting the same file ....



  
    
  
  
    
...

This is not a "make". Can you make Kontrollerlab print the make file itself?

Quote:

About my hardware I am using STK500v2 and JTAGICE mkII now my connections are as follows, (both are communicating using STK500 JTAG adapter) Serial programming cable connected to JTAG and and usb for power supply . please let me know what options may I try?

First, can you use avrdude outside kontrollerlab? If you are trying to use either the serial or the USB port, you might run into problems related to permissions. You can't do that by default as an average user.

Quote:

About makefile option when I uncheck the box and compiling my program Its crashing again and again (otherwise it was OK) and when I backtrace it the output is like this give below :-

Again, the question is whether you can generate a make file that works as it is supposed to.
By the way, we do you need the make file in the first place? You said, you could generate the hex file, and you had had problems with avrdude only. Uploading the hex file hasn't got anything to do with the make file. You should be able to do that by issuing the command

avrdude -p m16 -c stk500 -P usb -y -U something.hex

or something similar, depending on your settings. Again, you'll need root permission for this, unless you fixed your group settings.
Zoltan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
First, can you use avrdude outside kontrollerlab?

Yes its working fine.

Quote:
You can't do that by default as an average user.

I am working as a root.

How can I work in command mode in kontrollerlab.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You need to give the average user permission to access the serial/USB port. It should be something like this

chmod a+rw /dev/serport0

where, obviously, you should replace serport0 by the appropriate name on your system. Once you are done with that, you should be able to run avrdude from kontrollerlab.
Zoltan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I fired that command throung terminal ie. chmod a+rw /dev/ttyS0 even now I am getting the same error after successful compilation of the program

avrdude -p m16 -u -e
avrdude: no programmer has been specified on the command line or the confing file

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

anmol2701 wrote:

avrdude -p m16 -u -e
avrdude: no programmer has been specified on the command line or the confing file

This tells you all: you pass only m16 to avrdude (i.e., you specify that you will program an Atmega16), but you don't tell it which programmer you want to use.

avrdude -p m16 -c stk500 -u -e

or

avrdude -p m16 -c stk500v2 -u -e

if you have 2.x firmware on your STK500. (I have just realised that I pointed this out in my previous post. In the future, it would be beneficial, if you read the replies to your question before complaining that the proposed solution doesn't work.)
By the way, I've learnt all this by reading the avrdude manual. http://download.savannah.gnu.org...
Zoltan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Zoltan,

Its right that I have to mention this option. I know it already, as you can see my post on 14th of jan. (see above). But the question was how to fire this command. How can I work with kontrollerlab in command mode.

Anmol Kumar

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Kontrollerlab doesn't use makefiles btw. It just takes each .c file it can find in your project, compiles it, throws it together, links it, and then optionally calls uisp or avrdude for programming.

Therefore uisp and avrdude can only be configured by 'Configure programmer' from Kontrollerlab. Easiest thing to do is trying to configure it from there, and try to read your fuses. If you can read your fuses, you can program as well.

If your programmer type isn't listed in the avrdude list, just choose a wrong one, close kontrollerlab, and edit the XML project file and replace the name of the programmer with the right one. It doesn't contain every programmer in it's drop-down which avrdude supports (I believe the 'bsd' one isn't in the list, but I use that one myself). Or just use UISP if you need that.

That said, the lack of Makefiles is what makes Kontrollerlab both easy to use and harder to use for big things. If you need to link in some LCD library, some one-wire library, and some other things, you need to copy them all completely to your project, and add them to your project, you can't simply 'share' your libraries from a central location.

Hope this helps.