mega128 USART0 versus USART1 issue You certainly are. :D
I fell for exactly the same mistake when I read your code.
Clever old David. :)
A
Wednesday, 12 November 2008 - 13:10
UART1 problem Hi David
It was my daughter's Harris Hawk, aka Rocky. She spent roughly seven years working with birds of prey at a falconry centre in East Devon.
Funny how somebody who is...
UART1 problem Just for posterity, David Prentice spotted the problem and posted the solution in another thread.
The line
UCSR1C = (1<<USBS1);
clears the two "UCSZ" bits, putting that...
Wednesday, 12 November 2008 - 12:00
Non-printing characters in progmem string? Hi Jim
I think that
"\x1CThis is a string"
will suit your needs.
One minor problem I have seen is
"\x1CCheers, mate!"
will give you a compile error (as it cannot make an 8...
Tuesday, 11 November 2008 - 17:14
Shift MSB out first My 2 pence worth (even though I know you have already sorted out your problem)...
I would just have reversed the order of the bits in the original array.
const unsigned char...
Tuesday, 11 November 2008 - 09:03
Data Type - One Bit Quote:The Renesas is big endian?Yes, but even if you have a collection of bits in a single byte, you cannot rely on the bit order (I believe.)
Of course, this may be a consequence...
Tuesday, 11 November 2008 - 08:52
Data Type - One Bit Thanks Cliff - didn't know about the efficiency thing.
However, if one is not particularly worried about efficiency, but are simply saving RAM, (a situation that we find we are in...
Monday, 10 November 2008 - 11:31
Data Type - One Bit If you want to have variables that only occupy a single bit, you can do this type of thing:
typedef struct
{
unsigned char TransmitBusy : 1 ;
unsigned char DoXonXOff :...
Monday, 10 November 2008 - 11:12
Return If you take the line
char LCD_getaddr(void)
there are two type specifiers that you need to take into account.
char specifies the return type of the function. It returns an 8-...
You certainly are. :D I fell for exactly the same mistake when I read your code. Clever old David. :) A
Hi David It was my daughter's Harris Hawk, aka Rocky. She spent roughly seven years working with birds of prey at a falconry centre in East Devon. Funny how somebody who is...
UCSR1C |= (1<<USBS1); will work much better Marcel. A
Just for posterity, David Prentice spotted the problem and posted the solution in another thread. The line UCSR1C = (1<<USBS1); clears the two "UCSZ" bits, putting that...
Hi Jim I think that "\x1CThis is a string" will suit your needs. One minor problem I have seen is "\x1CCheers, mate!" will give you a compile error (as it cannot make an 8...
My 2 pence worth (even though I know you have already sorted out your problem)... I would just have reversed the order of the bits in the original array. const unsigned char...
Quote:The Renesas is big endian?Yes, but even if you have a collection of bits in a single byte, you cannot rely on the bit order (I believe.) Of course, this may be a consequence...
Thanks Cliff - didn't know about the efficiency thing. However, if one is not particularly worried about efficiency, but are simply saving RAM, (a situation that we find we are in...
If you want to have variables that only occupy a single bit, you can do this type of thing: typedef struct { unsigned char TransmitBusy : 1 ; unsigned char DoXonXOff :...
If you take the line char LCD_getaddr(void) there are two type specifiers that you need to take into account. char specifies the return type of the function. It returns an 8-...
Sorry, didn't see the "Fedora" bit. A
Hi Ashok C:\WinAVR\avr\include is where all my system include files are and it is one of those. Is it the same on your machine? A
Pages