Hi list,
Like many people I guess, I am using in-lined nop asm statements to
respect the timing of external devices, when toggling their control
lines.
In the case at hand I am driving a text LCD module, and the
Enable line must be pulsed low for 250ns.
void lcd_send_nibble(uint8_t data)
{
...
-Original Message-
From:
avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Vincent Trouilliez
Sent: Thursday, February 19, 2009 11:02 AM
To: avr-gcc-list@nongnu.org
Subject: [avr-gcc-list]
On Thursday 19 February 2009 19:01, Vincent Trouilliez wrote:
I made a few trials. It appears that up to and including 3 nop
statements, GCC leaves them alone. But if I put 4 of them, it removes
them all !
Are you absolutely sure they are really left out? I assume they are
just not shown in
Hi Vincent,
If I understand correctly, the word volatile itself is to tell the compiler
not to ignore the statement. I am not sure if your statement is correct, but I
have used
asm volatile (nop::);
and the compiler never removed the nops from code.
Nayani
--- On Thu, 2/19/09, Vincent
On Thu, 19 Feb 2009 11:14:40 -0700
Weddington, Eric ewedding...@cso.atmel.com wrote:
If you are using WinAVR 20081205 then you can use one of the new builtin
functions:
void __builtin_avr_delay_cycles(unsigned long __n);
Hmm, sweet !
Unfortunately I am on Linux so no WinAVR for me ! ;-)
--
Hello all,
I needed to create a buffer of 256 bytes starting at a page boundary (xx00) in
the RAM memory (Mega8).
I added this line in the makefile
LDFLAGs = -wl,--section-start=.test=0x800200
and defined a variable in the .C file (shown below)
unsigned char mem3 __attribute__
On Thu, 19 Feb 2009 10:22:23 -0800 (PST)
Parthasaradhi Nayani partha_nay...@yahoo.com wrote:
Hi Vincent,
If I understand correctly, the word volatile itself is to tell the compiler
not to ignore the statement. I am not sure if your statement is correct, but
I have used
asm volatile
On Thu, Feb 19, 2009 at 11:14:40AM -0700, Weddington, Eric wrote:
If you are using WinAVR 20081205 then you can use one of the new
builtin functions:
void __builtin_avr_delay_cycles(unsigned long __n);
The prototype can be found in avr/builtins.h, but you shouldn't need
the prototype
-Original Message-
From:
avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of David Kelly
Sent: Thursday, February 19, 2009 12:36 PM
To: avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list]
On Thu, Feb 19, 2009 at 12:46:50PM -0700, Weddington, Eric wrote:
Hey Joerg, you must be busy! FreeBSD's avr-gcc used to track WinAVR
closer than this. :-)
He has been busy. He's been working on support for the new
ATmega128RFA1 device, which has been added recently to the toolchain.
-Original Message-
From:
avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Parthasaradhi Nayani
Sent: Thursday, February 19, 2009 11:37 AM
To: avr-gcc-list
Subject: [avr-gcc-list]
David Kelly wrote:
Related to another thread: as to why *not* to use an 8051:
Doesn't have avr-gcc.
So true. Althought it's pointless to add to the recent Freaks AVR vs
PIC thread, this is one of the most significant reasons why I prefer
the AVR line. They are inexpensive, the programmers
David Kelly wrote:
I have a Microchip 1000 or 2000 ICE thingy that cost about $2000 and was
used for one project. Given a choice I much prefer the ECROS
ICE Cube, avr-gcc, and of course an AVR.
Could I possibly quote that on the User Testimonials page, please?
Now that Atmel have replaced
Hello all,
I sent a mail on the subject but it seems to have got lost and therefore
posting again
I need to have a buffer of about 256 bytes starting at a page boundary in the
ram of Mega8. To get this I introduced a new section and assigned it an address
in makefile. I defined variables,
On Feb 19, 2009, at 9:44 PM, Graham Davies wrote:
David Kelly wrote:
I have a Microchip 1000 or 2000 ICE thingy that cost about $2000
and was used for one project. Given a choice I much prefer the
ECROS
ICE Cube, avr-gcc, and of course an AVR.
Could I possibly quote that on the User
David Kelly dke...@hiwaay.net wrote:
Strangely the JTAGICE mkII didn't work on the above hardware where the
ICE Cube did. I put a small 50 mA or maybe 100 mA linear regulator on
the 3.3V supply and the mkII drew more power off the target than the
regulator would provide.
The JTAG ICE
Vincent Trouilliez vincent.trouill...@modulonet.fr wrote:
Unfortunately I am on Linux so no WinAVR for me ! ;-)
Once I'm done with updating the FreeBSD toolchain (see the other
part of this thread), Bingo600's Linux build script will also
track that as well.
--
cheers, Jorg
Vincent Trouilliez vincent.trouill...@modulonet.fr wrote:
lcd.c:96: error: »asm« undeclared (first use in this function)
That's because you are using a -std setting the prevents GCC from
using its extensions by a name (asm) that is in the application name
space, like -std=c99. Either use
--- On Fri, 2/20/09, Weddington, Eric ewedding...@cso.atmel.com wrote:
First off, is that a typo above? It's suppose to be an uppercase
'W' like so:
LDFLAGs = -Wl,--section-start=.test=0x800200
It was a typo. Will test and reply. Thank you for your time.
Regards
Nayani
19 matches
Mail list logo
