March 2009 - U-Boot

[U-Boot] Coldfire: MCF5271: Periodic HW watchdog petting and sleep function does not work.
by Richard Retanubun 04 Mar '09

04 Mar '09

Hi Guys, I am using u-boot 2009.03-rc1 and a board based on Coldfire MC5271EVB eval platform. Our external watchdog is a MAX6369. I have #define CONFIG_HW_WATCHDOG and #undef CONFIG_WATCHDOG in our board's config file and have created the hw_watchdog_reset function to toggle the WDI line to pet the watchdog. However, my board keeps resetting at the watchdog timeout. Upon probing, I found out that the watchdog toggle line in not being toggled periodically by u-boot. Which means a regular call to WATCHDOG_RESET() is not happening. If I execute commands, the WDI will get toggled and the watchdog will not timeout, which means that the WATCHDOG_RESET() mapping to hw_watchdog_reset function is working, it is just not being called periodically. I am looking at the programmable interrupt timer that the get_timer() function uses, and so far everything checks out. I'm also stuck at using u-boot's sleep command, e.g. "sleep 1" will never return. Which I suspect may be the same root cause. (this can also be observed on the M5271EVB board). What am I missing here? Thank you for all your time. Regards, - Richard Retanubun.

2 2

[U-Boot] How to Remove the padding bits from u-boot.bin
by kuldeep nigam 04 Mar '09

04 Mar '09

Hi All, I am using MIP405T board and trying to reduce the size of u-boot.bin by disabling the drivers that i didn't need. But the image size is not changing because it is padding all 1's at the end of the image. Can anyone tell me how to remove these padding bits. Image size is 512 K Actual image size is 207 K (approx.) u-boot version is 1.3.2 Hexdump of u-boot.bin is as follows: 00337d0 0000 0200 0000 0100 f9ff a8d0 faff 78f8 00337e0 faff 90f8 faff acf8 0000 1000 0000 0100 00337f0 f9ff 68ce faff b4f8 faff d4f8 faff 04fa 0033800 0000 1000 0000 0100 f9ff 68ce faff 08fa 0033810 0000 0000 ffff ffff ffff ffff ffff ffff 0033820 ffff ffff ffff ffff ffff ffff ffff ffff * 007fff0 ffff ffff ffff ffff ffff ffff f84b 0421 0080000 with regards, kuldeep nigam

3 2

[U-Boot] Vector set up in u-boot for OMAP3530.
by Rahanesh 04 Mar '09

04 Mar '09

Hi All, I am trying to port a RTOS to OMAP3530 board. I use CCSv4 and XDS510 PP + JTAG emulator to connect to the board. I am trying to set up vector table for a my custom RTOS. ARM provides 0x0000:0000 and 0xFFFF:0000 as the Vector base address. I planned to use 0x0000:0000 for my development. I have decided to hard-code the opcode for the corresponding branches to the loactions respectively.(0x00000000 to 0x0000001C) When i write to 0x00000000 location , i get a prefetch abort exception. Why am i not able to write to 0x00000000? How did U boot handle this? How did U boot set up Vector table? Can anyone help me please? Regards Rahanesh The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.

2 1

[U-Boot] [PATCH 1/1] Fix for running examples on OMAP3 EVM board
by Manikandan Pillai 04 Mar '09

04 Mar '09

Example binaries to be downloaded to 0x80300000 for OMAP3 EVMs. Signed-off-by: Manikandan Pillai <mani.pillai(a)ti.com> --- examples/Makefile | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/examples/Makefile b/examples/Makefile index dbcfa92..75e6c87 100644 --- a/examples/Makefile +++ b/examples/Makefile @@ -36,10 +36,14 @@ else ifeq ($(CPU),omap3) LOAD_ADDR = 0x80300000 else +ifeq ($(CPU),arm_cortexa8) +LOAD_ADDR = 0x80300000 +else LOAD_ADDR = 0xc100000 endif endif endif +endif ifeq ($(ARCH),mips) LOAD_ADDR = 0x80200000 -T mips.lds -- 1.5.6

5 6

[U-Boot] Watchdog timer and booting in Linux kernel
by Sachin Rane 04 Mar '09

04 Mar '09

Hi, I am using u-boot and linux kernel on our custom PPC440gx board. The board was booting without any issue. The board started rebooting while booting in linux kernel after enabled the watchdog timer in u-boot by defining 'CONFIG_WATCHDOG'. I have observed that the board gets reset while booting in Linux. I followed the discussion available on: http://osdir.com/ml/boot-loaders.u-boot/2001-07/msg00121.html I modified the code given in above link to run it on ppc440gx processor. I have written a function 'reset_watchdog()' in kernel which will reset the Watchdog Timer (same as available in u-boot) and called in 'timer_interrupt()' of /arch/ppc/kernel/time.c' But the function is not giving any effect. The board is still getting rebooted. 8<-------------------------arch/ppc/kernel/time.c ------------------------------------ unsigned long sched_watchdog_counter = 0; void reset_watchdog() { unsigned long val = 0; char buff[20]; local_irq_disable(); val = mfspr(0x150); mtspr(0x150, !(val) | 0x40000000); val = mfspr(0x150); sprintf(buff,"val = %x\n",val); local_irq_enable(); } void timer_interrupt(struct pt_regs * regs) { : : : reset_watchdog(); irq_exit(); } 8<-------------------------arch/ppc/kernel/time.c ------------------------------------ Can you help me to boot the board in Linux kernel with watchdog enabled in u-boot? Regards, Sachin

2 4

[U-Boot] FW: U-Boot hangs after loading device tree
by Afzal Nadirshah 04 Mar '09

04 Mar '09

Hi Pieter, Thanks for your suggestion. I guess its halting at the point where u-boot is handing over to the Linux kernel image. For doing the post mortem analysis, I am not able to obtain the virtual address of the log_buf. grep log_buf System.map or grep __log_buf System.map doesn't give nay output. Sorry for the double post. Regards, Afzal Nadirshah -----Original Message----- From: Pieter [mailto:phenning@vastech.co.za] Sent: Monday, March 02, 2009 4:24 PM To: Afzal Nadirshah Subject: Re: [U-Boot] U-Boot hangs after loading device tree Afzal Nadirshah wrote: > Hi, > I am trying to bring linux up on our custom board, by loading the kernel.img , canynlands.dtb and Ramdisk onto the RAM using the serial port. > However the boot process is getting hung. The boot boot process stops after the following messages : > > > => run flash_self > ## Booting kernel from Legacy Image at 1c000000 ... > Image Name: Linux-2.6.25.7-00002-geaaf8db > Created: 2008-06-30 13:53:11 UTC > Image Type: PowerPC Linux Kernel Image (gzip compressed) > Data Size: 1547704 Bytes = 1.5 MB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 1c200000 ... > Image Name: Simple Embedded Linux Framework > Created: 2002-10-24 9:30:38 UTC > Image Type: PowerPC Linux RAMDisk Image (gzip compressed) > Data Size: 1476478 Bytes = 1.4 MB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 1c1e0000 > Booting using the fdt blob at 0x1c1e0000 > Uncompressing Kernel Image ... OK > Loading Ramdisk to 1fc78000, end 1fde077e ... OK > Loading Device Tree to 007f9000, end 007ff0b4 ... OK > > > I have changed the kernel_addr, fdt_addr and the ramdisk_addr to the RAM addresses. > This is the output of the printenv command : > > > => printenv > bootdelay=5 > baudrate=115200 > loads_echo= > preboot=echo;echo Type "run flash_nfs" to mount root filesystem over NFS;echo > hostname=canyonlands > netdev=eth0 > nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} > ramargs=setenv bootargs root=/dev/ram rw > addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}1 > addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} > addmisc=setenv bootargs ${bootargs} > initrd_high=30000000 > kernel_addr_r=400000 > fdt_addr_r=800000 > ramdisk_addr_r=C00000 > hostname=canyonlands > bootfile=canyonlands/uImage > ramdisk_file=canyonlands/uRamdisk > rootpath=/opt/eldk/ppc_4xxFP > flash_self=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > flash_nfs=run nfsargs addip addtty addmisc;bootm ${kernel_addr} - ${fdt_addr} > net_nfs=tftp ${kernel_addr_r} ${bootfile}; tftp ${fdt_addr_r} ${fdt_file}; run nfsargs addip a} > net_self_load=tftp ${kernel_addr_r} ${bootfile};tftp ${fdt_addr_r} ${fdt_file};tftp ${ramdisk_; > net_self=run net_self_load;run ramargs addip addtty addmisc;bootm ${kernel_addr_r} ${ramdisk_a} > fdt_file=canyonlands/canyonlands.dtb > load=tftp 200000 canyonlands/u-boot.bin > update=protect off 0x01000000 FFFFFFFF;era 0x01000000 FFFFFFFF;cp.b ${fileaddr} 0x01000000 ${fv > upd=run load update > nload=tftp 200000 canyonlands/u-boot-nand.bin > nupdate=nand erase 0 100000;nand write 200000 0 100000;setenv filesize;saveenv > nupd=run nload nupdate > pciconfighost=1 > pcie_mode=RP:RP > fdt_addr=1c1e0000 > ramdisk_addr=1c200000 > ram_root=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > ram_ws=1C000000 > kernel_addr=1c000000 > stdin=serial > stdout=serial > stderr=serial > ver=U-Boot 2009.01 (Feb 25 2009 - 15:12:15) > bootcmd=run flash_self > bootargs=root=/dev/ram rw ip=::::canyonlands:eth0:off panic=1 console=ttyS0,115200 > filesize=1687BE > > Have anybody faced a similar problem? > I recently had a similar problem - the solution was a combination of DTS tweaks and U-Boot defines for my board. have a look at the post mortem debugging and recheck all your defines. <http://www.denx.de/wiki/view/DULG/LinuxPostMortemAnalysis> or search the mailing list for my postings: [U-Boot] Custom MPC8548 boot using FDT problem cheers pieter http://www.mindtree.com/email/disclaimer.html

2 1

Re: [U-Boot] U-Boot hangs after loading device tree
by Afzal Nadirshah 04 Mar '09

04 Mar '09

Hi Pieter, Thanks for your suggestion. I guess its halting at the point where u-boot is handing over to the Linux kernel image. For doing the post mortem analysis, I am not able to obtain the address of the virtual Regards, Afzal Nadirshah -----Original Message----- From: Pieter [mailto:phenning@vastech.co.za] Sent: Monday, March 02, 2009 4:24 PM To: Afzal Nadirshah Subject: Re: [U-Boot] U-Boot hangs after loading device tree Afzal Nadirshah wrote: > Hi, > I am trying to bring linux up on our custom board, by loading the kernel.img , canynlands.dtb and Ramdisk onto the RAM using the serial port. > However the boot process is getting hung. The boot boot process stops after the following messages : > > > => run flash_self > ## Booting kernel from Legacy Image at 1c000000 ... > Image Name: Linux-2.6.25.7-00002-geaaf8db > Created: 2008-06-30 13:53:11 UTC > Image Type: PowerPC Linux Kernel Image (gzip compressed) > Data Size: 1547704 Bytes = 1.5 MB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at 1c200000 ... > Image Name: Simple Embedded Linux Framework > Created: 2002-10-24 9:30:38 UTC > Image Type: PowerPC Linux RAMDisk Image (gzip compressed) > Data Size: 1476478 Bytes = 1.4 MB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 1c1e0000 > Booting using the fdt blob at 0x1c1e0000 > Uncompressing Kernel Image ... OK > Loading Ramdisk to 1fc78000, end 1fde077e ... OK > Loading Device Tree to 007f9000, end 007ff0b4 ... OK > > > I have changed the kernel_addr, fdt_addr and the ramdisk_addr to the RAM addresses. > This is the output of the printenv command : > > > => printenv > bootdelay=5 > baudrate=115200 > loads_echo= > preboot=echo;echo Type "run flash_nfs" to mount root filesystem over NFS;echo > hostname=canyonlands > netdev=eth0 > nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} > ramargs=setenv bootargs root=/dev/ram rw > addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}1 > addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} > addmisc=setenv bootargs ${bootargs} > initrd_high=30000000 > kernel_addr_r=400000 > fdt_addr_r=800000 > ramdisk_addr_r=C00000 > hostname=canyonlands > bootfile=canyonlands/uImage > ramdisk_file=canyonlands/uRamdisk > rootpath=/opt/eldk/ppc_4xxFP > flash_self=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > flash_nfs=run nfsargs addip addtty addmisc;bootm ${kernel_addr} - ${fdt_addr} > net_nfs=tftp ${kernel_addr_r} ${bootfile}; tftp ${fdt_addr_r} ${fdt_file}; run nfsargs addip a} > net_self_load=tftp ${kernel_addr_r} ${bootfile};tftp ${fdt_addr_r} ${fdt_file};tftp ${ramdisk_; > net_self=run net_self_load;run ramargs addip addtty addmisc;bootm ${kernel_addr_r} ${ramdisk_a} > fdt_file=canyonlands/canyonlands.dtb > load=tftp 200000 canyonlands/u-boot.bin > update=protect off 0x01000000 FFFFFFFF;era 0x01000000 FFFFFFFF;cp.b ${fileaddr} 0x01000000 ${fv > upd=run load update > nload=tftp 200000 canyonlands/u-boot-nand.bin > nupdate=nand erase 0 100000;nand write 200000 0 100000;setenv filesize;saveenv > nupd=run nload nupdate > pciconfighost=1 > pcie_mode=RP:RP > fdt_addr=1c1e0000 > ramdisk_addr=1c200000 > ram_root=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > ram_ws=1C000000 > kernel_addr=1c000000 > stdin=serial > stdout=serial > stderr=serial > ver=U-Boot 2009.01 (Feb 25 2009 - 15:12:15) > bootcmd=run flash_self > bootargs=root=/dev/ram rw ip=::::canyonlands:eth0:off panic=1 console=ttyS0,115200 > filesize=1687BE > > Have anybody faced a similar problem? > I recently had a similar problem - the solution was a combination of DTS tweaks and U-Boot defines for my board. have a look at the post mortem debugging and recheck all your defines. <http://www.denx.de/wiki/view/DULG/LinuxPostMortemAnalysis> or search the mailing list for my postings: [U-Boot] Custom MPC8548 boot using FDT problem cheers pieter http://www.mindtree.com/email/disclaimer.html

1 0

[U-Boot] AT91SAM926x Nor Boot
by Jens Scharsig 04 Mar '09

04 Mar '09

Hello, I'm start with a port for a new customer board with NOR-flash only. Our customer don't like use AT91Bootstrap. I look at the source, but don't found any initialization code for AT91SAM926x. My question: Are there any plans or patches which support to use u-boot without AT91Bootstrap? or Should I do this by myself? Best regards J. Scharsig

4 4

[U-Boot] Uboot NAND sub system and it's commands
by Swapnali C. Patil 04 Mar '09

04 Mar '09

Hello All, I am using DM6446 (TI DaVinci) customized board. 1. I am not able to understand meaning of NAND Sub system U boot commands, e.g. nand write, nand read, nand erase etc. 2. I want to use the NAND sub system U boot command in Linux (ARM side of DM6446 core), is it possible ? may be some utiliy to export these commands or some paralle command which have similar functionality (such as writting on specific location of RAM (87000000) from nand(0X1000000)).? Thanks in advance -swapnali Thanks and regards -swapnali

2 2

[U-Boot] U-boot with SMSC LAN8700
by Louis Ruch 04 Mar '09

04 Mar '09

Hello all, We have developed a board based on the Freescale MPC8315E-RDB. We have made some changes to the board in order to cut costs, and one of the changes made was to replace the standard Ethernet chip with the SMSC LAN8700 chip. We are able to start up the board and get it to launch u-boot: "=>" However once in the u-boot command line we are unable to perform any network functions. Ping fails as well as the tftp command to get our linux image acrross to the board. >From what we can tell it should not be a problem and all we need to do is enable RMII support for the uboot and it should detect the chip. Is this correct? If it is how do we go about enabling RMII support for the device, and is there anything else we need to do in order to get this chip supported by the u-boot? We compiled our version of u-boot by using the LTIB software that came with the MPC8315E-RDB BSP which automatically generated our u-boot version. Regards, Louis

2 1