[people/ms/u-boot.git] / doc / README.INCA-IP


Flash programming on the INCA-IP board is complicated because of the
EBU swapping unit. A BDI2000 can be used for flash programming only
if the EBU swapping unit is enabled; otherwise it will not detect the
flash memory. But the EBU swapping unit is disadbled after reset, so
if you program some code to flash with the swapping unit on, it will
not be runnable with the swapping unit off.

The consequence is that you have to write a pre-swapped image to
flash using the BDI2000. A simple host-side tool "inca-swap-bytes" is
provided in the "tools/" directory. Use it as follows:

	bash$ ./inca-swap-bytes <u-boot.bin >u-boot.bin.swp

Note that the current BDI config file _disables_ the EBU swapping
unit for the flash bank 0. To enable it, (this is required for the
BDI flash commands to work) uncomment the following line in the
config file:

	;WM32   0xb8000260      0x404161ff ; Swapping unit enabled

and comment out

	WM32    0xb8000260      0x004161ff ; Swapping unit disabled

Alternatively, you can use "mm 0xb8000260 <value>" commands to
enable/disable the swapping unit manually.

Just for reference, here is the complete sequence of actions we took
to install a U-Boot image into flash.

    1. ./inca-swap-bytes <u-boot.bin >u-boot.bin.swp

    2. From BDI:

	mm 0xb8000260  0x404161ff
	erase 0xb0000000
	erase 0xb0010000
	prog 0xb0000000 /tftpboot/INCA/u-boot.bin.swp bin
	mm 0xb8000260 0x004161ff
	go 0xb0000000


Ethernet autonegotiation needs some time to complete. Instead of
delaying the boot process in all cases, we just start the
autonegotiation process when U-Boot comes up and that is all. Most
likely, it will complete by the time the network transfer is
attempted for the first time. In the worst case, if a transfer is
attempted before the autonegotiation is complete, just a single
packet would be lost resulting in a single timeout error, and then
the transfer would proceed normally. So the time that we would have
lost unconditionally waiting for the autonegotiation to complete, we
have to wait only if the file transfer is started immediately after
reset. We've verified that this works for all the clock
configurations.

(C) 2003 Wolfgang Denk
Commit	Line	Data
3e38691e WD	1
	2	Flash programming on the INCA-IP board is complicated because of the
	3	EBU swapping unit. A BDI2000 can be used for flash programming only
	4	if the EBU swapping unit is enabled; otherwise it will not detect the
	5	flash memory. But the EBU swapping unit is disadbled after reset, so
	6	if you program some code to flash with the swapping unit on, it will
	7	not be runnable with the swapping unit off.
	8
	9	The consequence is that you have to write a pre-swapped image to
	10	flash using the BDI2000. A simple host-side tool "inca-swap-bytes" is
	11	provided in the "tools/" directory. Use it as follows:
	12
	13	bash$ ./inca-swap-bytes <u-boot.bin >u-boot.bin.swp
	14
	15	Note that the current BDI config file _disables_ the EBU swapping
	16	unit for the flash bank 0. To enable it, (this is required for the
	17	BDI flash commands to work) uncomment the following line in the
	18	config file:
	19
	20	;WM32 0xb8000260 0x404161ff ; Swapping unit enabled
	21
	22	and comment out
	23
	24	WM32 0xb8000260 0x004161ff ; Swapping unit disabled
	25
	26	Alternatively, you can use "mm 0xb8000260 <value>" commands to
	27	enable/disable the swapping unit manually.
	28
	29	Just for reference, here is the complete sequence of actions we took
	30	to install a U-Boot image into flash.
	31
	32	1. ./inca-swap-bytes <u-boot.bin >u-boot.bin.swp
	33
	34	2. From BDI:
	35
	36	mm 0xb8000260 0x404161ff
	37	erase 0xb0000000
	38	erase 0xb0010000
	39	prog 0xb0000000 /tftpboot/INCA/u-boot.bin.swp bin
	40	mm 0xb8000260 0x004161ff
	41	go 0xb0000000
	42
	43
e0ac62d7 WD	44	Ethernet autonegotiation needs some time to complete. Instead of
	45	delaying the boot process in all cases, we just start the
	46	autonegotiation process when U-Boot comes up and that is all. Most
	47	likely, it will complete by the time the network transfer is
	48	attempted for the first time. In the worst case, if a transfer is
	49	attempted before the autonegotiation is complete, just a single
	50	packet would be lost resulting in a single timeout error, and then
	51	the transfer would proceed normally. So the time that we would have
	52	lost unconditionally waiting for the autonegotiation to complete, we
	53	have to wait only if the file transfer is started immediately after
	54	reset. We've verified that this works for all the clock
	55	configurations.
	56
3e38691e	57	(C) 2003 Wolfgang Denk