SD卡启动问题 - TMS320DM8168 - 嵌入式开发者社区 - 51ele.net
设为首页收藏本站

嵌入式开发者社区

 找回密码
 立即注册

QQ登录

只需一步,快速开始

查看: 63|回复: 2

[未解决] SD卡启动问题

[复制链接]

1

主题

3

帖子

1019

积分

金牌会员

Rank: 6Rank: 6

积分
1019
发表于 2018-1-8 10:01:28 | 显示全部楼层 |阅读模式
我用nfs挂载根文件系统之后,想回到SD卡启动,也就改了bootcmd、bootargs、optargs,其他也没动,启动失败了。
printenv如下:

  1. bootdelay=3
  2. baudrate=115200
  3. autoload=no
  4. verify=yes
  5. bootfile=uImage
  6. ramdisk_file=ramdisk.gz
  7. loadaddr=0x81000000
  8. script_addr=0x80900000
  9. console_args=console=ttyO2,115200n8
  10. mmcdev=0
  11. mmcroot=/dev/mmcblk0p2 rw rootwait
  12. loadimage=fatload mmc ${mmcdev} ${loadaddr} ${bootfile}
  13. loadbootscript=fatload mmc ${mmcdev} ${script_addr} boot.scr
  14. bootscript= echo Running bootscript from MMC/SD to set the ENV...; source ${script_addr}
  15. mmcargs=setenv bootargs ${console_args} ${mem_args} root=${mmcroot} ${optargs}
  16. mmcboot=mmc list; if mmc rescan ${mmcdev}; then if run loadbootscript; then run bootscript; fi; if run loadimage; then echo Booting from mmc${mmcdev} ...; run mmcargs; bootm ${loadaddr}; fi; fi;
  17. nandroot=ubi0_0 ubi.mtd=8,2048
  18. nandrootfstype=ubifs
  19. nandargs=setenv bootargs ${console_args} ${mem_args} root=${nandroot} rootfstype=${nandrootfstype} ${optargs}
  20. spidev=0
  21. spibootaddr=0x100000
  22. spibootsize=0x400000
  23. spiargs=nandargs
  24. spiboot=if sf probe ${spidev}; then sf read ${loadaddr} ${spibootaddr} ${spibootsize}; run ${spiargs}; bootm ${loadaddr}; fi;
  25. rootpath=/export/rootfs
  26. nfsopts=nolock
  27. bootfile=uImage
  28. netloadimage=tftpboot ${loadaddr} ${serverip}:${bootfile}
  29. netargs=setenv bootargs ${console_args} ${mem_args} root=/dev/nfs nfsroot=${serverip}:${rootpath},${nfsopts} rw ip=dhcp ${optargs}
  30. netboot=echo Booting from network ...; run netargs; run netloadimage; bootm ${loadaddr}
  31. ethaddr=e8:eb:11:c9:80:02
  32. ethact=DaVinci EMAC
  33. serverip=192.168.1.118
  34. ipaddr=192.168.1.100
  35. bootcmd=run mmcboot; run spiboot; run netboot
  36. stdin=serial
  37. stdout=serial
  38. stderr=serial
  39. mem_args=mem=256M@0x80000000
  40. ver=U-Boot 2010.06-00037-g4831b2f (Jun 28 2017 - 19:59:42)
  41. bootargs=console=ttyO2,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=100M vram=20M notifyk.vpssm3_sva=0xbee00000 ddr_mem=1024M ip=dhcp noinitrd

  42. Environment size: 1790/8188 bytes
复制代码
boot之后的问题如下:
  1. *** Bootargs Validated for mem param ***
  2. *** This RDK version requires notifyk.vpssm3_sva=0xbfd0 in bootargs ***
  3. Kernel bootargs mismatch.!!!!ABORTING!!!
  4. Dev_pollOpen: Couldn't open /dev/syslinkipc_Osal: No such file or directory
  5.     Please ensure that SysLink's device driver moduyslink.ko) is installed
  6. OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
  7. Odriver close: /dev/syslinkipc_Osal: Bad file descriptor
  8. Dev_pollOpen: Couldn't open /dev/syslinkipc_MultiProc: No such file or directory
  9.     Please ensure that SysLink's device driver(syslink.ko) is installed
  10. /dev/syslinkipc_MultiProc: No such file or directory
  11. MultiProc drive: : Bad file descriptor
  12. Dev_pollOpen: Couldn't open /dev/syslinkipc_SharedRegion: No such file or directory
  13.     Please ysLink's device driver module (syslink.ko) is installed
  14. SharedRegion driver open: : No such filirectory
  15. SharedRegion driver close: : Bad file descriptor
复制代码

之后就一直重复cut here那一段错误。
请问一下,这个应该怎么解决?
我知道答案 本帖寻求最佳答案回答被采纳后将获得系统奖励0 , 目前已有2人回答
最近访问 头像模式 列表模式
回复

使用道具 举报

1

主题

3

帖子

1019

积分

金牌会员

Rank: 6Rank: 6

积分
1019
 楼主| 发表于 2018-1-8 10:03:36 | 显示全部楼层
  1. ------------[ cut here ]------------
  2. WARNING: at drivers/dsp/syslink/omap_notify/notify.c:779 notify_send_event+0xd4/0x26c()
  3. Modules linked in: vpss(+) ipv6 ads7846
  4. Backtrace:
  5. [<c0050bdc>] (dump_backtrace+0x0/0x110) from [<c03cd1bc>] (dump_stack+0x18/0x1c)
  6. r7:00000000 r6:c0309470 r5:c04f2374 r4:0000030b
  7. [<c03cd1a4>] (dump_stack+0x0/0x1c) from [<c0077488>] (warn_slowpath_common+0x54/0x6c)
  8. [<c0077434>] (warn_slowpath_common+0x0/0x6c) from [<c00774c4>] (warn_slowpath_null+0x24/0x2c)
  9. r9:c053eac8 r8:00000001 r7:00000002 r6:00000000 r5:00000009
  10. r4:00000000
  11. [<c00774a0>] (warn_slowpath_null+0x0/0x2c) from [<c0309470>] (notify_send_event+0xd4/0x26c)
  12. [<c030939c>] (notify_send_event+0x0/0x26c) from [<bf05253c>] (vps_fvid2_init+0x110/0x314 [vpss])
  13. [<bf05242c>] (vps_fvid2_init+0x0/0x314 [vpss]) from [<bf0520f4>] (vps_probe+0x8c/0x1a0 [vpss])
  14. [<bf052068>] (vps_probe+0x0/0x1a0 [vpss]) from [<c022574c>] (platform_drv_probe+0x20/0x24)
  15. r7:cbc63380 r6:bf061f2c r5:c053ead0 r4:c053ead0
  16. [<c022572c>] (platform_drv_probe+0x0/0x24) from [<c02246b8>] (driver_probe_device+0xd0/0x190)
  17. [<c02245e8>] (driver_probe_device+0x0/0x190) from [<c02247e0>] (__driver_attach+0x68/0x8c)
  18. r7:cbc63380 r6:bf061f2c r5:c053eb04 r4:c053ead0
  19. [<c0224778>] (__driver_attach+0x0/0x8c) from [<c0223e64>] (bus_for_each_dev+0x50/0x84)
  20. r7:cbc63380 r6:bf061f2c r5:c0224778 r4:00000000
  21. [<c0223e14>] (bus_for_each_dev+0x0/0x84) from [<c02244dc>] (driver_attach+0x20/0x28)
  22. r6:bf061f2c r5:bf061f18 r4:00000000
  23. [<c02244bc>] (driver_attach+0x0/0x28) from [<c022373c>] (bus_add_driver+0xb4/0x234)
  24. [<c0223688>] (bus_add_driver+0x0/0x234) from [<c0224b18>] (driver_register+0xb0/0x13c)
  25. [<c0224a68>] (driver_register+0x0/0x13c) from [<c0225a38>] (platform_driver_register+0x4c/0x60)
  26. r9:cb080000 r8:bf068000 r7:40014000 r6:0001b008 r5:bf061f18
  27. r4:00000000
  28. [<c02259ec>] (platform_driver_register+0x0/0x60) from [<c0225a6c>] (platform_driver_probe+0x20/0x70)
  29. [<c0225a4c>] (platform_driver_probe+0x0/0x70) from [<bf068030>] (vps_init+0x30/0x5c [vpss])
  30. r5:bf062300 r4:00000000
  31. [<bf068000>] (vps_init+0x0/0x5c [vpss]) from [<c004242c>] (do_one_initcall+0xd0/0x1a4)
  32. [<c004235c>] (do_one_initcall+0x0/0x1a4) from [<c00a2ba4>] (sys_init_module+0x9c/0x1bc)
  33. [<c00a2b08>] (sys_init_module+0x0/0x1bc) from [<c004ce00>] (ret_fast_syscall+0x0/0x30)
  34. r7:00000080 r6:00000000 r5:0001b008 r4:00001030
  35. ---[ end trace 45c79fd2abdde260 ]---
  36. Dev_pollOpen: Couldn't open /dev/syslinkipc_ListMP: No such file or directory
  37.     Please ensure that SysLink's device driver module (syslink.ko) is installed
  38. /dev/syslinkipc_ListMP: No such file or directory
  39. Dev_pollOpen: Couldn't open /dev/syslinkipc_ListMP: No such file or directory
  40.     Please ensure that SysLink's device driver module (syslink.ko) is installed
  41. /dev/syslinkipc_ListMP: No such file or directory
复制代码
回复 支持 反对

使用道具 举报

1

主题

3

帖子

1019

积分

金牌会员

Rank: 6Rank: 6

积分
1019
 楼主| 发表于 2018-1-8 10:05:55 | 显示全部楼层
  1. Assertion at Line no: 344 in /home/teddy/tl138/dvrrdk/DVRRDK_04.01.00.02/dvr_rdk/../ti_tools/syslink/syslink_2_20_02_20/packages/ti/syslink/utils/hlos/usr/MultiProc.c: (MultiProc_module->refCount > 0) : failed
  2. Invalid <Core name> specified!
  3. Usage : ./fw_load.out <startup|shutdown> <Core name> [File path]

  4. Supported core names:
  5. Note: [File path] argument is only reosa_kermod: disagrees about version of symbol module_layout
  6. quired when first argument is 'startup'
  7. insmod: error inserting '../kermod/osa_kermod.ko': -1 Invalid module format
  8. BusyBox v1.13.2 (2012-12-26 15:45:54 IST) multi-call binary
复制代码
回复 支持 反对

使用道具 举报

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

本版积分规则  回帖提醒

QQ|手机版|小黑屋|嵌入式开发者社区 ( 粤ICP备15055271号-1  

GMT+8, 2018-1-19 03:55 , Processed in 0.283576 second(s), 39 queries .

Powered by Discuz! X3.2

© 2001-2015 Comsenz Inc.

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