User wince5 app can not start in 9260 board

This forum is for users of Atmel's SAM Series and who are interested in using WinCE OS.

Moderator: nferre

devmail
Posts: 3
Joined: Sat Mar 30, 2013 3:58 am

User wince5 app can not start in 9260 board

Sat Mar 30, 2013 4:15 am

Hi, I have a problem.
In a 9260 Evaluation Board, everything is ok.
When plug the 9260 core board in my mainboard, wince 5.0 starts ok. ftpd and telnetd can be accessed. USB port also works.
But my app in nandflash directory can not start, and text files in this directory are in a mess. Back in EVB, everything is ok.
It seems wince can not read file in nandflash direcotry. If something wrong in nandflash, why wince starts ok?
No debug serial in my mainboard, so it is not easy for me to find the cause.

Some bus transceiver on EBI bus, they are controlled by RD and CS4.

Could anyone help me?

Following is the boot message on EVB:

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Mar 13
2013 17:29:29
Microsoft Windows CE 5.0 Ethernet Bootloader for the AT91SAM926xEK board
Adaptation performed by ADENEO (c) 2007

Master Clock is 49908901 Hz
Master Clock is 49908901 Hz

Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 0 seconds
System ready!
Preparing for download...
Initialize image flash .......Master Clock is 49908901 Hz
NandFlash_LowLevelInit::Addr : Base 0x40000000 | Ale 0x40200000 | Cle 0x40400000

NandFlash_LowLevelInit::DeviceIDs : Man 0xEC | Dev 0xF1
NandFlash_LowLevelInit::Device name : Samsung - K9F1G08U0A
NandFlash_LowLevelInit::Bus Width 8
NandFlash_LowLevelInit::Large Pages
->LoadBlocksInfo
LoadBlocksInfo::g_pBlocksInfo : 0x80043420
<-LoadBlocksInfo
OK
Launching windows CE image by jumping at address 0x20068000Master Clock is 4erne
l for ARM (Thumb Enabled) Built on Aug 4 2008 at 18:38:38
ProcessorType=0926 Revision=5
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 80068020
Windows CE Firmware Init
BSP 1.2.0 for the AT91SAM9260EK board (built Mar 13 2013)
Adaptation performed by ADENEO (c) 2005
+OALIntrInit
+SOCPioIntrInit()
-SOCPioIntrInit()
-OALIntrInit(rc = 1)
Initialize driver globals Zeros area...
pDrvGlobalArea 0x80058000 size 0x800 (0x80058800 -0x80058000)
IniMaster Clock is 99049984 Hz
OALTimerInit
+OALTimerInit
Master Clock is 99049984 Hz
Test : 0x182e
g_oalTimer.msecPerSysTick : 0x1
g_oalTimer.countsPerMSec : 0x182e
g_oalTimer.countsMargin : 0x0
g_oalTimer.maxPeriodMSec : 0xa8
g_oalTimer.countsPerSysTick : 0x182e
g_oalTimer.actualMSecPerSysTick : 0x1
g_oalTimer.actualCountsPerSysTick : 0x182e
g_oalTimer.curCounts : 0x0
Master Clock is 99049984 Hz
-OALTimerInit
pDrvGlobalArea->bEboot == TRUE. Forcing Clean Object store
+OEMPowerManagerInit
-OEMPowerManagerInit
OALKitlStart
Firmware Init Done.
+OEMInitWatchDogTimer
AT91SAM926x_DispWatchDog 3fff2fff!
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 3769933984
-OALIoCtlHalInitRTC(rc = 1)
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
Handle Event:0xe3ea33ce, sysintr=0x10Master Clock is 99049984 Hz
FMD_GetBlockStatus::Logical block 0x1C4 is marked as bad
FMD_GetBlockStatus::Logical block 0x2F7 is marked as bad
OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49
OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49
SPIDriver - SPI_Init - Context: Drivers\Active\04
SPIDriver - SPI_Init - Context: Drivers\Active\05
SPIDriver - SPI_Init - Context: Drivers\Active\06
SPIDriver - SPI_Init - Context: Drivers\Active\07
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
Loading WinCE driver for ATMEL EMACB controller
Using registry ethernet configuration
PHY ID : 25278624
PHY_GetConfiguration : autoneg not complete

EMAC Init : 100 Mbit/s FULL DUPLEX (RMII)
USB:OhcdPdd_Init
++InitializeOHCI
--InitializeOHCI
Master Clock is 99049984 Hz
PLLA Clock is 198099968 Hz
InitializeSSC - no settings match to obtain calibrated bit rate. Please review y
our PLL settings
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
Master Clock is 99049984 Hz
OEMIoControl: Unsupported Code 0x10100fc - device 0x0101 func 63
cable attached
The Update Flag Is Not Exiting,Run The Current Program!
Using The User IP Settings
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: User wince5 app can not start in 9260 board

Sat Mar 30, 2013 3:44 pm

Perhaps you can enumerate the differences between your board and the reference design? ie circuit and part changes

Perhaps a log from the failing board might be useful to contrast the results.

You might also consider injecting some test code into the platform to probe the SDRAM and NAND devices. How did you validate the board/design, or test in production?
devmail
Posts: 3
Joined: Sat Mar 30, 2013 3:58 am

Re: User wince5 app can not start in 9260 board

Mon Apr 01, 2013 8:12 am

CptTitanic wrote:Perhaps you can enumerate the differences between your board and the reference design? ie circuit and part changes

Perhaps a log from the failing board might be useful to contrast the results.

You might also consider injecting some test code into the platform to probe the SDRAM and NAND devices. How did you validate the board/design, or test in production?
Thanks to CptTitanic.
I am new to this project, some document is lost............
I attached a serial cable with the core board, sometimes a error in debug message:
+OALIoCtlHalInitRTC(...)
I2C Error: AT91C_TWI_NACK
-OALIoCtlHalInitRTC(rc = 0)

I have put a test app in wince image. It starts a network service successfully.
How to solve this problem?
Last edited by devmail on Thu Apr 04, 2013 7:37 am, edited 1 time in total.
CptTitanic
Posts: 877
Joined: Sat Oct 30, 2010 6:04 pm

Re: User wince5 app can not start in 9260 board

Mon Apr 01, 2013 3:50 pm

I'd start by validating the hardware outside the OS (WINCE, or whatever), using a bare metal development tools like Keil or IAR. This will require a reasonable understanding of the chips involved, perhaps you have some engineers within your organization familiar with validation tasks?

As you think there is a problem with the NAND, start there.

>>Some bus transceiver on EBI bus, they are controlled by RD and CS4.

Make sure that these changes do not alter the timing of the NAND, or if they require you to change how the EBI is initially configured. Again writing code that stresses the interface is what you're looking to achieve, and confirm it functions correctly. If it fails such tests, it's not going to work if you layer more OS code on top of it.
devmail
Posts: 3
Joined: Sat Mar 30, 2013 3:58 am

Re: User wince5 app can not start in 9260 board

Thu Apr 04, 2013 2:53 am

I found the problem, and solve it.
CS4 is pulled up until wince start(not finished, but network cable is detected), the it is keeped pulled down, so tconflicts in databus.

cs4 is multiplexed with RTS3. Modify serial driver in BSP, and it is ok now.

Thanks to CptTitanic

Return to “WinCE”

Who is online

Users browsing this forum: No registered users and 1 guest