Sp=ffffc7cc运行不下去

yanshu117 2008-03-24 01:54:22
做一个项目,开发板用的YL(优龙)的2440开发板,由于考虑成本问题,核心板是按照YL给的资料画的,今天板子做回来了,拿YL的BOOTLOADER一试还行,能运行,而且利用其测试外围设备程序,各个硬件还都行.
接下来就是烧内核了.可是,内核烧好后,运行到下面部分就不运行了
InitDisplay:320*240
Sp=ffffc7cc
OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35

那位大侠给指导下,谢谢
...全文
224 11 打赏 收藏 转发到动态 举报
写回复
用AI写文章
11 条回复
切换为时间正序
请发表友善的回复…
发表回复
wangpangwei 2008-10-19
  • 打赏
  • 举报
回复
你好
我也出现过你的问题
你是不是nand flash 不是用的优龙提供的那个型号?
在内核的驱动里固化了一个nand flash 的出厂ID号
如果ID号不匹配的话烧写内核后是无法启动的
你把ID号改成你自己的试试
我就是这样搞好了
songtitan 2008-10-09
  • 打赏
  • 举报
回复
需要更多的debug语句才能找到调试的线索。
ffeige1984 2008-10-09
  • 打赏
  • 举报
回复
zai BOOTLOADER 下把内存检测的那段删了,直接清0
slyzhang 2008-10-08
  • 打赏
  • 举报
回复
这种情况基本上使用DEBUG模式下是可以查出来哪里出现问题了,,, 强烈建议DEBUG模式下完成。


一般情况下,这里会是注册表保存和文件系统出问题的几率比较大,特别是由龙 的板子。

gooogleman 2008-09-30
  • 打赏
  • 举报
回复
[Quote=引用楼主 yanshu117 的帖子:]
做一个项目,开发板用的YL(优龙)的2440开发板,由于考虑成本问题,核心板是按照YL给的资料画的,今天板子做回来了,拿YL的BOOTLOADER一试还行,能运行,而且利用其测试外围设备程序,各个硬件还都行.
接下来就是烧内核了.可是,内核烧好后,运行到下面部分就不运行了

C/C++ codeInitDisplay:320*240
Sp=ffffc7cc
OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
OEMIoControl: Uns…
[/Quote]

----------------------------楼主,我用优龙的BIOS和BSP,自己做开发板一切正常哦。估计是你自己的问题啊,你猜测啊,估计有些编译选项是不能选的的。例如KITL。
想要详细聊,加我的群,晚上可以聊聊,国庆几天假期,大部分时间都上QQ的
xqhrs232 2008-09-29
  • 打赏
  • 举报
回复
用的注册表是什么类型?HIVE的?如果是换成RAM看看,一般基本的应该跑的起来的.ARM正常,NAND FLASH正常,RAM正常这些基本单元能够工作就应该跑的起来!

开始只加基本的组件进NK.
graduated 2008-09-29
  • 打赏
  • 举报
回复
老大,不知道你的问题解决没?我是使用smdk2440的bsp,现在也是你的情况。
yanshu117 2008-04-02
  • 打赏
  • 举报
回复
恩,用YL提供的BSP自己建工程,就可以过去,但到了我上述问题点,也要停留20多秒,才能过去,但这个核里面,FLASH分区,SD卡驱动.什么的都没有.如果是利用YL给的基础工程建立的内核,运行到上述地点就过不去,
而且YL给的BOOTLOADER有一点不好.没有提供格式化FALSH的功能.郁闷
yashi 2008-03-25
  • 打赏
  • 举报
回复
这个要自己跟踪调试一下,出现这种情况的原因很多。猜是不可能有结果的。
View Flow for Android ViewFlow is an Android UI widget providing a horizontally scrollable ViewGroup with items populated from an Adapter. Scroll down to the bottom of the page for a screen shot. The component is a Library Project. This means that there's no need to copy-paste resources into your own project, simply add the viewflow component as a reference to any project. When to use This library might be suitable if you have an indeterminate number of views in your viewflow, if instead you have a static numbers of views you ought to look at Fragments and the ViewPager in the Compatibility Library instead. Usage In your layout The use of app:sidebuffer is optional. It defines the number of Views to buffer on each side of the currently shown View. The default sidebuffer is 3, making up a grand total of 7 (3 * 2 + 1) Views loaded at a time (at max). To be able to use the more convenient app:sidebuffer attribute, the application namespace must be included in the same manner as the android namespace is. Please refer to the layout main.xml in the example project for a full example. Again, note that it's the application namespace and not the viewflow namespace that must be referred like xmlns:app="http://schemas.android.com/apk/res/your.application.package.here". In your activity ViewFlow viewFlow = (ViewFlow) findViewById(R.id.viewflow); viewFlow.setAdapter(myAdapter); Setting a different initial position (0 being default) is as easy as: viewFlow.setAdapter(myAdapter, 8); Although possible, you should not call setSelection(...) immediately after calling setAdapter(myAdapter) as that might load unnecessary views giving you a decrease in performance. Listen on screen change events If you need to listen to screen change events you would want to implement your own ViewFlow.ViewSwitchListener and pass it to the setOnViewSwitchListener() method. viewFlow.setOnViewSwitchListener(new ViewSwitchListener() { public void onSwitched(View v, int position) { // Your code here } }); Listen on initialize view events If you need a lazy View initialization you would want to implement your own ViewFlow.ViewLazyInitializeListener and pass it to the setOnViewLazyInitializeListener() method. viewFlow.setOnViewLazyInitializeListener(new ViewLazyInitializeListener() { public void onViewLazyInitialize(View view, int position) { // Your code here e.g. ((MyAdapter)((AbsListView)view).getAdapter()).initializeData(); } }); Flow Indicator It is also possible to add a flow view indicator to your layout. The purpose of a FlowIndicator is to present a visual representation of where in the item list focus is at. You may either implement a FlowIndicator yourself or use an implementation provided by the View Flow library. The View Flow library currently supports the following indicators: Circle Flow Indicator This indicator shows a circle for each View in the adapter with a special circle representing the currently selected view (see screenshot below). And then you'll need to connect your ViewFlow with the FlowIndicator: CircleFlowIndicator indic = (CircleFlowIndicator) findViewById(R.id.viewflowindic); viewFlow.setFlowIndicator(indic); By default, the 'active' indicator moves smoothly from one 'inactive' indicator to the next, as the user scrolls. If you set the snap attribute to true, it will instead jump to the next position when the flow settles at the next page. The following attributes are supported: activeColor, inactiveColor, activeType (either fill or stroke), inactiveType (either fill or stroke), fadeOut (time in ms until indicator fades out, 0 = never), radius, sync (see above). Title Flow Indicator This indicator presents the title of the previous, current and next View in the adapter (see screenshot below). And then you'll need to connect your ViewFlow with the FlowIndicator: TitleFlowIndicator indicator = (TitleFlowIndicator) findViewById(R.id.viewflowindic); indicator.setTitleProvider(myTitleProvider); viewFlow.setFlowIndicator(indicator); Building a jar file If you rather want a jar file instead of a including the project as an android library, run ant jar in the android-viewflow/viewflow folder, to build a jar file. Caveats The manifest states a min sdk version of 4, which is true. But in any case you want to support an api level < 8 you will have to forward an onConfigurationChanged event to the ViewFlow from your Activity. I know this isn't a very nice solution, feel free to propose better ones! @Override public void onConfigurationChanged(Configuration newConfig) { super.onConfigurationChanged(newConfig); viewFlow.onConfigurationChanged(newConfig); } Contributions The following persons deserves a mention for their contributions: Eric Taix Marc Reichelt, http://marcreichelt.blogspot.com/ Want to contribute? GitHub has some great articles on how to get started with Git and GitHub and how to fork a project. Contributers are recommended to fork the app on GitHub (but don't have too). Create a feature branch, push the branch to git hub, press Pull Request and write a simple explanation. One fix per commit. If let's say a commit closes the open issue 12. Just add closes #12 in your commit message to close that issue automagically. If you still feel uncomfortable contributing the project github-wise, don't hesistate to send a regular patch. All code that is contributed must be compliant with Apache License 2.0. License Copyright (c) 2011 Patrik Åkerfeldt Licensed under the Apache License, Version 2.0

19,522

社区成员

发帖
与我相关
我的任务
社区描述
硬件/嵌入开发 嵌入开发(WinCE)
社区管理员
  • 嵌入开发(WinCE)社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧