Yahoo Groups archive

AVR-Chat

Index last updated: 2026-04-28 22:41 UTC

Messages

Browse messages

Page 31 of 307 · 15341 messages matched

Re: [AVR-Chat] ATTiny programming and debug

2010-09-03 by Jim Wagner

That argues for an external pullup on the SS line to make sure it is not asserted during reset. Jim Wagner Oregon Research Electronics On Sep 2, 2010, at 9:20 PM, Clark Martin wrote: > > On Sep 2, 2010, at 9:02 PM, Jim Wagner wrote: > > > Most of the ATtinys that that have debugg

Thread view Attachments: 0

Re: [AVR-Chat] ATTiny programming and debug

2010-09-03 by Clark Martin

On Sep 2, 2010, at 9:02 PM, Jim Wagner wrote: > Most of the ATtinys that that have debugging have DebugWire which uses > the reset pin, only. Check the processor you are interested in for > DebugWire. If it does not have it, then no debugging on that chip. > > You might need a wa

Thread view Attachments: 0

RE: [AVR-Chat] ATTiny programming and debug

2010-09-03 by Dave McLaughlin

Hi Philippe, You need to check the datasheet for the intended devices you want to use. Some of the later Tiny devices have debug wire to allow in circuit software debugging. This uses the reset line so no IO lines need be used up. As for sharing the I2C with programming, you can

Thread view Attachments: 0

Re: [AVR-Chat] ATTiny programming and debug

2010-09-03 by Jim Wagner

Most of the ATtinys that that have debugging have DebugWire which uses the reset pin, only. Check the processor you are interested in for DebugWire. If it does not have it, then no debugging on that chip. You might need a way to isolate the other lines during operation if you nee

Thread view Attachments: 0

ATTiny programming and debug

2010-09-03 by Philippe Habib

I'm considering an ATTiny part but I'm not totally clear on the programming and if source level debug is supported. My reason for the ATTiny is the physical size I can have is very constrained. The programming data line is also the I2C data line. Does that mean no I2C if I want i

Thread view Attachments: 0

RE: [AVR-Chat] Re: xmega programming

2010-09-02 by Steve Hodge

Thanks, I did that and it looks like I'm good to go for PDI with my JTAGICE MkII. Steve From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Don Kinzer Sent: Thursday, September 02, 2010 9:04 AM To: AVR-Chat@yahoogroups.com Subject: [AVR-Chat] Re: xmega p

Thread view Attachments: 0

Re: [AVR-Chat] Re: xmega programming

2010-09-02 by Jim Hatley

My AVRISP mk2 says 20080801 and programs xmega chips just fine. From the command line you must have the -md option specified for PDI programming. Jim ----- Original Message ----- From: Leon Heller To: AVR-Chat@yahoogroups.com Sent: Thursday, September 02, 2010 9:44 AM Subject: Re

Thread view Attachments: 0

Re: [AVR-Chat] Re: xmega programming

2010-09-02 by Leon Heller

On 02/09/2010 16:50, Steve Hodge wrote: > Well, it's definitely on a JTAGICE MkII. It sounds though that I don't > have to be concerned about having the correct version on the JTAGICE MkII to > do PDI, because I can just upgrade the firmware with AVR Studio. Is that > correct? St

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-09-02 by Leon Heller

On 02/09/2010 15:55, Steve Hodge wrote: > Leon, do you know just how current current needs to be? My JTAG Mk2 has > "20071109" on its sticker, presumably that means Nov 2007. Steve I'm not sure, I've got one of the old ones. You can tell from the LEDs that come on when it is conn

Thread view Attachments: 0

RE: [AVR-Chat] problems with AVRISP mk2

2010-09-02 by Tim Mitchell

Follow up to this: Have tried upgrading the AVRISP to 0x010d (v1.14) using the latest AVRStudio, but no difference. Does anyone know where I can get older versions of the AVRISP firmware to try rolling it back to the version which works? At this point I am not clear if the AVRISP

Thread view Attachments: 0

RE: [AVR-Chat] Re: xmega programming

2010-09-02 by Steve Hodge

Well, it's definitely on a JTAGICE MkII. It sounds though that I don't have to be concerned about having the correct version on the JTAGICE MkII to do PDI, because I can just upgrade the firmware with AVR Studio. Is that correct? Steve. From: AVR-Chat@yahoogroups.com [mailto:AVR-

Thread view Attachments: 0

problems with AVRISP mk2

2010-09-02 by Tim Mitchell

AVR Studio recently upgraded the firmware in my AVRISP mk2 so it'll do PDI programming as described in the previous thread. This is firmware v0x010c. Now I am having problems programming some boards by SPI. The software reports various lines shorted on the programming header and

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-02 by Steve Hodge

Leon, do you know just how current current needs to be? My JTAG Mk2 has "20071109" on its sticker, presumably that means Nov 2007. Steve From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Leon Heller Sent: Wednesday, September 01, 2010 2:33 AM To: AVR-C

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-02 by Steve Hodge

Thanks for everyone's advice on xmega programming, particularly alerting me to the bugs. I checked them out and they either don't apply in my case or I can easily work around them. This is a new project so migration is not an issue. Also thanks for the leads on programmers. Steve

Thread view Attachments: 0

Re: xmega programming

2010-09-02 by Don Kinzer

--- In AVR-Chat@yahoogroups.com, "Steve Hodge" wrote: > Well, it's definitely on a JTAGICE MkII. >It sounds though that I don't have to be concerned >about having the correct version on the JTAGICE MkII to >to PDI, because I can just upgrade the firmware with AVR Studio. >Is that

Thread view Attachments: 0

Re: xmega programming

2010-09-02 by Don Kinzer

--- In AVR-Chat@yahoogroups.com, "Steve Hodge" wrote: >My JTAG Mk2 has "20071109" on its sticker, presumably >that means Nov 2007. That number sounds like an ATAVRISP2 number. My ATAVRISPISP2 has the number 20071005 and it can do PDI programming (after a firmware update, of cours

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-09-01 by Leon Heller

On 01/09/2010 09:19, Tim Mitchell wrote: > > As far as I know any AVRISP MK2 (the USB version) will do PDI if loaded with the correct firmware. > The latest version of AVR-Studio - download from Atmel - will do this automatically when it detects an old version of software in the

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-09-01 by Leon Heller

On 01/09/2010 01:20, Steve Hodge wrote: > Thanks, John. I have both an Atmel STK500 and JTAG Mk2, and both have 2x3 > and 2x5 headers on them for programming. I presume the 2 PDI pins should > map to 2 pins on each of these headers, but the manuals for both of these > don't menti

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-01 by Tim Mitchell

As far as I know any AVRISP MK2 (the USB version) will do PDI if loaded with the correct firmware. The latest version of AVR-Studio - download from Atmel - will do this automatically when it detects an old version of software in the AVRISP. Xmega is a very capable device with som

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-09-01 by H. Carl Ott

On Tue, Aug 31, 2010 at 11:35 PM, Dave McLaughlin wrote: > Don't use the STK500 to programme it, even if it could. As I recall, the > STK500 is 5V operation only and will likely damage the XMEGA running on the > lower voltages. > > Dave. > The STK500 has voltage translators and h

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-01 by Dave McLaughlin

Don't use the STK500 to programme it, even if it could. As I recall, the STK500 is 5V operation only and will likely damage the XMEGA running on the lower voltages. Dave. From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Steve Hodge Sent: 01 September

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-01 by John Samperi

At 10:20 AM 1/09/2010, you wrote: >How does one connect it up? Is there any way >to use the old ISP with xmega's? The AVRISP Mk2 will do PDI programming for Xmegas. See AVRISP mkII User Guide in the Tools help of Studio under 1.5 Supported Devices. Also 2.5.2 PDI Interface show t

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-01 by Steve Hodge

Thanks. That's all the help I needed. At this point, anyway. Steve From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Bob Paddock Sent: Tuesday, August 31, 2010 5:36 PM To: AVR-Chat@yahoogroups.com Subject: Re: [AVR-Chat] xmega programming On Tue, Aug 3

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-09-01 by Bob Paddock

On Tue, Aug 31, 2010 at 8:20 PM, Steve Hodge wrote: > > > Thanks, John. I have both an Atmel STK500 and JTAG Mk2, and both have 2x3 > and 2x5 headers on them for programming. I presume the 2 PDI pins should > map to 2 pins on each of these headers, but the manuals for both of the

Thread view Attachments: 0

RE: [AVR-Chat] xmega programming

2010-09-01 by Steve Hodge

Thanks, John. I have both an Atmel STK500 and JTAG Mk2, and both have 2x3 and 2x5 headers on them for programming. I presume the 2 PDI pins should map to 2 pins on each of these headers, but the manuals for both of these don't mention PDI at all. How does one connect it up? Is th

Thread view Attachments: 0

Re: [AVR-Chat] xmega programming

2010-08-31 by John Samperi

At 07:33 AM 1/09/2010, you wrote: >I'd appreciate it if someone could explain in a nutshell PDI >vs old ISP. PDI uses 1 dedicated pin + reset so there is no "wasted" pins, ISP uses 3 SPI pins + reset. PDI can also do debugging if you have the right tool like a JTAG Mk2 of later t

Thread view Attachments: 0

xmega programming

2010-08-31 by Steve Hodge

I am thinking of migrating up from mega series to xmega. It's not clear to me, however, if you can still program them in the "traditional" ISP way. There seems to be something called "PDI" now, but still using a 6-pin connection. It's pretty clear you can still do it through JTAG

Thread view Attachments: 0

RE: *****SPAM***** [AVR-Chat] ATMega8 Prices gone up?

2010-08-31 by Tim Mitchell

Farnell and RS in the UK are now out of stock of just about all Atmel parts, delivery out to June 2011 on some parts!! So I am not surprised that prices are going up, market forces will do that. -- Tim Mitchell

Thread view Attachments: 0

Re: *****SPAM***** [AVR-Chat] ATMega8 Prices gone up?

2010-08-31 by David Kelly

On Mon, Aug 30, 2010 at 09:04:36AM -0000, Eugene wrote: > I agree that digi-key and others aren't indicators, I don't agree with your statement that Digi-Key is not an "indicator." I know it P.O.'ed my Atmel rep and local distributor that I looked at DK prices, they said as much.

Thread view Attachments: 0

RE: [AVR-Chat] 16 channel I2C LED driver

2010-08-31 by Tim Mitchell

The other potential problem with this device is it multiplexes the LED's 1/9 which will reduce the brightness a lot. The TI devices provide a full on drive. ----Original Message---- From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf Of Dave McLaughlin Sent

Thread view Attachments: 0

Re: [AVR-Chat] Chip Security

2010-08-31 by STEVEN HOLDER

Exactly as Jim says, if you really want it secure do a bootloader with DES/AES security built in, and encrypt with the create application from avr, this create an enc file which can be bootloaded in with update, do all the security fuses as well and it is pretty dam hard to crack

Thread view Attachments: 0

Re: [AVR-Chat] Chip Security

2010-08-31 by Jim Wagner

On Aug 30, 2010, at 5:50 PM, Dean Claxton wrote: > Hi everyone, > > just wondering how secure these AVR's are - how much effort is > involved to > read the flash and eeprom off a chip with security fuses enabled and > jtag > disabled? > > [Non-text portions of this message have b

Thread view Attachments: 0

Re: Chip Security

2010-08-31 by Eugene

Hello. The methods are simple: just open the crystal, find the fuses block and restore some of them i think. :) --- In AVR-Chat@yahoogroups.com, Dean Claxton wrote: > > Hi everyone, > > just wondering how secure these AVR's are - how much effort is involved to > read the flash an

Thread view Attachments: 0

Chip Security

2010-08-31 by Dean Claxton

Hi everyone, just wondering how secure these AVR's are - how much effort is involved to read the flash and eeprom off a chip with security fuses enabled and jtag disabled? [Non-text portions of this message have been removed]

Thread view Attachments: 0

Re: *****SPAM***** [AVR-Chat] ATMega8 Prices gone up?

2010-08-30 by Eugene

I agree that digi-key and others aren't indicators, but we have the same situation and we do not use DK etc. Even if we order a serious quantity in a local market we can't get the prices we had 1 year ago (we had atmega16 for ~1,4$). More of that we must pre-order atmel productio

Thread view Attachments: 0

RE: [AVR-Chat] 16 channel I2C LED driver

2010-08-29 by Dave McLaughlin

This looks pretty neat but you are not going to be using these in home projects unless you can solder down BGA style packages and for that you will need a stencil machine and a reflow oven or you will have to have them made professionally and that is going to cost you if only for

Thread view Attachments: 0

Re: [AVR-Chat] 16 channel I2C LED driver

2010-08-28 by DHINESH KUMAR

you may use TPIC6A595 shift register, with 1A o/p per channel.., but its spi., similay to 74hc595.., but powerfull On Sat, Aug 28, 2010 at 9:34 PM, Philippe Habib wrote: > > > Its so great you posted this. A friend of mine is looking to drive a > bunch of LEDs with only a few wir

Thread view Attachments: 0

Re: [AVR-Chat] 16 channel I2C LED driver

2010-08-28 by Philippe Habib

Its so great you posted this. A friend of mine is looking to drive a bunch of LEDs with only a few wires. I'll have to check this out. On Aug 27, 2010, at 5:59 PM, Chuck Hackett wrote: > I have done a lot of searching for an LED driver with: > - I2C interface > - 16 channels (or,

Thread view Attachments: 0

RE: [AVR-Chat] 16 channel I2C LED driver

2010-08-28 by Chuck Hackett

> From: Russell Shaw > > Chuck Hackett wrote: > > I have done a lot of searching for an LED driver with: > > - I2C interface > > - 16 channels (or, two 8 channel devices if 1/2 the price of a 16 channel > device) > > - 10 to 30 ma per channel > > - Individual PWM adjustable const

Thread view Attachments: 0

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.