S3C2240运行CE6.0无画面???

zjj0001   2010-3-18 18:54 楼主
各位好...我又上来求救了!!

刚接触2440这块开发板,已从5.0运行完成

今天想试着去把6.0用上去,由于还是新手,就去下载了网路上已移植好的BSP

可是把NK.nb0烧进去后,却无画面显示,或是整个白屏

似乎touch上有错误,我试着把BSP上的touch driver拿掉,状况仍然一样...

另外有些个问题想请教,开发版厂商有提供 nboot1st 及 nboot2nd 两个 nboot

nboot1st 引导 nboot2nd,那是由nboot2nd引导eboot麻,是的话代码写在何处??

因为还是沿用5.0在用的eboot,这有需要更换吗? 可是看前面OEM init有起来,应该是有正确引导到NK.nb0吧?

以下是接收到的部分讯息!


  1. SDHC -Init
  2. DeviceFolder::LoadDevice(Drivers\BuiltIn\SDHC_SMDK2440) last 337 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\SC2440USBFN\BusPrefix) returned 2
  3. OSAXST1: >>> Loading Module 'sc2440usbfn.dll' (0x83EA05A8) at address 0xC0620000-0xC0664000 in Process 'NK.EXE' (0x82708AA0)
  4. UsbFnMdd!DllEntry: Attach
  5. SC2440UsbFn!UfnPdd_Init: Using IO Base b1200000
  6. SC2440UsbFn!UfnPdd_Init: Using SysIntr 23
  7. SC2440UsbFn!UfnPdd_Init: Using IST priority 100
  8. SC2440UsbFn!MapRegisterSet: VirtualCopy Succeeded, pVMem:d04d0000
  9. UsbFnMdd!UFN_Init: PDD has 5 endpoints
  10. UsbFnMdd!UFN_Init: PDD supports speeds 0x1
  11. UsbFnMdd!CUfnBus::CreateChild: Using client driver key "\Drivers\USB\FunctionDrivers\Serial_Class"
  12. DEVICE!RegReadActivationValues RegQueryValueEx(\Drivers\USB\FunctionDrivers\Serial_Class\DllName) returned 2
  13. DEVICE!I_ActivateDeviceEx: can't find all required activation values in '\Drivers\USB\FunctionDrivers\Serial_Class'
  14. DeviceFolder::LoadDevice(\Drivers\USB\FunctionDrivers\Serial_Class) last 19 TicksUsbFnMdd!CUfnBus::ActivateChild: ActivateChild failed.
  15. UsbFnMdd!CUfnBus::PostInit: ActivateChild failed.
  16. DeviceFolder::LoadDevice(Drivers\BuiltIn\SC2440USBFN) last 173 TicksDEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\DllName) returned 2
  17. DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCI'
  18. DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 16 TicksFILESYS: SignalStarted loop = 2
  19. FILESYS: Launching gwes.dll
  20. OSAXST1: >>> Loading Module 'gwes.dll' (0x83EA0E1C) at address 0xC0200000-0xC02BE000 in Process 'NK.EXE' (0x82708AA0)
  21. Filesys: Loaded gwes.dll
  22. FILESYS: Done launching apps
  23. -DEVICE!DevloadPostInit
  24. This device has booted 1 times !!!
  25. Ceddk!CalibrateStallCounter: Enter
  26. Ceddk!CalibrateStallCounter: Stall counter loaded from registry(23)
  27. System Default HKL value set to 00000409
  28. Grow Gdi handle table from 0 to 64
  29. LogFontFromRegistry(SYSTEM\GDI\SysFnt), lfHeight = -12OSAXST1: >>> Loading Module 's3c2440disp.dll' (0x83E9D378) at address 0xC0500000-0xC055F000 in Process 'NK.EXE' (0x82708AA0)
  30. 13
  31. Bits-per-pixel: 16
  32. OSAXST1: >>> Loading Module 'mgtt_o.dll' (0x83E9DAF8) at address 0xC02C0000-0xC0344000 in Process 'NK.EXE' (0x82708AA0)
  33. Kernel DLL 'mgtt_o.dll' needs thread creation/deletion notification
  34. Loaded font driver '\windows\mgtt_o.dll' @ index '0'.
  35. Adding font resource '\Windows\tahoma.ttf'...
  36. **** Signature of FONT File is: '0100'...
  37. Font loaded by driver @ index '0'.
  38. ** Got 1 faces in font file...
  39. Font \Windows\tahoma.ttf: pffv = 0xd04c3b50 { 0xd0500838, 135848 }  hff = 0xd04c3b90AddFonts(.ttf) returned 1 fontsAddFonts(.ttc) returned 0 fontsAddFonts(*) returned 1 fontsAddAllEUDCFonts(tte) returned 0 fontsCreating secondary frame buffer for POR and SaveBits
  40. OSAXST1: >>> Loading Module 'kbdmouse.dll' (0x83E52480) at address 0xC0570000-0xC0583000 in Process 'NK.EXE' (0x82708AA0)
  41. Layout Manager : DLL_PROCESS_ATTACH
  42. PS2_NOP_Entry: Initialize NOP ID 0
  43. PS2_NOP_Entry: Initialization complete
  44. KeybdDriverInitializeEx: Initialized PDD 0 - PS/2 NOP (Mask 4)
  45. KeybdDriverInitializeEx: Found default input method 00000409
  46. IsAPIReady is being deprecated, use WaitForAPIReady instead!!
  47. KeybdDriverInitializeEx: Layout Manager successfully initialized
  48. KeybdDriverInitializeEx: Layout Manager successfully initialized to  1
  49. OSAXST1: >>> Loading Module 'touch.dll' (0x83E4B300) at address 0xC0590000-0xC059B000 in Process 'NK.EXE' (0x82708AA0)
  50. calibrating 0 point set
  51. TOUCH:TouchPanelpGetPriority - RegOpenKeyEx(\Drivers\BuiltIn\Touch) failed 2, using default thread priorities
  52. calibrating 5 point set
  53. Maximum Allowed Error 7:
  54. Calibration Results:
  55.    Screen    =>    Mapped
  56. ( 300,  200) => ( 303,  200)
  57. (  60,   40) => (  60,   38)
  58. (  60,  360) => (  59,  362)
  59. ( 540,  360) => ( 540,  358)
  60. ( 540,   40) => ( 539,   42)
  61. Maximum error (square of Euclidean distance in screen units) = 9
  62. UpdateIdleTimeoutFromRegistry
  63. GWES initialized properly




回复评论 (6)

OEMInit都已经到了说明前边的两个NBOOT及EBOOT都已经成功,且开始执行NK了,检查一下你的显示驱动是否有问题,是否LCD及LCD寄存器没初始化,你可以尝试在其它驱动中建个线程,让其每过一会就打印些东西,看是不是卡死了,如果有不断的信息打印就没卡死,显示驱动有问题的可能性就非常大。
点赞  2010-3-18 20:53
LCD 的相应参数都配置好了吧?
点赞  2010-3-18 21:00
白屏的原因比较多哦,当你的跳线没有设置正确时,也会出现白屏…
点赞  2010-3-19 05:54
回覆Veabol:我会照着你提供的方式做,如果假使是驱动的问题?那该如何解决?因为驱动是沿用5.0的!

回覆arm9linuxpp:硬件运行平台都是相同的,唯读烧写的ce版本不同,5.0 :ok 6.0:白屏,这样参数有哪些会需要重新更改?

回覆WolfMvP:是说母板上的跳线设置吗??可是这板子在运行ce5.0都一切正常,应该跟硬件比较没关系吧!!

多谢楼上各位的热情回应!!
点赞  2010-3-19 07:17
LCD 不一样的,呵呵,要慎重。这个看不出啥毛病的。呵呵。
点赞  2010-3-19 08:38
目前已经把原先5.0的display driver 移到6.0 PB了,画面出現了!!

可是却只会显示右上一角,其他都是白屏和黑平交接,这是LCD设置不正确?

目前是找到
[HKEY_LOCAL_MACHINE\Drivers\Display\S3C2440\CONFIG]
"LCDVirtualFrameBase"=dword:ac100000
"LCDPhysicalFrameBase"=dword:30100000

这两个设定值是5.0上的,除此两设定值还有哪些需要修改呢?
点赞  2010-3-19 18:41
电子工程世界版权所有 京B2-20211791 京ICP备10001474号-1 京公网安备 11010802033920号
    写回复