SMDK2410 FMD/SmartMedia block problem

From: Tim Schuerewegen (wincepb-at-xgsdev-dot-com)
Date: 08/30/04 

Date: Mon, 30 Aug 2004 18:42:49 +0200

Platform Builder 5.0

I am currently modifying the SMDK2410 SmartMedia FMD driver for my custom
BSP and there is something very strange going but can not investigate this
myself due to missing source code for "FLASHDRV.DLL:BuildupMappingInfo()".
Any help is appreciated.

For every logical block, which is contained within the spare area of each
nand page, with a value larger than 0x7F following message pops up
"FLASHDRV.DLL:BuildupMappingInfo() - Unable to map logical sector 0xffffffff
to physical sector <value>"
Followed by a FMD_WriteSector() of sector 0.

On a sidenote, will the SmartMedia card automatically get mounted using the
default registry settings from the SMDK2410 BSP or do I need to add
something? If not, then can someone please point out what to add because the
help file was not very clear about that.

My device contains a 32MB SmartMedia card which was formatted as FAT by
another device.
pFlashInfo->wDataBytesPerSector = 0x200
pFlashInfo->dwNumBlocks = 0x800
pFlashInfo->wSectorsPerBlock = 0x20
pFlashInfo->dwBytesPerBlock = (pFlashInfo->wSectorsPerBlock *
pFlashInfo->wDataBytesPerSector)

------

Block 0x2F4 is OK (6th byte of spare area is 0xFF) and the logical block is
0x7F (= (0x10FE >> 1) & 0x3FF)

<snip>
1832033 PID:8c489e7e TID:8c489342 ++FMD_GetBlockStatus
1832053 PID:8c489e7e TID:8c489342 blockID = 0x2f4
1832073 PID:8c489e7e TID:8c489342 ++FMD_ReadSector
1832095 PID:8c489e7e TID:8c489342 startSectorAddr=0x5e80 pSectorBuff=0x0
pSectorInfoBuff=0x802e818 dwNumSectors=0x1
1832132 PID:8c489e7e TID:8c489342 RdPageInfo
1832150 PID:8c489e7e TID:8c489342 FF FF FF FF FF FF 10 FE C3 0C F3 10 FE FF
CF FF
1832178 PID:8c489e7e TID:8c489342 --FMD_ReadSector
1832198 PID:8c489e7e TID:8c489342 --FMD_GetBlockStatus
<snip>

Block 0x2F5 is OK (6th byte of spare area is 0xFF) and the logical block is
0x80 (= (0x1100 >> 1) & 0x3FF)

<snip>
1831716 PID:8c489e7e TID:8c489342 ++FMD_GetBlockStatus
1831737 PID:8c489e7e TID:8c489342 blockID = 0x2f5
1831757 PID:8c489e7e TID:8c489342 ++FMD_ReadSector
1831776 PID:8c489e7e TID:8c489342 startSectorAddr=0x5ea0 pSectorBuff=0x0
pSectorInfoBuff=0x802e834 dwNumSectors=0x1
1831822 PID:8c489e7e TID:8c489342 RdPageInfo
1831840 PID:8c489e7e TID:8c489342 FF FF FF FF FF FF 11 00 03 0F 33 11 00 56
A9 6B
1831868 PID:8c489e7e TID:8c489342 --FMD_ReadSector
1831888 PID:8c489e7e TID:8c489342 --FMD_GetBlockStatus
<snip>

However, FLASHDRV.DLL complains about sector 0x5EA0 (block 0x2F5) and wants
to write something to the spare area of sector 0 (block 0).

<snip>
1832219 PID:8c489e7e TID:8c489342 FLASHDRV.DLL:BuildupMappingInfo() - Unable
to map logical sector 0xffffffff to physical sector 0x00005ea0
1832262 PID:8c489e7e TID:8c489342 ++FMD_WriteSector
1832283 PID:8c489e7e TID:8c489342 startSectorAddr=0x0 pSectorBuff=0x0
pSectorInfoBuff=0x802e884 dwNumSectors=0x1
1832318 PID:8c489e7e TID:8c489342 WrPageInfo
1832337 PID:8c489e7e TID:8c489342 FF FF FF FF FF FF FE FF
1833435 PID:8c489e7e TID:8c489342 --FMD_WriteSector
<snip>

After the status of the last block (0x7FF) has been retrieved the following
is reported

<snip>
4540653 PID:8c489e7e TID:cc491686 FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() -
Secondary table doesn't exist for logical sector 0x0!!!
4540695 PID:8c489e7e TID:cc491686 FLASHDRV.DLL:ReadFromMedia() - Unable to
determine physical sector address for logical sector 0x00000000
4540738 PID:8c489e7e TID:cc491686 FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() -
Secondary table doesn't exist for logical sector 0x0!!!
4540779 PID:8c489e7e TID:cc491686 FLASHDRV.DLL:ReadFromMedia() - Unable to
determine physical sector address for logical sector 0x00000000

<snip>

Relevant Pages