|
I have AT91SAM9261-EK board and a custom board based on the AT91SAM9261-ek. I am able to load the Win CE 5.0 demo image onto the AT91SAM9261-EK board without a problem using SAM-BA 2.7. However, whenever I load it onto the custom board, the loading process goes as described but the Win CE image never boots up.
**** The only difference between the two boards is that AT91SAM9261-EK uses Samsung Nandflash K9F2G08U0M and the custom board uses K9F2G08U0A. Do I need different BSP for the different Nandflash chips? Here is the information that the custom board sends out through the DBGU, and it may be helpful***********************
INFO : Low Level Init : OK
Dataflash init OK
Starting eboot ...
Master Clock is 48054841 Hz
ÿMaster Clock is 49920000 Hz
ÿMaster Clock is 49920000 Hz
5
Debug serial initialized ........OK
OK
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built May 29 2007 15:47:33
Microsoft Windows CE 5.0 Ethernet Bootloader for the AT91SAM926xEK board
Adaptation performed by ADENEO (c) 2007
Master Clock is 49920000 Hz
Master Clock is 49920000 Hz
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 5 seconds 4 seconds 3 seconds 2 seconds 1 seconds 0 seconds
System ready!
Preparing for download...
Initialize image flash .......Master Clock is 49920000 Hz
->LoadBlocksInfo
LoadBlocksInfo::g_pBlocksInfo : 0x80043340
<-LoadBlocksInfo
OK
Launching windows CE image by jumping at address 0x2006a000Master Clock is 49920000 Hz
]¥¹‘½ÃÃÂCE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00
ProcessorType=0926 Revision=5
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8006a020
Windows CE Firmware Init
BSP 1.7.0 for the AT91SAM9261EK board (built Aug 10 2007)
Adaptation performed by ADENEO (c) 2007
+OALIntrInit
+SOCPioIntrInit()
-SOCPioIntrInit()
-OALIntrInit(rc = 1)
Initialize driver globals Zeros area...
pDrvGlobalArea 0x80068000 size 0x800 (0x80068800 -0x80068000)
Initialize driver globals Zeros area...done
2º8hüzh:3*-------------------
|PLLA : 180633600 Hz|
|PLLB : 95846400 Hz|
--------------------
Master Clock is 90316800 Hz
Master Clock is 90316800 Hz
OALTimerInit
+OALTimerInit
Master Clock is 90316800 Hz
Test : 0x160c
g_oalTimer.msecPerSysTick : 0x1
g_oalTimer.countsPerMSec : 0x160c
g_oalTimer.countsMargin : 0x0
g_oalTimer.maxPeriodMSec : 0xb8
g_oalTimer.countsPerSysTick : 0x160c
g_oalTimer.actualMSecPerSysTick : 0x1
g_oalTimer.actualCountsPerSysTick : 0x160c
g_oalTimer.curCounts : 0x0
Master Clock is 90316800 Hz
-OALTimerInit
pDrvGlobalArea->bEboot == TRUE. Forcing Clean Object store
+OEMPowerManagerInit
-OEMPowerManagerInit
OALKitlStart
Firmware Init Done.
+OEMInitWatchDogTimer
AT91SAM926x_DispWatchDog 8000!
AT91SAM926x_SetWatchDogConfiguration 20000 => 5120
Clipping The Watchdog period to the maximum : 0xFFF (15996 ms)
-OEMInitWatchDogTimer (result = 15996)
Sp=ffffc7cc
OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
+OALIoCtlHalInitRTC(...)
setrealtime 2857574912
-OALIoCtlHalInitRTC(rc = 1)
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
Handle Event:0x43f5c49a, sysintr=0x10Master Clock is 90316800 Hz
FMD_GetBlockStatus::Logical block 0x417 is marked as bad
FMD_GetBlockStatus::Logical block 0x6BA is marked as bad
SPIDriver - SPI_Init - Context: Drivers\Active\03
SPIDriver - SPI_Init - Context: Drivers\Active\04
SPIDriver - SPI_Init - Context: Drivers\Active\05
Master Clock is 90316800 Hz
Loading eboot settings in registry ...
DHCP ... 1
IP ... 0.0.0.0
MASK ... 0.0.0.0
MAC ... 00-12-72-72-20-20
+OALIntrDisableIrqs(1, 0x81204ee8)
RomBOOT
|
Forum
