移植2440官方bsp遇到的问题

losedo   2009-6-13 09:04 楼主
我现在在把官方的 5.0bsp移植到我的mini2440 上发现当下载完nk后串口打印信息到这句就结束了 系统应该死机了 我在debug版本下也看到这种情况到那句就死机了 下面是我的debug信息  是什么原因导致的啊  
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Jun 11 2009 02:17:32
Microsoft Windows CE Bootloader for the Samsung SMDK2440 Version 2.4 Built Jun 11 2009

BP_Init
FMD::FMD_Init
FMD::FMD_Init - pBSPArgs->nfsblk = 0x0
FMD::FMD_Init - READ_REGISTER_BYTE(pNFSBLK) = 0x0
FMD::FMD_Init IPL .....
FMD::FMD_Init Done
MID = 0xec, DID = 0x76 4th Cycle : 0xa5
NUMBLOCKS : 512(0x200), SECTORSPERBLOCK = 256(0x100), BYTESPERSECTOR = 512(0x200)
MID = 0xec, DID = 0x76 4th Cycle : 0xa5
NUMBLOCKS : 512(0x200), SECTORSPERBLOCK = 256(0x100), BYTESPERSECTOR = 512(0x200)
wNUM_BLOCKS : 512(0x200)
Press [ENTER] to download image stored on boot media, or [SPACE] to enter boot monitor.

Initiating image download in 10 seconds. 9 seconds. 8 seconds.
Ethernet Boot Loader Configuration:

0) IP address: 192.168.17.112
1) Subnet mask: 255.255.255.0
2) DHCP: Disabled
3) Boot delay: 10 seconds
4) Reset to factory default configuration
5) Startup image: DOWNLOAD NEW
6) Program disk image into SmartMedia card: Disabled
7) Program DM9000 MAC address (12:23:34:45:56:67)
8) Kernel Debugger: ENABLED
9) Format Boot Media for BinFS
E) Erase Reserved Block
B) Mark Bad Block at Reserved Block
F) Low-level format the Smart Media card
D) Download image now
L) LAUNCH existing Boot Media image
R) Read Configuration
U) DOWNLOAD image now(USB)
W) Write Configuration Right Now
A) Erase All Blocks

Enter your selection: d
INFO: Probe: DM9000 is detected.
DM9000: MAC Address: 12:23:34:45:56:67
System ready!
Preparing for download...
OEMPreDownload
INFO: *** Device Name 'SMDK244022119' ***
INFO: Using static IP address 12181.1.
INFO: Using subnet mask 2525250.
BEFORE EbootInitEtherTransport
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 192.168.17.112 Port 0400   Dest IP 192.168.17.101 Port 0621
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
AFTER EbootInitEtherTransport

Download BIN file information:
-----------------------------------------------------
[0]: Base Address=0x80200000  Length=0x19d8784
-----------------------------------------------------
[DM9000]RX status error!!!=[8]rom_offset=0x0.
ROMHDR at Address 80200044h
waitforconnect
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
INFO: OEMLaunch: Jumping to Physical Address 0x30201000h (Virtual Address 0x80201000h)...

$Windows CE Kernel for ARM (Thumb Enabled) Built on Feb  8 2007 at 23:37:12
ProcessorType=0920  Revision=0
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 802010e8
DCache: 8 sets, 64 ways, 32 line size, 16384 size
ICache: 8 sets, 64 ways, 32 line size, 16384 size
OALKitlStart : NONE
Error Reporting Memory Reserved, dump size = 00020000
Booting Windows CE version 5.00 for (ARM)
&pTOC = 80209e4c, pTOC = 81bd6e4c, pTOC->ulRamFree = 82081000, MemForPT = 00000000

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 7516, Secondary pages: 0, Filesystem pages = 3758

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 82082000, extension: 00002000, length: 01d5c000
Sp=ffffc7cc
ARMInit done.
Windows CE KernelInit
Updated eptr->e32_vsize to = 000e6000
Scheduling the first thread.
0x83ddf024: KernelInit2: pCurThread=83ddf024 hCurThread=03ddf266 hCurProc=03ddf002, KernelInit = 8024faec
0x83ddf024: Detecting VFP...0x83ddf024:  VFP Not Found!
0x83ddf024: Updated eptr->e32_vsize to = 00006000
0x83ddf024: Updated eptr->e32_vsize to = 00029000
0x83ddf024: Updated eptr->e32_vsize to = 00009000
0x83ddf024: Updated eptr->e32_vsize to = 00022000
0x83ddf024: ERROR: d:\macallan\private\winceos\coreos\nk\kernel\kwin32.c line 777: 0x83ddf024: ConnectDebugger failed
0x83ddf024: first = 01e40000, last = 02000000, SharedDllBase = 027e0000
0x83ddf024: OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
0x83dc88c8: CertMod.dll not found, using old OEM Trust Model
0x83dc88c8: FileSystem Starting - starting with clean file system
0x83dc88c8: FS: initializing ROM/RAM file system
0x83dc88c8: SC_CreateAPIHandle: pvData == NULL
0x83dc88c8: FS: Registering file system ROM, index 2, flags 0x00000031
0x83dc88c8: FS: Mount complete (ROM, index 2, flags 0x00000031)
0x83dc88c8: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
0x83dc88c8: Succeeded on CheckFile
0x83dc88c8: RestoreFile(0x83db0d92) called fDelete = TRUE
0x83dc88c8: FS: Registering file system StoreMgr, index 3, flags 0x00000001
0x83dc88c8: FMD::FMD_Init
0x83dc88c8: FMD::FMD_Init - pBSPArgs->nfsblk = 0x0
0x83dc88c8: FMD::FMD_Init - READ_REGISTER_BYTE(pNFSBLK) = 0x0
0x83dc88c8: FMD::FMD_Init IPL .....
0x83dc88c8: FMD::FMD_Init Done
0x83dc88c8: MID = 0xec, DID = 0x76 4th Cycle : 0xc0
0x83dc88c8: NUMBLOCKS : 512(0x200), SECTORSPERBLOCK = 256(0x100), BYTESPERSECTOR = 512(0x200)
0x83dc88c8: FLASHDRV.DLL:BuildupMappingInfo() - Enter.
0x83dc88c8: FMD_OEMIoControl: unrecognized IOCTL (0x71c24).
0x83dc88c8: Loading partition driver mspart.dll hModule=83DA7EF4
0x83dc88c8: Driver mspart.dll loaded
0x83dc88c8: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!!
0x83dc88c8: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000
0x83dc88c8: Opened the store hStore=000B2350
0x83dc88c8: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!!
0x83dc88c8: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000
0x83dc88c8: NumSec=129280 BytesPerSec=512 FreeSec=0 BiggestCreatable=0
0x83dc88c8: InitSharedHeap: 44000000 10000 c
0x83dc88c8:   InitSharedHeap: return 44000060
0x83dc88c8: OEMIoControl: Unsupported Code 0x10100cc - device 0x0101 func 51
0x83dc88c8: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
0x83dc88c8: FSREG: Logging in default user.
0x83dc88c8: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars
0x83dc88c8: SetCurrentUser: Logging out (nobody), logging in default
0x83dc88c8: FS: Using default path "\profiles\"
0x83dc88c8: BuildPath: profiles
0x83dc88c8: BuildPath: profiles\default
0x83dc88c8: SetCurrentUser: User hives not supported -- using same registry for all users
0x83dc88c8: FS: Using default path "Windows\"
0x83dc88c8: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
0x83dc88c8: OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dc88c8: FS: Using default path "Windows\"
0x83dc88c8: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars
0x83dc88c8: Failure on copy of \Windows\camtest.exe
0x83dc88c8:
Initializing Database
0x83dc88c8: DB:Validation: Name already exists DB_notify_events
0x83dc88c8: DB:CeCreateDatabase failed
0x83dc88c8: Filesystem initialized!
0x83dc88c8: FILESYS: Waiting for kernel to be ready to launch apps
0x83dc8400: InitMUI: DISABLED (-1039860968)
0x83dc88c8: FS: Creating signal event SYSTEM/DevMgrApiSetReady
0x83dc88c8: FS: Creating signal event SYSTEM/PowerManagerReady
0x83dc88c8: FS: Creating signal event SYSTEM/GweApiSetReady
0x83dc88c8: FS: Creating signal event ReleaseFSD
0x83dc88c8: FS: Creating signal event system/events/notify/APIReady
0x83dc88c8: FS: Creating signal event SYSTEM/ShellAPIReady
0x83dc88c8: FS: Creating signal event SYSTEM/BatteryAPIsReady
0x83dc88c8: FS: Creating signal event SYSTEM/NLedAPIsReady
0x83dc88c8: FILESYS: Launching apps
0x83dc88c8: FILESYS: Launching shell.exe
0x83d8c000: InitSharedHeap: 44000000 0 c
0x83d8c000:   InitSharedHeap: return 44000060
0x83dc88c8: FILESYS: Launching device.exe
0x83d96328: InitSharedHeap: 44000000 0 c
0x83d96328:   InitSharedHeap: return 44000060
0x83d96328: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x23d8c6ca ***
0x83d96328: +InitDeviceFileSystems
0x83d96328: FS: Registering file system $device, index 4, flags 0x00000001
0x83d96328: FS: Registering file system $bus, index 5, flags 0x00000001
0x83d96328: -InitDeviceFileSystems: status is 1
0x83d96328: Ceddk!CalibrateStallCounter: Enter
0x83d96328: Ceddk!CalibrateStallCounter: Could not find stall counter
0x83d96328: Ceddk!BeginCalibration: min(1042) max(1157)
0x83d96328: Ceddk!BeginCalibration: Elapsed is 1150
0x83d96328: Ceddk!BeginCalibration: Delay is 13
0x83dc88c8: FILESYS: SignalStarted loop = 2
0x83d96328: DEVICE!DevloadInit
0x83d96328: DEVICE!InitDevices: Root Key is Drivers\BuiltIn.
0x83d96328: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
0x83d96328: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
0x83d96328: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Battery\BusPrefix) returned 2
0x83d96328: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NLed\BusPrefix) returned 2
0x83d96328: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Serial\BusPrefix) returned 2
0x83d96328: HalTranslateBusAddress: 0 0 0000000056000000 0 --> 0000000056000000 1
0x83d96328: HalTranslateBusAddress: 0 0 0000000050000000 0 --> 0000000050000000 1
0x83d96328: HalTranslateBusAddress: 0 0 000000004a000000 0 --> 000000004a000000 1
0x83d96328: INFO: CReg2440Uart::CReg2440Uart using processor frequency reported by the OAL (35400000).
我现在都不最大怎么追踪下面的语句kitl现在上去usb的驱动不认  我是直接把eboot下载到nor中去然后引导系统的

回复评论 (2)

已经启动了啊......
点赞  2009-6-13 11:16
我现在是把串口的驱动去掉了 系统能够起来了 但是屏幕还是不亮,
串口老是打印这一句
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
0x83dcbb90: OEMIoControl: Unsupported Code 0x1010024 - device 0x0101 func 9
我想应该是串口冲突了  官方的驱动应该是不会有错的 我看别的bsp也是用的相同的驱动。我现在发现mini2440用的uart0 而官方的是用uart1  我想是不是在这里导致了驱动的错误 或者说是在注册表中的错误 就是会不会是串口的重复  还没深入到这地步
现在我发现又有一个问题就是官方的usb的是使能脚是gpg12脚而mini2440的是gpc5  我现在把mini2440的从口插上电脑发现电脑老是报告是未知设备 而不是发现新硬件。这个我应该怎么改呢 我把它的涉及到gpg12的脚改成了gpc5  还有别的地方需要改的吗
点赞  2009-6-13 13:13
电子工程世界版权所有 京B2-20211791 京ICP备10001474号-1 京公网安备 11010802033920号
    写回复