Databases
StackOverflow2013
Postsdbo
POSDHC SPI write issues
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSDHC SPI write issues
    primarykey
    data
    text
    <p>I've been trying to do an SD card interface with the <a href="http://www.keil.com/dd/chip/4629.htm" rel="nofollow">LPC1766</a> <a href="http://en.wikipedia.org/wiki/Serial_Peripheral_Interface_Bus" rel="nofollow">SPI</a> peripheral for a while and right now I'm stuck in a problem that I couldn't find the answer anywhere.</p> <p>The problem is: SDHC cards are not responding to write and read commands as expected.</p> <p>Everything works fine on the initialization that was based on Chan's flowchart and on an NXP application note. I can differentiate the cards versions, read the OCR, CID, CSD and determine their sizes.</p> <p>After that step I start writing single blocks every one second and reading it back to check the data integrity. On a Kingston SDHC 4&nbsp;GB Class&nbsp;4 card I can send a first write command but on the second one the card does not even answer (0x00 or 0x01) to the CMD24. With a SanDisk 4&nbsp;GB Class&nbsp;4 card the results are different, every command is answered by the card, but I get only zeroes when reading the data back (I'm sure I'm not writing zeroes). If I use SDSC cards, everything works fine.</p> <p>I'm aware that SDHC are block addressed and not byte addressed and that I need to send ACMD41 with the CCS on for SDHC. I also know that the clock frequency is not an issue (using 400&nbsp;KHz to start and then 20&nbsp;MHz to write/read), because I just turned on the CRC checking and all cards are accepting the commands and data. If I stop calculating the CRC all cards reject commands and data.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeter Mortensen
    1. USMartini
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSDHC SPI write issues
      1. USjeb
      1. VTFavorite
    2. VO
      singulars
      1. POSDHC SPI write issues
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSDHC SPI write issues
      1. This table or related slice is empty.
      1. VTUpMod
    1. COUsing Chan's [FatFs](http://elm-chan.org/fsw/ff/00index_e.html), I have had variable success with cards greater than 2Gb. I have always assumed that the cards that worked were SD Version 1.01 SDSC cards with 2048 byte blocks rather than v2.0 SDHC. I have never looked into it further as I did not need the higher capacity.
      singulars
      1. POSDHC SPI write issues
      1. USClifford
    2. COI remember that I had modified Chan's code a bit, so I could initialize SanDisk cards properly without powerUps. Do you could show the SD-Card code you used?
      singulars
      1. POSDHC SPI write issues
      1. USjeb
    3. COThe cause could be also the SPI driver, if you are using the FIFO's, be aware of the problem that the RX-Fifo can overflow when filling the TX-Fifo completly, as it can send effectivly 17 bytes ( my driver failed there)
      singulars
      1. POSDHC SPI write issues
      1. USjeb
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload