* Joerg Wunsch [EMAIL PROTECTED] [2005-11-28 12:59]:
Günter Dannoritzer [EMAIL PROTECTED] wrote:
Not sure whether it was the additional switch --program-prefix that
was not shown in the installation instructions ...
That option is normally not needed. It defaults to ${prefix}/bin,
for
Günter Dannoritzer wrote:
Eric Weddington wrote:
You need to use the -mmcu= option for the link stage too, and specify
your microcontroller type.
I actually used that Makefile with WinAVR before and it always worked. I
tried it with the broken installation and it did not make any
David Kelly wrote:
The cleanest way to pull this off would be to lay a structure on the
memory-mapped device and allocate it in a named section. See
http://gcc.gnu.org/onlinedocs/gcc-3.4.3/gcc/Variable-
Attributes.html#Variable-Attributes
Then in the linking stage define the location of the
Looking at the schematic for the Butterfly, it's not readily apparent how it
manages to translate levels for outbound data. The docs seem to say it's
supposed to work, but my primitive understanding of electronics matches the
results: non-receipt of transmitted data. It could also be my
Mike Young [EMAIL PROTECTED] wrote:
Looking at the schematic for the Butterfly, it's not readily
apparent how it manages to translate levels for outbound data.
Well, it's a bit tricky, but it can be seen.
The incoming RxD is normally held at negative level by the external
transmitter (i.e.
[EMAIL PROTECTED] wrote:
Hi all:
I am looking for an automated way to update a static string in program
space when my project is built. Is there an easy way to do this, either
by adding an extra target to the makefile, or some other way? I'd prefer
not to manually have to change the
I tried exactly this, however I now get a linker error:
c:\apps\WinAVR\bin\..\lib\gcc\avr\3.4.3\..\..\..\..\avr\bin\ld.exe:main.
o: file format not recognized; treating as linker script
c:\apps\WinAVR\bin\..\lib\gcc\avr\3.4.3\..\..\..\..\avr\bin\ld.exe:main.
o:1: parse error
make: *** [main.elf]
Thanks. The pin is completely dead when I probe it with a scope. It can
hardly be hardware in this day and age. Right?
The gcc-port code looks as follows. Connection settings on the PC are 19200,
8N1, no handshake. Receive works just fine, else I wouldn't be bothering you
with it. I know for
Having solved all that, I wanted to add an auto-incrementing build
number to the build process, which lives in program memory. Here's how I
did it:
I made a buildnumber file, as follows:
buildnumber:
=8--
# This is the current build
On Wed, 30 Nov 2005 10:54, Mike Young wrote:
// Set baud rate
UBRRH = (unsigned char)(baudrate8);
UBRRL = (unsigned char)baudrate;
// Enable 2x speed
UCSRA = (1U2X);
// Enable receiver
UCSRB = (1RXEN)|(0TXEN)|(0RXCIE)|(0UDRIE);
This line turns the
[EMAIL PROTECTED] wrote:
Hi all:
I am looking for an automated way to update a static string in program
space when my project is built. Is there an easy way to do this, either
by adding an extra target to the makefile, or some other way? I'd prefer
not to manually have to change the
11 matches
Mail list logo