next topic »

[Reply #30 on:]

I wasn't showing a TX LED, only RX, driven by D25.
The Activity LED is driven when SCK is high (D13).

The shrunken ATMega32U4 design I started from didn't have a TX LED so didn't tie up a pin with one either.

[Reply #31 on:]

Crossroads, that question was for fm. :-)

[Reply #32 on:]

I wasn't showing a TX LED, only RX, driven by D25.
The Activity LED is driven when SCK is high (D13).

The shrunken ATMega32U4 design I started from didn't have a TX LED so didn't tie up a pin with one either.

Hi CrossRoads, the activity LEDs should be fine. Going through the data sheet suggests so.
Any way, we will soon know I've ordered a batch for distributing to the chaps on the other thread, they should be arriving the week after next.

[Reply #33 on:]

The shrunken ATMega32U4 design I started from didn't have a TX LED so didn't tie up a pin with one either.

Hi CrossRoads, the activity LEDs should be fine. Going through the data sheet suggests so.
Any way, we will soon know I've ordered a batch for distributing to the chaps on the other thread, they should be arriving the week after next.
[/quote]

fm,

I tried it already, it is ground switched when using the arduino boot loader(LED pin is always high).

Roy

[Reply #34 on:]

Hi Roy, thanks for the feedback. Will see how it looks.

What happens after the boot loader ends?
Have you tried while sending information through Serial (i.e. the CDC serial) on a sketch?

[Reply #35 on:]

FM,

It runs the program after the boot loader ends(takes about 3~4 seconds on my board).It sets up the USB serial stuff and make use of the RX/TX LEDs. Make sure you get the latest leonardo boot loader from Arduino's Github pages, the one from RC2 is messed up.

I tried running the example serial sketch and the RX and TX LEDs flash as expected.

I changed the fuses to activate the HWB pin and running without the bootloader disables the serial and the RX/TX LEDs( but TX pin is held low so LED is always turned on)

Roy

[Reply #36 on:]

Thanks for the info. Cheers roypogi

[Reply #37 on:]

Though I would share that the vinciDuino boards are on their way and soon we will get our hands on with them. This is how they should look. We will keep you posted.

[Reply #38 on:]

Looks nice.
I Philosophically disagree with making SCD/SDL moved away from A4/A5, just because it means any shields that used SCL/SDA will now need some wires added to get those signals.
Some jumpers or solder pads to make that an option would have worked.

[Reply #39 on:]

Just a small thing, the overlay for D10-13 has the 10s digit on the bottom, I would think it should be on the top.

Is the SDA/SCL placing what the official board will be doing?

______
Rob

[Reply #40 on:]

I Philosophically disagree with making SCD/SDL moved away from A4/A5, just because it means any shields that used SCL/SDA will now need some wires added to get those signals.

 Your right, the pin listing puts SCL/SDA on the other side of the board. Correct?

Code:

// D2 PD1 SDA SDA/INT1
// D3# PD0 PWM8/SCL OC0B/SCL/INT0

[Reply #41 on:]

Yes, PD0, PD1 are the SCL/SDA line.

[Reply #42 on:]

Found this listing of pins here (which did not paste in nicely at all)

http://morecatlab.akiba.coocan.jp/lab/index.php/2011/09/leonardo-on-arafruit-32u4/?lang=en
 

Code:

// ATMEL ATMEGA32U4 / ARDUINO LEONARDO //
// D0                 PD2          RXD1/INT2
// D1                 PD3          TXD1/INT3
// D2                 PD1          SDA         SDA/INT1
// D3#               PD0         PWM8/SCL    OC0B/SCL/INT0
// D4      A6       PD4        ADC8
// D5#                PC6         ???         OC3A/#OC4A
// D6#     A7       PD7       FastPWM      #OC4D/ADC10
// D7                 PE6          INT6/AIN0 //
// D8                 PB4          ADC11/PCINT4
// D9#       A8       PB5       PWM16        OC1A/#OC4B/ADC13/PCINT5
// D10#      A9      PB6       PWM16        OC1B/0c4B/ADC12/PCINT6
// D11#               PB7       PWM8/16      0C0A/OC1C/#RTS/PCINT7
// D12       A10     PD6                         T1/#OC4D/ADC9
// D13#               PC7       PWM10        CLK0/OC4A //
// A0                   PF7                    ADC7
// A1                   PF6                    ADC6
// A2                   PF5                    ADC5
// A3                   PF4                    ADC4
// A4                   PF1                    ADC1
// A5                   PF0                    ADC0 //
// New pins D14..D17 to map SPI port to digitial pins //
// D14                 PB0                    RXLED,SS/PCINT0
// D15                 PB1                    SCK,PCINT1
// D16                 PB2                    MOSI,PCINT2
// D17                 PB3                    MISO,PCINT3 //
// TXLED             PD5
// RXLED             PB0
// HWB               PE2                    HWB
 

And from adafruit re: their ATMega23U4 breakout board
http://www.ladyada.net/wiki/products/atmega32u4breakout/index.html

You can use this board with Arduino v1.0 (RC2 or higher) by selecting Leonardo as the board type, and the matching serial port.

The Arduino pins are as follows

Code:

PB0 - digital 14 / also RX LED
PB1 - digital 15 / SPI SCK
PB2 - digital 16 / SPI MOSI
PB3 - digital 17 / SPI MISO

PB4 - digital 8
PB5 - digital 9
PB6 - digital 10
PB7 - digital 11

PC6 - digital 5
PC7 - digital 13

PD0 - digital 3
PD1 - digital 2
PD2 - digital 0 / serial RX
PD3 - digital 1 / serial TX
PD4 - digital 4 / A6
PD5 - used as Serial TX LED
PD6 - digital 12
PD7 - digital 6

PE2 - unused - HWB
PE6 - (also the green BOOT LED) digital 7

PF7 - A0
PF6 - A1
PF5 - A2
PF4 - A3
PF1 - A4
PF0 - A5

Note that some pins are used as the RX/TX LEDs and so you shouldnt use them in your code because the IDE 'takes over' the pins for LED blinking

[Reply #43 on:]

I've been reviewing the ATMega32U4 pins usage, looking for ways to make a Leonardo Clone compatible with existing shields.
This chart captures what I think would be a more compatibe usage of the mixed up IO that Atmel has for this part.
With some 0.025" square posts & jumpers, or solder bridges, the 6 additional pins could be brought out as well.

The 2 8-pin ports and the 6 pin port could be conveniently left grouped together for direct port manipulation of complete ports.

What's the group think on this vs the current Leonardo declarations?

http://www.crossroadsfencing.com/pin_usage_review.pdf

[Reply #44 on:]

@graynomad - well I suppose you are right about the orientation, but it depends if you read them from the board out to the board in. Don't know really I guess is a question of taste.

@crossroads - I also agree with you that they should have maintained the pinout for the I2C and SPI. There are a good range of shields out there that use these features. A message exchange with David from the Arduino team, says that they made a trade off and that they have informed shield developers about it in advance.

Don't agree that much, in the sense that PWM placement, from a shield perspective is not as important as these othe two interfaces.