SylixOS嵌入式操作系统|论坛

 找回密码
 注册
搜索
查看: 5953|回复: 3

通过uboot如何引导编译好的sylixos

[复制链接]

4

主题

21

帖子

103

积分

注册会员

Rank: 2

积分
103
发表于 2016-6-14 14:38:38 | 显示全部楼层 |阅读模式
我编译了mini2440的bspmini2440.bin,我通过uboot将bin文件下载到ram的起始地址,然后跳转到起始地址,不能正确引导出现如下错误: 这是怎么回事
## Starting application at 0x30000000 ...API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_SemaphoreMPend() error: semaphore handle invalidate.
in thread "t_boot" context.
API_SemaphoreMPost() error: semaphore handle invalidate.
in thread "t_boot" context.
API_SemaphoreMPend() error: semaphore handle invalidate.
in thread "t_boot" context.
API_SemaphoreMPost() error: semaphore handle invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.
API_IosWrite() error: file descriptor invalidate.
in thread "t_boot" context.

回复

使用道具 举报

17

主题

81

帖子

1079

积分

管理员

Rank: 9Rank: 9Rank: 9

积分
1079
发表于 2016-6-23 09:01:47 | 显示全部楼层
t_boot 内核线程还没有到初始化标准文件描述符时,崩溃了, 你把内核 log 在启动参数中打开,看看内核初始化到哪里出现了错误。klog=yes
回复 支持 反对

使用道具 举报

4

主题

21

帖子

103

积分

注册会员

Rank: 2

积分
103
 楼主| 发表于 2016-6-24 09:47:25 | 显示全部楼层
我在编译uboot的时候,发现地址30001000是uboot的全局变量存储地址,当我下载编译后的镜像文件时把这段全局变量地址给覆盖了,我修改了bspmini2440的内存起始地址为30010000跳过前面一段地址后,问题得到解决,可以正常启动了。
回复 支持 反对

使用道具 举报

4

主题

21

帖子

103

积分

注册会员

Rank: 2

积分
103
 楼主| 发表于 2016-6-24 09:48:24 | 显示全部楼层
sylixos 发表于 2016-6-23 09:01
t_boot 内核线程还没有到初始化标准文件描述符时,崩溃了, 你把内核 log 在启动参数中打开,看看内核初始 ...

谢谢回复
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|手机版|Acoinfo Inc. All Rights Reserved. ( 京ICP备15059934号

GMT+8, 2024-2-23 22:28 , Processed in 0.041908 second(s), 21 queries .

Powered by Discuz! X3.2

© 2001-2013 Comsenz Inc.

快速回复 返回顶部 返回列表