January 2005 - U-Boot

[U-Boot-Users] Re: [PATCH] Cleanup cpu/arm920t using SoC
by Wolfgang Denk 24 Jan '05

24 Jan '05

In message <4120DD8B.8040709(a)imc-berlin.de> you wrote: > > * Patch by Steven Scholz, 16 Aug 2004: > - Introducing the concept of SoCs "./cpu/$(CPU)/$(SOC)" > - creating subdirs for SoCs ./cpu/arm920t/imx and ./cpu/arm920t/s3c24x0 > - moving SoC specific code out of cpu/arm920t/ into cpu/arm920t/$(SOC)/ > - moving drivers/s3c24x0_i2c.c and drivers/serial_imx.c out of drivers/ > into cpu/arm920t/$(SOC)/ Added, thanks. Please feel free to go on now with the next step of cleanup. And sorry it took so long. Viele Grüße, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de Anyone who isn't confused here doesn't really know what's going on.

6 18

[U-Boot-Users] [patch] add support for AMD Alchemy Pb1x00 boards to u-boot-1.1.2
by Thomas Sailer 24 Jan '05

24 Jan '05

The patch referenced below does: - support AMD's Pb1x00 eval board, based on the Dbau1x00 support. I've tested it by loading it into the board SDRAM. It works both in big endian mode and, if you change all linker scripts to output little endian srec files and use the appropriate compiler command line, also in little endian mode Note that the usb ohci driver doesn't yet work for me. Root hub seems to work, but any data transfer from a device fails. On the other hand, current linux mips 2.6 hangs when I load the ohci driver, so it doesn't work there too. - fix the mii and usb commands which can dereference a null pointer when called without arguments. - added mii routines to the au1x00 ethernet driver. - add the objects as explicitly in the examples makefile, to avoid the use of a builtin make rule that goes directly from source to executable without going through the object files. Btw, it seems to me that the Dbau1x00 port sets up the auxilliary PLL way too fast. Thomas http://www.baycom.org/~tom/uboot-pb1000.patch

1 0

RE: [U-Boot-Users] BDI2000 with pxa255
by Paugam Luc 24 Jan '05

24 Jan '05

Hi, There is a problem with your JTAG link or chain. The important line is: - TARGET: Bypass check: 0x000000001 => 0x00000000 It says roughly: (as you know, a JTAG chain is let say "a serial link looped") After setting all JTAG controllers into the JTAG chain to bypass mode, I sent a 1 (only 1 bit) and tried to get back this bit ... but in your case without success! Regards - Luc -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Hinko Kocevar Sent: jeudi 20 janvier 2005 15:51 To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] BDI2000 with pxa255 Hi, I've connected bdi2000 to the host computer and successfully updated firmware and managed to telnet to the bdi. I also adapted cfg file for my platform (KK trizeps2). When I power up the target device I get this error: ... - TARGET: target will be restarted in 10 sec - TARGET: processing reset request - TARGET: BDI asserts RESET and TRST - TARGET: BDI removed TRST - TARGET: Bypass check: 0x000000001 => 0x00000000 - TARGET: JTAG exists check failed # TARGET: resetting target failed # JTAG: communication with target failed - TARGET: target will be restarted in 10 sec ... Can somebody point me to the possible causes for this behaviour? PS. Is it mandatory to supply ~RESET pin to BDI? Can I just keep it in reset with a jumper closed? Trizeps2 is lacking this pin on JTAG connector. best regards, hk -- hinko <dot> kocevar <at> iskramedical <dot> si Hinko Kocevar, embedded systems developer Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU "Aì rén" | [Analects XII:22] ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] BDI2000 with pxa255
by Hinko Kocevar 24 Jan '05

24 Jan '05

Hi, I've connected bdi2000 to the host computer and successfully updated firmware and managed to telnet to the bdi. I also adapted cfg file for my platform (KK trizeps2). When I power up the target device I get this error: ... - TARGET: target will be restarted in 10 sec - TARGET: processing reset request - TARGET: BDI asserts RESET and TRST - TARGET: BDI removed TRST - TARGET: Bypass check: 0x000000001 => 0x00000000 - TARGET: JTAG exists check failed # TARGET: resetting target failed # JTAG: communication with target failed - TARGET: target will be restarted in 10 sec ... Can somebody point me to the possible causes for this behaviour? PS. Is it mandatory to supply ~RESET pin to BDI? Can I just keep it in reset with a jumper closed? Trizeps2 is lacking this pin on JTAG connector. best regards, hk -- hinko <dot> kocevar <at> iskramedical <dot> si Hinko Kocevar, embedded systems developer Iskra Medical d.o.o., Stegne 23, 1k LJ, SLO-EU "Aì rén" | [Analects XII:22]

2 2

[U-Boot-Users] U-boot code etiquette
by Neil Bryan 24 Jan '05

24 Jan '05

Hello group, I have a problem to solve which effects U-boot environment variable storage. Before I submit changes to core U-boot code, I want to find out from the group 'what is acceptable code to modify?'. I am afraid that this description is quite long, but I do not know how to describe it in very few words. TARGET DESCRIPTION: Based on the AT91RM9200 MCU from Atmel with 8kbytes of I2C EEPROM. For my initial investigation I am using the AT91RM9200DK port of U-boot. PROBLEM: The board has a limited EEPROM storage area and it has been decided that U-boot environment variables are to be stored in EEPROM. U-boot uses quite a large amount of environment variable space, in fact the default size for the AM91RM9200DK CFG_ENV_SIZE is 0x2000 (8kbytes). So all my EEPROM disappears to U-boot leaving non for Linux. I can reduce this by changing ./include/configs/at91rm9200dk.h CFG_ENV_SIZE to 0x800 (2kbytes). U-boot builds, runs and all is well. BUT, cetain variables such as the board IP address need to be common to both Linux and U-boot. So if the board IP address is changed by the OS or by Linux, the change needs to be visible to the other. SOLUTION: To divide the EEPROM into a psuedo-file structure. We have data structures of varying lengths and types to pack more data into the EEPROM. We need to support a variety of OSes on the board and will have several OS-specific data structures. One data structure would be reserved for U-boot, length 2kBytes, However, common values such as IP address will be stored in this psuedo-file structure. AFFECT ON U-BOOT: When U-boot reads the environment variables, it needs to check in two places in EEPROM: 1) The standard U-boot storage of NUL terminated strings, e.g. bootdelay, bootargs, bootcmd, etc. 2) Our board specific data structure(s) which most likely will be baudrate, ethaddr, ethxaddr, ipaddr, serverip. COMMENTS: o I don't want to make board-specific changes in common code areas. I can see my proposal affecting cmd_nvedit.c. This code does not have pre-processing for multiple board-types and so architecturaly it feels wrong. o I need to hook into functions getenv() and setenv(). I will read a table of constant strings and compare with the environment variable which is being sought and then parse it appropriately. So, people with lots of U-boot experience, I need your advice. I don't want to spend lots of time making theses suggested changes to have it rejected for inclusion into the mainline code. Will it be accepted or is it just too far outside of the way U-boot evolves? Is there a better solution? Thanks for your time on this. Regards, Neil.

3 3

[U-Boot-Users] Flash Burst Mode
by Konstantin Kletschke 24 Jan '05

24 Jan '05

Hi People :) At the moment I am trying to get the burst read mode of my flash chips running. I have a Motorola i-MX CPU with ARM9 core. The Flash device is a 28F128K18: "Intel StrataFlash(R) Synchronous Memory". If I understood right I tell the flash device with some commands and data register words delivered by address bus to work in sync mode. After that I program the chip select control signal of the microcontroller to enable burst modus. I am doing that by hand with the u-boot CLI but I manage to read garbage after enabling the burst mode only. Does anybody have made such a setup working? Or is there one board in the u-boot source tree make use of flash burst mode so I can put this into i.MX arch also? Kind Regards, Konsti -- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF

1 0

[U-Boot-Users] Modifying CFG_IMMR in a MPC885
by Bruno 24 Jan '05

24 Jan '05

Hello Everybody, I'm developing a project that uses a MPC885 processor, that has a embedded security processor. The MPC885 Reference Manual (http://www.freescale.com/files/32bit/doc/ref_manual/MPC885RM.pdf - Section 10.4.1) and a Application Note (http://www.freescale.com/files/32bit/doc/app_note/AN2800.pdf) say that bits D14-D15 of the IMMR register should be set to '10' to enable the access of the security processor (SEC Lite) registers. I tried to change my define CFG_IMMR from 0xFF000000 to 0xFF020000, but as result the U-boot hanged. I searched the source codes of another boards (NETVIA, NETTAx) that also use the MPC885 but all of them set the IMMR to 0xFF000000. So, I ask: someone here uses the Security Processor of MPC885? How to set the IMMR register to achieve the access of the SEC Lite registers?? Thanks in advance and Best Regards, Bruno _______________________________________________________ Yahoo! Acesso Grátis - Instale o discador do Yahoo! agora. http://br.acesso.yahoo.com/ - Internet rápida e grátis

3 3

[U-Boot-Users] Spectacularly Weird U-Boot Behavior w/NE2000
by Craig A. Vanderborgh 24 Jan '05

24 Jan '05

Hello Everybody, I have just completed a port to our board of u-boot-1.1.3, from CVS. Everything is actually working very well, so kudos to everybody for all of the fine work done in the past few months. I have incorporated Christian's NE2000 driver for PCMCIA, and have configured it for my PXA255 custom board according to his instructions and the instructions in the README.PXA_CF in /doc. I am have had some success with this - and an amazing problem. I can successfully activate the PCMCIA card using "pinit on". When I do this, I see the following: $ pinit on PCMCIA Card detected Low Power Ethernet LAN Adapter Socket Communications, Inc Revis Network Adapter Card So u-boot can read the CIS and figure out that I have a socket LPE. Nice. Then, I try to do a ping - and it works: $ ping 10.250.1.7 NE2000 - eeprom ESA: 09:09:84:8a:08:0c host 10.250.1.7 is alive $ Wonderful. But now, after doing the ping, u-boot's "view" of flash memory gets corrupted. For example, look at this: $ md 80000 00080000: 56190080 65070080 40300080 18670080 ...V...e..0@..g. 00080010: 00000080 00000080 dfc00080 00020080 ................ 00080020: 2e340080 762d0080 2d310080 31610080 ..4...-v..1-..a1 00080030: 52450080 41440080 72650080 006c0080 ..ER..DA..er..l. 00080040: e1a00080 e1a00080 e1a00080 e1a00080 ................ 00080050: e1a00080 e1a00080 e1a00080 e1a00080 ................ 00080060: ea000080 016f0080 00000080 000b0080 ......o......... 00080070: e1a00080 e3a00080 e10f0080 e3120080 ................ 00080080: 1a000080 e3a00080 ef120080 e10f0080 ................ 00080090: e3820080 e1210080 e3cf0080 e2820080 ......!......... 000800a0: e4920080 e1320080 1aff0080 ee070080 ......2......... 000800b0: ee070080 ee110080 e3c00080 e3c00080 ................ 000800c0: ee010080 e3a00080 00000080 00000080 ................ 000800d0: 00000080 00000080 00000080 00000080 ................ 000800e0: e28f0080 e8900080 e0500080 e3300080 ..........P...0. 000800f0: 0a000080 e0850080 e0860080 e08c0080 ................ Notice how the high-order 16 bits of each long word are always "0080"? This is completely bogus. However, flash has not actually been corrupted. If I do a reset, and then do an "md 8000", everything is perfectly right. Now don't get me wrong - I hardly expect you u-boot experts to "debug my program". It's just that this is SO strange, I hardly know where to start. Please just toss me one small bone here and answer this question: What could possibly be going on here? Is the NE2000 driver messing up the memory controller, or is it something else? By the way, after the "ping" is done the PXA register settings continue to look good, so I doubt if it's a register-related problem. But then again, maybe I'm missing something. Please let me know what you think - I'm pretty stuck at the moment. Thanks in advance, craig vanderborgh voxware incorporated

4 3

[U-Boot-Users] patch to add compact flash support for altera NIOS DK1C20
by Shlomo Kut 23 Jan '05

23 Jan '05

Hi, Here is a patch that adds Compact flash support to the NIOS DK1C20 board. Changelog entry: Add Compact Flash support to NIOS DK1C20. regards, Shlomo Kut Vyyo Ltd POB 45017 Jerusalem 91450 Israel +972-2-5889822 <<new.diff>>

1 0

[U-Boot-Users] request for help
by sushant mishra 22 Jan '05

22 Jan '05

sir, i am using the das u-boot.now i want that the POST tests to be configured by mine.that is i want to customize the POST test according to mine.what i should do plz suggest the solution.i will be happy if u reply me the solution in mail. with regards sushant kumar mishra Yahoo! India Matrimony: Find your life partneronline.

2 1