Hawkboard - Revision history

Jeff Cobb: /* Booting Linux Kernel and Mounting RAMDISK */

2011-06-17T18:50:11Z

‎Booting Linux Kernel and Mounting RAMDISK

Prpplague: /* Common Issues */

2011-01-19T21:18:20Z

‎Common Issues

Ksinkar: /* Setting up the Linux Environment */

2010-12-26T12:27:24Z

‎Setting up the Linux Environment

Ksinkar: /* Building & Booting Uboot images from source */

2010-12-26T11:54:38Z

‎Building & Booting Uboot images from source

Ksinkar: /* Setting up the Linux Environment */

2010-12-26T11:52:29Z

‎Setting up the Linux Environment

Ksinkar: /* Building & Booting Uboot images from source */

2010-12-26T11:51:15Z

‎Building & Booting Uboot images from source

Gaston: /* Common Issues */

2010-12-19T09:49:18Z

‎Common Issues

Gaston: /* Common Issues */

2010-12-19T09:48:45Z

‎Common Issues

Gaston: /* Common Issues */

2010-12-19T09:35:03Z

‎Common Issues

DavidAustin: /* Common Issues */

2010-11-04T22:39:08Z

‎Common Issues

@@ Line 295: / Line 295: @@
   $bootm c0700000
-The TFTP transferred image can be written to the NAND Flash for future use to perform kernel upgrades and enable booting without network connection.
+The TFTP transferred images can be written to the NAND Flash for future use to perform kernel upgrades and enable booting without network connection.
-To do this erase the section of the NAND containing the kernel and write the kernel image from RAM to the NAND.
+To do this erase the sections of the NAND containing the kernel and file system and write the images from RAM to the NAND.
   $nand erase 200000 200000
   $nand write.e 0xc0700000 0x200000 0x200000
-The written image can be read back using
+The written images can be read back using
   $nand read.e 0xc0700000 0x200000 0x200000
 ==== Booting Linux Kernel and Mounting NFS (Network File System) ====

@@ Line 455: / Line 455: @@
 problems many problems have been discussed on the mailing list regarding failure
 to boot linux and problems with tftp
-There has been a hardware fix posted on [http://www.innovatesolutions.net www.innovatesolutions.net]. Summary of the fix is either to send the faulty board to distributor who will send them on to innovate alternatively, the fix can also be done by customers without voiding guarantees. The fix is made up by removing two ferrite beads and shortening the pads afterwards.
+There has been a hardware fix posted on [http://www.innovatesolutions.net www.innovatesolutions.net] and discussed [[Hawkboard_problem|HERE]]. Summary of the fix is either to send the faulty board to distributor who will send them on to innovate alternatively, the fix can also be done by customers without voiding guarantees. The fix is made up by removing two ferrite beads and shortening the pads afterwards.
 [[File:Late_2010_Batch_Hawkboard_Before.jpg|400px|Hawkboard as delivered]][[File:Late_2010_Batch_Hawkboard_After.jpg|379px|Hawkboard after the fix has been applied]]

@@ Line 133: / Line 133: @@
 *Installing WINE and MONO
-    '''host#'''yum install wine mono* -y
+    '''host#''' yum install wine mono* -y
 You need to install wine and mono(make sure your mono is v2.4 and above) packages. They will help you install and run the TI provided development tools.
 *Installing the TI development tools
-    '''host$'''wine AISgen_d800k002_Install_v1.3.exe
+    '''host$''' wine AISgen_d800k002_Install_v1.3.exe
 These tools are installed in your wine/drive_C directory where-ever that is defined for your particular distribution. For Fedora the steps are as follows, from your home directory.
 *Using the actual tools
-    '''host$'''cd .wine/drive_c/Program Files/Texas Instruments/AISgen for D800K002/
+    '''host$''' cd .wine/drive_c/Program Files/Texas Instruments/AISgen for D800K002/
 *Running the AISgen tool
-    '''host$'''mono AISgen_d800k002.exe
+    '''host$''' mono AISgen_d800k002.exe
 *Running the UartHost tool
-    '''host$'''cd UartHost
+    '''host$''' cd UartHost
-    '''host$'''mono UartHost.exe
+    '''host$''' mono UartHost.exe
 Now you can follow all the instructions given below from your Linux machine.

@@ Line 132: / Line 132: @@
 Most of the following instruction for UART booting  are meant for Windows environment. For people who only have Linux on their machines the UART booting steps and creating the UART and NAND image from the ELF files seems impossible. But nothing is impossible on Linux. Hence the way out. The following instructions are Fedora specific. If you have a Debian based distro please make the corresponding changes with apt-get.
-#Installing WINE and MONO
+*Installing WINE and MONO
-'''host#'''yum install wine mono* -y
+   '''host#'''yum install wine mono* -y
 You need to install wine and mono(make sure your mono is v2.4 and above) packages. They will help you install and run the TI provided development tools.
-##Installing the TI development tools
+*Installing the TI development tools
-'''host$'''wine AISgen_d800k002_Install_v1.3.exe
+   '''host$'''wine AISgen_d800k002_Install_v1.3.exe
 These tools are installed in your wine/drive_C directory where-ever that is defined for your particular distribution. For Fedora the steps are as follows, from your home directory.
-###Using the actual tools
+*Using the actual tools
-'''host$'''cd .wine/drive_c/Program Files/Texas Instruments/AISgen for D800K002/
+   '''host$'''cd .wine/drive_c/Program Files/Texas Instruments/AISgen for D800K002/
-####Running the AISgen tool
+*Running the AISgen tool
-'''host$'''mono AISgen_d800k002.exe
+   '''host$'''mono AISgen_d800k002.exe
-####Running the UartHost tool
+*Running the UartHost tool
-'''host$'''cd UartHost
+   '''host$'''cd UartHost
-'''host$'''mono UartHost.exe
+   '''host$'''mono UartHost.exe
 Now you can follow all the instructions given below from your Linux machine.

@@ Line 137: / Line 137: @@
 You need to install wine and mono(make sure your mono is v2.4 and above) packages. They will help you install and run the TI provided development tools.
-#Installing the TI development tools
+##Installing the TI development tools
 '''host$'''wine AISgen_d800k002_Install_v1.3.exe
 These tools are installed in your wine/drive_C directory where-ever that is defined for your particular distribution. For Fedora the steps are as follows, from your home directory.
-#Using the actual tools
+###Using the actual tools
 '''host$'''cd .wine/drive_c/Program Files/Texas Instruments/AISgen for D800K002/
-#Running the AISgen tool
+####Running the AISgen tool
 '''host$'''mono AISgen_d800k002.exe
-#Running the UartHost tool
+####Running the UartHost tool
 '''host$'''cd UartHost
 '''host$'''mono UartHost.exe
 Now you can follow all the instructions given below from your Linux machine.
 === Compiling u-boot (bootloader) ===

@@ Line 127: / Line 127: @@
 unless you have Bricked the Bootloader or want to change something.So You can Skip this Section
 and can go Directly to [http://elinux.org/Hawkboard#Compiling_Linux_Kernel  Compiling Linux Kernel] or [http://elinux.org/Hawkboard#Booting_2  Booting] Kernel Section.
 === Compiling u-boot (bootloader) ===

← Older revision		Revision as of 22:39, 4 November 2010
Line 422:		Line 422:
	==Common Issues==		==Common Issues==

		+	At this stage it appears that the latest (late 2010) batch of boards have serious
		+	problems many problems have been discussed on the mailing list regarding failure
		+	to boot linux and problems with tftp

	==Projects Based on HawkBoard==		==Projects Based on HawkBoard==