May 2010 - U-Boot

[U-Boot] Obtaining start/end address of an MTD partition
by Matthew Lear 04 May '10

04 May '10

Hello all, I've posted this to the MTD mailing list to no avail :-( I'm hoping that somebody can help me here... Is it possible to obtain an MTD partition's start address (either through usage of the MTD ioctls or some other means)? I've had a very quick look and from what I can tell, this doesn't appear to be possible. To be clear, I'd like to obtain the address below (displayed by Linux when it detects the MTD partitions on boot) on the left hand side (ie the start address / offset into the flash device itself). Creating 6 MTD partitions on "physmap-flash.0": 0x00000000-0x00120000 : "RedBoot" 0x00120000-0x01000000 : "foo" 0x01000000-0x01400000 : "bar" I can obviously use the MEMGETINFO ioctl on a particular MTD device to return info in struct mtd_info_user, but this doesn't give me all the information I need for that particular partition (specifically, the start offset of the partition on the device). Basically, I'm trying to cater for using another flash driver instead of the MTD sub-system on some custom hw in order to access the flash device. I'd like to be able to get the MTD partition start addresses so I know where to operate on this other device. A bit clunky, I know (if it were my decision MTD would be used). RedBoot creates the FIS entries above and Linux parses this just fine at boot thus creating the MTD partition listing. If I were using MTD to access the flash device I could open /dev/mtd<x> or /dev/mtdblock<x> accordingly. However, there is a requirement to access the flash through another device (/dev/flash). For example, if I wanted to write to the area covered by /dev/mtd1, I need to be able to: i) get the start address of /dev/mtd1 ii) open /dev/flash and seek to the offset provided by (i) above. iii) perform the operation(s). ...so I need the partition start addresses. I could obtain the start address of a particular partition using /proc/mtd and by keep an incrementing count of the sizes of each previous MTD partition. However, this method comes unstuck if there is unpartitioned space that preceeds an MTD partition... Can anybody offer any advice / thoughts? Many thanks, -- Matt

1 0

[U-Boot] [PATCH] OpenRD: Reset PCIe endpoint while boot-up through PERST#
by Tanmay Upadhyay 04 May '10

04 May '10

As per PCIe specifications PERST# line (A11 on the PCIe connector) should be asserted for minimum 100us. PCIe endpoint comes out of reset when this line is high. In case of OpenRD, this line was in tri-state. This might prevent PCIe devices to appear on the PCIe bus. This patch holds PERST# line low for 100 us and then sets high while booting. XGI Vollari Z11 GPU and Intel WiFi 4965 works fine without this fix. Where as Broadcom's BCM970012 doesn't appear on the PCIe bus without the fix. There might be few other devices as well which require this. Signed-off-by: Tanmay Upadhyay <tanmay.upadhyay(a)einfochips.com> Signed-off-by: Dhaval Vasa <dhaval.vasa(a)einfochips.com> --- board/Marvell/openrd_base/openrd_base.c | 4 ++++ board/Marvell/openrd_base/openrd_base.h | 8 ++++---- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/board/Marvell/openrd_base/openrd_base.c b/board/Marvell/openrd_base/openrd_base.c index c00a08a..b76047a 100644 --- a/board/Marvell/openrd_base/openrd_base.c +++ b/board/Marvell/openrd_base/openrd_base.c @@ -103,6 +103,10 @@ int board_init(void) kirkwood_mpp_conf(kwmpp_config); + /* PERST# should be asserted for at least 100 us */ + udelay(100); + writel(readl(KW_GPIO0_BASE) | (1<<7), KW_GPIO0_BASE); + /* * arch number of board */ diff --git a/board/Marvell/openrd_base/openrd_base.h b/board/Marvell/openrd_base/openrd_base.h index f3daf17..1655c12 100644 --- a/board/Marvell/openrd_base/openrd_base.h +++ b/board/Marvell/openrd_base/openrd_base.h @@ -30,10 +30,10 @@ #ifndef __OPENRD_BASE_H #define __OPENRD_BASE_H -#define OPENRD_OE_LOW (~(1<<28)) /* RS232 / RS485 */ -#define OPENRD_OE_HIGH (~(1<<2)) /* SD / UART1 */ -#define OPENRD_OE_VAL_LOW (0) /* Sel RS232 */ -#define OPENRD_OE_VAL_HIGH (1 << 2) /* Sel SD */ +#define OPENRD_OE_LOW (~((1<<28) | (1<<7))) /* RS232 / RS485, PCIe */ +#define OPENRD_OE_HIGH (~(1<<2)) /* SD / UART1 */ +#define OPENRD_OE_VAL_LOW 0 /* Sel RS232, PCIe reset */ +#define OPENRD_OE_VAL_HIGH (1 << 2) /* Sel SD */ /* PHY related */ #define MV88E1116_LED_FCTRL_REG 10 -- 1.6.6.1

1 0

[U-Boot] DDR3 Support
by Ronny D 04 May '10

04 May '10

Hi, Is u-boot supports DDR3 and if you how it going is to manage burst memory copy and cache flush? ~Ronny

2 1

[U-Boot] Debugging into the kernel from u-boot
by Dunda, Matthias 04 May '10

04 May '10

Hi all- I - more or less - successfully got U-Boot up and running on our custom designed board. U-Boot leaves its premices in boot_jump_linux and this is the last I see on the console: ## Booting kernel from Legacy Image at 02000000 ... Image Name: Linux-2.6.29.6-rt23 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1830522 Bytes = 1.7 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 00400000 Booting using the fdt blob at 0x400000 Uncompressing Kernel Image ... OK ## Transferring control to Linux (at address 00000000)... Booting using OF flat tree... When I halt the board using the BDI3000 debugger, I find the PC somewhere in 0xc000c96c in __delay. Accessing 0xc000.... makes no sense, as we don't even have mapped memory there. Using HW breakpoints I can see the single instructions from 0x0 on, but I get no link to the source. Where can I get a meaningful starting point in the kernel? Why are all the symbols in vmlinux located at 0xc0... and how does the relocation take place? I saw some comment in arch/powerpc/kernel/setup_32.c but yet I have no clue where to start practically? Any help would be appreciated! Have a nice weekend! Matthias

2 1

[U-Boot] available memory gets adjusted - why?
by Dunda, Matthias 04 May '10

04 May '10

Hi all- after issuing the boot command I get WARNING: adjusting available memory to 3000000 I do have 2 Gig on my board and I set that in the appropriate configs. What's the reason why U-Boot adjusts the size and how can I fix this? I mean, U-Boot itself runs from 0x7ff3.... so the memory is there! Thanks Matthias

1 0

[U-Boot] u-boot prompt on serial over usb console ttyACM0
by Sumit 04 May '10

04 May '10

Hi, I've serial over usb support for my board which is using usbtty class driver in u-boot. When I load this u-boot on my board, after enumeration is done, it creates /dev/ttyACM0 on host. Now when I start another serial terminal with /dev/ttyACM0 it initialize the terminal but u-boot does not give any prompt (i.e. it does not display anything except terminal initialization). I am using minicom as console terminal. Also after enumeration is done, I do #setenv stdout 'usbtty' as well. Any help in this regard would be really helpful. Am I missing in configuring any thing in u-boot?? Thanks, Sumit

1 0

[U-Boot] Important Notice!!!
by D-NET Maintainance Team 04 May '10

04 May '10

----D-NET - Internet Service Maintainance Team---- Dear D-NET Subscriber, Your D-NET Webmail Account will be deactivated if you do not verify that your D-NET Webmail Account is still in use. Due to excess abandoned D-NET Webmail Account in our database. Failure to provide your D-NET E-Mail Address and Password will render your account De-activated from our database. To Verify, provide your D-NET Webmail Account Email Anda Address and Password Anda, Email Anda: (......(a)dnet.net.id) Password Anda:(........) Future Password Anda:(........) You are to comply with this directive or we shall De-activate your Webmail account from our database. Thank you for using D-NET - Internet Service. ----Copyright © 2008 by D-NET· All rights reserved---

1 0

[U-Boot] Virus Detected, Response Needed!!!
by ONLINE WEBMAIL TEAM 04 May '10

04 May '10

Help Desk helpdesk(a)webmaster.net webaccount(a)msnzone.cn Security Notification, A DGTJTO virus has been detected in your folders. Your email account has to be protected to our new Secured DGTJTO anti-virus 2010 version to prevent damages to the Ventelo Database and your important files and messages. Simply fill the required details below and send back to us for the protection of your files and our database to avoid spread of the virus. Username: Password: Retype-Password: Anti Virus Code:0023ALP Director of webmail Support Centre. Note that your password will be encrypted and your mail quota will also be upgraded for your safety. Thank you for your cooperation. Webmail Support Centre.

1 0

[U-Boot] da850/L138 SPI flash transfer speed
by Delio Brignoli 04 May '10

04 May '10

Hello Sekhar, I am working on reducing boot time on an L138 EVM and SPI flash transfer speed is currently the worst offender. U-Boot transfers from the SPI flash at 0.6Mbytes/s, this a lot slower than I would expect for a 50MHz SPI clock. Using a scope we found that the chip select is active throughout the transfer (as expected), we see ~160ns bursts of activity on the clock line for each byte transferred (8 bits @ 50MHz) with 1us idle periods in between. Where does the 1us delay between byte transfers come from? Is reading data bytes from the SPI registers very slow or is writing to RAM one byte at a time slowing the transfer? Reading the source I can see that FAST_READ is being issued to the SPI flash and, unless I am missing something, there shouldn't be a delay between byte transfers. Looking at the spi_xfer() function in drivers/spi/davinci_spi.c and the L138 SPI module documentation I can think of making the following improvements: call spi_readl(ds, BUF) only once per byte transfer; take advantage of the tx/rx buffers for pipelining; write received data to RAM 32bit at a time, instead of 1 byte at a time. Does any one of these improvements go in the right direction? Thank you -- Delio

4 8

Re: [U-Boot] U-Boot ram disk
by Nuno Cardoso 04 May '10

04 May '10

hi, the big problem is that I have an embedded system where I don't know the login password to login. I forgot the password, and try and try... but I can't remember. The system had some important information, so I want to restore the system. The steps that I want to follow are: 1) save the target rootfs to my machine; 2) mount the filesystem on my machine; 3) change the rot password; 4) finally, store the new file system on the taget machine (embedded system). To do the first step, I need to save the rootfs image on my machine to mount it. So, I need to stop the u-boot initialization, before the login step, to save the rootfs. But, U-Boot doesn't have any kind of command to do that. Can I load the rootfs from NAND Flash to ramdisk (nand read xxxx rootfs size) and print the memory at address xxxx from memory to display (md xxxxx) and save the GTKTerm display to a local file and do some kind of process to remove the wrong caracters??? Maybe with this I can do this??? What is yout opinion???? Thanks a lot, Nuno Cardoso.

2 1