December 2007 - U-Boot

Re: [U-Boot-Users] how memory mapping is done at reset
by Martijn de Gouw 07 Dec '07

07 Dec '07

> i have one doubt....At reset we start executing from > Flash,which is at #CS0,in my system it starts with address > 0x00000000..now after that we call the function cpu_init_f() > which will remap the starting address of the flash to > 0x02000000...but after this PC is at somewhere greater than > 0x00000000..so the next instruction should fail as CS0 is > already modified.... What platform are you talking about? Gr, Martijn

1 0

[U-Boot-Users] how memory mapping is done at reset
by yusuf khan 07 Dec '07

07 Dec '07

hi all i have one doubt....At reset we start executing from Flash,which is at #CS0,in my system it starts with address 0x00000000..now after that we call the function cpu_init_f() which will remap the starting address of the flash to 0x02000000...but after this PC is at somewhere greater than 0x00000000..so the next instruction should fail as CS0 is already modified.... can anybody tell me how it is achieved.... thanks in advance Yusuf

1 0

[U-Boot-Users] u-boot source codes for utx8245 don't install intel82559 pci interrupt handler
by xianghui ren 07 Dec '07

07 Dec '07

I am studying u-boot codes for utx8245. now I am confused with intel82559 pci interrupt handler. . I find that u-boot source codes for mpc824x don't implement call handler codes after getting vector, and just assign pci_interrupt_line, but don't install handler. How to find intel82559 pci interrupt handler in the source codes? Thanks in advance!

1 0

Re: [U-Boot-Users] Uboot and ML410
by John Hahn 07 Dec '07

07 Dec '07

Bringing a discussion thread over from https://ozlabs.org/mailman/listinfo/linuxppc-embedded > From: linuxppc-embedded-bounces+jhahn=bcfsemi.com(a)ozlabs.org > [mailto:linuxppc-embedded-bounces+jhahn=bcfsemi.com@ozlabs.org] On > Behalf Of khollan > Sent: Thursday, December 06, 2007 11:01 AM ... > > John Hahn wrote: > > > > We are also using 3.81 make (Centos 5 distro) with ELDK 4.1 version > > downloaded from www.denx.de and have had no problems using the > > u-boot.zip srcs from www.xilinx.com/ml410_p, though we use uboot for > > our ml403 based development, we can build u-boot for ml403_config as > well as ml410_config. > > > > > > Cheers > > > > John > > > > When I try compiling with my tools I get the message No rule to make > target `hello_world.srec', needed by `all' > Any way to work around this. I have compiled everything else I use on > my system with these tools and it works fine. I did some research on > this problem and it seemed to be a problem with the newer versions of > make, but if thats not the case what is the problem? I don't really > want to install ELDK to keep things consistent. > Thanks > Kevin > -- The targets in examples are example programs for uboot to load/exec and is not part of u-boot. You can avoid building in examples. But the build problem appears to be due to examples/Makefile syntax. Try: -BIN = hello_world hello_world.bin +BIN = hello_world.bin hello_world ... similar corrections for the other targets, and finally -all: .depend $(OBJS) $(LIB) $(BIN) $(SREC) +all: .depend $(OBJS) $(LIB) $(SREC) $(BIN) Cheers John _________________ John S Hahn BCF Semiconductor

2 1

[U-Boot-Users] [PATCH] Add support CONFIG_UEC_ETH3 in MPC83xx
by Joakim Tjernlund 06 Dec '07

06 Dec '07

>From 23bc0c555be82eda79425c4d0364834565aacc79 Mon Sep 17 00:00:00 2001 From: Joakim Tjernlund <Joakim.Tjernlund(a)transmode.se> Date: Thu, 6 Dec 2007 16:43:40 +0100 Subject: [PATCH] Add support CONFIG_UEC_ETH3 in MPC83xx Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund(a)transmode.se> --- cpu/mpc83xx/cpu.c | 116 ++++++++++++++++++++++++++++++++++++++++++++++++++++- drivers/qe/uec.c | 23 ++++++++++ net/eth.c | 3 + 3 files changed, 141 insertions(+), 1 deletions(-) diff --git a/cpu/mpc83xx/cpu.c b/cpu/mpc83xx/cpu.c index e634f0a..b838381 100644 --- a/cpu/mpc83xx/cpu.c +++ b/cpu/mpc83xx/cpu.c @@ -485,6 +485,15 @@ static const struct { "local-mac-address", fdt_set_eth0 }, +#elif CFG_UEC1_UCC_NUM == 1 /* UCC2 */ + { "/" OF_QE "/ucc@3000", + "mac-address", + fdt_set_eth0 + }, + { "/" OF_QE "/ucc@3000", + "local-mac-address", + fdt_set_eth0 + }, #elif CFG_UEC1_UCC_NUM == 2 /* UCC3 */ { "/" OF_QE "/ucc@2200", "mac-address", @@ -494,10 +503,28 @@ static const struct { "local-mac-address", fdt_set_eth0 }, +#elif CFG_UEC1_UCC_NUM == 3 /* UCC4 */ + { "/" OF_QE "/ucc@3200", + "mac-address", + fdt_set_eth0 + }, + { "/" OF_QE "/ucc@3200", + "local-mac-address", + fdt_set_eth0 + }, #endif #endif /* CONFIG_UEC_ETH1 */ #ifdef CONFIG_UEC_ETH2 -#if CFG_UEC2_UCC_NUM == 1 /* UCC2 */ +#if CFG_UEC2_UCC_NUM == 0 /* UCC1 */ + { "/" OF_QE "/ucc@2000", + "mac-address", + fdt_set_eth1 + }, + { "/" OF_QE "/ucc@2000", + "local-mac-address", + fdt_set_eth1 + }, +#elif CFG_UEC2_UCC_NUM == 1 /* UCC2 */ { "/" OF_QE "/ucc@3000", "mac-address", fdt_set_eth1 @@ -506,6 +533,15 @@ static const struct { "local-mac-address", fdt_set_eth1 }, +#elif CFG_UEC2_UCC_NUM == 2 /* UCC3 */ + { "/" OF_QE "/ucc@2200", + "mac-address", + fdt_set_eth1 + }, + { "/" OF_QE "/ucc@2200", + "local-mac-address", + fdt_set_eth1 + }, #elif CFG_UEC2_UCC_NUM == 3 /* UCC4 */ { "/" OF_QE "/ucc@3200", "mac-address", @@ -517,6 +553,84 @@ static const struct { }, #endif #endif /* CONFIG_UEC_ETH2 */ +#ifdef CONFIG_UEC_ETH3 +#if CFG_UEC3_UCC_NUM == 0 /* UCC1 */ + { "/" OF_QE "/ucc@2000", + "mac-address", + fdt_set_eth2 + }, + { "/" OF_QE "/ucc@2000", + "local-mac-address", + fdt_set_eth2 + }, +#elif CFG_UEC3_UCC_NUM == 1 /* UCC2 */ + { "/" OF_QE "/ucc@3000", + "mac-address", + fdt_set_eth2 + }, + { "/" OF_QE "/ucc@3000", + "local-mac-address", + fdt_set_eth2 + }, +#elif CFG_UEC3_UCC_NUM == 2 /* UCC3 */ + { "/" OF_QE "/ucc@2200", + "mac-address", + fdt_set_eth2 + }, + { "/" OF_QE "/ucc@2200", + "local-mac-address", + fdt_set_eth2 + }, +#elif CFG_UEC3_UCC_NUM == 3 /* UCC4 */ + { "/" OF_QE "/ucc@3200", + "mac-address", + fdt_set_eth2 + }, + { "/" OF_QE "/ucc@3200", + "local-mac-address", + fdt_set_eth2 + }, +#endif +#endif /* CONFIG_UEC_ETH3 */ +#ifdef CONFIG_UEC_ETH4 +#if CFG_UEC4_UCC_NUM == 0 /* UCC1 */ + { "/" OF_QE "/ucc@2000", + "mac-address", + fdt_set_eth3 + }, + { "/" OF_QE "/ucc@2000", + "local-mac-address", + fdt_set_eth3 + }, +#elif CFG_UEC4_UCC_NUM == 1 /* UCC2 */ + { "/" OF_QE "/ucc@3000", + "mac-address", + fdt_set_eth3 + }, + { "/" OF_QE "/ucc@3000", + "local-mac-address", + fdt_set_eth3 + }, +#elif CFG_UEC4_UCC_NUM == 2 /* UCC3 */ + { "/" OF_QE "/ucc@2200", + "mac-address", + fdt_set_eth3 + }, + { "/" OF_QE "/ucc@2200", + "local-mac-address", + fdt_set_eth3 + }, +#elif CFG_UEC4_UCC_NUM == 3 /* UCC4 */ + { "/" OF_QE "/ucc@3200", + "mac-address", + fdt_set_eth3 + }, + { "/" OF_QE "/ucc@3200", + "local-mac-address", + fdt_set_eth3 + }, +#endif +#endif /* CONFIG_UEC_ETH4 */ #endif /* CONFIG_QE */ }; diff --git a/drivers/qe/uec.c b/drivers/qe/uec.c index 5f48153..84ef85d 100644 --- a/drivers/qe/uec.c +++ b/drivers/qe/uec.c @@ -69,6 +69,25 @@ static uec_info_t eth2_uec_info = { }; #endif +#ifdef CONFIG_UEC_ETH3 +static uec_info_t eth3_uec_info = { + .uf_info = { + .ucc_num = CFG_UEC3_UCC_NUM, + .rx_clock = CFG_UEC3_RX_CLK, + .tx_clock = CFG_UEC3_TX_CLK, + .eth_type = CFG_UEC3_ETH_TYPE, + }, + .num_threads_tx = UEC_NUM_OF_THREADS_4, + .num_threads_rx = UEC_NUM_OF_THREADS_4, + .riscTx = QE_RISC_ALLOCATION_RISC1_AND_RISC2, + .riscRx = QE_RISC_ALLOCATION_RISC1_AND_RISC2, + .tx_bd_ring_len = 16, + .rx_bd_ring_len = 16, + .phy_address = CFG_UEC3_PHY_ADDR, + .enet_interface = CFG_UEC3_INTERFACE_MODE, +}; +#endif + static int uec_mac_enable(uec_private_t *uec, comm_dir_e mode) { uec_t *uec_regs; @@ -1237,6 +1256,10 @@ int uec_initialize(int index) #ifdef CONFIG_UEC_ETH2 uec_info = &eth2_uec_info; #endif + } else if (index == 2) { +#ifdef CONFIG_UEC_ETH3 + uec_info = &eth3_uec_info; +#endif } else { printf("%s: index is illegal.\n", __FUNCTION__); return -EINVAL; diff --git a/net/eth.c b/net/eth.c index 1b56a35..a230277 100644 --- a/net/eth.c +++ b/net/eth.c @@ -202,6 +202,9 @@ int eth_initialize(bd_t *bis) #if defined(CONFIG_UEC_ETH2) uec_initialize(1); #endif +#if defined(CONFIG_UEC_ETH3) + uec_initialize(2); +#endif #if defined(FEC_ENET) || defined(CONFIG_ETHER_ON_FCC) fec_initialize(bis); -- 1.5.3.6

1 0

[U-Boot-Users] Problems in making Ram disk image
by ravic＠dynalogindia.com 06 Dec '07

06 Dec '07

Problems in making Ram disk imageDear friends, I am facing some problems in making initrd image for at91rm9200.I am using this command,as per mentioned in README file of u-boot-1.1.6. tools/mkimage -n 'Simple Ramdisk Image' -a arm -0x00000000 linux -T ramdisk -C gzip -d /ArmLinux/images/SIMPLE-ramdisk.image.gz/ examples/simple-initrd tools/mkimage: invalid load address arm My loading address is 0x00000000 Ravi

2 1

[U-Boot-Users] this is my understanding of pciauto_region_align function, is it right?
by xianghui ren 06 Dec '07

06 Dec '07

void pciauto_region_align(struct pci_region *res, unsigned long size) { res->bus_lower = ((res->bus_lower - 1) | (size - 1)) + 1; } The above function is to do address align with size. Belows is my explanation with example: According to PCI specification, size must be the power of 2, assume Size is 0x100, then size-1 = 0xFF; (res->bus_lower - 1) | (size - 1) = 0x??????FF; ((res->bus_lower - 1) | (size - 1)) + 1=0x??????00; So, the result is aligned with size of 0x100. Now let analyse "res->bus_lower", we must divide it into two aspects: 1. res->bus_lower = 0x??????0? because or operate with 0x??????FF, substracting 1 is not important. 2. res->bus_lower = 0x??????00 Obviously, the address is aligned with size of 0x100, so doing substract 1 is necessary, then the result of ((res->bus_lower - 1) | (size - 1)) + 1 is the same with the original value of res->bus_lower.

1 0

[U-Boot-Users] pci auto allocate region problem?
by xianghui ren 06 Dec '07

06 Dec '07

hello, everybody: In pciauto_region_allocate function, I can't understand the mean of the sentence "addr = ((res->bus_lower - 1) | (size - 1)) + 1;". why to do "-1" and "+1" operate? why to do or operate? What does the variable "addr" mean? Thanks in advance!

1 0

[U-Boot-Users] [PATCH] Fix ppc4xx clear_bss() code
by agustschin＠t-online.de 05 Dec '07

05 Dec '07

ppc4xx clear_bss() fails if BSS segment size is not divisible by 4 without remainder. This patch provides fix for this problem. Signed-off-by: Anatolij Gustschin <agust(a)denx.de> --- cpu/ppc4xx/start.S | 17 +++++++++++++---- 1 files changed, 13 insertions(+), 4 deletions(-) diff --git a/cpu/ppc4xx/start.S b/cpu/ppc4xx/start.S index 9626b65..9175e31 100644 --- a/cpu/ppc4xx/start.S +++ b/cpu/ppc4xx/start.S @@ -1566,16 +1566,25 @@ clear_bss: lwz r4,GOT(_end) cmplw 0, r3, r4 - beq 6f + beq 7f li r0, 0 -5: + + andi. r5, r4, 3 + beq 6f + sub r4, r4, r5 + mtctr r5 + mr r5, r4 +5: stb r0, 0(r5) + addi r5, r5, 1 + bdnz 5b +6: stw r0, 0(r3) addi r3, r3, 4 cmplw 0, r3, r4 - bne 5b -6: + bne 6b +7: mr r3, r9 /* Init Data pointer */ mr r4, r10 /* Destination Address */ bl board_init_r -- 1.5.3.3

3 2

[U-Boot-Users] u-boot mmu enable
by Pankaj PANDEY 05 Dec '07

05 Dec '07

Hi all, I am worknig on u-boot-1.1.2 for arm926ejs target cpu, here i am not able to get virtual address mode for kernel zImage debugging. Can any one please give some idea that Is u-boot is responisible to get virtual memory map for kernel zImage ? and How we can enable MMU in u-boot-1.1.2 for arm926ejs target cpu ? Regards Pankaj

2 1