We have a custom board based on 9263-EK eval board, with a NandFlash chip compatible with the one on the eval board (it is running Linux perfectly) but it fails when we try to boot WinCE image.

We follow all the steps as indicated by the docs in Adeneo´s binary BSP, but when we try to launch resident image in nanflash we obtain:

>System ready!
Preparing for download...
Master Clock is 49971200 Hz
---------------------------------------
--- Configuring Chip Select 3 ---
---------------------------------------
--- Desired timings ---
---------------------------------------
dwNWE_SETUP 0
dwNCS_WR_SETUP 0
dwNRD_SETUP 0
dwNCS_RD_SETUP 0
dwNWE_PULSE 28
dwNCS_WR_PULSE 60
dwNRD_PULSE 28
dwNCS_RD_PULSE 60
dwNRD_CYCLE 56
dwNWE_CYCLE 56
dwClockPeriod_ns 20
---------------------------------------
--- Real timings ---
---------------------------------------
dwNWE_SETUP 0
dwNCS_WR_SETUP 0
dwNRD_SETUP 0
dwNCS_RD_SETUP 0
dwNWE_PULSE 40
dwNCS_WR_PULSE 60
dwNRD_PULSE 40
dwNCS_RD_PULSE 60
dwNRD_CYCLE 60
dwNWE_CYCLE 60
Unknown flash device : Manufacturer 0x20 - Model 0xf1
FAILED


We think it's only because the vendor ID as we have another design based on the same board but with a nandflash chip from the samen vendor as the eval board (SAMSUNG) and it boots ok.
So, we would want to know if this must be fixed on EBOOT or WinCE sources.

Thanks in advance.
Ferdy.

The Device ID 0xF1 refers to an product of Samsung, however MID 0x20 refers to STM instead of Samsung.
So could you check 2 things?
1. Use some third party method to read the MID and DEVID of the NandFlash. For example, a hardware Nand Flash programmer can be used for this case. See whether those values are really 0xF1 and 0x20.

2. Use existing WinCE Demo package to boot up the AT91SAM9263EK you have and capture the debug output message. See whether the master clock settings and timing settings of NandFlash controller are the same as the ones from your custom board.

Thanks for the reply.

It's correct, the NandFlash in our custom board is from STM but it is suppossed to be compatible with the samsung one in timings as we have it working with Linux without problem.
The thing is that WinCE Demo only accept Samsung memories (onli de MID is what it checks, DEVID doesn´t matter) as we have other custom board with samsung NandFlash and it works with WinCE.
What we suppose is that there is a hard-coded list of MID where there isn´t STM MID, so it doesn´t work, and we would want to know where is this list, in EBOOT sources or in WinCE BSP sources or whatever.

Anyway, finally we have managed to unsolder the STM memory and solder a Samsung one and it's now working, but this will rise again in case it works for te client.

Thanks a lot.

So, that's the reason why the code cannot work with your Flash.
You are right, there is a list of supported devices and associated timing settings.
It is located in file PLATFORM\COMMON\SRC\SOC\ATMEL\COMMON\DRIVERS\NandFlash\Nandflashlib\NandIds.c.

You can update it and include your own setting.