October 2004 - U-Boot

[U-Boot-Users] Booting from Ethernet
by pankaj goyal 28 Oct '04

28 Oct '04

HI, I want to make a boot loader for an ARM based platform.Can anyone please tell me what all configuration parameters i need to define in the configuration file and how to setupo a ehternet connection Pankaj

2 1

Re: [U-Boot-Users] [OT] character sets
by Craig Hughes 28 Oct '04

28 Oct '04

On Oct 27, 2004, at 3:19 PM, Dan Poirot wrote: >> -----Original Message----- >> >> Not sure how one would do this if one is Chinese and using >> hotmail for email... In the 21st century one might suggest >> that if a base64-encoded message in a non-western character >> set is unreadable, the problem is on the receiving side not >> the sending side. >> >> C > > > ...so perhaps you would prefer if Wolfgand responded to the list in > German > calligraphy script in the form of a 10 megabyte TIFF file? > > Hard to use 'grep' on that... Looks, if your mail-searching tool doesn't decode base64 before doing its search, then your mail-searching tool is broken. If your mailing list archive tool won't map character sets for you so that "foo" matches the representation of "foo" in some oddball character set, then your mailing list archive tool is broken. And if you want to search an un-indexed mail spool which hasn't been QP/base64/uuencode/MIME decoded using grep, then you should seriously look into the "formail" utility which comes as part of the procmail package. You can then apply MIME transforms on each message in your un-indexed file before piping to grep. Of course it'll be slower than an amputee sloth, but hey, if you want to search large archives quickly, then index them. Look, ultimately, Wolfgang gets to make the rules for his list, and I'm not suggesting otherwise, but really, when the only reason you choose to not read someone's email message asking for help is because your email app is broken, it seems a little bit rude to suggest that the problem is on the other end. C PS Not trying to get everyone all upset, but in my previous life I did a lot of email processing stuff, and MIME/character set issues are really trivially solved these days with the vast amount of very high-quality decoding libraries available out there.

2 1

[U-Boot-Users] Cross compiling problem of u-boot-1.1.1 on powerpc850
by flab 28 Oct '04

28 Oct '04

Hello everyone, I am porting uboot1.1.1 on my powerpc850 board. With the reference files of TQM850L board, I changed some configuration settings and flash driver. But there is a problem when I use cross compiling. /*********************************/ /LinuxPPC/CDK/bin/powerpc-linux-gcc -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE=0x10000000 -I/root/u-boot-1.1.1/include -fno-builtin -ffreestanding -nostdinc -isystem /LinuxPPC/CDK/lib/gcc-lib/powerpc-linux/2.95.2/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8xx -ffixed-r2 -ffixed-r29 -mstring -mcpu=860 -msoft-float -Wall -Wstrict-prototypes -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE=0x10000000 -I/root/u-boot-1.1.1/include -fno-builtin -ffreestanding -nostdinc -isystem /LinuxPPC/CDK/lib/gcc-lib/powerpc-linux/2.95.2/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_8xx -ffixed-r2 -ffixed-r29 -mstring -mcpu=860 -msoft-float -I.. -Bstatic -T /root/u-boot-1.1.1/board/tqm8xx/u-boot.lds -Ttext 0x10000000 -n hello_world.c -o hello_world powerpc-linux-gcc: 0x10000000: ????????? /LinuxPPC/CDK/powerpc-linux/bin/as:??"-n"????? In file included from /root/u-boot-1.1.1/include/linux/posix_types.h:46, from /root/u-boot-1.1.1/include/linux/types.h:8, from /root/u-boot-1.1.1/include/common.h:37, from hello_world.c:24: /root/u-boot-1.1.1/include/asm/posix_types.h:13: output pipe has been closed cpp: output pipe has been closed powerpc-linux-gcc: file path prefix `static' never used make[1]: *** [hello_world] Error 1 make[1]: Leaving directory `/root/u-boot-1.1.1/examples' make: *** [examples] Error 2 /******************************************/ I changed the setting of flash_base,and I don't know that if I have to change somewhere in u-boot.lds. Any kind of guidance is appreciated. Best Regards Flab

4 5

Re: [U-Boot-Users] CFI driver
by York Sun 27 Oct '04

27 Oct '04

Yuli, I have confirm the problem on more boards. On Mon, 2004-10-25 at 11:53, Yuli Barcohen wrote: > York> Yes. I agree. I polled the DQ7 at the same address of being > York> written. I know the AMD polling algorithm. Actually I have > York> been using polling DQ7 for a long time. Hundreds of our boards > York> were shipped with this algorithm. I am very sure the image has > York> been programmed correctly. > > So I assume that if you program kernel image you can then successfully > boot it. Correct? Yes. > York> I also found the flash_make_cmd has some defect. You cannot > York> simply multiply the offset with the port width. That would > York> generate error address if you are using 8-bit port > York> width. Modification is needed for 32-bit chip width. I made > York> modification. But I need some boards to verify. > > There can be bugs for the very same reason: I haven't got enough boards > to verify all possible configuration. In particular, I've got no board > using 8-bit port width. I received recently a board with 32-bit flash > (2x16) and the CFI driver worked unchanged. Maybe only 4x8 needed the > modification... > > I'd suggest trying this driver on a different board with the same flash > if you've got one. This would rule out possible hardware issue. On my > Adder, the driver works so I can't reproduce the problem in our lab. I tried 4 more boards. I confirm the problem on one board with the same two flash chips (AM29LV641DH). I also found two boards with mixed chips (one AM29LV641MH and AM29LV641DH). One of those board has problem on erasing, no problem on programming. The other board is fine. The problem did show up on the board with two AM29LV641MH. I have revised the driver to support port width from 8-bit to 64-bit, chip width from 8-bit to 32-bit. Also, I modified the driver to poll DQ6 at the same address where the date is being written to. And I add the polling DQ7, which is not enabled by default. With these modification, all my boards passed testing. By the way, here is the feedback from AMD, "It is a good practice to use the exact address where data is being written to when using the "DQ6" method, even though in theory you don't have to." If you want to confirm, I can generate a patch. Wolfgang? Regards, York

2 1

RE: [U-Boot-Users] Memory Testing (Flash,EEPROM)
by Fillod Stephane 27 Oct '04

27 Oct '04

Wolfgang Denk wrote: > It makes no real sense to perform a write testing on flash memory, > for example, as you must erase the flash to write it, and erase it > again to write it again, and the fact that you can write it now is no > guarantee that it is still erasable the next time. IMHO, the point is not to test the chip, but to test the wires to the chip, for industrial purpose. For the other matters, the customer will find it out by himself anyway :*) Best Regards, -- Stephane

2 1

[U-Boot-Users] U-boot for pxa255
by swamy 27 Oct '04

27 Oct '04

Hi, We have a custom built PXA255 board with 32 MB SDRAM, 32MB Flash( one 28F256L30b 16MX16 bit wide) and FFUART for serial port. I am unable to boot U-boot after loading to flash through JflashMM program. Flash loading is verified successfully. 1. How do I debug? 2. Does u-boot support the above flash configuration? 3. Are there any patches to u-boot to make it work for the above configuration? Appreciate your response Regards, swamy

2 1

[U-Boot-Users] Memory Testing (Flash,EEPROM)
by Vikrant_Basotra 27 Oct '04

27 Oct '04

Hi, The u-boot code (version 1.1.1) contains the SDRAM testing code. The Test cases involved for the SDRAM are Address Bus Test, Data Bus Test and Device Integrity Test. For SDRAM each and every thing is OK, but for EEPROM and Flash Memory No such test Cases are their using which the user can check the correctness of these Devices at the command prompt. It would be highly appreciated if any one will describe the process of Flash memory and EEPROM Testing by modifying the U-Boot Code. Thanks in anticipation. Regards!!! Vikrant ************************************************************************** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. **************************************************************************

2 1

[U-Boot-Users] Srec problem and TQM860
by Charles J Gillan 26 Oct '04

26 Oct '04

Folks, I have encountered a problem with downloading Linux to my TQM860L board using S records via the serial port. Any help or suggestions would be greatly appreciated. Last week I followed the ELDK instructions to replace the TQ Monitor on my board with Das U-Boot. I use ELDK 3.0 but download the U-Boot 1.1.1 source and compiled it rather than the 1.0.2 source delivered with ELDK 3.0. I built U-Boot using make TQM860L_config I now realise that I have FEC on my board, and should have used Make TQM860L_FEC_config but I did not expect that this would impact on the serial port comms. Perhaps this is the source of the problem ??? I used "cu" on my SuSe 8.2 PC to download U-Boot as SRECs over the serial port. All of this went well - I can log into U-Boot and execute commands such as flinfo. I then built the linux 2.4.24 kernel that comes with ELDK 3.0 and converted this to S records. My downloads fail at the seventh S record (see attached debug from "cu" at end of file); record 6 required a retry. 7 cu: fconn_io: Writing 44 "S2140000507800E45A0F701367767FAB3FB6843D4452" cu: fconn_io: Wrote 44 of 44, read 0 of 16383 cu: fconn_io: Writing 1 "\r" cu: fconn_io: Wrote 1 of 1, read 0 of 16383 cu: fconn_read: Read 16 "## S-Record down" <----------- Error starts here cu: fconn_read: Read 8 "load abo" cu: fconn_read: Read 9 "rted\r\n=> " I have also tried using a RedHat PC which has a different implementation of "cu". The same problem exists. Has this problem been seen before? Is there anything that can be done to work around it? Regards and thanks, Charles. ======================================================================== = Initial output ============== U-Boot 1.1.1 (Oct 21 2004 - 11:46:31) CPU: XPC86xxxZPnnD3 at 50 MHz: 16 kB I-Cache 8 kB D-Cache FEC present Board: TQM860LDB0A3-P50.208 DRAM: 16 MB FLASH: 8 MB In: serial Out: serial Err: serial Net: SCC ETHERNET [PRIME], FEC ETHERNET PCMCIA: No Card found Type "run flash_nfs" to mount root filesystem over NFS Hit any key to stop autoboot: 5 => flinfo Bank # 1: FUJITSU AM29LV160B (16 Mbit, bottom boot sect) Size: 4 MB in 35 Sectors Sector Start Addresses: 40000000 (RO) 40008000 (RO) 4000C000 (RO) 40010000 (RO) 40020000 (RO) 40040000 40060000 40080000 400A0000 400C0000 400E0000 40100000 40120000 40140000 40160000 40180000 401A0000 401C0000 401E0000 40200000 40220000 40240000 40260000 40280000 402A0000 402C0000 402E0000 40300000 40320000 40340000 40360000 40380000 403A0000 403C0000 403E0000 Bank # 2: FUJITSU AM29LV160B (16 Mbit, bottom boot sect) Size: 4 MB in 35 Sectors Sector Start Addresses: 40400000 40408000 4040C000 40410000 40420000 40440000 40460000 40480000 404A0000 404C0000 404E0000 40500000 40520000 40540000 40560000 40580000 405A0000 405C0000 405E0000 40600000 40620000 40640000 40660000 40680000 406A0000 406C0000 406E0000 40700000 40720000 40740000 40760000 40780000 407A0000 407C0000 407E0000 => erase 40040000 400fffff ... done Erased 6 sectors => ~[approach]. Output from "loads" =================== 6 cu: fconn_io: Writing 44 "S2140000401F8B0808B40979410203766D6C696E75DA" cu: fconn_io: Wrote 44 of 44, read 0 of 16383 cu: fconn_io: Writing 1 "\r" cu: fconn_io: Wrote 1 of 1, read 0 of 16383 cu: fconn_read: Read 36 "S2140000401F8B0808B40979410036DC9E5A" cu: fconn_read: Read 0 "" R cu: fconn_io: Writing 1 "\025" cu: fconn_io: Wrote 1 of 1, read 0 of 16348 cu: fconn_io: Writing 44 "S2140000401F8B0808B40979410203766D6C696E75DA" cu: fconn_io: Wrote 44 of 44, read 0 of 16383 cu: fconn_io: Writing 1 "\r" cu: fconn_io: Wrote 1 of 1, read 0 of 16383 cu: fconn_read: Read 25 "\025S100401F8B0808B409794102" cu: fconn_read: Read 8 "03766D66" cu: fconn_read: Read 8 "96E75DA\r" 7 cu: fconn_io: Writing 44 "S2140000507800E45A0F701367767FAB3FB6843D4452" cu: fconn_io: Wrote 44 of 44, read 0 of 16383 cu: fconn_io: Writing 1 "\r" cu: fconn_io: Wrote 1 of 1, read 0 of 16383 cu: fconn_read: Read 16 "## S-Record down" <----------- Error starts here cu: fconn_read: Read 8 "load abo" cu: fconn_read: Read 9 "rted\r\n=> " 8 cu: fconn_io: Writing 44 "S214000060C1B230E03F3230D40EAA232E305959C2E6" cu: fconn_io: Wrote 44 of 44, read 0 of 16383 cu: fconn_io: Writing 1 "\r" cu: fconn_io: Wrote 1 of 1, read 0 of 16383 cu: fconn_read: Read 12 "S214000060C1" cu: fconn_read: Read 16 "B230E03F3230D40E" cu: fconn_read: Read 8 "AA232E30" cu: fconn_read: Read 8 "5959C2E6" cu: fconn_read: Read 16 "\r\r\nUnknown comma" ======================================================================== = Dr Charles J Gillan The Institute of Electronics, Communications and Information Technology (ECIT), Queen's University Belfast, Titanic Quarter Queens Road, Queens Island, Belfast, BT3 9DT Northern Ireland, UK Tel: +44 (0) 2890 971847

2 3

[U-Boot-Users] cfi driver - wrong sector protection detection with AMD flashes
by Martin Krause 26 Oct '04

26 Oct '04

Hi all, I tried the cfi flash driver on our custom MPC5200 board (TQM5200). It works fine with different flash chips soldered. The only problem is with an AMD (Spansion) AM29L160M Flash. There u-boot comes up with _all_ sectors protected: => flinfo Bank # 1: CFI conformant FLASH (32 x 16) Size: 4 MB in 35 Sectors Erase timeout 16384 ms, write timeout 0 ms, buffer write timeout 1 ms, buffer s ize 1 Sector Start Addresses: FC000000 RO FC008000 RO FC00C000 RO FC010000 RO FC020000 RO FC040000 RO FC060000 ERO FC080000 ERO FC0A0000 ERO FC0C0000 ERO FC0E0000 ERO FC100000 ERO FC120000 ERO FC140000 ERO FC160000 ERO FC180000 ERO FC1A0000 ERO FC1C0000 ERO FC1E0000 ERO FC200000 ERO FC220000 ERO FC240000 ERO FC260000 ERO FC280000 ERO FC2A0000 ERO FC2C0000 ERO FC2E0000 ERO FC300000 ERO FC320000 ERO FC340000 ERO FC360000 ERO FC380000 ERO FC3A0000 ERO FC3C0000 ERO FC3E0000 ERO => I tracked down the problem to the function flash_get_size() in cfi_flash.c. There a special mechanism is used to query the flash for the protection status of each sector. As far as I know, the used mechanism is not part of the CFI Spec. And worse the mechanism is different for Intel and AMD (Spansion). For Intel flashes the sector protection status could be read when the flash is in the CFI query state (at offset 02h on each sector address). For AMD flashes this works only in the "autoselect" mode and in the actual driver the "autoselect" mode is not used. And I could not say, if autoselect and CFI Query mode would work at the same time. I wonder if anyone else encountered similar problems with AMD flahes and sector protection detection? As solution for flashes with AMD command set I disabled the sector protection detection in the cfi driver (see patch). Comments are welcome. Is there anybody out there who uses the cfi driver and _really_ protected flash sectors (not the software based protection used by u-boot)? If not, we could perhaps disable the protection detection mechanism completely. Also because the used mechanism is not part of the cfi specification. Regards, Martin ------------------------------------------------------------------ Martin Krause TQ-Systems GmbH Gut Delling, Mühlstr. 2, 82229 Seefeld, Germany Fax: +49 8153 4223 Phone: +49 8153 9308 157 Personal Fax: +49 8153 9308 7157 Email: martin.krause(a)tqs.de http://www.tq-group.com ------------------------------------------------------------------

1 0

[U-Boot-Users] Support for SuperH processors
by Andrew STURGES 26 Oct '04

26 Oct '04

Hi, I'm interested in providing a port of u-boot to SH-4 platforms and I was interested in - anyone else was already doing this or interested. - Any help in getting started in porting u-boot to a new architecture (other than reading the source & readme files) Thanks for any Help Andy Sturges STMicroelectronics

2 1