RTOS/TMS320C6746: emmc pdk driver

Hi Ilan,

You shouldn't need to call MMCSD_Params_init(&MMCSDParams) as MMCSD_open is passing NULL parameter which will pass the default values anyway.

What do you see when you halt the program? Is it stuck in a while loop somewhere or is it giving you an error?

Best,
Sahin

Hi Sahin

when I am halting the program it stops in function 

MMCSD_v0_transfer(MMCSD_Handle handle,MMCSD_v0_Transaction *transaction, mmcsdCmd_t cmd)

in the line in red:

/*
* Wait for the transfer to complete here.
* It's OK to block from here because the MMCSD's Hwi will unblock
* upon errors
*/
if(0U != hwAttrs->enableInterrupt)
{
MMCSD_osalPendLock(object->commandComplete, SemaphoreP_WAIT_FOREVER);
}
else
{
uint32_t status =0;
cnt = MMCSD_TIME_OUT_COUNT;
while(0 == (status & transaction->checkStatus) && (cnt != 0))
{
status = MMCSDGetIntrStatus(hwAttrs->baseAddr);
MMCSD_v0_cmdStatusFxn((uintptr_t) handle, status);
cnt--;
}
}

I notes that In the driver file 

MMCSD_V0.c

the code that check for definition MMCSD_EDMA_ENABLED and ENABLE_EMMC are grey indicating that those definition are not defined.

I looked at the project in predefined symbol and the  MMCSD_EDMA_ENABLED was defined but ENABLE_EMMC was not so I add it but it didn't change the behavior.

do I need to define some predefined symbol like MMCSD_EDMA_ENABLED and ENABLE_EMMC before driver compilation? (I tried to define it in the driver code and recompile it, but without any change)

As i don't use uart0 in my board I cannot see the error message from the driver

Is there a way to compile the driver without optimization so I could debug the driver code?

Best Regards

Ilan

Hello Ilan,

You can change optimization settings by going to Project Properties -> Build -> Compiler -> Optimization

Regards,
Sahin

Hi

I need to change driver code optimization and not the test example project. I build the drivers by using gmake, is there any option to compile the driver for debug?

If I look on the mmcsd0 lines with scope I can see that after the open command there is some activity in the CMD line, and clk=215.5khz, and no activity on data lines.

Best Regards

Ilan

Hi Sahin

I still have this problem. I managed to compile the mmcsd driver in a way that i can use the debugger by moving all the driver source to my test project. in that way i can debug the code and use breakpoints.

when I call the open function it calls the function MMCSD_v0_initEmmc. this function send command to the emmc device. the commands are sent on the CMD and CLK lines. the first command that is being sent has the ID 0. this is used to reset the device. the second command  with ID 1 is sent and the emmc need to return an answer - the OCR register value with bit31=1. this indicates that the device is ready. I check the CMD line with scope and I can see that the first and second command are being sent to the device and the device return (only a single time after power up) the value 0x00ff8080. in the device datasheet it says that the device need to return the value 0xc0ff8080. (bit31 indicate that the device is ready) but in my case the device return not ready. 

The driver send command 1 in a loop till the device will return that it is ready but in my case the device return an answare only on the first try after power up with the value not ready. after that the device do not return any value even after reset.

I check the printed board and it seems OK. we tried also to make an X RAY check on the memory chip and the company that assembled the board found out that there may be a problem with the device assembly so they assembled it again. but still I have the same problem.

Currently I am trying to contact the device manufacturer - the device is from sandisk, SDIN8DE2-4G-XI.

It seems strange that after power up the device return an answer that is is not ready but after that it does not return any answer. even if I start the test program (in the test program I also set the device reset line)

the device do not response. it seems that the reset line do not work as there is some hardware problem. 

Any advice will be welcome

Best Regards

Ilan 

Hi Ilan R,

          I'm trying to use the eMMC driver, and I use  a 16Gb eMMC device (MTFC16GAKAECN-2M),

          I follow the modifications as you did in the main_emmc.c file, while taking no changes with the MMCSD_v0.c file.

         I find the MMCSD_lcdkOMAPL138_c674xTestProject project, which is a non-DMA with polling mode test project, can work normally.

         But the MMCSD_lcdkOMAPL138_DMA_c674xTestProject project can not work normally:

       and then I modified the MMCSD_v0.c file as you did, nothing changes.

       Have you tried the driver with EDMA or with Interrupt?

       B.R.

Frank

Hi Frank 

you can use the following steps to build the DMA project:

• import project: MMCSD_FatfsConsole_lcdkOMAPL138_DMA_c674xExampleProject

• add files main_emmc.c , MMCSD_log.c , MMCSD_log .h that can be found at  \pdk_omapl138_1_0_2\packages\ti\drv\mmcsd\test\src

• in main_emmc.c  change all SOC_OMAPL137 to SOC_OMAPL138

• delete main.c

• change file\pdk_omapl138_1_0_2\packages\ti\drv\mmcsd\src\v0\ MMCSD_v0.c  according to the instruction below (I had problem to upload the file)

change line 159 to:

#define EMMC_FIX

/** \brief MMC Argument Register value for OCR command. */
#ifdef EMMC_FIX
#define MMCSD_OCR_AGRHL_REG_VAL (0x40FF8080)
#else
#define MMCSD_OCR_AGRHL_REG_VAL (0x00FF8000)
#endif

and lines 1753 to:

#ifdef EMMC_FIX
cmdObj.cmd.xferType = MMCSD_DIR_READ;
#else
cmdObj.cmd.xferType = MMCSD_DIR_DONTCARE;
#endif
cmdObj.cmd.lineChr = MMCSD_LINECHR_PUSHPULL;
transaction.arg = object->rca << 16U;
transaction.blockCount = 1U;
transaction.blockSize = 512U;
#ifdef EMMC_FIX
transaction.checkStatus = MMCSD_EVENT_EOFCMD | MMCSD_EVENT_READ;
transaction.flags = MMCSD_CMDRSP_READ | MMCSD_CMDRSP_DATA;
#else
transaction.checkStatus = MMCSD_EVENT_EOFCMD | MMCSD_EVENT_ERROR;
transaction.flags = MMCSD_CMDRSP_READ | MMCSD_CMDRSP_WRITE;
#endif

• build the mmcsd driver according to ti instruction

this test work for me but I had some other problems with the driver after trying to integrate it in my project

•  if I try to read from memory after open, the read stuck after board power up (turning power off and on) but on the second run from debug it run correctly. this means that after programming the unit and switch it on, it will stuck. the work around I currently use is to write dummy data to the emmc to an address space not in use and then use the device normally.
• I do not understand why can I read and write data from address 0, If I use address less then 0x4000 the read and write are unstable - it can work for 10 times and then fail
• I have also have another board that work on debug but not on power up (even after the work around of writing and then reading.
• I add also delay between write operation (I had some problem when reading write command one after the other without delay)

It seems to be some problem with the Edma or memory that do not work correctly,

In my project   I use the starterWare drivers (EDMA and other), as I didn't find support for EMMC in starterWare I tried this driver from the new SDK, but lately I found out that there is support for the emmc driver in starterWare sourceforge site I am planing to check it too and to find out if it work correctly.

Sahin can you please let us know if you have any solution for the EMMC driver?

What is the address space that I can use for read and write?

why does after power up the read operation stuck (on EDMA transfer) after driver open?

the changes I made in the driver code were -

• argument for CMD1 was not correct in the original driver (the memory is block address and not byte address)
• CMD 8 read CSD_EXT register using DMA and memory data lines so I change the transfer to be as read command

Thanks

Ilan

Hi Ilan R,

       Which exmaple do you use, the DMA version or the nonDMA version?

       I use MTFC16GAKAECN-2M, and I take some tests and find:

       https://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/112/t/668731

       The phenonmen is a little different from yours. But in conclusion, I agree with you, I think there is some problem with this driver for the C6748 (OMAP138) or with the driver building scripts.

       Need help from TI!

       B.R.

Frank

Hi Sahin Okur,

I use MTFC16GAKAECN-2M, and I take some tests and find:

e2e.ti.com/.../668731

The phenonmen is a little different from Ilan R. But in conclusion, I agree with Ilan R, I think there is some problem with this driver for the C6748 (OMAP138) or with the driver building scripts.
Need help from TI!

B.R.

Frank

Hi Sahin

Can you please let me know if Ti planed to update this driver - as I mention above the driver for OMAP138 and c6748 dsp is complied with V0 source files, and the problems currently detected:

- the driver work with 1 data line width only - low speed and not with 8 data lines

- there are bugs in CMD1 and CMD8 (see my report above)

- some times the read and write operation fails (the data written is not the data that was reading)

Best Regards

Ilan

Hi Sahin,

      Thank you so much for reply.

      I follow your guide and rebuild the emmc driver (add #define ENABLE_EMMC in the MMCSD_v0.c ), and then run the nonDMA version test program, the program stuck at the emmc_write() function.

      Could you provide me a        DMA version project with Interrupt enabled that suit for C6748+eMMC, which can work normally?

      Could you provide me a nonDMA version project with Interrupt enabled that suit for C6748+eMMC, which can work normally? As I metioned, I found the nonDMA version have to use "delay" between emmc_write/emmc_read, which means the app cannot be used freely.

      We've stuck at this problem for several month. And if the emmc cannot be used, we have to give up C6748 and move to other platforms. Really need TI's help!

      For the block size of the MTFC16GAKAECN-2M I use, it's 512.

      For the boot mode, do you mean that. If the dsp BOOT MODE = 00010000  which means NAND16 boot, the DMA driver cannot work normally, while the if the Boot mode=00001110  which means  NAND8 boot, the driver can work normally? I use  BOOT MODE = 0001 1100, which is emmc boot, can the DMA driver work normally?

Thank you so much!

Frank