Back
[07:14:47] <jaggz-a> have any of you compiled a Lufa module with other than the default chip/board/etc?
[07:17:09] <Lambda_Aurigae> I did once.
[07:18:05] <Lambda_Aurigae> I didn't have the problems you seem to be running into though.
[07:18:26] <Lambda_Aurigae> if I were you I would go back to the basic configuration and make sure it compiles.
[07:18:35] <Lambda_Aurigae> then make one change at a time and deal with the errors.
[07:25:07] <jaggz-a> where do you properly make the changes? I edited in the Mouse/makefile
[07:26:14] <DO9XE> I did also :)
[07:26:59] <DO9XE> I copyed evrything to another folder ans started deleting and movin stuff :)
[07:28:05] <jaggz> DO9XE: so you didn't need to make any changes to some global makefile somewhere?
[07:31:58] <DO9XE> no, i copyed the LUFA Folfer to the projekt-dir and changed the dir-path in the project make file.
[07:32:01] <DO9XE> like here:
[07:32:28] <DO9XE> this "was" the GenericHID example :)
[07:32:29] <DO9XE> https://github.com/LabConnect/Signalgenerator/tree/master/firmware
[07:44:33] <jaggz> right when I change BOARD to BOARD=LEONARDO I begin getting:
[07:44:37] <jaggz> In file included from Mouse.h:50:0,
[07:44:37] <jaggz> from Mouse.c:37:
[07:44:37] <jaggz> ../../../../LUFA/../LUFA/Drivers/Board/Joystick.h:125:31: fatal error: Board/Joystick.h: No such file or directory
[07:44:37] <jaggz> #include "Board/Joystick.h"
[07:45:55] <jaggz> I can change the MCU (to atmega32u4) and F_CPU (to 16000000) without issues. make will still compile without errors
[07:46:16] <malinus> then just use that?
[07:46:29] <malinus> isn't the leonardo board just an atmega32u4 anyway?
[07:50:21] <jaggz> malinus: in 2012, the docs say all 3 changes (and two additions) are necessary
[07:50:31] <jaggz> http://fourwalledcubicle.com/blog/2012/08/lufa-and-the-arduino-leonardo/
[07:51:15] <jaggz> possibly for the avrdude programming of the board
[07:53:02] <jaggz> it seems weird, but probably for no good reason, that changing the BOARD would affect the include path of Board/Joystick.h
[07:53:50] <jaggz> Here's the output of
[07:54:04] <jaggz> Here's the output of 'make' from within the Mouse dir:
http://www.pasteall.org/56619
[08:03:04] <jaggz-a> here someone explains the same problem
[08:03:11] <jaggz-a> http://ssrb.github.io/gaming/2014/05/11/recycling-old-video-game-controllers/
[08:03:27] <megal0maniac> It's because the "Mouse" project requires a joystick - it's in the defines. You'll either need to use a target which implements the joystick, or modify your target so that it does
[08:03:53] <jaggz-a> down at " make make won’t succeed out of the box though: won’t succeed out of the
[08:04:12] <jaggz-a> box though
[08:04:55] <jaggz-a> I wonder why mouse and keyboardmouse require joystick
[08:05:57] <megal0maniac> Isn't it obvious?
[08:06:07] <megal0maniac> Mouse and keyboardmouse have 'mouse' in common
[08:06:28] <megal0maniac> So obviously 'mouse' control is implemented by means of a joystick
[08:15:06] <_abc__> Does anyone know if gcc iom328p.h was fixed recently to show BODLEVEL fuses in extended, not in high? My old copy shows them in high...
[09:49:51] <supay> hey, anybody know what this is?
http://i.imgur.com/lJGgfCP.jpg
[09:54:04] <malinus> supay: yes, it's a AVR & AT89 burner
[09:54:17] <supay> malinus: any idea what i can do with it?
[09:54:21] <malinus> you kno whow I know? It's called reading. Crazy, huh?
[09:54:25] <malinus> :D
[09:54:26] <supay> lol
[09:54:27] <supay> :D
[09:54:41] <supay> can it be programmed with c? or do i need asm?
[09:55:13] <malinus> you want to start programming avr's?
[09:55:20] <supay> malinus: yes sir!
[09:56:10] <malinus> :D. This is a a place you could start
http://www.avrbeginners.net/. You can program avrs with both C, C++ and asm.
[09:56:26] <malinus> even though they start with asm irrc.
[09:57:01] <supay> malinus: have you used one of these 'programmers' before? if so, what software would i require to start programming it?
[09:58:06] <malinus> usually the compiler: avr-gcc, and avrdude for flashing the avr.
[09:58:22] <malinus> and a text editor to edit your code ofc. :)
[09:59:17] <supay> nice, let me take a look!
[09:59:39] <supay> thanks! :D
[10:00:11] <malinus> where did you find that thing though?
[10:01:20] <supay> malinus: in a place called 'Radio market' in Jaipur, India!
[10:01:30] <supay> asked for a programmer for 8051, and he gave me this.
[10:01:36] <supay> costs around $2
[10:02:20] <malinus> lol. Well hopefully it can program avr's too :D
[10:02:29] <supay> hopefully! :P
[10:02:31] <malinus> what device does it show up as, when plugged into your pc?
[16:00:59] <malinus> supay: figured anything out yet :)?
[18:33:15] <Lambda_Aurigae> jaggz, when you set the board you tell the makefile that you have certain config files in a special directory for that board.
[18:35:45] <Lambda_Aurigae> the board directories are in the LUFA/Drivers/Board/ directory...
[18:35:57] <Lambda_Aurigae> there is an AVR8 for your standard atmega chips.
[18:36:08] <Lambda_Aurigae> err...AVR8 for atmega chip based boards.
[18:36:43] <Lambda_Aurigae> you will need to make a directory in there for your board and put the config files in it..
[18:37:11] <Lambda_Aurigae> mine has a LEONARDO directory already.
[21:58:52] <jaggz> Lambda_Aurigae: hallo... yeah.. leonardo is there .. but there seems to be a problem with the coding/dependencies of the Mouse and KeyboardMouse projects (lowlevel)
[21:59:03] <jaggz> I don't know what lowlevel vs. class driver means still
[22:43:07] <jerware> moin.
[23:54:09] <postmodern> so I have this FTDI/USB cable I'm using for reprogramming this atmega32 chip
[23:54:44] <postmodern> if i enable debugging, are the debug messages written back over the FTDI port?
