Hello,
I am relatively new, not only to Atmel but also to Embedded system.
I am doing my first embedded project, 24 channel Data-Logger system.
This is Time based data logging system.
We are supposed to log the data after every 15 min.
After each 15 min, 58 bytes of data is supposed to be saved.
Hello,
I'm new to compiling avr-gcc-compiler. I would develop code for the TinyOS
project, but the used compiler in the project doesn't support my
mikrocontroller (Atmel atmega1284p). So I have to build an new toolchain. I
would build the avr-gcc-4.2.2 version or newer. Which patches from the
On Monday 04 May 2009 11:36, B.A.f.H. wrote:
Hello,
I'm new to compiling avr-gcc-compiler. I would develop code
for the TinyOS project, but the used compiler in the project
doesn't support my mikrocontroller (Atmel atmega1284p).
So I have to build an new toolchain. I would build the
I am relatively new, not only to Atmel but also to Embedded system.
typedef struct eventdata
{ uint8_t unit_add;
uint8_t card_add;
uint8_t event_no; //Event counter
uint8_t type; //Event type
Hello Ruud,
thanks, but I have another problem, the computer for developing has no internet
connection and for the computer with internet connection, I have no
admin-privileges.
thomas
On Monday 04 May 2009 11:36, B.A.f.H. wrote:
Hello,
I'm new to compiling avr-gcc-compiler. I would
On Monday 04 May 2009 13:58, B.A.f.H. wrote:
thanks, but I have another problem, the computer for developing has
no internet connection and for the computer with internet connection,
I have no admin-privileges.
I see. Indeed the script starts with downloading the required files. Now,
i
On Mon, 4 May 2009, Bob Paddock wrote:
uint16_t voltage[24]; // adc counts of 24 channels
in an array } ED; // total data = 58 bytes
Because of issues of structure packing it is better to define
structure items from
the largest to the smallest, ie. uint16_t
On Mon, 4 May 2009, David Kelly wrote:
On Mon, May 04, 2009 at 10:21:50PM +0930, Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
? ? ? ? ? ? ? ?uint16_t voltage[24]; ? // adc counts of 24
channels in an array } ED; ? ? ? ? ? // total data = 58 bytes
Because of issues
Daniel O'Connor wrote:
On Mon, 4 May 2009, David Brown wrote:
Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
uint16_t voltage[24]; // adc counts of 24
channels in an array } ED; // total data = 58 bytes
Because of issues of structure packing it is
On Mon, May 04, 2009 at 10:21:50PM +0930, Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
? ? ? ? ? ? ? ?uint16_t voltage[24]; ? // adc counts of 24 channels
in an array } ED; ? ? ? ? ? // total data = 58 bytes
Because of issues of structure packing it is better to define
On Mon, 4 May 2009, David Brown wrote:
Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
uint16_t voltage[24]; // adc counts of 24
channels in an array } ED; // total data = 58 bytes
Because of issues of structure packing it is better to define
Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
uint16_t voltage[24]; // adc counts of 24 channels
in an array } ED; // total data = 58 bytes
Because of issues of structure packing it is better to define
structure items from
the largest to the smallest,
so your external EEPROM will be accessed by functions you write. The
compiler does not know how to interface to the external EEPROM.
The functions you will need will take a pointer to your data structure
and then pack it into the external EEPROM, the other will take a
pointer and extract
On Mon, May 04, 2009 at 11:06:06AM -0700, Steven Michalske wrote:
so your external EEPROM will be accessed by functions you write. The
compiler does not know how to interface to the external EEPROM.
IIRC the compiler doesn't know internal AVR EEPROM either. AVR EEPROM is
not mapped in CPU
On May 4, 2009, at 11:33 AM, David Kelly wrote:
On Mon, May 04, 2009 at 11:06:06AM -0700, Steven Michalske wrote:
so your external EEPROM will be accessed by functions you write. The
compiler does not know how to interface to the external EEPROM.
IIRC the compiler doesn't know internal AVR
On Mon, May 04, 2009 at 11:46:40AM -0700, Steven Michalske wrote:
On May 4, 2009, at 11:33 AM, David Kelly wrote:
IIRC the compiler doesn't know internal AVR EEPROM either. AVR
EEPROM is not mapped in CPU address space but it faked into the load
map for debugging and device programming.
Yes, I thought about adding another section for this.
I found a lot of external eeproms annoying because they didn't want to
write a byte at a time.
What about using internal flash? You can jump to the bootloader
section execute spm and then return, and in this way on a 64kb chip or
so, write
The OP might consider writing to FLASH for his data logger assignment.
Is harder to use as one must write bigger blocks at a time.
Might be a wear limit depending on how many write/erase
cycles are needed.
While using Flash is possible, this tends to raise more problems than it
cures.
-
On Mon, 4 May 2009, David Brown wrote:
Daniel O'Connor wrote:
On Mon, 4 May 2009, David Brown wrote:
Daniel O'Connor wrote:
On Mon, 4 May 2009, Bob Paddock wrote:
uint16_t voltage[24]; // adc counts of 24
channels in an array } ED; // total data = 58 bytes
-Original Message-
From:
avr-gcc-list-bounces+eric.weddington=atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eric.weddington=atmel@nongnu.
org] On Behalf Of Thomas D. Dean
Sent: Monday, May 04, 2009 4:37 PM
To: avr-gcc-list@nongnu.org
Subject: [avr-gcc-list] Using
-Original Message-
From:
avr-gcc-list-bounces+eric.weddington=atmel@nongnu.org
[mailto:avr-gcc-list-bounces+eric.weddington=atmel@nongnu.
org] On Behalf Of Thomas D. Dean
Sent: Monday, May 04, 2009 4:37 PM
To: avr-gcc-list@nongnu.org
Subject: [avr-gcc-list] Using
-Original Message-
From: Thomas D. Dean [mailto:tomd...@speakeasy.org]
Sent: Monday, May 04, 2009 5:24 PM
To: Weddington, Eric
Subject: RE: [avr-gcc-list] Using in/out Instructions with ATmega128
On Mon, 2009-05-04 at 17:08 -0600, Weddington, Eric wrote:
Also, you need to
22 matches
Mail list logo
