| Author |
Message |
|
|
 Posted: Feb 13, 2012 - 10:51 PM |
|
Joined: Nov 17, 2011
Posts: 8
|
|
| I am looking for XMEGA128A3-BU bootloader for USB. where can i find this? |
|
|
| |
|
|
|
|
|
|
Posted: Feb 14, 2012 - 01:45 AM |
|
Joined: Mar 28, 2001
Posts: 20311
Location: Sydney, Australia (Gum trees, Koalas and Kangaroos, No Edelweiss)
|
|
| Please do not cross post to unrelated threads. Other post deleted. |
_________________
John Samperi
Ampertronics Pty. Ltd.
www.ampertronics.com.au
* Electronic Design * Custom Products * Contract Assembly
|
| |
|
|
|
|
|
|
Posted: Feb 14, 2012 - 10:55 AM |
|
Joined: Jan 09, 2007
Posts: 1849
Location: Arlington, Texas, U.S.A.
|
|
|
|
|
|
|
|
Posted: Feb 15, 2012 - 12:41 AM |
|
Joined: Jan 31, 2012
Posts: 129
Location: Vancouver, BC, Canada
|
|
If you don't have a debugger (a physical unit I mean) then I would start with FLIP, although you won't be able to do any real-time debugging. But you can at least load your program via a hex file and test it out.
http://www.atmel.com/tools/FLIP.aspx |
_________________
ATMega644a
XMEGA-A3BU
JTAGICE3 Programmer
AVR Studio 5.1.148
FLIP 3.4.5 Build 106
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:58 AM |
|
Joined: Jul 18, 2005
Posts: 62209
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
you won't be able to do any real-time debugging
Yeah but if there is USB then when the app is running it can use this for real time debug output. |
_________________
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 06:19 PM |
|
Joined: Jan 31, 2012
Posts: 129
Location: Vancouver, BC, Canada
|
|
| Really? Wow, I have been missing out. How do you do that without a debugger? Any tips would be great... |
_________________
ATMega644a
XMEGA-A3BU
JTAGICE3 Programmer
AVR Studio 5.1.148
FLIP 3.4.5 Build 106
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 08:32 PM |
|
Joined: Jul 18, 2005
Posts: 62209
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
Really? Wow, I have been missing out. How do you do that without a debugger? Any tips would be great...
To whom is that question addressed and what hardware are you talking about?
OP started talking about an Xmega model that is non-USB so to add USB to that I assume we're talking about an FTDI which is just a USB CDC-ACM which can easily be used by the app code to make it appear as a VCOM on the PC.
However if we're talking about an AVR with built in USB then it can, of course, do CDC-ACM but you could use all sorts of device classes to appear as a debug device including (but not necessarily limited to) CDC-ACM, HID, MSD, generic. |
_________________
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:05 PM |
|
Joined: Jan 31, 2012
Posts: 129
Location: Vancouver, BC, Canada
|
|
I am relatively new to this so I might be asking what you consider really obvious questions, but here it goes.
I am using an A3BU Xplained board, but I am slowly transitioning to wiring up my own proto-board. I am currently using a JTAGICE3 debugger (I got it yesterday, so I am still getting used to it). You said you can do real-time debugging without a programmer like the JTAG? I was told otherwise, which is why I spent the money. Before the programmer I was using FLIP to load .hex files to run programs but I couldn't do any real-time debugging this way. My question was how are you doing real-time debugging without the programmer?
(To give you an idea of what stage I'm at, I had to google half of the acronyms you used to figure out what the meant...) |
_________________
ATMega644a
XMEGA-A3BU
JTAGICE3 Programmer
AVR Studio 5.1.148
FLIP 3.4.5 Build 106
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:24 PM |
|
Joined: Jul 18, 2005
Posts: 62209
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
My question was how are you doing real-time debugging without the programmer?
I'm not - I always use a debugger. But if you don't have one you can tell the outside world what's going on inside a CPU with any of:
1) a single LED that flashes in various places to say "I got this far"
2) a line of LEDs on a PORT to show a byte pattern
3) an LCD attached to the CPU and printf()s through the code
4) a UART link to a PC for the same printf()s but to a terminal on the PC. This may be AVR UART to MAX232 to USB-RS232 cable to PC or an FTDI doing all that in the AVR circuit
5) like (4) but if the CPU has USB then it can do CDC-ACM directly and just apepaer like a VCOM to the PC. You send strings off up a USB endpoint in the AVR code and it comes out in a terminal program on the PC
6) like (5) but rather than CDC-ACM do HID then write your own PC app that opens the VID/PID for HID
7) like (5) but implement MSD on the AVR and at the PC end it looks like files are being written by the PC
8) there's loads of other ways along these lines
For (4)/(5) your PC app code can CreateFile("COM7") (or whatever) to open a "COM port" as a file and then read/write data - just like a PC terminal program does. |
_________________
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:31 PM |
|
Joined: Jan 31, 2012
Posts: 129
Location: Vancouver, BC, Canada
|
|
Aah. I see what you mean now. Thanks for the tips; #5, 6 and 7 are definitely appetizing; I've been implementing the first few already.
Thanks again (in this thread and several others)  |
_________________
ATMega644a
XMEGA-A3BU
JTAGICE3 Programmer
AVR Studio 5.1.148
FLIP 3.4.5 Build 106
|
| |
|
|
|
|
|
|
Posted: Feb 15, 2012 - 09:38 PM |
|
Joined: Jul 18, 2005
Posts: 62209
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
| It depends how "realtime" you want it. I actually like doing it the MSD way. |
_________________
|
| |
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
