June 2007 - U-Boot

[U-Boot-Users] a problem of rtl8019.c
by buaafree 20 Jun '07

20 Jun '07

Hi,all I have a board with cpu-s3c2410,eth controller-realtek8019as.I found the function nic_to_pc() in ~/u-boot-1.2.0/drivers/rtl8019.c with a mistake.If using the following way rec_head_status = get_reg (RTL8019_DMA_DATA); next_packet_pointer = get_reg (RTL8019_DMA_DATA); packet_length0 = get_reg (RTL8019_DMA_DATA); packet_length1 = get_reg (RTL8019_DMA_DATA); for reading receive buffer,the four variable of "rec_head_status next_packet_pointer packet_length0 packet_length1" can't get correct value.But if reading the four bytes by using one array to store,it's ok.In other words,it's wrong,if storing every byte in an individual variable. Who can tell me why? Thanks! Darren buaafree 2007-06-20

1 0

Re: [U-Boot-Users] Intel Strata Flash Embedded Memory (P33) on a MPC8xx board with u-boot 1.2.0
by SETTE AGOSTINO - technolabs 20 Jun '07

20 Jun '07

Hi All, Finally I have a U-Boot 1.2.0 for Intel StrataFlash 28F128P33B and I made some modification to the source files, for example I added the Device IDs for all P33 into the file include/flash.h but I am not sure it is enough but anyway here are the differences diff include/flash.h ../u-boot-1.2.0/include/flash.h 295,300d294 < #define INTEL_ID_28F64P33T 0x881D881D /* 64M = 32K x 255 + 32k x 4 */ < #define INTEL_ID_28F64P33B 0x88208820 /* 64M = 32K x 255 + 32k x 4 */ < #define INTEL_ID_28F128P33T 0x881E881E /* 128M = 64K x 255 + 32k x 4 */ < #define INTEL_ID_28F128P33B 0x88218821 /* 128M = 64K x 255 + 32k x 4 */ < #define INTEL_ID_28F256P33T 0x881F881F /* 256M = 128K x 255 + 32k x 4 */ < #define INTEL_ID_28F256P33B 0x88228822 /* 256M = 128K x 255 + 32k x 4 */ Furthermore I removed the following lines from the file common/cmd_bootm.c #ifdef CONFIG_OF_FLAT_TREE "\tWhen booting a Linux kernel which requires a flat device-tree\n" "\ta third argument is required which is the address of the of the\n" "\tdevice-tree blob. To boot that kernel without an initrd image,\n" "\tuse a '-' for the second argument. If you do not pass a third\n" "\ta bd_info struct will be passed instead\n" #endif I have not defined the CONFIG_FLAT_OF_TREE but I have the following errors at compile time. ppc_8xx-gcc -g -Os -fPIC -ffixed-r14 -meabi -fno-strict-aliasing -D__KERNEL__ -DTEXT_BASE=0x40000000 -I/u-boot-1.2.0/include -fno-builtin -ffreestanding -nostdinc -isystem /eldk_1.0/usr/lib/gcc-lib/ppc-linux/2.95.3/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8xx -ffixed-r2 -ffixed-r29 -mstring -mcpu=860 -msoft-float -Wall -Wstrict-prototypes -c -o cmd_bootm.o cmd_bootm.c cmd_bootm.c:477: warning: preprocessing directive not recognized within macro arg cmd_bootm.c:477: warning: preprocessing directive not recognized within macro arg cmd_bootm.c:469: undefined or invalid # directive cmd_bootm.c:475: undefined or invalid # directive cmd_bootm.c:519: warning: `noinline' attribute directive ignored make[1]: *** [cmd_bootm.o] Error 1 make[1]: Leaving directory `/u-boot-1.2.0/common' make: *** [common/libcommon.a] Error 2 Could it depend from the very old eldk? Thanks Ciao Agostino -----Original Message----- From: SETTE AGOSTINO - technolabs Sent: mercoledì 13 giugno 2007 8.40 To: 'Tolunay Orkun' Cc: u-boot-users(a)lists.sourceforge.net Subject: RE: [U-Boot-Users] Intel Strata Flash Embedded Memory (P33) on a MPC8xx board with u-boot 1.2.0 Hello Tolunay, First of all thanks for your answer. I must confess you that I had that in mind, but I would like to have another opinion on it. Anyway, I am using word mode if you mean the CS to access the FLASH and BDI2000 config files BUSWIDTH 16. What I want to do now is to compare the .bin file and what is writter on the FLASH with BDI2000. -----Original Message----- From: Tolunay Orkun [mailto:listmember@orkun.us] Sent: mercoledì 13 giugno 2007 0.09 To: SETTE AGOSTINO - technolabs Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] Intel Strata Flash Embedded Memory (P33) on a MPC8xx board with u-boot 1.2.0 SETTE AGOSTINO - technolabs wrote: > Hello all, > > I'm working with u-boot 1.2.0 on a board with MPC8xx processor and > Intel Strata Flash Embedded Memory (I28F128P33B) mounted. > Up to now I am trying to read the Device Identifier Information with the > Abatron BDI2000 but I am a little bit confused. > In fact I have the following output on the display > > NEW_CCM_LC>mdh 0x40000000 > 40000000 : 0089 8821 0001 0001 0089 bfcf 0001 0001 ...!............ > 40000010 : 0089 8821 0001 0001 0089 bfcf 0001 0001 ...!............ > 40000020 : 0051 0052 0059 0001 0000 000a 0001 0000 .Q.R.Y.......... > 40000030 : 0000 0000 0000 0023 0036 0085 0095 0008 .......#.6...... > 40000040 : 0009 000a 0000 0001 0001 0002 0000 0018 ................ > 40000050 : 0001 0000 0006 0000 0002 0003 0000 0080 ................ > 40000060 : 0000 007e 0000 0000 0002 0000 0000 0000 ...~............ > > On the Intel Strata Flash Embedded Memory (P33) is written that at > offset 0x10 I should find thw CFI Query identification string but, > As you can see, I have them at offset 0x20. > You are using word mode. Offsets differ between word and byte modes. Read the data sheet more carefully.. > Anyway, after the unlock of the flash and the erasing I tried to load a > u-boot 1.2.0 generated for the board and was loaded correctly > (I read back the u-boot label at the beginning of the flash). > If after verifying the data using BDI command it checks OK you programed your flash OK. > The problem is that it doesn't start. > Does anyone know if there is a u-boot code available to manage this kind > of flash? > Programming the flash does not mean that you have a fully functional hardware. It also does not mean that U-Boot is correctly configured and implemented for your board. Anything can go wrong and your code will not boot. Tolunay

1 0

Re: [U-Boot-Users] U-Boot-Users Digest, Vol 13, Issue 65
by Vaibhav Hiremath 20 Jun '07

20 Jun '07

Hi, I am facing problem with serial console baudrate. Below is my procedure - 1. Boot the U-Boot booloader, and come to the uboot prompt. 2. configure the envirnment variable with command => setenv baudrate 9600 3. This displays message ## Switch baudrate to 9600 bps and press ENTER ... But after configuring console to 9600 shell doesn't come. Borad freezes. can anyone help me out in this? Thanks in advance. Thanks, Vaibhav

1 0

[U-Boot-Users] Can a BDI2K be used with a bare/erased 834x based system?
by Bruce_Leonard＠selinc.com 20 Jun '07

20 Jun '07

We're getting our custom HW in about a month and my HW designer came across something in the PowerQUICC Design Checklist that we hadn't considered. (BTW, our board is based around the MPC8347.) The following is a direct quote from the Checklist: "There may be issues with you usa a JTAG-based in-circuit emulator to boot the PowerQUICC Pro II device as reset configuration words are sourced from an unprogrammed Flash device on the local bus. There is no valid RCW already present in Flash memory when the PowerQUICC II Pro device performs the \PORESET sequence. The CPU core is disabled and the in-circuit emulator cannot take conrtol of the CPU." It never occured to me that this may be an issue as this is the first processor I've brought up that didn't get it's reset state from processor pins. I had planned on using the BDI2K to do the flash programming on our prototypes, but if I can't get the BDI2K to take control of the the processor I can't do the programming. Not a big deal, we have alternatives that we've thought of, but I'm curious about the "RCW" line in the configuration file. The BDI2K manual states the following for the RCW: "When this line is present, the BDI overrides the Reset Configuration Words with the values provided." Does anyone know if this means the BDI can override the RCW before the processor performs the \PORESET sequence? In other words, if I have and RCW line in the BDI configuration file, will it be able to provide RCW values to the proc essor when there are none present in the flash, and allow the \PORESET sequence to complete normally? Thanks for any feedback. Bruce

5 7

[U-Boot-Users] Exception occurs while uncompressing linux kernel
by Farrah Rashid 20 Jun '07

20 Jun '07

Sometimes while uncompressing the kernel image (gunzip), an illegal instruction program exception occurs. U-boot displays the registers, reboots, and usually doesn't have any problems loading the kernel. I'm having a hard time debugging the cause since the problem is intermittent. Has anyone experienced this? Is it due to a problem with the RAM? Any suggestions are greatly appreciated. Thanks, Farrah. Hit any key to stop autoboot: 0 ## Booting image at 00400000 ... Image Name: Linux-2.6.15 daqNet H11764D Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 739864 Bytes = 722.5 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... NIP: 07FEB04C XER: 20000000 LR: 07FEB9E0 REGS8 MSR: 00021000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00 GPR00: 00000000 07FA4FF0 000038B0 07FCE854 00000013 00000013 00000000 07FA4FF8 GPR08: FFFFFFFA 07FA5100 07FA4FF8 00000002 07FA50B4 00004340 08004800 07FA503C GPR16: FFFFFFFF 00000000 00000006 000B4A0D 00000000 00000002 000B4A06 00000006 GPR24: 00000007 00400052 00000005 00000000 00000000 07FA5F58 080048B0 07FA5AE0 ** Illegal Instruction ** Call backtrace: Program Check Exception

2 1

[U-Boot-Users] bootm shows Kernel info but reset
by Ingo Swieter 20 Jun '07

20 Jun '07

Hello, i have a problem starting Linux from U-Boot. I compile my Linux-Kernel with the make uImage command and copy it to my tftpboot directory. With U-Boot i can load the image through tftp and the bootm command shows the correct information. But after a while, around half second, it restarts U-Boot again. Do you have any hint for that problem? Best Regards, Ingo --- # t 100000 uImage Using FEC ETHERNET device TFTP from server 172.16.102.78; our IP address is 172.16.102.79 Filename 'uImage'. Load address: 0x100000 Loading: ################################################################# ################################################################# ### done Bytes transferred = 679637 (a5ed5 hex) # bootm 100000 ## Booting image at 00100000 ... Image Name: Linux-2.4.25 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 679573 Bytes = 663.6 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK U-Boot 1.2.0 (Jun 14 2007 - 11:03:06) BCS_EPDEV_P01-00 CPU: MPC885ZPnn at 100 MHz [40.0...133.0 MHz] 8 kB I-Cache 8 kB D-Cache FEC present Board: EP88xC 1.1 CPLD revision 2 Watchdog enabled DRAM: 64 MB FLASH: 32 MB In: serial Out: serial Err: serial Net: FEC ETHERNET, FEC2 ETHERNET # -- Ingo Swieter Tel: 05121/1760-821 Mail: ingo.swieter(a)brunel.de Brunel GmbH Bereich Communications Daimlerring 9 31135 Hildesheim Fax: 05121/1760-999 Internet: http://www.brunel.de Hauptsitz: Airport City, Hermann-Köhl-Str. 1 a, 28199 Bremen Amtsgericht Bremen HRB 16935 General Manager: Carsten Siebeneich

4 5

[U-Boot-Users] compile problems with u-boot
by sapirf fersht 19 Jun '07

19 Jun '07

I am trying to compile u-boot and i get the following error: common/libcommon.a(main.o): In function `readline': u-boot-1.2.0/common/main.c:953: undefined reference to `get_ticks' common/libcommon.a(main.o): In function `reset_cmd_timeout': u-boot-1.2.0/common/main.c:519: undefined reference to `get_ticks' u-boot-1.2.0/common/main.c:519: undefined reference to `get_tbclk' common/libcommon.a(main.o): In function `abortboot': u-boot-1.2.0/common/main.c:97: undefined reference to `get_ticks' u-boot-1.2.0/common/main.c:97: undefined reference to `get_tbclk' u-boot-1.2.0/common/main.c:163: undefined reference to `get_ticks' I checked for this error in google and it was suggested to add the following lines to include/configs/stamp.h #define CONFIG_BOOT_RETRY_TIME 0 #define CONFIG_BOOT_RETRY_MIN 20 I added them and it still throws the same error. It compiled before. The only changes i made are: #define CONFIG_BOOTDELAY 5 /* autoboot after 5 seconds */ #define CONFIG_AUTOBOOT_KEYED #define CONFIG_AUTOBOOT_PROMPT "\nEnter password - autoboot in %d seconds...\n" #define CONFIG_AUTOBOOT_DELAY_STR "somekey" #define CONFIG_BOOT_RETRY_TIME 900 #define CONFIG_BOOT_RETRY_MIN 30 Sapir

2 1

[U-Boot-Users] [Fwd: Re: [PATCH] bug in README and soft_i2c.c]
by Joakim Tjernlund 19 Jun '07

19 Jun '07

Wolfgang, I think the below patch is ready for wider audience and ask that you include it in your tree. I and 2 others has tested it to some extent and I don't think it will receive any more testing outside the u-boot tree. Jocke -------- Forwarded Message -------- From: Joakim Tjernlund <joakim.tjernlund(a)transmode.se> Reply-To: joakim.tjernlund(a)transmode.se To: Andrew Dyer <amdyer(a)gmail.com> Cc: U-Boot list <u-boot-users(a)lists.sourceforge.net> Subject: Re: [U-Boot-Users] [PATCH] bug in README and soft_i2c.c Date: Tue, 22 May 2007 18:23:31 +0200 On Mon, 2007-05-21 at 17:04 -0500, Andrew Dyer wrote: > Hi, I noticed a bug in soft_i2c.c (or in the README depending on how > you think about it). > > If CONFIG_SOFT_I2C is defined and using open-collector I/O, then the > README says that I2C_TRISTATE can be defined as null. If this is the > case, then doing: > > imd 29 0.0 2 > > will cause the following chain of calls in soft_i2c.c: > > send_start() > write_byte() > read_byte() > read_byte() > send_stop() > > The first read_byte() calls send_ack(0). send_ack(0) drives the data > line low without releasing it. The following call to read_byte() > calls I2C_TRISTATE, but in this case it is defined as NULL per the > README. This leaves the data line driven low during the read of the > 2nd byte causing data^h^h^h^hhair loss that I can ill afford :-) > > I propose the following fix - modify the README to make say that > I2C_TRISTATE should be defined even for open-collector setups, and add > code to soft_i2c.c to explictly tristate the data at the end of > send_ack(0) > > Signed-off-by: Andrew Dyer <amdyer(a)gmail.com> I think the README w.r.t I2C_TRISTATE is OK as is(don't change it). I do think the soft i2c driver is broken in several places w.r.t IC2_ACTIVE/I2C_TRISTATE and I2C reset sequence. The below patch is an attempt to fix it. Signed-off-by: Joakim Tjernlund <joakim.tjernlund(a)transmode.se> diff --git a/common/soft_i2c.c b/common/soft_i2c.c index edad51b..ed3f8f8 100644 --- a/common/soft_i2c.c +++ b/common/soft_i2c.c @@ -100,15 +100,18 @@ static void send_reset(void) #endif I2C_TRISTATE; for(j = 0; j < 9; j++) { + if(I2C_READ) + send_start(); I2C_SCL(0); I2C_DELAY; + I2C_TRISTATE; + I2C_SDA(1); I2C_DELAY; I2C_SCL(1); I2C_DELAY; I2C_DELAY; } send_stop(); - I2C_TRISTATE; } /*----------------------------------------------------------------------- @@ -124,12 +127,13 @@ static void send_start(void) #endif I2C_DELAY; + I2C_TRISTATE; I2C_SDA(1); - I2C_ACTIVE; I2C_DELAY; I2C_SCL(1); I2C_DELAY; I2C_SDA(0); + I2C_ACTIVE; I2C_DELAY; } @@ -152,9 +156,9 @@ static void send_stop(void) I2C_DELAY; I2C_SCL(1); I2C_DELAY; + I2C_TRISTATE; I2C_SDA(1); I2C_DELAY; - I2C_TRISTATE; } @@ -172,14 +176,17 @@ static void send_ack(int ack) I2C_SCL(0); I2C_DELAY; - I2C_ACTIVE; I2C_SDA(ack); + I2C_ACTIVE; I2C_DELAY; I2C_SCL(1); I2C_DELAY; I2C_DELAY; I2C_SCL(0); I2C_DELAY; + I2C_TRISTATE; + I2C_SDA(1); + I2C_DELAY; } @@ -215,8 +222,8 @@ static int write_byte(uchar data) */ I2C_SCL(0); I2C_DELAY; - I2C_SDA(1); I2C_TRISTATE; + I2C_SDA(1); I2C_DELAY; I2C_SCL(1); I2C_DELAY; @@ -224,7 +231,6 @@ static int write_byte(uchar data) nack = I2C_READ; I2C_SCL(0); I2C_DELAY; - I2C_ACTIVE; return(nack); /* not a nack is an ack */ } @@ -249,6 +255,7 @@ static uchar read_byte(int ack) * Read 8 bits, MSB first. */ I2C_TRISTATE; + I2C_SDA(1); data = 0; for(j = 0; j < 8; j++) { I2C_SCL(0); ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

Re: [U-Boot-Users] SOFT_I2C on at91rm9200 - FIXED
by Nils Gjerdevik 19 Jun '07

19 Jun '07

2007/6/18, Matteo Vit <matteo.vit(a)dave.eu>: > Nils Gjerdevik ha scritto: > > Hi, > > I'm trying to store the u-boot environment in an EEPROM (at24c128) on > > a custom at91rm9200 based board. This fails when using the included > > HARD_I2C driver, and since there are known problems with the I2C > > controller on this uC, I'm trying to set up SOFT_I2C instead, without > > success so far... Problem solved! Turns out the peripheral clock for the pio controller wasn't enabled. In the Linux code I looked at this was already done elsewhere. Thanks to Joakim and Matteo for valuable help. For the record, here is the code: /* enable I2C */ #define CONFIG_SOFT_I2C 1 /* I2C bit-banged */ #define CONFIG_I2C_CMD_TREE #define CFG_I2C_SPEED 10000 #define CFG_I2C_SLAVE 0 //Enable peripheral clock and configure data and clock pins for pio #define I2C_INIT { \ *AT91C_PMC_PCER = 1 << AT91C_ID_PIOA; \ *AT91C_PIOA_IDR = AT91C_PA25_TWD | AT91C_PA26_TWCK; \ *AT91C_PIOA_MDER = AT91C_PA25_TWD | AT91C_PA26_TWCK; \ *AT91C_PIOA_PUDR = AT91C_PA25_TWD | AT91C_PA26_TWCK; \ *AT91C_PIOA_ODR = AT91C_PA25_TWD | AT91C_PA26_TWCK; \ *AT91C_PIOA_PER = AT91C_PA25_TWD | AT91C_PA26_TWCK; \ } //Configure data pin as output #define I2C_ACTIVE (*AT91C_PIOA_OER = AT91C_PA25_TWD) //Configure data pin as input #define I2C_TRISTATE (*AT91C_PIOA_ODR = AT91C_PA25_TWD) //Read data pin #define I2C_READ (*AT91C_PIOA_PDSR & AT91C_PA25_TWD ? 1 : 0) //Set data pin #define I2C_SDA(bit) *AT91C_PIOA_OER = AT91C_PA25_TWD; \ if (bit) *AT91C_PIOA_SODR = AT91C_PA25_TWD; \ else *AT91C_PIOA_CODR = AT91C_PA25_TWD //Set clock pin #define I2C_SCL(bit) *AT91C_PIOA_OER = AT91C_PA26_TWCK; \ if (bit) *AT91C_PIOA_SODR = AT91C_PA26_TWCK; \ else *AT91C_PIOA_CODR = AT91C_PA26_TWCK #define I2C_DELAY udelay(2) /* 1/4 I2C clock duration */ The env_in_eeprom config is: #define CFG_ENV_IS_IN_EEPROM 1 #define CFG_ENV_OFFSET 0 /* Env in the beginning of EEPROM */ #define CFG_ENV_SIZE 0x800 /* 2kb */ #define CFG_I2C_EEPROM_ADDR 0x50 /* Default EEPROM address */ #define CFG_EEPROM_PAGE_WRITE_BITS 6 /* 64 byte page size */ #define CFG_EEPROM_PAGE_WRITE_DELAY_MS 5 /* 5ms delay between page writes */ #define CFG_I2C_EEPROM_ADDR_LEN 2 /* 2 bytes used for addressing in the EEPROM */ #define CFG_EEPROM_SIZE 0x4000 /* 16kb */ Nils

3 2

[U-Boot-Users] Port for M5329EVB ColdFire MCF5329 eval board - needs network!
by Robert S. Grimes 19 Jun '07

19 Jun '07

Hi all, I've been working on a port for the Freescale/LogicPD eval board with the ColdFire MCF5329 microcontroller. I've got it up and running from flash and all. No network yet - and I'm not sure how to proceed there. It seems from an example or two that U-Boot network drivers are usually fairly simple. Is it true that a simple polled driver is sufficient? I'd like to get Ethernet working, but I have more pressing concerns right now, so I can't really spend a lot of time on it. However, I'd be interested in working with others, and certainly would welcome a bit more guidance; I haven't really found much in the way of an "Ethernet Driver How-To", and I've looked. Of course, I could have missed it... On a different topic, I would like to submit my BSP. I don't know how interested people would be, given its current state - no Ethernet, and frankly, not extensively tested. I will be using it over the next few months, so I'd expect these to improve, but it's probably not really ready for formal inclusion. What does one do in such situations? What is the process for new BSPs, especially incomplete "beta" versions? Thanks for your time, -Bob

4 5