January 2006 - U-Boot

[U-Boot-Users] network driver link error
by Xuezhang Dong 14 Jan '06

14 Jan '06

I donot have network support in my board, but when I try to remove the network driver support from my config file, I got the link error.(otherwise everything is fine and I can run the u-boot 1.1.4 without any trouble now). So I want to understand that is it the mandatory to have network support? or I can disable the support of network by using some flag? /* * Hardware drivers */ #define CONFIG_DRIVER_LAN91C96 #define CONFIG_LAN91C96_BASE 0x04000300 #define CONFIG_LAN91C96_EXT_PHY Thanks. Xuezhang.

2 1

[U-Boot-Users] CFI flash – Problem with erasing boot block.
by John_s (sent by Nabble.com) 13 Jan '06

13 Jan '06

Hi All, I am developing a CFI based flash driver. I can query the device and get all sector/block information. I am having problems erasing sectors 1, 2, 3 and 4 (bottom 64-KB), please the flash geometry below. The problem is that when I attempt to erase sectors 1, 2, 3, OR 4 I end up erasing sectors 1-4 . Not sure why this is happening. I am able to erase the remaining sectors, sectors 5 through 19 individually without problems. Here is flash’s geometry. I would appreciate your expert opinion as how to avoid this or even as it why it is happening. Thanks in advance. Device: ST’s M29w800DB, Bottom boot block. Sector 1 0x00000 – 0x01fff Sector 2 0x02000 – 0x02fff Sector 3 0x03000 – 0x03fff Sector 4 0x04000 – 0x07fff -> First 64Kb boundary. Sector 5 0x08000 – 0x07fff -> All remaining sectors are 64 -Kb bulk sectors. …………………………………. Sector 19 0x78000 – 0x7ffff - John -- View this message in context: http://www.nabble.com/CFI-flash-Problem-with-erasing-boot-block.-t911704.ht… Sent from the Uboot - Users forum at Nabble.com.

2 1

[U-Boot-Users] MC9328MXL/1 SDRAM initialization
by llandre 13 Jan '06

13 Jan '06

I have a question about how MC9328MXL/1 initializes SDRAM memories. These is the instructions used to set up the Mode Command Register (file board/mx1ads/lowlevel_init.S) for MX1ADS evalutaion board: /* Issue Mode Register Command */ ldr r3, =0x08111800 /* Mode Register Value */ ldr r2, [r3] In my understanding address lines are connected as follows: SDRAM -> MC9328MXL ------------------- A12 -> A13 A11 -> A12 A10 -> MA11 A9 -> MA10 A8 -> A10 A7 -> A9 A6 -> A8 A5 -> A7 A4 -> A6 A2 -> A5 A1 -> A3 A0 -> A2 Thus, when writing to address 0x08111800, microprocessor address lines from A8 to A6 are set to 0. It implies that SDRAM address lines from A6 to A4 are set to 0. These lines are decoded by the SDRAM chips as CAS latency. Allowed values are 010 (CAS latency = 2) and 011 (CAS latency = 3). The value 000 is reserved. So I think I'm misunderstanding how the SDRAM controller works. Anybody can help me? Thanks in advance, llandre DAVE Electronics System House - R&D Department web: http://www.dave-tech.it email: r&d2(a)dave-tech.it

2 2

[U-Boot-Users] how to generate uImage of ramdisk.gz for mips arch?
by zhuzhenhua 13 Jan '06

13 Jan '06

what the -a and -e should be for ramdisk.gz i see in kernel image, the -a means where kernel to load and -e means kernel entry but i am not sure what -a and -e mean for ramdisk.gz, are they always be 0x0? thanks for any hints Best reagards zhuzhenhua

2 1

[U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

Hi, all I have a board with arm926 big-endian, serial port, NOR/SRAM. I used omap 1610H2 as my code base since the cpu type is same. Problem is that the printf() function doesnot work, for example: printf("\n%s\n", uboot_version); instead of print the real string, it give me the "%s" as is. So I want to know it is a big-edian problem or ..., any clue will be appreciated. Thanks. Xuezhang.

3 3

[U-Boot-Users] Excluding Env Variable section from the u-boot.bin
by Albert David 13 Jan '06

13 Jan '06

Dears, For my ppc405EP based custom board I would like to make few changes to the u-boot memory map, so that every time I update the u-boot, environment variables in the flash remain untouched. Flash Memory used:S29GL128M(spansion 16MB Flash with 128 uniform sectors of 128KB each) Current mapping U-Boot Start Flash Address 0xFFF60000 - 2 sectors U-Bot Env Variable Start Addr 0xFFFA000 - 1 sector U-Bot Env Variable(Redundant)Start Addr 0xFFFC000 - 1 sector U-Boot End sector - 1 sector Size of the binary output of u-boot(u-boot.bin) after build is 128kb*5sectors=648Kbytes. Current settings in the source tree: U-boot-1.1.4/include/configs/my_board.h #define CFG_FLASH_BASE 0xFFF60000 #define CFG_MONITOR_BASE CFG_FLASH_BASE #define CFG_MONITOR_LEN (640 * 1024) #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFFA0000 #define CFG_ENV_SECT_SIZE 0x20000 #define CFG_ENV_ADDR_REDUND 0xFFFC0000 #define CFG_ENV_SIZE_REDUND 0x20000 U-boot-1.1.4/my_board/config.mk TEXT_BASE = 0xFFF60000 U-boot-1.1.4/my_board/u-boot.lds ppcenv_assert = ASSERT(. < 0xFFFA0000, ".bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified."); . = 0xFFFA0000; .ppcenv : { common/environment.o(.ppcenv); } Required mapping: U-Bot Env Variable Start Addr 0xFFF8000 - 1 sector U-Bot Env Variable(Redundant)Start Addr 0xFFFA000 - 1 sector U-Boot Start Flash Address 0xFFFC0000 - 2 sectors Required Size of the binary output of u-boot(u-boot.bin) after build is 128kb*2sectors=256Kbytes. I have already tried to modify the above specified files to: U-boot-1.1.4/include/configs/my_board.h #define CFG_FLASH_BASE 0xFFFC0000 #define CFG_MONITOR_BASE CFG_FLASH_BASE #define CFG_MONITOR_LEN (256 * 1024) #define CFG_ENV_IS_IN_FLASH 1 #define CFG_ENV_ADDR 0xFFF80000 #define CFG_ENV_SECT_SIZE 0x20000 #define CFG_ENV_ADDR_REDUND 0xFFFA0000 #define CFG_ENV_SIZE_REDUND 0x20000 U-boot-1.1.4/my_board/config.mk TEXT_BASE = 0xFFFC0000 U-boot-1.1.4/my_board/u-boot.lds ppcenv_assert = ASSERT(. < 0xFFF80000, ".bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified."); . = 0xFFF80000; .ppcenv : { common/environment.o(.ppcenv); } But after doing "make all" I get the message ppc_4xx-ld:.bss section too big, overlaps .ppcenv section. Please update your confguration: CFG_MONITOR_BASE, CFG_MONITOR_LEN and TEXT_BASE may need to be modified. In a simple term, I wanted to build my u-boot by excluding environment variable section of the memory.. Can any one help me? Where am I going wrong?? Is there any other modification needs to be done other than the above specified changes? Thanks in advance for your support, With best regards, Albert.

3 4

RE: [U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

I figure out this problem, it is due to the code in start.S set up Align, so the data read from 16-bit-bus throught ldrb will revert in big-endian case, and OMAP is little-endian, so they are OK. cpu_init_crit: /* * flush v4 I/D caches */ mov r0, #0 mcr p15, 0, r0, c7, c7, 0 /* flush v3/v4 cache */ mcr p15, 0, r0, c8, c7, 0 /* flush v4 TLB */ /* * disable MMU stuff and caches */ mrc p15, 0, r0, c1, c0, 0 bic r0, r0, #0x00002300 /* clear bits 13, 9:8 (--V- --RS) */ bic r0, r0, #0x00000087 /* clear bits 7, 2:0 (B--- -CAM) */ orr r0, r0, #0x00000002 /* set bit 2 (A) Align */ orr r0, r0, #0x00001000 /* set bit 12 (I) I-Cache */ mcr p15, 0, r0, c1, c0, 0 /* * Go setup Memory and board specific bits prior to relocation. */ mov ip, lr /* perserve link reg across call */ bl platformsetup /* go setup pll,mux,memory */ mov lr, ip /* restore link */ mov pc, lr /* back to my caller */ I was debugging the ns16550 (serial driver), and find out that my serial port is not logically as same as theirs. I was assume that UART is very standard, is it true? Any suggestion of other serial drive I can try? Regards. Xuezhang. -----Original Message----- From: wd(a)denx.de [mailto:wd@denx.de] Sent: Thursday, January 12, 2006 5:04 PM To: Xuezhang Dong Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] board porting question In message <54AD0F12E08D1541B826BE97C98F99F11C29CE(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > Thanks for the reply and my appology for the HTML format, I thought > mail server will convert it. Never mind, it wonot happened again. Thanks. > I was using the latest toolchain from snapgear: > ARM/XSCALE - arm-linux-tools-20051123.tar.gz > > And I supplied the compiler with -mbigarm parameter. > > Any idea how I can verify/debug this problem? Attach your BDI2000 and fire up GDB? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de Microsoft Multimedia: You have nice graphics, sound and animations when the system crashes.

1 0

[U-Boot-Users] board porting question
by Xuezhang Dong 13 Jan '06

13 Jan '06

Thanks for the reply and my appology for the HTML format, I thought mail server will convert it. Never mind, it wonot happened again. I was using the latest toolchain from snapgear: ARM/XSCALE - arm-linux-tools-20051123.tar.gz And I supplied the compiler with -mbigarm parameter. Any idea how I can verify/debug this problem? Thanks. Xuezhang. In message <54AD0F12E08D1541B826BE97C98F99F11C29B3(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > > I have a board with arm926 big-endian, serial port, NOR/SRAM. I used > omap 1610H2 as my code base since the cpu type is same. Problem is > that the printf() function doesnot work, for example: > printf("\n%s\n", uboot_version); instead of print the real string, it > give me the "%s" as is. > So I want to know it is a big-edian problem or ..., any clue will be > appreciated. I can only speculate here. Eventually this is a toolchain problem (printf() being a variable argument list function and thus sensible against problems with parameter passing). > Content-Type: text/html; > charset=us-ascii > Content-Transfer-Encoding: quoted-printable And will you please stop posting HTML here??? I am *seriously* considering the option to move this list from SF and reject all messages that contain HTML (or even base64) encoded messages!!! Best regards, Wolfgang Denk

2 1

RE: [U-Boot-Users] board porting question
by Xuezhang Dong 12 Jan '06

12 Jan '06

Again this is the screen print out looks like: %s U-Boot code: lFsa:hB%** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB%** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn %s sU-Boot code: BlFsa:hB** *aWnrni g -ab dRC,Cu isgnd feuatle vnrinoemtn Regards. Xuezhang. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Xuezhang Dong Sent: Thursday, January 12, 2006 2:31 PM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] board porting question Thanks for the reply and my appology for the HTML format, I thought mail server will convert it. Never mind, it wonot happened again. I was using the latest toolchain from snapgear: ARM/XSCALE - arm-linux-tools-20051123.tar.gz And I supplied the compiler with -mbigarm parameter. Any idea how I can verify/debug this problem? Thanks. Xuezhang. In message <54AD0F12E08D1541B826BE97C98F99F11C29B3(a)NT-SJCA-0751.brcm.ad.broadcom.co m> you wrote: > > I have a board with arm926 big-endian, serial port, NOR/SRAM. I used > omap 1610H2 as my code base since the cpu type is same. Problem is > that the printf() function doesnot work, for example: > printf("\n%s\n", uboot_version); instead of print the real string, it > give me the "%s" as is. > So I want to know it is a big-edian problem or ..., any clue will be > appreciated. I can only speculate here. Eventually this is a toolchain problem (printf() being a variable argument list function and thus sensible against problems with parameter passing). > Content-Type: text/html; > charset=us-ascii > Content-Transfer-Encoding: quoted-printable And will you please stop posting HTML here??? I am *seriously* considering the option to move this list from SF and reject all messages that contain HTML (or even base64) encoded messages!!! Best regards, Wolfgang Denk ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=ick _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] Re: Problem with the cfi flash driver with a x8/x16 flash configuredin x8 mode.
by Alex BASTOS 12 Jan '06

12 Jan '06

Txema, > Does anybody test the cfi flash driver (cfi_flash.c) with a x8/x16 > flash configured in x8 mode ? I'm trying to port U-Boot for a Lite5200B > with a S29GL128N flash (CFI compliant) using the cfi flash driver. > U-Boot detects the flash correctly but It's unable to erase or write the > flash. In my case the following patch fix the bug but I'm not completly > sure If It's only a bug with my configuration. Any suggestions? Could > anybody test the patch in other architecture? I think your topic is very similar to this recent one: http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/19970 and previous similar patches have been submited and are still pending (but it seems they are coming, read the whole thread) So, yes, til now cfi_flash didn't support x8 mode for AMD chips, but it will. Best regards, Alex BASTOS

1 0