Post Created date
Atmega32: SPI SS signal drops prematurely
theusch wrote: In cases such as this, I try to conduct a sanity check.  You are pretty close already...   Create a complete small test program.  Most of what is...
Thursday, 25 October 2018 - 17:24
Atmega32: SPI SS signal drops prematurely
david.prentice wrote: All the same,   your code "looks" ok except for the mode setting.   It should be (mode << 2) for regular SPI peripheral. ...
Thursday, 25 October 2018 - 15:42
Atmega32: SPI SS signal drops prematurely
theusch wrote: The mode may not be wrong, but curious that with all of your other annotated statements there is no mention of data order or idle clock state or data/clock edge...
Thursday, 25 October 2018 - 15:24
Atmega32: SPI SS signal drops prematurely
Here's how I'm initializing the SPI. SPI_CS_N is the actual SS pin on the AVR and is fed to the SD card, SPI_CMD_CS_N and SPI_FILE_CS_N are just outputs to the FPGA and both the...
Thursday, 25 October 2018 - 13:21
Atmega32: SPI SS signal drops prematurely
ajcrm125 wrote: I'm not familiar with this gotcha. Can you clarify? Oh you mean how unless SS is defined as an output the spi mode can switch from a master to a slave? Yes I'm...
Thursday, 25 October 2018 - 11:13
Atmega32: SPI SS signal drops prematurely
I'm not familiar with this gotcha. Can you clarify?
Thursday, 25 October 2018 - 10:39
Atmega32: SPI SS signal drops prematurely
I don't see how the SPIF can ever be set when I enter the SPI_xfer function. According to the datasheet once I read from SPDR the SPIF bit gets cleared.    "...
Thursday, 25 October 2018 - 01:03
Atmega32: SPI SS signal drops prematurely
Above should read "SPIF should only be set once all bits are sent". (Can't seem to edit original post for some reason)
Wednesday, 24 October 2018 - 23:54
petitfs + Data Size Viewer = surprising results?
Ooooo this is good stuff. Thank you guys!
Tuesday, 17 October 2017 - 20:44
petitfs + Data Size Viewer = surprising results?
the DWORDs are 32 bits not bytes   Doh... I realized that shortly after I typed that :P   The usual "culprit" for over RAM usage in AVR are "const" things that could be...
Tuesday, 17 October 2017 - 18:07
petitfs + Data Size Viewer = surprising results?
Ahhhh the tool is telling me that function consumed 694 bytes of Text Segment space (code) not RAM.    Is there an option to tell me how much RAM is being used?  I'...
Tuesday, 17 October 2017 - 13:30
Infinite loop... Waiting for an condition that's already true?
theusch wrote:   "volatile" issue?   Bingo!  Thanks for the quick response!
Wednesday, 11 October 2017 - 18:47

Pages