Hello,
My latest results are written down
I found in the meantime the following project in the firmwarepackage.
STM32Cube_FW_H7_V1.11.0\Projects\STM32H745I-DISCO\Applications\FatFs\FatFs_Shared_Device
I can compile and download the project, but it is still not running as expected yet. After analyzing the program code, I saw, the eMMC memory interface will never be initialized (maybe I am blind, but I never reached a similiar function during debuggin the code step by step (Function MMC_MspInit in stm32h745i_discovery_mmc.c)).
I added the following lines in my main.c for the CM7 Core, . The pin assign seems as expected within the definition for the ports.
const uint32_t mmcInstance = 0; // If this is correct, I am not pretty sure.
res = BSP_MMC_Init(mmcInstance);
It seems, it is running until I want to read out the new created file. I excluded all influences from, the CM4 Core, but the result ist he same. While reading from the file, I get the error FR_DENIED.
(This is the serial output from UART to show the activities within the code (original from the code)
[CM7]: Welcome!
[CM7]: Creating FileSystem...
[CM7]: FileSystem Created successfully!
[CM7]: opening 'cm7.log' for writing...
[CM7]: 'cm7.log' '34' bytes written...
[CM7]: 'cm7.log' Read out failed...
When I step again through the code to look for the read and write functions ( I would expect to hit the functions like BSP_MMC_ReadBlocks(), BSP_MMC_WriteBlocks() , HAL_MMC_ReadBlocks() or HAL_MMC_WriteBlocks.
This is not the case. My read and write process is finished in the diskio.c within the following functions. Maybe something in the background is happen, but I have no clue, where and what.
But why I got the return value FR_OK for fs_write() and fs_mount()?
DRESULT disk_read (
BYTE pdrv, /* Physical drive nmuber to identify the drive */
BYTE *buff, /* Data buffer to store read data */
DWORD sector, /* Sector address in LBA */
UINT count /* Number of sectors to read */
)
{
DRESULT res;
res = disk.drv[pdrv]->disk_read(disk.lun[pdrv], buff, sector, count);
return res;
}
/**
* @brief Writes Sector(s)
* @param pdrv: Physical drive number (0..)
* @param *buff: Data to be written
* @param sector: Sector address (LBA)
* @param count: Number of sectors to write (1..128)
* @retval DRESULT: Operation result
*/
#if _USE_WRITE == 1
DRESULT disk_write (
BYTE pdrv, /* Physical drive nmuber to identify the drive */
const BYTE *buff, /* Data to be written */
DWORD sector, /* Sector address in LBA */
UINT count /* Number of sectors to write */
)
{
DRESULT res;
res = disk.drv[pdrv]->disk_write(disk.lun[pdrv], buff, sector, count);
return res;
}
Could it be possible, the example from ST is not completed yet?
Thanks for your feedback,
Jan
