RTOS/TM4C1294NCPDT: SD Card Board Connection

Would you please provide a list of which signals from the EK-TM4C129XL are connected to each of G, DO, CLK, DI, CS and + ? It is difficult to count pins and flip between the pictures.

Sure thing Bob,

G Red Wire connected to Ground Pin
DO Purple Wire connected to pin PD0
CLK White Wire connected to pin PD3
DI Black Wire connected to pin PD1
CS Green Wire connected to pin PC7
+ Yellow Wire connected to 3.3V

Also, it seems that my DI and DO pins from the manufacturer are flipped. When I reverse those two pins I get an error if I include a disk_initialize(0);, it returns 0x01. When they are in their current position, it returns 0x00.

Sorry guys!

    src = fopen(inputfile, "r");
    if (!src) {
        System_printf("Creating a new file \"%s\"...", inputfile);

        /* Open file for both reading and writing */
        src = fopen(inputfile, "w+");
        if (!src) {
            System_printf("Error: \"%s\" could not be created.\n"
                          "Please check the Getting Started Guide "
                          "if additional jumpers are necessary.\n",
                          inputfile);
//            System_abort("Aborting...\n");
        }
        //This is actually where the program crashes!
        fwrite(textarray, 1, strlen(textarray), src);
        fflush(src);

Hi Stephen,
I checked your wiring configuration against the TIRTOS FatFS example and everything looks correct. I also consulted another (better) expert who confirms that the SD card need not be preformatted.

Is it this card with the 3v/5v switch?
www.robotshop.com/.../micro-sd-card-breakout-module.html

I told Bob incorrect information! It does not format the SD card.

Yes, this is the board that I'm using. I know there is a null pointer somewhere in the code for fopen, but I don't remember exactly where. I'll step through the code and post what variable ends up being null.

Thanks Bob.

I have made sure the SD card I put in there is formatted to FatFS32.

I don't know if this helps at all:

When declaring the const char inputfile[] = "fat:0:input.txt"; and const char outputfile[] = "fat:0:output.txt"; if I change the value to "input.txt" and "output.txt" the code runs smoothly, just doesn't actually write the file to my sd card. Also, once I've done this one time, it will change from creating the file to using existing file.

Also running it without an SD card in this configuration the code still works.

Great points cb1_mobile.

I have not tested this board in any other capacity other than through the launchpad. I have a secondary sd board coming, but that doesn't necessarily give the information you're looking for.

I am currently using a 4 gb sdhc card. I will see if we have a lower capacity card and see if that does the trick.

Thank you - appreciated.

Too often - those w/"focused expertise" neglect and/or discount the value of, (KISS Directed/Inspired) broader-based, "fact-finding!"

The "difficulty or challenge" - enforced by "higher capacity" (even type) SD cards - has been recognized/reported - and I believed to warrant (some) mention here...

(as a "kid" I had (tested/proven) "photographic memory" (not so much now) yet IIRC - "HC" cards DO (or past HAD) challenged!)

I tried a 2 gb SD card and that was able to write.  It is still having an issue that I'm going to look further into where when it's trying to read the file back in I get this error:

Invalid CIO command (0) in the CIO buffer at address (0x20003948) was not recognized. Please check the device and program memory maps.

This is happening I'm guessing at this block of code because the error keeps being written until I end the program:

    while (true) {
        /* Read from output file */
        bytesRead = fread(cpy_buff, 1, CPY_BUFF_SIZE, dst);
        if (bytesRead == 0) {
            break; /* Error or EOF */
        }
        cpy_buff[bytesRead] = '\0';
        /* Write output */
        System_printf("%s", cpy_buff);
        System_flush();
    }

Thanks again - great to see "such responsiveness" here. And it (does) appear you are "gaining ground" - due to the "KISS" (make NO assumptions) method! (Pity that KISS is banned here...of course - minus ANY explanation/justification!)

I've added to my initial post - should memory serve "HC" cards (increase) the "degree of difficulty."

Here's a fun one. We got a 32 GB SDHC I and that works in the system. I think I'm having an ejection problem though because it stripped it's formatting.

As always - "when in doubt" - expand the "size of the sample."     (Pure KISS)

Thank you for your "Resolution" award - appreciated.

I would still, "Search for more (i.e. several) lower capacity, most basic, "SD cards" procure & test "those."    (i.e. yet even more, KISS)

Should those "work" - you then are (reasonably) well-armed to discover, "Where & When (maybe even Why) the more advanced SD Cards FAIL" - and potentially develop a, "Real Solution."