19,504
社区成员
发帖
与我相关
我的任务
分享请教AMD LX800的定制wince5.0 BSP的问题
手里有一块AMD LX800的工控板子，厂商不给提供BSP。
只好在csdn的下载频道下载了一个。
简单的配置之后，debug调试。加载到某个位置后就停住不动了~
产生这种情况的原因太多了，也不能定位到某点，就连想问为什么都问不出来！！！
有没有过来人，帮着分析分析哦？
另外用wince自带的geode那个bsp可以不？不过看那个好像是gx系列的cpu的....
如果有人能提供一份好用的BSP就更好了，国内的公司基本上都是按公板抄来抄去的，估摸着能兼容吧？
只好在csdn的下载频道下载了一个。
简单的配置之后，debug调试。加载到某个位置后就停住不动了~
产生这种情况的原因太多了，也不能定位到某点，就连想问为什么都问不出来！！！
有没有过来人，帮着分析分析哦？
另外用wince自带的geode那个bsp可以不？不过看那个好像是gx系列的cpu的....
如果有人能提供一份好用的BSP就更好了，国内的公司基本上都是按公板抄来抄去的，估摸着能兼容吧？
...全文
请发表友善的回复…
发表回复
lmlmlmnew 2010-01-22
- 打赏
- 举报
[Quote=引用 11 楼 lmlmlmnew 的回复:]
引用 8 楼 wangxin_801115 的回复:
可以
你加我
公司不让上QQ晚上加你好么 谢谢了
引用 9 楼 zhoukq 的回复:
你可以选择release方式编译nk文件的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
刚用release方式编了一下，在板子上能启动了~~~
是不是BSP那块的kitl的问题呢？
另外分辨率上有一些问题，你们那遇到过么？
[/Quote]
BSP的DISPLAY驱动我没加上，可能是这得问题 呵呵~~~
引用 8 楼 wangxin_801115 的回复:
可以
你加我
公司不让上QQ晚上加你好么 谢谢了
引用 9 楼 zhoukq 的回复:
你可以选择release方式编译nk文件的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
刚用release方式编了一下，在板子上能启动了~~~
是不是BSP那块的kitl的问题呢？
另外分辨率上有一些问题，你们那遇到过么？
[/Quote]
BSP的DISPLAY驱动我没加上，可能是这得问题 呵呵~~~
lmlmlmnew 2010-01-22
- 打赏
- 举报
[Quote=引用 10 楼 amorous 的回复:]
0x81fff030: Did not find emulation code for x86... using floating point
hardware.
==================================================================================
This occurs on the x86, as there are some versions of the i486 architecture that do not include the floating-point co-processor. The system will check for the presence of the FPEMUL library. (You can specify that your BSP uses one of these CPUs by setting BSP_FPEMUL=1.) All code on an x86 is written assuming the presence of the co-processor. In a case where there isn't one, the instructions cause a trap in the kernel, which then calls the emulation library to implement the floating-point calculations. This message simply informs you that the kernel did not find the emulation library and therefore is using the hardware co-processor. If your CPU doesn't have the co-processor, this would be an important message to look for if your fonts are not showing up in the Microsoft® Internet Explorer shell (or other applications).
[/Quote]
用过的几块x86的板子都会打出这句话~~
0x81fff030: Did not find emulation code for x86... using floating point
hardware.
==================================================================================
This occurs on the x86, as there are some versions of the i486 architecture that do not include the floating-point co-processor. The system will check for the presence of the FPEMUL library. (You can specify that your BSP uses one of these CPUs by setting BSP_FPEMUL=1.) All code on an x86 is written assuming the presence of the co-processor. In a case where there isn't one, the instructions cause a trap in the kernel, which then calls the emulation library to implement the floating-point calculations. This message simply informs you that the kernel did not find the emulation library and therefore is using the hardware co-processor. If your CPU doesn't have the co-processor, this would be an important message to look for if your fonts are not showing up in the Microsoft® Internet Explorer shell (or other applications).
[/Quote]
用过的几块x86的板子都会打出这句话~~
lmlmlmnew 2010-01-22
- 打赏
- 举报
[Quote=引用 8 楼 wangxin_801115 的回复:]
可以
你加我
[/Quote]
公司不让上QQ晚上加你好么 谢谢了
[Quote=引用 9 楼 zhoukq 的回复:]
你可以选择release方式编译nk文件的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
[/Quote]
刚用release方式编了一下，在板子上能启动了~~~
是不是BSP那块的kitl的问题呢？
另外分辨率上有一些问题，你们那遇到过么？
可以
你加我
[/Quote]
公司不让上QQ晚上加你好么 谢谢了
[Quote=引用 9 楼 zhoukq 的回复:]
你可以选择release方式编译nk文件的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
[/Quote]
刚用release方式编了一下，在板子上能启动了~~~
是不是BSP那块的kitl的问题呢？
另外分辨率上有一些问题，你们那遇到过么？
AMOROUS 2010-01-22
- 打赏
- 举报
0x81fff030: Did not find emulation code for x86... using floating point
hardware.
==================================================================================
This occurs on the x86, as there are some versions of the i486 architecture that do not include the floating-point co-processor. The system will check for the presence of the FPEMUL library. (You can specify that your BSP uses one of these CPUs by setting BSP_FPEMUL=1.) All code on an x86 is written assuming the presence of the co-processor. In a case where there isn't one, the instructions cause a trap in the kernel, which then calls the emulation library to implement the floating-point calculations. This message simply informs you that the kernel did not find the emulation library and therefore is using the hardware co-processor. If your CPU doesn't have the co-processor, this would be an important message to look for if your fonts are not showing up in the Microsoft® Internet Explorer shell (or other applications).
hardware.
==================================================================================
This occurs on the x86, as there are some versions of the i486 architecture that do not include the floating-point co-processor. The system will check for the presence of the FPEMUL library. (You can specify that your BSP uses one of these CPUs by setting BSP_FPEMUL=1.) All code on an x86 is written assuming the presence of the co-processor. In a case where there isn't one, the instructions cause a trap in the kernel, which then calls the emulation library to implement the floating-point calculations. This message simply informs you that the kernel did not find the emulation library and therefore is using the hardware co-processor. If your CPU doesn't have the co-processor, this would be an important message to look for if your fonts are not showing up in the Microsoft® Internet Explorer shell (or other applications).
中国168 2010-01-22
- 打赏
- 举报
你可以选择release方式编译nk文件的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
我们也用过lx800的bsp通常情况下用release方式生成的nk文件，默认就可以启动板卡的。
wangxin_801115 2010-01-22
- 打赏
- 举报
可以
你加我
你加我
lmlmlmnew 2010-01-22
- 打赏
- 举报
另外我添加了HIVE之后出错的地方又换了~
4294767416 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event SYSTEM/DevMgrApiSetReady
4294767417 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event SYSTEM/PowerManagerReady
之后再也没响应
4294767416 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event SYSTEM/DevMgrApiSetReady
4294767417 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event SYSTEM/PowerManagerReady
之后再也没响应
lmlmlmnew 2010-01-22
- 打赏
- 举报
[Quote=引用 3 楼 wangxin_801115 的回复:]
AMD LX800的BSP我有
[/Quote]
赫赫 能给我发一份么？
我在网上下的是Geode_LX_5536_WinCE50.msi
[Quote=引用 4 楼 veabol 的回复:]
最好还是找个相应CPU的BSP，至少也要是差不多型号的，否则需要改动的东西太多。
[/Quote]
我看了下下的BSP在启动引导方面没啥改动
主要是显示驱动 AES 以及USB方面驱动
如果错误出现在那些驱动的地方，也就能明确修改的方向了。
关键是从现在死的地方根本看不出来出问题的地方呢？
我现在顺着出问题的函数加一些东西作测试，都是private文件夹里面的函数~~
AMD LX800的BSP我有
[/Quote]
赫赫 能给我发一份么？
我在网上下的是Geode_LX_5536_WinCE50.msi
[Quote=引用 4 楼 veabol 的回复:]
最好还是找个相应CPU的BSP，至少也要是差不多型号的，否则需要改动的东西太多。
[/Quote]
我看了下下的BSP在启动引导方面没啥改动
主要是显示驱动 AES 以及USB方面驱动
如果错误出现在那些驱动的地方，也就能明确修改的方向了。
关键是从现在死的地方根本看不出来出问题的地方呢？
我现在顺着出问题的函数加一些东西作测试，都是private文件夹里面的函数~~
guopeixin 2010-01-21
- 打赏
- 举报
lz很强悍，学习
博说医械研发 2010-01-21
- 打赏
- 举报
最好还是找个相应CPU的BSP，至少也要是差不多型号的，否则需要改动的东西太多。
wangxin_801115 2010-01-21
- 打赏
- 举报
AMD LX800的BSP我有
kyzf 2010-01-21
- 打赏
- 举报
没用过，友情帮顶下。
MARK,期待高人，我也学习下。
MARK,期待高人，我也学习下。
lmlmlmnew 2010-01-21
- 打赏
- 举报
The Kernel Debugger is waiting to connect with target.
0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 g_dwCPUFeatures = 0088a93d
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
0 PID:0 TID:0 &pTOC = 802279d8, pTOC = 80fbb228, pTOC->ulRamFree = 81046000, MemForPT = 00004000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 41098, Secondary pages: 0, Filesystem pages = 20549
0 PID:0 TID:0
Booting kernel with clean memory configuration:
0 PID:0 TID:0 Memory Sections:
0 PID:0 TID:0 [0] : start: 8104b000, extension: 0000b000, length: 0a08a000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 81047000.
0 PID:0 TID:0 Windows CE KernelInit
4294767298 PID:b0df002 TID:b0df1de Updated eptr->e32_vsize to = 00090000
4294767298 PID:b0df002 TID:b0df1de Scheduling the first thread.
4294767299 PID:b0df002 TID:b0df1de 0x8b0df030: KernelInit2: pCurThread=8b0df030 hCurThread=0b0df1de hCurProc=0b0df002, KernelInit = 80260e20
4294767299 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00005000
4294767310 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00022000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00007000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00018000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Starting kernel debugger software probe (KdStub) - KD API version 18
4294767312 PID:b0df002 TID:b0df1de 0x8b0df030: Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt (FALSE, p)
4294767315 PID:b0df002 TID:b0df1de 0x8b0df030: >>> Loading module NK.EXE at address 0x80220000-0x802B0000 (RW data at 0x80FBD000-0x8102B21F)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is X86).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x80220000 / Data relocated at 0x80fbd000
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\NK.EXE'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\KD.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\OSAXST1.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\OSAXST0.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\HD.DLL'
4294767337 PID:b0df002 TID:b0df1de 0x8b0df030: first = 01ed0000, last = 02000000, SharedDllBase = 03320000
4294767339 PID:b0df002 TID:b0df1de 0x8b0df030: >>> Loading module coredll.dll at address 0x03F60000-0x04000000 (RW data at 0x01FFE000-0x01FFF765)
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\COREDLL.DLL'
4294767349 PID:b0df002 TID:b0df1de 0x8b0df030: Did not find emulation code for x86... using floating point hardware.
在此处就再也没响应了~
是什么引起的此问题的呢？
内存？
0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 g_dwCPUFeatures = 0088a93d
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
0 PID:0 TID:0 &pTOC = 802279d8, pTOC = 80fbb228, pTOC->ulRamFree = 81046000, MemForPT = 00004000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 41098, Secondary pages: 0, Filesystem pages = 20549
0 PID:0 TID:0
Booting kernel with clean memory configuration:
0 PID:0 TID:0 Memory Sections:
0 PID:0 TID:0 [0] : start: 8104b000, extension: 0000b000, length: 0a08a000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 81047000.
0 PID:0 TID:0 Windows CE KernelInit
4294767298 PID:b0df002 TID:b0df1de Updated eptr->e32_vsize to = 00090000
4294767298 PID:b0df002 TID:b0df1de Scheduling the first thread.
4294767299 PID:b0df002 TID:b0df1de 0x8b0df030: KernelInit2: pCurThread=8b0df030 hCurThread=0b0df1de hCurProc=0b0df002, KernelInit = 80260e20
4294767299 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00005000
4294767310 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00022000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00007000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Updated eptr->e32_vsize to = 00018000
4294767311 PID:b0df002 TID:b0df1de 0x8b0df030: Starting kernel debugger software probe (KdStub) - KD API version 18
4294767312 PID:b0df002 TID:b0df1de 0x8b0df030: Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt (FALSE, p)
4294767315 PID:b0df002 TID:b0df1de 0x8b0df030: >>> Loading module NK.EXE at address 0x80220000-0x802B0000 (RW data at 0x80FBD000-0x8102B21F)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is X86).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x80220000 / Data relocated at 0x80fbd000
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\NK.EXE'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\KD.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\OSAXST1.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\OSAXST0.DLL'
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\HD.DLL'
4294767337 PID:b0df002 TID:b0df1de 0x8b0df030: first = 01ed0000, last = 02000000, SharedDllBase = 03320000
4294767339 PID:b0df002 TID:b0df1de 0x8b0df030: >>> Loading module coredll.dll at address 0x03F60000-0x04000000 (RW data at 0x01FFE000-0x01FFF765)
Loaded symbols for 'F:\WINCE500\PBWORKSPACES\SIMPLE_LX800\RELDIR\GEODELX_X86_DEBUG\COREDLL.DLL'
4294767349 PID:b0df002 TID:b0df1de 0x8b0df030: Did not find emulation code for x86... using floating point hardware.
在此处就再也没响应了~
是什么引起的此问题的呢？
内存？
