Post Created date
ADC madness, help needed
Your code seems correct. What I'm more curious about is this: rblilja wrote:connected directly to the ADC0, ADC1 and ADC2 pins Is the output from the accelerometer connected to...
Friday, 28 September 2007 - 13:35
lss file does't mix source and assembly at high addresses?
goldspring wrote: the source and assembly are no longer mixed correctly. If you have functions that gets inlined when you build then this will happen, the c-code for the...
Thursday, 27 September 2007 - 09:11
GCC vs Imagecraft
Are you using AVR Studio to buil your project? And are you changing the makefile manually and are not using an external makefile? In that case it won't help to change the...
Friday, 21 September 2007 - 09:20
volatile variables
viktor_kun wrote:"And you don't have to declare ALL globals as volatile, just those that can change unexpectedly, like in interrupts." And what If my variables can change in...
Thursday, 20 September 2007 - 10:23
What is memory mapped mode?
Memory mapped is when you access peripherals and such in the same way as you access memory; for example instead of writing PORTA=0x11 and PORTB=0x12 you would write to the memory...
Thursday, 13 September 2007 - 07:45
optimization screws up do nothing loop
Try this in the while-loop: while(1) { volatile asm("nop"); } The compiler won't remove the asm so it should work. I think.
Tuesday, 11 September 2007 - 07:45
Problem at 115.2KBps with a 16MHz clock
Sounds like a grounding problem. Had the exact same issue with a battery powered device. I used an external MAX232 that I just connected to the ATmega with one wire (TXD). When...
Tuesday, 11 September 2007 - 07:39
Help please (error: redefinition of 'INTERRUPT') problem
You are probably using INTERRUPT(XXX_vector){..} which is the old way. Change all your INTERRUPT to ISR and the error should dissapear. ISR(XXX_vect){..} What happens is...
Friday, 7 September 2007 - 07:35
help AT93C56
js wrote:Quote:So you have to do the clocking of data manually. Huh? What's wrong with the "non manual" clock of the SPI? You may just have to select the correct SPI mode. Nothing...
Tuesday, 4 September 2007 - 08:47
help AT93C56
I donwloaded the datasheet for AT93C56A and it turns out it does not have an SPI interface, but just a 3-wire interface :) So you have to do the clocking of data manually.
Tuesday, 4 September 2007 - 07:45
help AT93C56
There is one thing that can be a problem. Since your EEPROM is active high you might have a pull-down somewhere for the CS. If you enable the SPI and set it to master mode and...
Monday, 3 September 2007 - 15:57
help AT93C56
malizia wrote:I write more information about my code. In the SPI_init I choose the AT8515 as a Master (MSTR=1), I enable the SPI com, DORD=1 and the clock rate (fclk/16=1Mhz,
Monday, 3 September 2007 - 12:51

Pages