Setting up U-Boot - Revision history

Jcmvbkbc: Blanked the page

2018-03-02T23:31:27Z

Blanked the page

← Older revision		Revision as of 23:31, 2 March 2018
Line 1:		Line 1:
	~~== LX60, LX200, ML605, KC705 U-Boot Installation ==~~

	~~=== Loading initial image through xocd + xt-gdb ===~~

	~~$ '''xt-gdb -n u-boot'''~~
	~~(xt-gdb) '''target remote localhost:20000 0'''~~
	~~(xt-gdb) '''reset'''~~
	~~(xt-gdb) '''load'''~~
	~~(xt-gdb) '''continue'''~~

	~~=== Flashing U-Boot image ===~~

	~~U-Boot> '''protect off ...'''~~
	~~U-Boot> '''erase ...'''~~
	~~U-Boot> '''tftp u-boot.bin'''~~
	~~U-Boot> '''cp.b 2000000 F8000000 20000'''~~

Jcmvbkbc: Replaced content with "== LX60, LX200, ML605, KC705 U-Boot Installation == === Loading initial image through xocd + xt-gdb === $ '''xt-gdb -n u-boot''' (xt-gdb) '''target remote localhos..."

2018-03-02T18:58:04Z

Replaced content with "== LX60, LX200, ML605, KC705 U-Boot Installation == === Loading initial image through xocd + xt-gdb === $ '''xt-gdb -n u-boot''' (xt-gdb) '''target remote localhos..."

Show changes

Jcmvbkbc: use 'Boot Select' instead of specific DIP switch number, fix typos, add KC705 bootloader area address/size

2014-06-05T20:47:12Z

use 'Boot Select' instead of specific DIP switch number, fix typos, add KC705 bootloader area address/size

← Older revision		Revision as of 20:47, 5 June 2014
Line 1:		Line 1:
	== LX60 ~~and~~ LX200 U-Boot Installation ~~(LX110 in Progress)~~ ==		== LX60, LX200, ML605, KC705 U-Boot Installation ==

	''('''News:''' U-Boot for the new DC233, with the V3 MMU, is now working fine and checked into the master branch. Work is almost complete with the Linux 2.6.29-smp kernel, with		''('''News:''' U-Boot for the new DC233, with the V3 MMU, is now working fine and checked into the master branch. Work is almost complete with the Linux 2.6.29-smp kernel, with
Line 7:		Line 7:

	[http://www.denx.de/wiki/UBoot U-Boot] is a very popular boot loader; especially within the [http://elinux.org/Bootloader Embedded Linux community].		[http://www.denx.de/wiki/UBoot U-Boot] is a very popular boot loader; especially within the [http://elinux.org/Bootloader Embedded Linux community].
	The U-Boot loader runs on the FPGA boards which are equipped with a dip switch, number 8, which can select where the memory location for the reset		The U-Boot loader runs on the FPGA boards which are equipped with a Boot Select dip switch, (number 8 on Avnet and ML605 boards, number 1 on KC705),
	vector (0XFE00,0000) comes from. With ~~switch number 8~~ off the board will map the memory at the reset vector to a small block of SRAM located in the		which can select where the memory location for the reset vector (0XFE00,0000) comes from.
	I/O block with the UART and Ethernet buffer memory. When ~~switch number 8~~ is on the ~~Avnet~~ boards map the ~~beginning~~ of the Flash Memory at 0XF800,~~000~~		With the Boot Switch off the board will map the memory at the reset vector to a small block of SRAM located in the
	to the reset vector at 0xFE00,~~000~~.		I/O block with the UART and Ethernet buffer memory. When the Boot Switch is on the xtfpga boards map the Bootloader area of the Flash Memory
			(at 0XF800,0000 on Avnet and ML605 boards, at 0xF600,0000 on KC705) to the reset vector at 0xFE00,0000.

	What we are going to do here is build a version of U-Boot for your ~~Avnet~~ board and Variant, install that ELF file into memory		What we are going to do here is build a version of U-Boot for your xtfpga board and Variant, install that ELF file into memory
	with xt-gdb and run U-Boot. Then we are going to download a another copy of this identical program with '''tftp'''. The version we		with xt-gdb and run U-Boot. Then we are going to download a another copy of this identical program with '''tftp'''. The version we
	are going to download is just the ELF file with the headers and debug information removed. It's just the actual bits that get		are going to download is just the ELF file with the headers and debug information removed. It's just the actual bits that get
	loaded into memory. For the new V3 MMU the default '''loadaddr''' is typically 0x20,0000 and for the older V2 MMU this is in the		loaded into memory. For the new V3 MMU the default '''loadaddr''' is typically 0x20,0000 and for the older V2 MMU this is in the
	Linux mapping equivalent, 0xD0200,0000. The default location can be ~~change~~ by setting the U-Boot 'loadaddr' environment variable		Linux mapping equivalent, 0xD0200,0000. The default location can be changed by setting the U-Boot 'loadaddr' environment variable
	or by changing the variable '''CONFIG_SYS_LOAD_ADDR''' in the boards U-Boot config file.		or by changing the variable '''CONFIG_SYS_LOAD_ADDR''' in the boards U-Boot config file.

	Once the virgin copy of the U-Boot program has been loaded into memory, the Flash memory is un-protected and ~~errasd~~, then the		Once the virgin copy of the U-Boot program has been loaded into memory, the Flash memory is un-protected and erased, then the
	memory with the U-Boot program in it is copied to the flash memory and protected. Next you will set dip switch 8 on, ~~recycle~~		memory with the U-Boot program in it is copied to the flash memory and protected. Next you will set Boot Select dip switch on, cycle
	power on the board, and U-Boot will be accessible via the serial UART at 38400 baud. U-Boot works without any MMU mapping,		power on the board, and U-Boot will be accessible via the serial UART at 38400 baud. U-Boot works without any MMU mapping,
	and should be fine on configurations without an MMU. Only an ethernet and serial interface are required.		and should be fine on configurations without an MMU. Only an ethernet and serial interface are required.
Line 130:		Line 131:
	U-Boot>		U-Boot>

	The timeout and error messages are likley just warning messages and you board has been ~~errased~~. You can see that with the flash info command '''flinfo'''. Below is an example with a LX200 board, which has a much larger flash than the smaller LX60:		The timeout and error messages are likley just warning messages and you board has been erased. You can see that with the flash info command '''flinfo'''. Below is an example with a LX200 board, which has a much larger flash than the smaller LX60:

	U-Boot> '''flinfo'''		U-Boot> '''flinfo'''
Line 291:		Line 292:
	so turn off protection on the 1st 11 sectors and		so turn off protection on the 1st 11 sectors and
	erase the current contents.		erase the current contents.

			On KC705 you do this:

			U-Boot> '''tftp tensilica/u-boot.bin.test_kc705'''
			ethoc
			Using ETHOC-0 device
			TFTP from server 192.168.11.1; our IP address is 192.168.11.2
			Filename 'tensilica/u-boot.bin.test_kc705'.
			Load address: 0x2000000
			Loading: #########
			691.4 KiB/s
			done
			Bytes transferred = 126050 (1ec62 hex)

	For the '''LX60''' you do this:		For the '''LX60''' you do this:
Line 310:		Line 324:
	U-Boot> '''erase F8000000 F803FFFF'''		U-Boot> '''erase F8000000 F803FFFF'''
	Erased 2 sectors		Erased 2 sectors
			U-Boot>

			For the '''KC705''' the starting address is '''(F6000000)''' and the the reserved area is 8 Megabytes, with the last address of '''(F67fFFFF)'''. There's no need to unprotect areas that you're not going to use though:

			U-Boot> '''protect off F6000000 +20000'''
			. done
			Un-Protected 1 sectors
			U-Boot> '''erase F6000000 +20000'''
			Erased 1 sectors
	U-Boot>		U-Boot>

Line 320:		Line 343:


	For the LX60 with the '''NEW''' V3 MMU you copy ~~0x24000~~ bytes from 0x2000000 to F8000000:		For the LX60 with the '''NEW''' V3 MMU you copy 0x20000 bytes from 0x2000000 to F8000000:

	U-Boot> '''cp.b 2000000 F8000000 20000'''		U-Boot> '''cp.b 2000000 F8000000 20000'''
Line 331:		Line 354:

	For the LX110 with a V3-MMU you copy 0x40000 bytes from 0x2000000 to F8000000:		For the LX110 with a V3-MMU you copy 0x40000 bytes from 0x2000000 to F8000000:
	U-Boot> cp.b 2000000 F8000000 40000		U-Boot> '''cp.b 2000000 F8000000 40000'''
	Copy to Flash... done		Copy to Flash... done

			For the KC705 with the V3 MMU you copy 0x20000 bytes from 0x2000000 to F6000000:

			U-Boot> '''cp.b 2000000 F6000000 20000'''
			Copy to Flash... done


Line 479:		Line 507:
	of this LX200.		of this LX200.

	~~On both the LX60 and the LX200 now~~ move DIP switch ~~8 to the ON position, on the LX110 move DIP switch 4~~ to the ON position.		Now move Boot Select DIP switch to the ON position.
	Next, power cycle the board. On the LX60 you should see U-boot in the LCD display.		Next, power cycle the board. On the LX60 you should see U-boot in the LCD display.

Piet: /* LX60 and LX200 U-Boot Installation (LX110 in Progress) */

2012-03-21T02:37:11Z