Devkit8500FAQ - Revision history

Yclinda666 at 08:33, 13 December 2011

2011-12-13T08:33:08Z

Yclinda666 at 08:16, 13 December 2011

2011-12-13T08:16:21Z

Yclinda666: /* No response when booting u-boot */

2011-12-13T08:15:22Z

‎No response when booting u-boot

Yclinda666: /* DVSDK problem */

2011-12-13T08:14:01Z

‎DVSDK problem

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

2011-12-13T08:00:30Z

‎Why I can only see one partition after TF card partitioning?

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

2011-12-13T07:59:47Z

‎Why I can only see one partition after TF card partitioning?

Yclinda666: /* Why I can only see one partition after TF card partitioning? */

2011-12-13T07:59:04Z

‎Why I can only see one partition after TF card partitioning?

Yclinda666 at 07:57, 13 December 2011

2011-12-13T07:57:45Z

Yclinda666: /* Why WinCE BSP could not be compiled successfully? */

2011-12-13T07:43:12Z

‎Why WinCE BSP could not be compiled successfully?

Yclinda666: /* Why WinCE BSP could not be compiled successfully? */

2011-12-13T07:41:21Z

‎Why WinCE BSP could not be compiled successfully?

← Older revision		Revision as of 08:33, 13 December 2011
Line 1:		Line 1:
−	This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[DevKit8500]]. Hope it would give you some help.	+	This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[DevKit8500]]. Hope it would give you some help. Please find the FAQ in Chinese from [[DevKit8500_FAQ]].

	=Hardware problem=		=Hardware problem=

← Older revision		Revision as of 08:16, 13 December 2011
Line 1:		Line 1:
−	This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[~~Devkit8500~~]]. Hope it would give you some help.	+	This page mainly summarizes solutions to some main problems during the development of [http://www.armkits.com Embest] [[DevKit8500]]. Hope it would give you some help.

	=Hardware problem=		=Hardware problem=

@@ Line 115: / Line 115: @@
 . You had input more spaces in commands line before inputing other commands;<br>
 We suggest copying and pasting the commands directly from pdf files.<br>
-<br>
-setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M<br>
+    setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M<br>
       <br>
      setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000'<br>

← Older revision		Revision as of 08:14, 13 December 2011
Line 74:		Line 74:
	b) Please operate once again;<br>		b) Please operate once again;<br>
	c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card).<br>		c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card).<br>
		+
		+	==No response when booting u-boot==
		+	Answer: when starting u-boot in DVSDK, the hyper-terminal will appear status below:<br>
		+	''60<br>
		+	<br>
		+	Texas Instruments X-Loader 1.47 (Feb 17 2011 - 17:33:15)<br>
		+	Devkit8500 xM Rev A<br>
		+	Starting X-loader on MMC <br>
		+	Reading boot sector<br>
		+	<br>
		+	1153660 Bytes Read from MMC <br>
		+	Starting OS Bootloader from MMC...<br>
		+	Starting OS Bootloader...<br>
		+	<br>
		+	<br>
		+	U-Boot 2010.06-rc1-svn ( 5鏈?06 2011 - 10:05:25)<br>
		+	<br>
		+	OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz<br>
		+	OMAP3 Devkit8500 board + LPDDR/NAND<br>
		+	I2C: ready<br>
		+	DRAM: 512 MiB<br>
		+	NAND: 512 MiB<br>
		+	In: serial<br>
		+	Out: serial<br>
		+	Err: serial<br>
		+	Devkit8500 xM Rev A<br>
		+	Die ID #2cf600229e3800000163810d19031024<br>
		+	Net: dm9000<br>
		+	Hit any key to stop autoboot: 0 （此处在超级终端串口下按下任意按键）<br>
		+	OMAP3 devkit8500 # setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M<br>
		+	OMAP3 devkit8500 # setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000'<br>
		+	OMAP3 devkit8500 # saveenv<br>
		+	OMAP3 devkit8500 # boot''<br>
		+	OMAP3 devkit8500 # <br>
		+	<br>
		+	For normal u-boot, if user inputs "boot" in u-boot, it will excute:<br>
		+	setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000' <br>
		+	If commands have some syntax errors, it might stop the following excution, the problem might be:<br>
		+	1. When inputing some commands manually, you have ignored some space input;<br>
		+	2. You had input more spaces in commands line before inputing other commands;<br>
		+	We suggest copying and pasting the commands directly from pdf files.<br>
		+	<br>
		+	setenv bootargs console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rw rootwait mpurate=1000 mem=99M@0x80000000 mem=128M@0x88000000 omapdss.def_disp=lcd omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M<br>
		+	<br>
		+	setenv bootcmd 'mmc init;fatload mmc 0 80300000 uImage;bootm 80300000'<br>

@@ Line 73: / Line 73: @@
 a) Confirm if you had used ROOT right for partition in your operation;<br>
 b) Please operate once again;<br>
-c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card.<br>
+c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card).<br>

@@ Line 70: / Line 70: @@
 Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons:<br>
 . You have seen the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows;<br>
-. If you can only see on partition under Linux system, please follow below ways:<br>
+. If you can only see one partition under Linux system, please follow below ways:<br>
 a) Confirm if you had used ROOT right for partition in your operation;<br>
 b) Please operate once again;<br>

← Older revision		Revision as of 07:57, 13 December 2011
Line 64:		Line 64:
	4. Please check if you had added some of your own codes to make the compiling unsuccessfully;<br>		4. Please check if you had added some of your own codes to make the compiling unsuccessfully;<br>
	5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help.<br>		5. After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help.<br>
		+
		+	=DVSDK problem=
		+
		+	==Why I can only see one partition after TF card partitioning?==
		+	Answer: when using DVSDK, you need to prepare a TF card with partition. But we could only see one partition, there might be several reasons:<br>
		+	1. You see the only one partition under Windows system, the TF card first partition is FAT, the second partition is EXT3 and EXT3 can only be recognized under Linux, so you can only see FAT partition in Windows;<br>
		+	2. If you can only see on partition under Linux system, please follow below ways:<br>
		+	a) Confirm if you had used ROOT right for partition in your operation;<br>
		+	b) Please operate once again;<br>
		+	c) Change another TF card (please use TF card with good quality as partitioning requires high-quality TF card.<br>
		+
		+

@@ Line 61: / Line 61: @@
 Wrong: C:\WINCE600\OSDesigns\DevKit8500\Devkit8500 <br>
 Please do not repeat folders.<br>
-. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual; <br>
+. Please check if you had selected "Build Solution" in "[Build-> Build Solution]" of vs2005 window for compiling accroding to the user manual;<br>
 . Please check if you had added some of your own codes to make the compiling unsuccessfully;<br>
 . After above checking, if you still could not find the problem, please contact Embest support team: support@embedinfo.com, our engineer will give you some help.<br>

@@ Line 56: / Line 56: @@
 ==Why WinCE BSP could not be compiled successfully?==
 Answer: if you had installed WinCE compiling environment and want to rebuild the system, but after fully decompressed BSP to the platform directory of wince600 and also used the sln file attached with the software, it still failed. Please follow below ways to check: <br>
-. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no much problem;<br>
+. Please read the user manual to check if the compiling tools have been installed completely; if not complete, it will remind some error informaiton for being lack of some head files; We testing BSP carefully before goods delivery, so this part would usually no any problem;<br>
 . Please check if the folders copied to C:\WINCE600 are right, such as:<br>
 Right: C:\WINCE600\OSDesigns\DevKit8500 <br>