Re: SanDisk 128MB CF + WiFi

From: David Varley (David.Varley_at_cborn.com)
Date: 02/24/05 

Date: Fri, 25 Feb 2005 09:15:26 +1100

Thanks, would that explain the existing (SMC) internal CF being unaccessible
when the SanDisk was in the external CF slot?

David

"Me" <Me@there.what> wrote in message
news:uGnNbpjGFHA.580@TK2MSFTNGP15.phx.gbl...
> We have had timing problems with Industrial (and some Commercial grade)
> SanDisk cards (in a boot-loader), had to add a delay (at least 100ms)
> between issuing a reset and reading the first Tuple.
> Might be worth having a look at the driver and seeing if adding a delay
> helps.
>
>
> "David Varley" <David.Varley@cborn.com> wrote in message
> news:OMhdXYgGFHA.3628@TK2MSFTNGP15.phx.gbl...
> > My platform is a Kontron ThinkIO, an industrial X86 with a CE.NET 4.2
BSP
> > (CEPC based) supplied by Kontron.
> > It has onboard CF (32MB) and a single external CF slot.
> > I've been successfully using external 256MB CF, booting MSDOS and then
CE
> > via LOADCEPC, for some time.
> > Reading on this forum that Prism based WiFi cards should work with the
> > Intersil driver, I bought a SanDisk SDWCFB-128 to try. I installed the
> > software in the same way as on the other CF cards, and it boots MSDOS,
> > which
> > then loads CE. The problem is that neither the SanDisk or the internal
CF
> > appear as mounted volumes under CE. If I pull the SanDisk card and boot
> > the
> > same image from internal CF, the internal one appears fine.
> >
> > Tracing shows that both disks are detected, and identified, but have
> > read-errors when the system trys to mount them.
> > In the identification phase, the only difference between the SanDisk and
> > the
> > other external CF seems to be the PIO timing mode, 1 for SanDisk and 4
for
> > the other. Can anyone shed light on this? Have others used the SanDisk
> > card
> > successfully?
> >
> > 0x81bf11d8: ATAPI:ResetController entered
> > 0x81bf11d8: ATAPI:ResetController: Controller reset done
> > 0x81bf11d8: NumSec=62976 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
> > 0x81bf11d8: Partition HD0 NumSectors=62960
> > 0x81bf11d8: MSPART!PD_OpenPartition: dwStoreId=00089410, PartName=HD0
> > 0x81bf11d8: >>> Loading module fatfsd.dll at address
0x03F00000-0x03F22000
> > (RW data at 0x01FF9000-0x01FF9674)
> > 0x81bf11d8: FSD_MountDisk: mounting volumes for hDsk=00083E60
> > 0x81bf11d8: ATAPI:ResetController entered
> > 0x81bf11d8: ATAPI:ResetController: Controller reset done
> > 0x81bf11d8: FATFS!ReadWriteDisk(READ, sector 0) failed (30)
> > 0x81bf11d8: FATFS!ReadWriteDisk: retrying...
> > 0x81bf11d8: ATAPI:ResetController entered
> > 0x81bf11d8: ATAPI:ResetController: Controller reset done
> > 0x81bf11d8: FATFS!ReadWriteDisk(READ, sector 0) failed (30)
> > 0x81bf11d8: FATFS!MountDisk: error reading MBR (30)
> > 0x81bf11d8: FATFS!OpenVolume: access time updates disabled
> > 0x81bf11d8: FATFS!OpenVolume: event logging enabled
> > 0x81bf11d8: FATFS!OpenVolume: automatic scanning disabled
> > 0x81bf11d8: FATFS!OpenVolume: write verify disabled
> > 0x81bf11d8: FATFS!OpenVolume: extra FAT on format disabled
> > 0x81bf11d8: FATFS!OpenVolume: force write through enabled
> > 0x81bf11d8: FATFS!OpenVolume: Codepage = 1
> > 0x81bf11d8: FATFS!OpenVolume: Number of path cache entries = 50
> > 0x81bf11d8: FATFS!InitVolume: sector 0 byte 0 suspicious (0x0)
> > 0x81bf11d8: FATFS!InitVolume: invalid BPB, volume deemed invalid
> > 0x81bf11d8: FATFS: Sec/FAT = 0!!!
> > 0x81bf11d8: FATFS: CacheSize = 16!!!
> >
> > Thanks for your help,
> >
> > David
> >
> >
>
>