Post Created date
XMEGA RTC without interrupts
Hi Kabasan, thank you for helping me with that. Regarding clock, I saw, that I make mistake to assign 1kHz from 32kHz instead 32kHz. Will know for future.   Regards  ...
Friday, 11 December 2020 - 18:35
XMEGA RTC without interrupts
Hi Kabas, actually checking interrupt flag can be another option. Regarding RTC_CNT, as you noticed I put code on beginning on loop to generate pulse every time when loop will...
Friday, 11 December 2020 - 15:02
XMEGA RTC without interrupts
1. ATMEL ATXMEGA256A3U   2.   #include <avr/io.h> #include <util/delay.h> int main(void) { uint8_t merac_ukazovatel; uint32_t whole_time,j; uint16_t...
Friday, 11 December 2020 - 13:41
Xmega A3U I2C STOP signal missing
Hi Jim, mystery solved. As per datasheet, write time is up to 5ms, but slave not indicated when is done. Therefore after sending STOP signal I added delay 5ms and now working well...
Saturday, 26 October 2019 - 08:28
Xmega A3U I2C STOP signal missing
This is sequence of I2C instructions (From analyzer):   Setup Write to ['170'] + ACK      //Sending Slave address together with bit setup for reading ' ' + ACK...
Friday, 25 October 2019 - 19:47
Xmega A3U I2C STOP signal missing
Hi Jim, I'm seeing STOP on analyzer (previous attached screenshot is showing it), but STOP will only happen, if there is delay after instruction:   TWIE_MASTER_CTRLC|=3;...
Friday, 25 October 2019 - 19:14
Xmega A3U I2C STOP signal missing
I found out, that after command:   TWIE_MASTER_CTRLC|=3;   STOP will occur but I need to wait at least 26 uS to continue (attachment from analyzer). Can somebody please...
Friday, 25 October 2019 - 17:29
Xmega A3U I2C STOP signal missing
To be sure, that previous respond wasn't interpreted as answer will put question again here: this code is relevant:   i2c_slave_address_e=I2C_ADDRESS_EEPROM;  //...
Friday, 25 October 2019 - 05:11
Xmega A3U I2C STOP signal missing
Hi Jim, as per screenshot with I2C sequence, first is "Setup Write to['170'] +ACK", which is respond from device.. actual device address is 0x55. This should indicate, that device...
Tuesday, 22 October 2019 - 20:22
SPI not working well
With hint from Jim, I changed code as follow:   #define F_CPU 4000000UL   #define SPI_PORT PORTC #define SPI_MOSI 5 #define SPI_MISO 6 #define SPI_SCK 7 #define SPI_SS 4...
Wednesday, 19 June 2019 - 04:32
SPI not working well
Thank you Jim again. Now it is working.
Tuesday, 18 June 2019 - 16:48
SPI not working well
Hi Jim, I created extra function for read because read, that you should test SPIC.STATUS to be sure, that value is actual "while(!(SPIC.STATUS & 0x80)) spi_hodnota=SPIC.DATA...
Tuesday, 18 June 2019 - 14:50

Pages