September 2005 - U-Boot

[U-Boot-Users] Runninng ELDK_BUILD : Pls help
by batsayan.das＠tcs.com 03 Sep '05

03 Sep '05

Running ELDK_BUILD script gives the following o/p. It was looking to patch something. ************************************************************** ## Building "2005-09-01" for architecture "ppc" step rpm ---- Step 'rpm' started at Thu Sep 1 02:39:53 IST 2005 ---- tar: /opt/eldk/build/ppc-2005-09-01/cross_rpms/rpm/SOURCES/rpm-4.1.1.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: Error exit delayed from previous errors /opt/eldk/build/build.sh: line 386: cd: rpm-4.1.1: No such file or directory /opt/eldk/build/build.sh: line 387: /opt/eldk/build/ppc-2005-09-01/cross_rpms/rpm/SOURCES/rpm-4.1.1-yellowdog.patch: No such file or directory can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -Naur rpm-4.1.1.orig/Makefile.in rpm-4.1.1.new/Makefile.in |--- rpm-4.1.1.orig/Makefile.in Fri Oct 10 10:02:01 2003 |+++ rpm-4.1.1.new/Makefile.in Fri Oct 10 10:03:09 2003 -------------------------- File to patch: *************************************************************** My /opt/eldk contains "SPRMS, build, tarballs" directory along with other normal directory. I donloaded the SPRMS from the yellowdog ftp site. I modified the ELDK_BUILD so that ncftpget command in the script works. The modified lines are : ${SRPMS_URL:='ftp://127.0.0.1/pub/SRPMS'} : ${SRPMS_UPDATES_URL:='ftp://127.0.0.1/pub/U_SRPMS'} I put the SPRMS( ftp://ftp.yellowdoglinux.com/pub/yellowdog/yellowdog-3.0/en/os/SRPMS ) and U_SPRMS(ftp://ftp.yellowdoglinux.com/pub/yellowdog/updates/yellowdog-3.0/SR… downloded from the yellowdog ftp site at /var/ftp/pub. Actually I plan to get the updates from the yellowdog ftp site. But as the site (ftp://ftp.yellowdoglinux.com/pub/yellowdog/updates/yellowdog-3.0/SRPMS) does not open up; I copied the SPRMS to U_SPRMS. So, SPRMS and U_SPRMS are same, in my case. I did this because from my m/c it not possible to get files from yellowdog ftp site by ncftpget. I started vsftpd service. Pls help Thanks, Batsayan Das Tata Consultancy Services Limited Mailto: batsayan.das(a)tcs.com Website: http://www.tcs.com Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

2 1

[U-Boot-Users] CAN bus support on MCF5282
by David Peters 02 Sep '05

02 Sep '05

Has anyone done anything in U-Boot for the CAN bus on the MCF5282? Is there any code available that might help test a CAN bus?

2 1

[U-Boot-Users] [PATCH] Support OF Flat Tree for embedded PPC
by Pantelis Antoniou 02 Sep '05

02 Sep '05

Hi all. The following patch supports the passing of a OF flat tree from the bootloader to the kernel, for embedded PPC processors. For reference purposes this is done for 8xx processors. The bulk of the patch deals of the disentanglement of OF support from the generic PMAC & CHRP code. Please comment. Regards Pantelis

1 0

[U-Boot-Users] [PATCH] Fix default command set.
by Pantelis Antoniou 02 Sep '05

02 Sep '05

Hi all. The following patch fixes the default command set by not including the CFG_CMD_DISPLAY commands. Regards Pantelis diff --git a/include/cmd_confdefs.h b/include/cmd_confdefs.h --- a/include/cmd_confdefs.h +++ b/include/cmd_confdefs.h @@ -109,6 +109,7 @@ CFG_CMD_DATE | \ CFG_CMD_DHCP | \ CFG_CMD_DIAG | \ + CFG_CMD_DISPLAY | \ CFG_CMD_DOC | \ CFG_CMD_DTT | \ CFG_CMD_ECHO | \

1 0

[U-Boot-Users] u-boot bringup
by Raghu 02 Sep '05

02 Sep '05

Hello All, I successfully ported u-boot on a PPC405EP processor, But I get the u-boot prompt only when I connect and execute it using the BDI2000, including all the serial outputs. But if I disconnect the BDI nothing comes up on the Serial COM. Any clues please ?? Thanks, Raghu. ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

4 3

[U-Boot-Users] U-boot port issue on a MPC8280 Custom board
by Srivatsan CR 02 Sep '05

02 Sep '05

Dear all, 1) We have a custom designed MPC8280 board. We have brought up the board using BDi2000 ofcourse after a long struggle. :-) 2) We are trying to bringup the board with u-boot. 3) We are using 2 Micron Flash devices MT28F128J3 so total size is 32 MB. Also our system clock is 83.3 Mhz. Our flash device has a 125ns/25nsec read access time. 4) Our initial boot space as configured in Bdi is 0xfff00100. Our flash base address is 0xfe000000. 12 clock cycle is configured for system clock cycle. 5) In u-boot erase and write time-out are configured for 5000 and 5000 respectively. 6) While we try to debug the code using gdb, the program stops at 0xfff10108. This address is inside ListInserItem. 7) Before u-boot executes, there was data in 0xfff10108 but after it executes, the flash displays the status of the commands (flash specific commands for writing/erasing). When we write the following command in bdi: mm 0xfe000000 0xffffffff the flash displays the normal data. That means u-boot data is available from 0xfe000000 but at 0xfff00000 we are seeing all F's but at 0xfff10108 alone we see in the following manner. Something is trying to do a flash erase and that is causing the problem. 0xfff10108 0000ffff 8) From Bdi2000, the stepping happens fine. Atleast it not going till board_init_f, cpu_init_f yes. My problem is doing debugging from GDB : Why is data at 0xfff00000 gets erased ? And also why is the command given incomplete ? Hope somebody will help me solve the issue. I can send the map file if somebody needs it. I don't have any special logging or console buffer enabled. Even ethernet code is disabled. Only serial is enabled on SMC1. With Thanks and Regards, C.R.Srivatsan

1 0

RE: [U-Boot-Users] BDI2000 and MPC8260
by Rune Torgersen 01 Sep '05

01 Sep '05

> -----Original Message----- > From: Pantelis Antoniou > Sent: Thursday, September 01, 2005 13:44 > > That doesn't sound quite right, but worst case all you need to do > > is pull RSTCONF to ground and the 82xx will use an internal > > configuration word to get you going. > If your boot flash is not written correctly, you'd better > have a way to pull RSTCONF low. Different BDI settings are > required however, beware. Eh.. According to the 8260 Users manual it is excactly opposite... (8260UM ch 5.4) RSTCONF should be tied to GND for reading HRCW from EPROM. RSTCONF should be tied to VCC for slave configuration or if you want to use the default all 0 HRCW.

1 0

[U-Boot-Users] BDI2000 and MPC8260
by Alex Zeffertt 01 Sep '05

01 Sep '05

Hi, I hope this isn't considered off topic here.... I am trying to load u-boot.bin into the flash device on my PM828 board using a BDI2000 and the config file ftp://ftp.denx.de/pub/BDI2000/pm826.cfg. On the PM828 platform the HRW - hard reset configuration word- is loaded into the CPU from bottom of the flash device on CS0. The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not present in the flash device. I.e. you need u-boot.bin already loaded into flash in order to load u-boot.bin into flash! At the moment I can work around this problem by setting some jumpers on the board to remap CS0 to a PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so that CS0 is mapped to the flash again. Unfortunately I will not be able to do this on our custom hardware as there will only be a flash device and no PROM. Here is the output from the BDI2000 session when the flash on CS0 is erased (i.e. the HRW is 0xffffffff): - TARGET: waiting for target Vcc - TARGET: waiting for target Vcc - TARGET: waiting for target Vcc [ PM828 is switched on ] - TARGET: processing power-up delay - TARGET: processing user reset request - BDI asserts HRESET - Reset JTAG controller passed - Bypass check: 0x00000001 => 0x00000001 - JTAG exists check passed - COP status is 0x01 - Check running state passed - BDI scans COP freeze command - BDI removes HRESET - Target PVR is 0x80822011 - COP status is 0x05 - Check stopped state passed - Check LSRL length passed - BDI sets breakpoint at 0xFFF00100 - BDI resumes program execution - Waiting for target stop passed - TARGET: Target PVR is 0x80822011 - TARGET: resetting target passed - TARGET: processing target startup .... - TARGET: processing target startup passed [ 10 second gap ] *** TARGET: reset detected, restarting target - BDI asserts HRESET - Reset JTAG controller passed - Bypass check: 0x00000001 => 0x00000001 - JTAG exists check passed - COP status is 0x05 - Check running state failed - TARGET: Target PVR is 0x80822011 *** TARGET: resetting target failed # PPC: unexpected response from target - TARGET: target will be restarted in 10 sec - TARGET: processing user reset request [ the above repeats indefinitely ] Does anybody have any idea how to work around this circular dependency? Regards, Alex

3 2

[U-Boot-Users] Executing an application from a specific address
by Swapnil Ashok Narkhede 01 Sep '05

01 Sep '05

HI, I have my bootloader running and i get the boot prompt. Now i am trying to load hello_world.bin and trying to execute it. 1>> I have a pxa250 (ARM)processor on Accelent board. As per Readme.Standalone i should be loading the application at 0x0c100000 and executing from the same address.But no where in the hello_world.c i find any link which tells the application that it should stick to the above specified address. Then why is it that U-boot can run the application only if it is at that address. I read some previous posts which say that we can download the application anywhere other than 0x0c100000,but u boot wont execute them. Why is it so? Where has it been specified that u-boot should execute standalone application only if it is at that address 2>>The memory map for pxa250 which i received says nCS0: 0x00000000-0x03ffffff J77 1-2 Flash ROM (default) J78 2-3 M-Systems Disk On Chip nCS1: 0x04000000-0x07ffffff J78 1-2 M-Systems Disk On Chip (default) J77 2-3 Flash ROM nCS2: 0x08000000-0x0bffffff Unused, available on expansion buses nCS3: 0x0c000000-0x0fffffff J49 1-2: MediaQ MQ1132 J49 open: Unused, available on expansion buses which means address space 0x0c000000-0x0fffffff is unused. Then how can i download my application to that address and execute it. Regards, Swapnil Narkhede Mob:- 0432025023 Email:- s3092131(a)student.rmit.edu.au School of Computer Science and Information Technology RMIT University, Melbourne

2 1

Re: [U-Boot-Users] PPC440GX reset command doesn't work
by Renaud Barbier 01 Sep '05

01 Sep '05

Just saw that old email. I am haveing the sme problem with my 440GX. Have you found any clue of why a system reset does not work? Andrew Wozniak wrote: >Andrew Wozniak wrote: > > >>We have a custom PPC440GX board running a ported version of U-Boot based >>on the OCOTEA codebase. Most U-Boot commands are working - life is good. >> >>Except for the 'reset' command. The do_reset() source code at >>cpu/ppc4xx/cpu.c appears to be the function for doing the reset via the >>PPC "debug control register". The PPC manual shows that a cpu reset is >>possible thru this register, but I'm a PPC assembly newbee and need to >>figure it out the macros in the cpu.c source code. >> >>Just wondering if anyone else with a PPC440 target had any special >>modifications to make 'reset' work. >> >> > >Ok, understand the assembly macro (except for the ::: "r3"). Must have >something to do with do_reset args? > >Anyway, it appears that a PPC "system reset" does not work as >implemented via DBCR0 value 0x30000000. > >If I change the value to 0x20000000 to do a "chip reset", the U-Boot >'reset' command works! > >Is this an appropriate solution or might our hardware design have a flaw? > >Thanks for all suggestions. > > > >>Thank you. >> >> > > > >------------------------------------------------------- >This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput >a projector? How fast can you ride your desk chair down the office luge track? >If you want to score the big prize, get to know the little guy. >Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 >_______________________________________________ >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] BDI2000 and MPC8260
by Alex Zeffertt 01 Sep '05

01 Sep '05

Hi, I hope this isn't considered off topic here.... I am trying to load u-boot.bin into the flash device on my PM828 board using a BDI2000 and the config file ftp://ftp.denx.de/pub/BDI2000/pm826.cfg. On the PM828 platform the HRW - hard reset configuration word- is loaded into the CPU from bottom of the flash device on CS0. The problem I am seeing is that the bdi2000 cannot communicate with the PM828 if the HRW is not present in the flash device. I.e. you need u-boot.bin already loaded into flash in order to load u-boot.bin into flash! At the moment I can work around this problem by setting some jumpers on the board to remap CS0 to a PROM device containing u-boot, writing the HRW into flash, and returning the jumpers so that CS0 is mapped to the flash again. Unfortunately I will not be able to do this on our custom hardware as there will only be a flash device and no PROM. Here is the output from the BDI2000 session when the flash on CS0 is erased (i.e. the HRW is 0xffffffff): - TARGET: waiting for target Vcc - TARGET: waiting for target Vcc - TARGET: waiting for target Vcc [ PM828 is switched on ] - TARGET: processing power-up delay - TARGET: processing user reset request - BDI asserts HRESET - Reset JTAG controller passed - Bypass check: 0x00000001 => 0x00000001 - JTAG exists check passed - COP status is 0x01 - Check running state passed - BDI scans COP freeze command - BDI removes HRESET - Target PVR is 0x80822011 - COP status is 0x05 - Check stopped state passed - Check LSRL length passed - BDI sets breakpoint at 0xFFF00100 - BDI resumes program execution - Waiting for target stop passed - TARGET: Target PVR is 0x80822011 - TARGET: resetting target passed - TARGET: processing target startup .... - TARGET: processing target startup passed [ 10 second gap ] *** TARGET: reset detected, restarting target - BDI asserts HRESET - Reset JTAG controller passed - Bypass check: 0x00000001 => 0x00000001 - JTAG exists check passed - COP status is 0x05 - Check running state failed - TARGET: Target PVR is 0x80822011 *** TARGET: resetting target failed # PPC: unexpected response from target - TARGET: target will be restarted in 10 sec - TARGET: processing user reset request [ the above repeats indefinitely ] Does anybody have any idea how to work around this circular dependency? Regards, Alex

2 2

[U-Boot-Users] [PATCH] wrsbc8560 support
by Wessel, Jason 01 Sep '05

01 Sep '05

This patch add the Wind River wrsbc8560 support back into u-boot. At one time it worked until some code conflicting code was removed to support the Motorolla 85xx evaluation platforms. The PHY code for the wrsbc8560 has been added in again. Signed-off-by: Jason Wessel <jason.wessel(a)windriver.com> -------------BEGIN PATCH-------------------------- Separate Motorolla sbc8540 and sbc8560 from wrsbc8560 --- commit fe3c13d77c1d36fddcf751d8c4b183bc2373b9da tree 9aab5c704d53170090d7152d56daa739d06cbfc3 parent 77f6580cc078fea22c2b1348f5b177edcd63885f author <jwessel(a)jwessel3-lx.(none)> Sat, 01 Oct 2005 11:10:05 -0500 committer <jwessel(a)jwessel3-lx.(none)> Sat, 01 Oct 2005 11:10:05 -0500 CHANGELOG | 3 Makefile | 13 + doc/README.wrsbc8560 | 57 ++++++ drivers/tsec.c | 32 +++ include/configs/wrsbc8560.h | 410 +++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 515 insertions(+), 0 deletions(-) diff --git a/CHANGELOG b/CHANGELOG --- a/CHANGELOG +++ b/CHANGELOG @@ -2,6 +2,9 @@ Changes for U-Boot 1.1.4: ====================================================================== +* Fix Wind River wrsb8560 support + Patch by Jason Wessel, 01 Sep 2005 + * Fix problems with ld version 2.16 (dot outside sections problem) Pointed out by Gerhard Jaeger, 31 Aug 2005; cf. http://sourceware.org/ml/binutils/2005-08/msg00412.html diff --git a/Makefile b/Makefile --- a/Makefile +++ b/Makefile @@ -1301,6 +1301,19 @@ sbc8560_66_config: unconfig fi @./mkconfig -a sbc8560 ppc mpc85xx sbc8560 + +wrsbc8560_config \ +wrsbc8560_33_config \ +wrsbc8560_66_config: unconfig + @if [ "$(findstring _66_,$@)" ] ; then \ + echo "#define CONFIG_PCI_66" >>include/config.h ; \ + echo "... 66 MHz PCI" ; \ + else \ + >include/config.h ; \ + echo "... 33 MHz PCI" ; \ + fi + @./mkconfig -a wrsbc8560 ppc mpc85xx sbc8560 + stxgp3_config: unconfig @./mkconfig $(@:_config=) ppc mpc85xx stxgp3 diff --git a/doc/README.wrsbc8560 b/doc/README.wrsbc8560 new file mode 100644 --- /dev/null +++ b/doc/README.wrsbc8560 @@ -0,0 +1,57 @@ +The port was tested on Wind River System wrsbc8560 board +<www.windriver.com>. U-Boot was installed on the flash memory of the +CPU card (not the SODIMM). + +NOTE: Please configure uboot compile to the proper PCI frequency and +setup the appropriate DIP switch settings. + +wrsb8560 board: + +Make sure boards switches are set to their appropriate conditions. +Refer to the Engineering Reference Guide ERG-00300-002. Of particular +importance are: 1) the settings for JP4 (JP4 1-3 and 2-4), which +select the on-board FLASH device (Intel 28F128Jx); 2) The settings +for the Clock SW9 (33 MHz or 66 MHz). + + Note: SW9 Settings: 66 MHz + 4:1 ratio CCB clocks:SYSCLK + 3:1 ration e500 Core:CCB + pos1 - on, pos2 - on, pos3 - off, pos4 - on, pos5 - off, pos6 - on + Note: SW9 Settings: 33 MHz + 8:1 ratio CCB clocks:SYSCLK + 3:1 ration e500 Core:CCB + pos1 - on, pos2 - on, pos3 - on, pos4 - off, pos5 - off, pos6 - on + + +Flashing the FLASH device with the "Wind River ICE": + +1) Properly connect and configure the Wind River ICE to the target + JTAG port. This includes running the wrsbc8560 register script. Make + sure target memory can be read and written. + +2) Build the u-boot image: + make distclean + make wrsbc8560_66_config or wrsbc8560_33_config + make CROSS_COMPILE=.../ELDK3.0/ppc_8xx-/ all + + Note: reference is made to the ELDK3.0 compiler. Further, it seems + the ppc_8xx compiler is required for the 85xx (no 85xx + designated compiler in ELDK3.0) + +3) Convert the uboot (.elf) file to a uboot.bin file (using + visionClick converter). The bin file should be converted from + fffc0000 to ffffffff + +4) Setup the Flash Utility (tools menu) for: + + Do a "dc clr" [visionClick] to load the default register settings + Determine the clock speed of the PCI bus and set SW9 accordingly + Note: the speed of the PCI bus defaults to the slowest PCI card + PlayBack the "default" register file for the wrsbc8560 + Select the uboot.bin file with zero bias + Select the initialize Target prior to programming + Select the V28F640Jx (8192 x 8) 1 device FLASH Algorithm + Select the erase base address from FFFC0000 to FFFFFFFF + Select the start address from 2000 with size of 60000 + +5) Erase and Program diff --git a/drivers/tsec.c b/drivers/tsec.c --- a/drivers/tsec.c +++ b/drivers/tsec.c @@ -681,6 +681,37 @@ static void tsec_halt(struct eth_device* phy_run_commands(priv, priv->phyinfo->shutdown); } +struct phy_info phy_info_BCM5421S = { + 0x02060e, + "BCM 5421S", + 4, + (struct phy_cmd[]) { /* config */ + /* Reset and configure the PHY */ + {MIIM_CONTROL, MIIM_CONTROL_RESET, NULL}, + {0x1d, 0x1f, NULL}, + {0x1e, 0x200c, NULL}, + {0x1d, 0x5, NULL}, + {0x1e, 0x0, NULL}, + {0x1e, 0x100, NULL}, + {MIIM_GBIT_CONTROL, MIIM_GBIT_CONTROL_INIT, NULL}, + {MIIM_ANAR, MIIM_ANAR_INIT, NULL}, + {MIIM_CONTROL, MIIM_CONTROL_RESET, NULL}, + {MIIM_CONTROL, MIIM_CONTROL_INIT, &mii_cr_init}, + {miim_end,} + }, + (struct phy_cmd[]) { /* startup */ + /* Status is read once to clear old link state */ + {MIIM_STATUS, miim_read, NULL}, + /* Auto-negotiate */ + {MIIM_STATUS, miim_read, &mii_parse_sr}, + /* Read the status */ + {MIIM_88E1011_PHY_STATUS, miim_read, &mii_parse_88E1011_psr}, + {miim_end,} + }, + (struct phy_cmd[]) { /* shutdown */ + {miim_end,} + }, +}; struct phy_info phy_info_M88E1011S = { 0x01410c6, @@ -892,6 +923,7 @@ struct phy_info *phy_info[] = { &phy_info_M88E1111S, &phy_info_dm9161, &phy_info_lxt971, + &phy_info_BCM5421S, NULL }; diff --git a/include/configs/wrsbc8560.h b/include/configs/wrsbc8560.h new file mode 100644 --- /dev/null +++ b/include/configs/wrsbc8560.h @@ -0,0 +1,410 @@ +/* + * (C) Copyright 2005 Wind River Systems Inc <www.windriver.com>. + * Added support for Wind River SBC8560 board - Jason Wessel + * + * (C) Copyright 2002,2003 Motorola,Inc. + * Xianghua Xiao <X.Xiao(a)motorola.com> + * + * + * See file CREDITS for list of people who contributed to this + * project. + * + * This program is free software; you can redistribute it and/or + * modify it under the terms of the GNU General Public License as + * published by the Free Software Foundation; either version 2 of + * the License, or (at your option) any later version. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + * + * You should have received a copy of the GNU General Public License + * along with this program; if not, write to the Free Software + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, + * MA 02111-1307 USA + */ + +/* mpc8560ads board configuration file */ +/* please refer to doc/README.mpc85xx for more info */ +/* make sure you change the MAC address and other network params first, + * search for CONFIG_ETHADDR,CONFIG_SERVERIP,etc in this file + */ + +#ifndef __CONFIG_H +#define __CONFIG_H + +/* High Level Configuration Options */ +#define CONFIG_BOOKE 1 /* BOOKE */ +#define CONFIG_E500 1 /* BOOKE e500 family */ +#define CONFIG_MPC85xx 1 /* MPC8540/MPC8560 */ +#define CONFIG_MPC85xx_REV1 1 /* MPC85xx Rev 1.0 chip */ + + +#define CONFIG_CPM2 1 /* has CPM2 */ +#define CONFIG_SBC8560 1 /* configuration for SBC8560 board */ + +/* XXX flagging this as something I might want to delete */ +#define CONFIG_MPC8560ADS 1 /* MPC8560ADS board specific */ + +#define CONFIG_TSEC_ENET /* tsec ethernet support */ +#undef CONFIG_PCI /* pci ethernet support */ +#undef CONFIG_ETHER_ON_FCC /* cpm FCC ethernet support */ + + +#define CONFIG_ENV_OVERWRITE + +/* Using Localbus SDRAM to emulate flash before we can program the flash, + * normally you need a flash-boot image(u-boot.bin), if so undef this. + */ +#undef CONFIG_RAM_AS_FLASH + +#if defined(CONFIG_PCI_66) /* some PCI card is 33Mhz only */ + #define CONFIG_SYS_CLK_FREQ 66000000/* sysclk for MPC85xx */ +#else + #define CONFIG_SYS_CLK_FREQ 33000000/* most pci cards are 33Mhz */ +#endif + +/* below can be toggled for performance analysis. otherwise use default */ +#define CONFIG_L2_CACHE /* toggle L2 cache */ +#undef CONFIG_BTB /* toggle branch predition */ +#undef CONFIG_ADDR_STREAMING /* toggle addr streaming */ + +#define CONFIG_BOARD_EARLY_INIT_F 1 /* Call board_early_init_f */ + +#undef CFG_DRAM_TEST /* memory test, takes time */ +#define CFG_MEMTEST_START 0x00200000 /* memtest region */ +#define CFG_MEMTEST_END 0x00400000 + + +/* + * Base addresses -- Note these are effective addresses where the + * actual resources get mapped (not physical addresses) + */ +#define CFG_CCSRBAR_DEFAULT 0xff700000 /* CCSRBAR Default */ + +#if XXX + #define CFG_CCSRBAR 0xfdf00000 /* relocated CCSRBAR */ +#else + #define CFG_CCSRBAR 0xff700000 /* default CCSRBAR */ +#endif +#define CFG_IMMR CFG_CCSRBAR /* PQII uses CFG_IMMR */ + +#define CFG_DDR_SDRAM_BASE 0x00000000 /* DDR is system memory */ +#define CFG_SDRAM_BASE CFG_DDR_SDRAM_BASE +#define CFG_SDRAM_SIZE 512 /* DDR is 512MB */ +#define SPD_EEPROM_ADDRESS 0x55 /* DDR DIMM */ + +#undef CONFIG_DDR_ECC /* only for ECC DDR module */ +#undef CONFIG_SPD_EEPROM /* Use SPD EEPROM for DDR setup */ + +#if defined(CONFIG_MPC85xx_REV1) + #define CONFIG_DDR_DLL /* possible DLL fix needed */ +#endif + +#undef CONFIG_CLOCKS_IN_MHZ + +#if defined(CONFIG_RAM_AS_FLASH) + #define CFG_LBC_SDRAM_BASE 0xfc000000 /* Localbus SDRAM */ + #define CFG_FLASH_BASE 0xf8000000 /* start of FLASH 8M */ + #define CFG_BR0_PRELIM 0xf8000801 /* port size 8bit */ + #define CFG_OR0_PRELIM 0xf8000ff7 /* 8MB Flash */ +#else /* Boot from real Flash */ + #define CFG_LBC_SDRAM_BASE 0xf8000000 /* Localbus SDRAM */ + #define CFG_FLASH_BASE 0xff800000 /* start of FLASH 8M */ + #define CFG_BR0_PRELIM 0xff800801 /* port size 8bit */ + #define CFG_OR0_PRELIM 0xff800ff7 /* 8MB Flash */ +#endif +#define CFG_LBC_SDRAM_SIZE 64 /* LBC SDRAM is 64MB */ + +/* local bus definitions */ +#define CFG_BR1_PRELIM 0xe4001801 /* 64M, 32-bit flash */ +#define CFG_OR1_PRELIM 0xfc000ff7 + +#define CFG_BR2_PRELIM 0x00000000 /* CS2 not used */ +#define CFG_OR2_PRELIM 0x00000000 + +#define CFG_BR3_PRELIM 0xf0001861 /* 64MB localbus SDRAM */ +#define CFG_OR3_PRELIM 0xfc000cc1 + +#if defined(CONFIG_RAM_AS_FLASH) + #define CFG_BR4_PRELIM 0xf4001861 /* 64M localbus SDRAM */ +#else + #define CFG_BR4_PRELIM 0xf8001861 /* 64M localbus SDRAM */ +#endif +#define CFG_OR4_PRELIM 0xfc000cc1 + +#define CFG_BR5_PRELIM 0xfc000801 /* 16M CS5 misc devices */ +#if 1 + #define CFG_OR5_PRELIM 0xff000ff7 +#else + #define CFG_OR5_PRELIM 0xff0000f0 +#endif + +#define CFG_BR6_PRELIM 0xe0001801 /* 64M, 32-bit flash */ +#define CFG_OR6_PRELIM 0xfc000ff7 +#define CFG_LBC_LCRR 0x00030002 /* local bus freq */ +#define CFG_LBC_LBCR 0x00000000 +#define CFG_LBC_LSRT 0x20000000 +#define CFG_LBC_MRTPR 0x20000000 +#define CFG_LBC_LSDMR_1 0x2861b723 +#define CFG_LBC_LSDMR_2 0x0861b723 +#define CFG_LBC_LSDMR_3 0x0861b723 +#define CFG_LBC_LSDMR_4 0x1861b723 +#define CFG_LBC_LSDMR_5 0x4061b723 + +/* just hijack the MOT BCSR def for SBC8560 misc devices */ +#define CFG_BCSR ((CFG_BR5_PRELIM & 0xff000000)|0x00400000) +/* the size of CS5 needs to be >= 16M for TLB and LAW setups */ + +#define CONFIG_L1_INIT_RAM +#define CFG_INIT_RAM_LOCK 1 +#define CFG_INIT_RAM_ADDR 0x70000000 /* Initial RAM address */ +#define CFG_INIT_RAM_END 0x4000 /* End of used area in RAM */ + +#define CFG_GBL_DATA_SIZE 128 /* num bytes initial data */ +#define CFG_GBL_DATA_OFFSET (CFG_INIT_RAM_END - CFG_GBL_DATA_SIZE) +#define CFG_INIT_SP_OFFSET CFG_GBL_DATA_OFFSET + +#define CFG_MONITOR_LEN (256 * 1024) /* Reserve 256 kB for Mon */ +#define CFG_MALLOC_LEN (128 * 1024) /* Reserved for malloc */ + +/* Serial Port */ +#undef CONFIG_CONS_ON_SCC /* define if console on SCC */ +#undef CONFIG_CONS_NONE /* define if console on something else */ + +#define CONFIG_CONS_INDEX 1 +#undef CONFIG_SERIAL_SOFTWARE_FIFO +#define CFG_NS16550 +#define CFG_NS16550_SERIAL +#define CFG_NS16550_REG_SIZE 1 +#define CFG_NS16550_CLK 1843200 /* get_bus_freq(0) */ +#define CONFIG_BAUDRATE 9600 + +#define CFG_BAUDRATE_TABLE \ + {300, 600, 1200, 2400, 4800, 9600, 19200, 38400,115200} + +#define CFG_NS16550_COM1 ((CFG_BR5_PRELIM & 0xff000000)+0x00700000) +#define CFG_NS16550_COM2 ((CFG_BR5_PRELIM & 0xff000000)+0x00800000) + +/* Use the HUSH parser */ +#define CFG_HUSH_PARSER +#ifdef CFG_HUSH_PARSER +#define CFG_PROMPT_HUSH_PS2 "> " +#endif + +/* I2C */ +#define CONFIG_HARD_I2C /* I2C with hardware support*/ +#undef CONFIG_SOFT_I2C /* I2C bit-banged */ +#define CFG_I2C_SPEED 400000 /* I2C speed and slave address */ +#define CFG_I2C_SLAVE 0x7F +#define CFG_I2C_NOPROBES {0x69} /* Don't probe these addrs */ + +#define CFG_PCI_MEM_BASE 0xC0000000 +#define CFG_PCI_MEM_PHYS 0xC0000000 +#define CFG_PCI_MEM_SIZE 0x10000000 + +#if defined(CONFIG_TSEC_ENET) /* TSEC Ethernet port */ + +#define CONFIG_PHY_BCM5421S 1 +#define CONFIG_NET_MULTI 1 +#define CONFIG_MII 1 /* MII PHY management */ +#undef CONFIG_MPC85XX_FEC +#define CONFIG_MPC85XX_TSEC1 1 +#define CONFIG_MPC85XX_TSEC1_NAME "TSEC0" +#define CONFIG_MPC85XX_TSEC2 1 +#define CONFIG_MPC85XX_TSEC2_NAME "TSEC1" +#define TSEC1_PHY_ADDR 25 +#define TSEC1_PHYIDX 0 +#define TSEC2_PHY_ADDR 26 +#define TSEC2_PHYIDX 0 +/* Options are: TSEC0 */ +#define CONFIG_ETHPRIME "TSEC0" + +#elif defined(CONFIG_ETHER_ON_FCC) /* CPM FCC Ethernet */ + + #undef CONFIG_ETHER_NONE /* define if ether on something else */ + #define CONFIG_ETHER_ON_FCC2 /* cpm FCC ethernet support */ + #define CONFIG_ETHER_INDEX 2 /* which channel for ether */ + + #if (CONFIG_ETHER_INDEX == 2) + /* + * - Rx-CLK is CLK13 + * - Tx-CLK is CLK14 + * - Select bus for bd/buffers + * - Full duplex + */ + #define CFG_CMXFCR_MASK (CMXFCR_FC2 | CMXFCR_RF2CS_MSK | CMXFCR_TF2CS_MSK) + #define CFG_CMXFCR_VALUE (CMXFCR_RF2CS_CLK13 | CMXFCR_TF2CS_CLK14) + #define CFG_CPMFCR_RAMTYPE 0 + #define CFG_FCC_PSMR (FCC_PSMR_FDE) + + #elif (CONFIG_ETHER_INDEX == 3) + /* need more definitions here for FE3 */ + #endif /* CONFIG_ETHER_INDEX */ + + #define CONFIG_MII /* MII PHY management */ + #define CONFIG_BITBANGMII /* bit-bang MII PHY management */ + /* + * GPIO pins used for bit-banged MII communications + */ + #define MDIO_PORT 2 /* Port C */ + #define MDIO_ACTIVE (iop->pdir |= 0x00400000) + #define MDIO_TRISTATE (iop->pdir &= ~0x00400000) + #define MDIO_READ ((iop->pdat & 0x00400000) != 0) + + #define MDIO(bit) if(bit) iop->pdat |= 0x00400000; \ + else iop->pdat &= ~0x00400000 + + #define MDC(bit) if(bit) iop->pdat |= 0x00200000; \ + else iop->pdat &= ~0x00200000 + + #define MIIDELAY udelay(1) + +#endif + +/*--------------------------------------------------------------------- -- + * FLASH and environment organization + */ + +#define CFG_FLASH_CFI 1 /* Flash is CFI conformant */ +#define CFG_FLASH_CFI_DRIVER 1 /* Use the common driver */ +#if 0 +#define CFG_FLASH_USE_BUFFER_WRITE 1 /* use buffered writes (20x faster) */ +#define CFG_FLASH_PROTECTION /* use hardware protection */ +#endif +#define CFG_MAX_FLASH_SECT 64 /* max number of sectors on one chip */ +#define CFG_MAX_FLASH_BANKS 1 /* max number of memory banks */ + +#undef CFG_FLASH_CHECKSUM +#define CFG_FLASH_ERASE_TOUT 200000 /* Timeout for Flash Erase (in ms) */ +#define CFG_FLASH_WRITE_TOUT 50000 /* Timeout for Flash Write (in ms) */ + +#define CFG_MONITOR_BASE TEXT_BASE /* start of monitor */ + +#if 0 +/* XXX This doesn't work and I don't want to fix it */ +#if (CFG_MONITOR_BASE < CFG_FLASH_BASE) + #define CFG_RAMBOOT +#else + #undef CFG_RAMBOOT +#endif +#endif + +/* Environment */ +#if !defined(CFG_RAMBOOT) + #if defined(CONFIG_RAM_AS_FLASH) + #define CFG_ENV_IS_NOWHERE + #define CFG_ENV_ADDR (CFG_FLASH_BASE + 0x100000) + #define CFG_ENV_SIZE 0x2000 + #else + #define CFG_ENV_IS_IN_FLASH 1 + #define CFG_ENV_SECT_SIZE 0x20000 /* 128K(one sector) for env */ + #define CFG_ENV_ADDR (CFG_MONITOR_BASE - CFG_ENV_SECT_SIZE) + #define CFG_ENV_SIZE 0x2000 /* CFG_ENV_SECT_SIZE */ + #endif +#else + #define CFG_NO_FLASH 1 /* Flash is not usable now */ + #define CFG_ENV_IS_NOWHERE 1 /* Store ENV in memory only */ + #define CFG_ENV_ADDR (CFG_MONITOR_BASE - 0x1000) + #define CFG_ENV_SIZE 0x2000 +#endif + +#define CONFIG_BOOTARGS "root=/dev/nfs rw nfsroot=192.168.0.251:/tftpboot ip=192.168.0.105:192.168.0.251::255.255.255.0:sbc8560:eth0:off console=ttyS0,9600" +/*#define CONFIG_BOOTARGS "root=/dev/ram rw console=ttyS0,115200"*/ +#define CONFIG_BOOTCOMMAND "bootm 0xff800000 0xffa00000" +#define CONFIG_BOOTDELAY 5 /* -1 disable autoboot */ + +#define CONFIG_LOADS_ECHO 1 /* echo on for serial download */ +#define CFG_LOADS_BAUD_CHANGE 1 /* allow baudrate change */ + +#if defined(CFG_RAMBOOT) || defined(CONFIG_RAM_AS_FLASH) + #if defined(CONFIG_PCI) + #define CONFIG_COMMANDS ((CONFIG_CMD_DFL | CFG_CMD_PCI | \ + CFG_CMD_ELF | \ + CFG_CMD_PING | CFG_CMD_I2C) & \ + ~(CFG_CMD_ENV | \ + CFG_CMD_LOADS )) + #elif (defined(CONFIG_TSEC_ENET) || defined(CONFIG_ETHER_ON_FCC)) + #define CONFIG_COMMANDS ((CONFIG_CMD_DFL | CFG_CMD_MII | \ + CFG_CMD_ELF | \ + CFG_CMD_PING | CFG_CMD_I2C) & \ + ~(CFG_CMD_ENV)) + #endif +#else + #if defined(CONFIG_PCI) + #define CONFIG_COMMANDS (CONFIG_CMD_DFL | CFG_CMD_PCI | \ + CFG_CMD_ELF | \ + CFG_CMD_PING | CFG_CMD_I2C) + #elif (defined(CONFIG_TSEC_ENET) || defined(CONFIG_ETHER_ON_FCC)) + #define CONFIG_COMMANDS (CONFIG_CMD_DFL | CFG_CMD_MII | \ + CFG_CMD_ELF | \ + CFG_CMD_PING | CFG_CMD_I2C) + #endif +#endif + +#include <cmd_confdefs.h> + +#undef CONFIG_WATCHDOG /* watchdog disabled */ + +/* + * Miscellaneous configurable options + */ +#define CFG_LONGHELP /* undef to save memory */ +#define CFG_PROMPT "SBC8560=> " /* Monitor Command Prompt */ +#if (CONFIG_COMMANDS & CFG_CMD_KGDB) + #define CFG_CBSIZE 1024 /* Console I/O Buffer Size */ +#else + #define CFG_CBSIZE 256 /* Console I/O Buffer Size */ +#endif +#define CFG_PBSIZE (CFG_CBSIZE+sizeof(CFG_PROMPT)+16) /* Print Buffer Size */ +#define CFG_MAXARGS 16 /* max number of command args */ +#define CFG_BARGSIZE CFG_CBSIZE /* Boot Argument Buffer Size */ +#define CFG_LOAD_ADDR 0x1000000 /* default load address */ +#define CFG_HZ 1000 /* decrementer freq: 1 ms ticks */ + +/* + * For booting Linux, the board info and command line data + * have to be in the first 8 MB of memory, since this is + * the maximum mapped by the Linux kernel during initialization. + */ +#define CFG_BOOTMAPSZ (8 << 20) /* Initial Memory map for Linux */ + +/* Cache Configuration */ +#define CFG_DCACHE_SIZE 32768 +#define CFG_CACHELINE_SIZE 32 +#if (CONFIG_COMMANDS & CFG_CMD_KGDB) + #define CFG_CACHELINE_SHIFT 5 /* log base 2 of the above value */ +#endif + +/* + * Internal Definitions + * + * Boot Flags + */ +#define BOOTFLAG_COLD 0x01 /* Normal Power-On: Boot from FLASH */ +#define BOOTFLAG_WARM 0x02 /* Software reboot */ + +#if (CONFIG_COMMANDS & CFG_CMD_KGDB) + #define CONFIG_KGDB_BAUDRATE 230400 /* speed to run kgdb serial port */ + #define CONFIG_KGDB_SER_INDEX 2 /* which serial port to use */ +#endif + +/*Note: change below for your network setting!!! */ +#if defined(CONFIG_TSEC_ENET) || defined(CONFIG_ETHER_ON_FCC) +# define CONFIG_ETHADDR 00:01:af:07:9b:8a +# define CONFIG_HAS_ETH1 +# define CONFIG_ETH1ADDR 00:01:af:07:9b:8b +# define CONFIG_HAS_ETH2 +# define CONFIG_ETH2ADDR 00:01:af:07:9b:8c +#endif + +#define CONFIG_SERVERIP 192.168.0.131 +#define CONFIG_IPADDR 192.168.0.105 +#define CONFIG_GATEWAYIP 0.0.0.0 +#define CONFIG_NETMASK 255.255.255.0 +#define CONFIG_HOSTNAME SBC8560 +#define CONFIG_ROOTPATH /home/ppc +#define CONFIG_BOOTFILE pImage + +#endif /* __CONFIG_H */

1 0

[U-Boot-Users] [PATCH] - request to change default debug assembly flags from stabs to dwarf2
by Wessel, Jason 01 Sep '05

01 Sep '05

The default for the C portion of the u-boot compile is set to dwarf-2 because the -g option for gcc 3.x defaults to dwarf-2, but the assembly portion is not. If possible, I would like to see the debug formats made consistent so as to allow the debugger to more reliably step through assembly source with gdb and other debuggers with the more modern dwarf2 debug format. I have tested this change with gcc 3.4.3 on Arm9, MPC82xx, PPC85xx, PPC 40x and PPC 44x. I also tested with ELDK 3.1.1 on all the PPC archs and it works quite well. Signed-off-by: Jason Wessel <jason.wessel(a)windriver.com> diff --git a/config.mk b/config.mk --- a/config.mk +++ b/config.mk @@ -133,7 +133,7 @@ CFLAGS := $(CPPFLAGS) -Wall -Wno-trigrap endif endif -AFLAGS_DEBUG := -Wa,-gstabs +AFLAGS_DEBUG := -Wa,-gdwarf2 AFLAGS := $(AFLAGS_DEBUG) -D__ASSEMBLY__ $(CPPFLAGS) LDFLAGS += -Bstatic -T $(LDSCRIPT) -Ttext $(TEXT_BASE) $(PLATFORM_LDFLAGS)

1 0

[U-Boot-Users] Port U-Boot to SBC-2410X
by luo.jinhua 01 Sep '05

01 Sep '05

hi, all. SBC-2410X is a board based on SAMSUNG S3C2410 made by friendly-arm, which is similiar to smdk2410. Now, I succeed to port U-Boot to SBC-2410X. In addition to write the new hardware-specific configurations for SBC-2410X according to steps from U-Boot's README, I make U-Boot's nand subsystem work on SBC-2410X and add to hush cmdline-editing (but AUTO_COMPLETE cannot work to go with it yet). About bugs of NAND subsystem ============================= The original nand subsystem lacks flash_chip-specific functions like NF_Conf and the related enum variable NFCE_STATE for each board, right? Though some boards put them in one sole head file in their board directory, it seems broken because the compilation always shows errors. Take VCMA9 board for example. Though VCMA9 defines NFCE_STATE, NF_Cmd etc in "board/mpl/vcma9/vcma9.h", but when compiling arm-linux-gcc will complains: In file included from /root/u-boot-1.1.3/include/config.h:2, from /root/u-boot-1.1.3/include/common.h:35, from cmd_nand.c:11: /root/u-boot-1.1.3/include/configs/VCMA9.h:280:1: warning: this is the location of the previous definition cmd_nand.c: In function `NanD_WaitReady': cmd_nand.c:557: warning: implicit declaration of function `NF_WaitRB' cmd_nand.c: In function `NanD_Command': cmd_nand.c:572: warning: implicit declaration of function `NF_Cmd' cmd_nand.c:566: warning: unused variable `nandptr' cmd_nand.c: In function `NanD_Address': cmd_nand.c:614: warning: implicit declaration of function `NF_Addr' cmd_nand.c: In function `NanD_IdentChip': cmd_nand.c:645: warning: implicit declaration of function `NF_SetCE' cmd_nand.c:645: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:645: error: (Each undeclared identifier is reported only once cmd_nand.c:645: error: for each function it appears in.) cmd_nand.c:652: error: `NFCE_HIGH' undeclared (first use in this function) cmd_nand.c:671: warning: implicit declaration of function `NF_Read' cmd_nand.c: In function `NanD_ReadBuf': cmd_nand.c:812: warning: unused variable `nandptr' cmd_nand.c: In function `nand_read_ecc': cmd_nand.c:915: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:1029: error: `NFCE_HIGH' undeclared (first use in this function) cmd_nand.c: In function `nand_write_page': cmd_nand.c:1136: warning: implicit declaration of function `NF_Write' cmd_nand.c:1047: warning: unused variable `nandptr' cmd_nand.c: In function `nand_write_ecc': cmd_nand.c:1278: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:1324: error: `NFCE_HIGH' undeclared (first use in this function) cmd_nand.c: In function `nand_read_oob': cmd_nand.c:1356: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:1385: error: `NFCE_HIGH' undeclared (first use in this function) cmd_nand.c: In function `nand_write_oob': cmd_nand.c:1407: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:1461: error: `NFCE_HIGH' undeclared (first use in this function) cmd_nand.c:1399: warning: unused variable `nandptr' cmd_nand.c: In function `nand_erase': cmd_nand.c:1530: error: `NFCE_LOW' undeclared (first use in this function) cmd_nand.c:1609: error: `NFCE_HIGH' undeclared (first use in this function) make[1]: *** [cmd_nand.o] Error 1 make[1]: Leaving directory `/root/u-boot-1.1.3/common' make: *** [common/libcommon.a] Error 2 I finally put them in "include/linux/mtd/nand.h", and it works. cmdline editing ================== Though U-Boot brings in hush, it lacks cmdline-editing. That is inconvenient. I pick codes heavily borrowed from vivi bootloader and integrate them into U-Boot. Now, the hush can locate the history command and acts like xterm. I would like to pack the new board codes and nand subsystem fixes as one patch, while the cmdline-editing codes (in "common/main.c") is the other. Is this ok? gdlc mail Open WebMail Project (http://openwebmail.org)

3 5