TQ2440A怎么样使用KITL？？

ghoulich

TQ2440A怎么样使用KITL？？ [复制链接]

我是这样做的：
1. 修改C:\WINCE600\PLATFORM\TQ2440下的TQ2440.bat，将“set BSP_NOUSBFN=”改为“set BSP_NOUSBFN=1”
2. 修改C:\WINCE600\PLATFORM\TQ2440\Src\Inc下的kitl_cfg.h，将“//#define KITL_USBSERIAL”改为“#define KITL_USBSERIAL”，也就是把注释去掉
3. 在Build Option中打开“Enable eboot space in memory”、“Enable kernel debugger”、“Enable KITL”
4. 在Connectivity Options中选择Transport为USB，Debugger为KdStub
5. 在Release Directory Modules中添加想要调试的驱动程序的dll文件
6. 编译并生成镜像，烧写入开发板

然后我在启动开发板的时候观察超级终端上的log，发现使能了KITL，但是KITL的初始化出错，说是找不到设备。。。

ghoulich

怎么老要进行回复审查的啊？我都发了两遍log了，还是不给显示。。。

ghoulich

下面是我启动WinCE 6.0时超级终端打出来的log：



Contact: mobyfab@netyxia.net
http://mini2440.netyxia.net
This program uses LibUsbDotNet.
## Version: 0.3.5.19918

## Could not find or open device.
Please plug the device, I will detect it.
## Serial port selected: COM4
?
##### Eboot for TQ2440/SKY2440 #####
#####     www.embedsky.net     #####

Microsoft Windows CE Bootloader for TQ2440/SKY2440 Version 6.0 Built Jun 23 2011

Press [ENTER] to launch image stored on boot media, or [SPACE] to enter boot monitor.

Initiating image launch in 1 seconds. 0 seconds.g image from boot media ...
OEMPlatformInit: IMAGE_TYPE_RAMIMAGE
+=OEMVerifyMemory+ dwStartAddr:0x80200000  dwLength:0x4
RAM image 0xa 0x80200003
+=OEMVerifyMemory+ dwStartAddr:0x80201000  dwLength:0x4
RAM image 0xa 0x80201003
waitforconnect
INFO: OEMLaunch: Jumping to Physical Address 0x30201000h (Virtual Address 0x80201000h)...

?C?Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 25 2009 at 11:04:23
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
+OEMInit
DCache: 8 sets, 64 ways, 32 line size, 16384 size
ICache: 8 sets, 64 ways, 32 line size, 16384 size
+OALArgsInit()
Arguments area has some values
-OALArgsInit()
InitDisplay:240*320
USB SERIAL
SERIAL!!
KITL is enabeld.
Call OALKitlInit().
DeviceId................. 2440USBSerKitlpArgs->flags............. 0x1pArgs->devLoc.IfcType.... 0pArgs->devLoc.LogicalLoc. 0x52000140pArgs->devLoc.PhysicalLoc 0x0pArgs->devLoc.Pin........ 25pArgs->ip4address........ 0pDevice->Name............  spDevice->ifcType......... 0pDevice->id.............. 0x52000140pDevice->resource........ 0pDevice->type............ 1pDevice->pDriver......... 0x821584B0ERROR: OALKitlInit: No supported KITL device at interface 0 bus 0 location 0x 8x-OEMInit
+OALIoCtlHalGetDeviceInfo(...)
OALIoCtlHalGetDeviceInfo():SPI_GETOEMINFO
-OALIoCtlHalGetDeviceInfo(SPI = SPI_GETOEMINFO, rc = 1)
+OALIoCtlHalGetDeviceInfo(...)
OALIoCtlHalGetDeviceInfo():SPI_GETPLATFORMNAME
-OALIoCtlHalGetDeviceInfo(SPI = SPI_GETPLATFORMNAME, rc = 1)
+OALIoCtlHalGetDeviceInfo(...)
OALIoCtlHalGetDeviceInfo():SPI_GETPLATFORMVERSION
-OALIoCtlHalGetDeviceInfo(SPI = SPI_GETPLATFORMVERSION, rc = 1)
FMD_OEMIoControl: unrecognized IOCTL (0x71c24).
INFO: CReg2440Uart::CReg2440Uart using processor frequency reported by the OAL (67500000).
INFO: CReg2440Uart::CReg2440Uart using processor frequency reported by the OAL (67500000).
I2C Init
IIC IRQ mapping: [IRQ:27->sysIRQ:20].
Prescaler:3
PWM: DLL_PROCESS_ATTACH
INFO: DAC_Init:: using processor frequency reported by the OAL (405000000).
::: PWM_Init Sucessfully.
+OALIoCtlHalGetHWEntropy
CAM clock:24000000
CamClockOn = 1
Camera::Product id is 0xffff
Camera:: OV9650 initialize is faile
CAMERA.DLL::InterruptThread Initialized.
CAMERA: CIS_Open
CIS: IOCTL_POWER_CAPABILITIES
CAMERA: CIS_Open
CAMERA: CIS_Close
STRINGS: STR_Init
VBridge:: VB_INITIALIZED returns [0]VMini:: VBridge is not initialized!   Bail out..
[dm9: Chip signature is 90000A46
[dm9: Chip signature is 90000A46
GPIO Initialize ...OK !!!
INT_Init----
INT_GPIO_Setting----
LCD: display instance 'Drivers\Display\S3C2440\CONFIG', num monitors 1
LayMgr.cpp: Layout Manager successfully initialized to  2
Maximum Allowed Error 7:
CamClockOn = 0
Explorer(V2.0) taskbar thread started.
NDISPWR:: Found adapter [DM9CE1]

ghoulich

杯具啊，木有人回答。。。