2008-01-24 by Philippe Habib
The problem is that these things are like dog food. The consumer and the purchaser have different priorities. I'm sure that if you got a few beers into an Atmel exec, they'd tell you the purpose of the studio is to sell parts by making people like us think it will make our lives
Thread view
Attachments: 0
2008-01-24 by David VanHorn
On Jan 24, 2008 3:50 PM, Tim Gilbert wrote: > What's the secret to the JTAG-ICE. I've had one for several years but haven't used it because it never wants to connect consistently. I'm now on a project where it would be really nice to use but the silly thing won't talk to my ATmeg
Thread view
Attachments: 0
2008-01-24 by David VanHorn
On Jan 24, 2008 3:48 PM, Dennis Clark wrote: > Has anyone used the ICE MK II with GDB or Avarice? It'd be interesting to > see if those debuggers work better than the Atmel IDE. The only reason > that I mentioned this ICE is that I own that one, so of course its more > interestin
Thread view
Attachments: 0
2008-01-24 by Zapper77DK
------------ I deleted all previous history because this post is just my experience with DebugWire. ------------ I tried all sorts of things - with and without pull up resistor on a JTAGICE Mk2. However, my conclusion after having spent hours (and four different JTAGS) was that t
Thread view
Attachments: 0
2008-01-24 by Dennis Clark
I'm in the same boat. The JTAG_ICE doesn't work with most AVR's I use, and won't work with the ones it is supposed to work with... Grr. DLC > What's the secret to the JTAG-ICE. I've had one for several years but > haven't used it because it never wants to connect consistently. I'
Thread view
Attachments: 0
2008-01-24 by Tim Gilbert
What's the secret to the JTAG-ICE. I've had one for several years but haven't used it because it never wants to connect consistently. I'm now on a project where it would be really nice to use but the silly thing won't talk to my ATmega128. I've programmed the JTAG fuse, what else
Thread view
Attachments: 0
2008-01-24 by Dennis Clark
Has anyone used the ICE MK II with GDB or Avarice? It'd be interesting to see if those debuggers work better than the Atmel IDE. The only reason that I mentioned this ICE is that I own that one, so of course its more interesting to me... Does anyone have any experience at all wit
Thread view
Attachments: 0
2008-01-24 by David VanHorn
Ok, things are becoming more interesting. Below is my update to avr@atmel.com, on my debugwire frustrations: Additional info. In the pic that I sent, you can see that the system failed to clear ZH, even though it was straightline code, "clr ZH" This has been absolutely consistent
Thread view
Attachments: 0
2008-01-24 by Dave VanHorn
And now that's broken. Now I'm getting other non-deterministic junk in other places. Basically, it's as if the ice is skipping some instructions according to some internal rule. I've seen this sort of problem in the ICE-50, Jtag Ice, and now the MkII. Various platforms, with litt
Thread view
Attachments: 0
2008-01-24 by john
--- In AVR-Chat@yahoogroups.com, Russell Shaw wrote: > > john wrote: > > I'm trying to declare a structure but I keep getting an error like this > > or similar depending on were I try to put __attribute__. > > > > error: expected '=', ',', ';', 'asm' or '__attribute__' before 'st
Thread view
Attachments: 0
2008-01-24 by Philippe Habib
The book is "An Embedded Software Primer" by David E. Simon. The author covers very basic hardware concepts, interrupts, different RTOS architectures along with their pluses/minuses, tasks & states, services that an RTOS might provide, designing using an RTOS, dev tools, debuggin
Thread view
Attachments: 0
2008-01-24 by David VanHorn
> Now you know why Microchip is still the micro of choice, even if the > Atmel processors are faster and superior technology - Atmel support is, > er, sub-standard (IMO). But I'm in the US, I think they are better > supported in the EU, but I'm not sure. Regardless, I soldier on,
Thread view
Attachments: 0
2008-01-24 by Tom Becker
> ... I can do 50,000 fp mults or fp adds with a 16mhz avr... FWIW, I did some Kalman work with the µMFPU v3.1 on a ZX-24 last year and found it is very useful - and fast if you keep your work on the FPU, i.e. keeping vars on the FPU and using user-defined functions instead of si
Thread view
Attachments: 0
2008-01-24 by Dennis Clark
Now you know why Microchip is still the micro of choice, even if the Atmel processors are faster and superior technology - Atmel support is, er, sub-standard (IMO). But I'm in the US, I think they are better supported in the EU, but I'm not sure. Regardless, I soldier on, but I d
Thread view
Attachments: 0
2008-01-24 by Dave VanHorn
--- In AVR-Chat@yahoogroups.com, dlc wrote: > > I've been wondering about debugwire, perhaps I'll stick to tracing with > "printf"... > Boy I tell ya. I was able to get it working, intermittently. When it works, I can debug pretty well. BUT. After working with it for a while yest
Thread view
Attachments: 0
2008-01-24 by np np
FPU's in microcontrollers ! I had to write my own FPU's in days gone by. Programming is so easy these days ! ----- Original Message ---- From: "BobGardner@aol.com" To: AVR-Chat@yahoogroups.com Sent: Thursday, 24 January, 2008 3:28:31 AM Subject: Re: [AVR-Chat] µMFPU Has anyone ti
Thread view
Attachments: 0
2008-01-24 by Russell Shaw
john wrote: > I'm trying to declare a structure but I keep getting an error like this > or similar depending on were I try to put __attribute__. > > error: expected '=', ',', ';', 'asm' or '__attribute__' before 'struct' > > Does avr-gcc allow plain-old structures? How should I w
Thread view
Attachments: 0
2008-01-24 by Russell Shaw
Bryan Martin wrote: > I am attempting to move to C (winavr) from bascom for programming but > getting hung up on some fundamentals. > > Given the following > > unsigned char byte_in = 0xA; > > I need to print the decimal value to UART so I want to see 10. Similar to > printf("%d"
Thread view
Attachments: 0
2008-01-24 by BobGardner@aol.com
Has anyone timed how long it takes to multiply and add floating point numbers in a loop? I can do 50,000 fp mults or fp adds with a 16mhz avr, so it has to be faster than that to be a performance win. In a message dated 1/23/2008 10:17:39 P.M. Eastern Standard Time, tjkeller1@win
Thread view
Attachments: 0
2008-01-24 by Tom
Juistb discoverd this chip, an 18 pin DIP (also available in SMD packaging) which provides a very powerful FPU + other functions, including 2 12 bit ADCs, a full RS-232 port (including level shifting), string processing, NMEA string parsing, numeric to string and string to numeri
Thread view
Attachments: 0
2008-01-24 by john
I'm trying to declare a structure but I keep getting an error like this or similar depending on were I try to put __attribute__. error: expected '=', ',', ';', 'asm' or '__attribute__' before 'struct' Does avr-gcc allow plain-old structures? How should I write this to get it to c
Thread view
Attachments: 0
2008-01-24 by Bryan Martin
Thanks Russell. I will check this out also and see if it works for my goal of smaller code. ----- Original Message ----- From: "Russell Shaw" To: Sent: Wednesday, January 23, 2008 8:58 PM Subject: Re: [AVR-Chat] Simple casting winavr > Bryan Martin wrote: >> I am attempting to mo
Thread view
Attachments: 0
2008-01-24 by Bryan Martin
HA.. Got it. You got me looking in the right direction with the itoa. Found example code at http://en.wikipedia.org/wiki/Itoa and now its working as desired without the added bloat. Again I owe ya. Thanks guys ----- Original Message ----- From: "Don Kinzer" To: Sent: Wednesday, J
Thread view
Attachments: 0
2008-01-24 by Mike
You will need to the I/O library #include You will need to link printf to the USART fdevopen((void*) Usart_Tx, (void*) Usart_Rx); You will then need to provide the low level "get a byte to/from the USART routines (called Usart_Tx and Usart_Rx above) You will also need to init the
Thread view
Attachments: 0
2008-01-24 by Russell Shaw
Bryan Martin wrote: > I am attempting to move to C (winavr) from bascom for programming but > getting hung up on some fundamentals. > > Given the following > > unsigned char byte_in = 0xA; > > I need to print the decimal value to UART so I want to see 10. Similar to > printf("%d"
Thread view
Attachments: 0
2008-01-24 by Bryan Martin
Thanks for the quick response Don. Your example works as expected (not that I doubted you). Can I have a do over please. One of the reasons for moving to C was due to the size of code being produced when using bascom. Nothing against bascom. What I am doing is getting data back f
Thread view
Attachments: 0
2008-01-24 by Mike
You will need to the I/O library #include You will need to link printf to the USART fdevopen((void*) Usart_Tx, (void*) Usart_Rx); You will then need to provide the low level "get a byte to/from the USART routines (called Usart_Tx and Usart_Rx above) YOu will also need to init the
Thread view
Attachments: 0
2008-01-24 by Bryan Martin
I am attempting to move to C (winavr) from bascom for programming but getting hung up on some fundamentals. Given the following unsigned char byte_in = 0xA; I need to print the decimal value to UART so I want to see 10. Similar to printf("%d", byte_in). Lord I hope this makes sen
Thread view
Attachments: 0
2008-01-24 by Don Kinzer
--- In AVR-Chat@yahoogroups.com, "Bryan Martin" wrote: > I need to print the decimal value to UART so I want to see 10. This issue has nothing to do with casting, by the way. That aside, the C run-time library has a function to convert a value to a string and the one that you men
Thread view
Attachments: 0
2008-01-23 by John Samperi
At 08:47 AM 24/01/2008, you wrote: > I've an odd issue. I'm finding that my AVRISP will work fine with my >old 90S2313 and ATMEGA8535 parts, but an AVRISPv2 will always get an >"Initialization failed" error in avrdude. I don't believe that the MK2 supports older chips out of the
Thread view
Attachments: 0
2008-01-23 by dlc
Hi all, I've an odd issue. I'm finding that my AVRISP will work fine with my old 90S2313 and ATMEGA8535 parts, but an AVRISPv2 will always get an "Initialization failed" error in avrdude. Now strictly speaking this probably isn't an avrdude issue, but that is what I use and I'm w
Thread view
Attachments: 0
2008-01-23 by Behrooz
Thanks Philippe, but an online document would be more useful to me. A simple google search returned this one and I found it interesting, AVR related: http://www.avrfreaks.net/index.php? module=FreaksArticles&func=downloadArticle&id=14 Behrooz --- In AVR-Chat@yahoogroups.com, "Phi
Thread view
Attachments: 0
2008-01-22 by Roy E. Burrage
Could you do that Philippe? There have been a couple of questions about multitasking and RTOS systems in the past little bit and that might help those who are coming to terms with uses for these...where to use them and where not. Thanks, REB Philippe Habib wrote: >I have a book t
Thread view
Attachments: 0
2008-01-22 by stereo type
Ya, throw out the title. I won't mind I promise. Philippe Habib wrote: I have a book that does a great job of explaining this, but its at home. If there is interest I can dig up the title. I used it as the textbook for an embedded programming course I took years ago. -----Origina
Thread view
Attachments: 0
2008-01-22 by Philippe Habib
I have a book that does a great job of explaining this, but its at home. If there is interest I can dig up the title. I used it as the textbook for an embedded programming course I took years ago. -----Original Message----- From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogro
Thread view
Attachments: 0
2008-01-22 by Philippe Habib
And that is the core of multi tasking real time code. The standard for fast is as fast as you need to go in order to get all the stuff you need done on time. If you're inside a laser printer and the mirror is coming around you'd better be ready so fast means one thing. In an inst
Thread view
Attachments: 0
2008-01-22 by subscriptions@aeolusdevelopment.com
David VanHorn Wrote >> U talked of RTOS. Never heared of it before, but my MCU needed to >> control RH, light level and temperature real time and show them on >> LCD, so I thought and then I made for myself a sort of virtual multi- >> tasking procedure, for example: >> >> Do >> G
Thread view
Attachments: 0
2008-01-22 by David VanHorn
On Jan 22, 2008 11:44 AM, Behrooz wrote: > What might be a standard for 'fast'? Depends ENTIRELY on the application. That's what they pay us the big bucks for, to know what's appropriate for a given system. >If Gosubs take one milisecons is it fast? That might be horribly slow fo
Thread view
Attachments: 0
2008-01-22 by David VanHorn
> U talked of RTOS. Never heared of it before, but my MCU needed to > control RH, light level and temperature real time and show them on > LCD, so I thought and then I made for myself a sort of virtual multi- > tasking procedure, for example: > > Do > Gosub v > Gosub w > Gosub x
Thread view
Attachments: 0
2008-01-22 by Behrooz
What might be a standard for 'fast'? If Gosubs take one milisecons is it fast? If the whole process takes less tha 0.1 Sec then what is the difference if you break it into 1000 piececs or 10? Doesnt it make you work harder, if you play too much with ISRs? Behrooz --- In AVR-Chat@
Thread view
Attachments: 0
2008-01-22 by Behrooz
--- In AVR-Chat@yahoogroups.com, "Chuck Hackett" wrote: Dear Chuck, Glad to hear from you, and thanks for your in depth reply to my questions. Your instructive explanations encouraged me to go more through this and take advantage of your experience. I wonder if it is good idea to
Thread view
Attachments: 0
2008-01-22 by David VanHorn
On Jan 22, 2008 9:06 AM, Dyan Fassett wrote: > I had 5 M168's that were bricked my JTAGICE MKII was useless... > Got a AVR Dragon and a Dragon Rider then using HVPP mode found that > the SPIEN fuse was reset and the clocks were messed up. > I reprogrammed them all and recovered t
Thread view
Attachments: 0
2008-01-22 by Dyan Fassett
I had 5 M168's that were bricked my JTAGICE MKII was useless... Got a AVR Dragon and a Dragon Rider then using HVPP mode found that the SPIEN fuse was reset and the clocks were messed up. I reprogrammed them all and recovered the price of the Dragon Rider :) Dyan...KV9R --- In AV
Thread view
Attachments: 0
2008-01-22 by dlc
I've been wondering about debugwire, perhaps I'll stick to tracing with "printf"... DLC David VanHorn wrote: > On Jan 18, 2008 5:38 PM, Owen wrote: >> Hi Dave, >> I have had some problems with debugwire going wrong when using >> an earlier version of studio (caused by "myself not
Thread view
Attachments: 0
2008-01-22 by John Samperi
At 11:00 AM 22/01/2008, you wrote: >indications are that the device is hosed up somehow. Try and use the STK500 in HVPP mode to check the fuses, maybe the clock gets messed up. Regards John Samperi ******************************************************** Ampertronics Pty. Ltd. 11
Thread view
Attachments: 0
2008-01-22 by David VanHorn
On Jan 18, 2008 5:38 PM, Owen wrote: > Hi Dave, > I have had some problems with debugwire going wrong when using > an earlier version of studio (caused by "myself not familiar with using > debugwire" not entering and exiting debugwire properly) the only solution > that I found wa
Thread view
Attachments: 0
2008-01-21 by David VanHorn
> I guess you are being a good boy and cycle the target power > as required just after any changes? Yup > > Brick wall coming up...... Yeah.. @#$!$%#^
Thread view
Attachments: 0
2008-01-21 by John Samperi
At 09:35 AM 22/01/2008, you wrote: >At that point, it told me that the debugwire wasn't enabled (correct) >and I told it to use ISP mode to enable debug wire. >That was the last I was able to talk to the chip. I guess you are being a good boy and cycle the target power as require
Thread view
Attachments: 0
2008-01-21 by David VanHorn
On Jan 21, 2008 4:43 PM, John Samperi wrote: > At 08:16 AM 22/01/2008, you wrote: > > After that, the part is inaccessible either way. > > Once in DW mode the only thing that will revert the chip to > normal mode is either exiting DW from within a debug session > or resetting the
Thread view
Attachments: 0
2008-01-21 by John Samperi
At 08:16 AM 22/01/2008, you wrote: > After that, the part is inaccessible either way. Once in DW mode the only thing that will revert the chip to normal mode is either exiting DW from within a debug session or resetting the fuse via HVPP. Are you using the Dragon or JTAG Mk2 for
Thread view
Attachments: 0