The LED Thread

[DJLO]

There is information scattered all over the place on how to get your LEDs working when you compile new source files. It took me a while to sort through it all and thanks to many people (sniffynose, ac1d, vma and all the rest i can't remember) that have submitted files and tips that have helped me get things working once and for all.

Keep checking this thread as i will try and update it with as much information as possible. Please feel free to add anything that i don't have here.

I have uploaded the led.h file for some of the popular boards.

All of these with the exception of the JMDBU2 use at90usb162 as the mcu and TEENSY as the board. All you have to do is copy the led.h for the board you wish to use to

folderofyourcode/lufa-lib/trunk/LUFA/Drivers/Board/TEENSY

if you have a different board, you put the file in the folder of that board name

If you have a chip with a atmega32u2, you can compile using at90usb162 as they are compatible, just make sure to change the f_cpu to whatever your board has

If you are compiling for different boards, replace the led.h and repeat the make clean, make process.

[DJLO]

Here is another really nice piece i found. If you are an owner of the Maximus (1 or 2) or a Minimus (1 or 2), there is a way you can have the LED shut off after a certain amount of time. Some people like this and find it useful.

You need to edit the psgroove.c and make the following changes:

under the enum section near the top of the file, add this:

done,
	blinky,
} state = init;

Next do a search for "// done" without the quotes. For the Maximus board add the following:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b11000000 portb 7,6
		if (state == blinky)
		{
			PORTB = 0xc0;
		}

	}
}

For the Minimus board, add this:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b01100000 portd 6,5
		if (state == blinky)
		{
			PORTD = 0x60;
		}

	}
}

There is a maximum of 9999ms (10 seconds) in LUFA. If you wish to increase it to say 30 seconds, do something like this:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b01100000 portd 6,5
		if (state == blinky)
		{
			PORTD = 0x60;
		}

	}
}

Note: I am not sure how this was done but i would love to find out so we can add this to other boards. The coding part is my achilles heel, if anyone is willing to dig in and try some other boards and post back, that would be awesome !

Here are the compiled files for both with 30 second delay

[splinter182]

Here is another really nice piece i found. If you are an owner of the Maximus (1 or 2) or a Minimus (1 or 2), there is a way you can have the LED shut off after a certain amount of time. Some people like this and find it useful.

You need to edit the psgroove.c and make the following changes:

under the enum section near the top of the file, add this:

done,
	blinky,
} state = init;

Next do a search for "// done" without the quotes. For the Maximus board add the following:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b11000000 portb 7,6
		if (state == blinky)
		{
			PORTB = 0xc0;
		}

	}
}

For the Minimus board, add this:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b01100000 portd 6,5
		if (state == blinky)
		{
			PORTD = 0x60;
		}

	}
}

There is a maximum of 9999ms (10 seconds) in LUFA. If you wish to increase it to say 30 seconds, do something like this:

// done
		if (state == done)
		{
			
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
			LED(GREEN);
			_delay_ms(9999);
			state = blinky;
		}

		// lights out binary 0b01100000 portd 6,5
		if (state == blinky)
		{
			PORTD = 0x60;
		}

	}
}

Note: I am not sure how this was done but i would love to find out so we can add this to other boards. The coding part is my achilles heel, if anyone is willing to dig in and try some other boards and post back, that would be awesome !

Here are the compiled files for both with 30 second delay

this is actually very interesting, i know enough coding to figure out how its done but never really written code for hardware before.

If you study the code, the if statement check for the value of state, maybe an integer with values that specify the state of the execution of the code. done is most likely a defined value.

Then you can see LED(GREEN); is a function, probably defined somewhere else in the code or in another .c file, maybe led.c, the GREEN parameter inside the parenthesis is a define value, usually intialized at the beginning of a .c file, again probably led.c, kinda like an alias for a specific numeric value. after the function is executed (turns on the led by setting its "port" or pin on the chip to a 1) Edit:Actually i don't know how the leds are being turn on, one would have to take a look at the LED() function to really figure that out. there is a delay, pauses the execution of code for the length of time specified

After that state is set to blinky
Then state is checked again, and if state is blinky, turns off the led by setting port 5 and 6 to 1s. that would be 1s at the 5th and 6th position of a 8 bit address, bits are numbered starting with 0 from right to left thus 01100000 or 60 in hex.

[h0bbit]

love to see a Teensy2.0 atmega32u4/16 LEDs.h. I still can't get mine to work.

as to the post above me, LED(GREEN) is defined in psgroove.c, not sure if its elsewhere.

#define RED	(LEDS_LED1)
#define GREEN	(LEDS_LED2)

[matchung]

i saw about PL3 code about flashing led during exploiting, i made changes for my PS3Yes dongle, quite funny..

led definition found in /lufa-lib/trunk/LUFA/Drivers/Board/xxxx/LEDs.h (something like that)

[ChokeD]

love to see a Teensy2.0 atmega32u4/16 LEDs.h. I still can't get mine to work.

I second that, I have the same board but cant figure out how to get the blinky code working. I'm not so sure it has to do with a LED.h though because I delete my LED.h out of my source and the light still works. Don't ask me. Without looking to confirm, I believe my psgroove.c file has values set for the led's. I'm also wanting to add some led's to my board. I'll be looking more in to this tomorrow.

This thread was needed SO bad, thanks DJLO. This, as I'm sure you know, is going to be a huge task but once done will be a great help. Thanks for all your hard work here and everywhere else.

[subcon959]

Here are the compiled files for both with 30 second delay

Thanks for that matey, any chance you could do them for kakaroto v3 instead of hermes?
Cheers

EDIT: Well I had a go at doing it myself. It was surprisingly easy to setup the git/winavr stuff. I managed to get a working hex out of it but the green led stays on so I must've done something wrong inserting the above code.

[JonahUK]

DJ,

Once people have got leds working for their boards (those that are not already available), it might be an idea to pass to evilsperm to includes in his github (which kakaroto is now including in his git).

That way, we can simply checkout the git and flash with working leds.

And it will also build up a nice repo of boards etc.

[IP1]

I have uploaded the led.h file for some of the popular boards.

I suspect my query to you yesterday requesting the LEDs.h for Blackcat USB prompted you to create this thread? If so, that's great -- you even went several major steps further.

Great contribution, DJLO.

[splinter182]

love to see a Teensy2.0 atmega32u4/16 LEDs.h. I still can't get mine to work.

as to the post above me, LED(GREEN) is defined in psgroove.c, not sure if its elsewhere.

#define RED	(LEDS_LED1)
#define GREEN	(LEDS_LED2)

You found the value of GREEN which is LEDS_LED2 which is another alias to another value. im guessing all these aliases is to make this code less hardware depended and more portable between chips.

#define Var (someValue)

is a way to define static values to a variable for later use

the LED() function should look like this:

LED(int led){
<code>
}

or something similar to it

also the led.h is a header file which can contain defines, aliases and function prototypes. function prototypes look like the first line of a func but end in a ";" it tells the code that incuded the header what functions are available