From: Federico Lucifredi Date: Thu, 02 Dec 2004 15:48:30 +0000 Subject: [U-Boot-Users] Re: U-Boot-Users digest, Vol 1 #1118 - 11 msgs Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello U-booters, Can someone shine some light on the TOC pointer's purpose and use in U-boot code? Hit me with the clue stick, please =) -Federico > -----Original Message----- > From: u-boot-users-request at lists.sourceforge.net [mailto:u-boot-users-request at lists.sourceforge.net] > Sent: Thursday, December 2, 2004 04:21 AM > To: u-boot-users at lists.sourceforge.net > Subject: U-Boot-Users digest, Vol 1 #1118 - 11 msgs > > Send U-Boot-Users mailing list submissions to > u-boot-users at lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/u-boot-users > or, via email, send a message with subject or body 'help' to > u-boot-users-request at lists.sourceforge.net > > You can reach the person managing the list at > u-boot-users-admin at lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of U-Boot-Users digest..." > > > Today's Topics: > > 1. Re: Welcome to the "U-Boot-Users" mailing list (Digest mode) (=?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?=) > 2. Port u-boot to a custom board with CPU S3C44B0X (=?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?=) > 3. help starting (Ilan Finci) > 4. Clarification regarding the Internal Flash Identification Code. (Vikrant_Basotra) > 5. Re: help starting (Wolfgang Denk) > 6. Re: Clarification regarding the Internal Flash Identification Code. (Wolfgang Denk) > 7. Re: help starting (Ilan Finci) > 8. Re: help starting (Wolfgang Denk) > 9. Re: help starting (Ilan Finci) > 10. Passing parameters (Santangelo Angelo (Tectel)) > 11. crosstool for PowerPc 8540 (Junita Ajith) > > --__--__-- > > Message: 1 > Date: Wed, 1 Dec 2004 12:36:06 +0800 > From: =?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?= > Reply-To: =?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?= > To: u-boot-users at lists.sourceforge.net > Subject: [U-Boot-Users] Re: Welcome to the "U-Boot-Users" mailing list (Digest mode) > > post to this list > > > --__--__-- > > Message: 2 > Date: Wed, 1 Dec 2004 14:27:35 +0800 > From: =?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?= > Reply-To: =?UTF-8?B?54Gw6ImyIOi9qOi/uQ==?= > To: u-boot-users at lists.sourceforge.net > Subject: [U-Boot-Users] Port u-boot to a custom board with CPU S3C44B0X > > Hi all. I'm porting u-boot to a custom board with CPU S3C44B0X now. > I modified include/configs/B2.h accroding to my configurations. > And I don't know how to set the u-boot's console as serial port. > Thanks for your replies. > > > --__--__-- > > Message: 3 > Date: Wed, 01 Dec 2004 08:44:11 +0200 > From: Ilan Finci > To: U-Boot users > Subject: [U-Boot-Users] help starting > > Hi, > I'm totally new to the world of porting U-Boot (or other boot loaders) > to new hardware. > > I have an older version of U-Boot (0.4.5) that was ported to 2 custom > made boards we have, based on the MPC5200 CPU, and the IceCube > evaluation board. Both has the same U-Boot up and running. > > We now have a new board, base on the same design, but with some > modification. > > I have BDI2000 up and running, and I can access the board's memory, > flash, cpu registers etc. > > When I try to run the same U-boot, it, as can be expected, fails to run, > and stop very soon after startup (no message comes out on the serial > console). > > I've tried to connect with GDB to debug, and I manage to do it, then > step few commands, and I get SIGSTOP. To make sure that this is not a > problem of the new board, I've tried the same with a working board, and > the U-Boot fails at the same place (right after the starting point). On > the other hand, if I don't try to do a step by step debugging, but give > a "cont" command, the U-boot (on the older board) does work. > > So I guess I have a basic problem in understanding how to debug the > U-Boot with GDB. > > Any help (either specific, or pointers to guides), will be great. > > Thanks, > Ilan > > > --__--__-- > > Message: 4 > From: Vikrant_Basotra > To: u-boot-users at lists.sourceforge.net > Date: Wed, 1 Dec 2004 12:52:44 +0530 > Subject: [U-Boot-Users] Clarification regarding the Internal Flash Identification Code. > > Hi All > In the file "include/flash.h" some # defines are there e.g for > Intel StrataFlash 28F320J5 three Macros (hash define values) are there: > > #define INTEL_MANUFACT 0x00890089 /*INTEL manuf. ID in D23..D16, > D7..D0 */ > #define INTEL_ID_28F320J5 0x00140014 /* 32M = 128K x 32 */ > #define FLASH_28F320J5 0x0085 /* Intel 28F320J5 ( 4M = 128K x 32 ) */ > > Since I am using Intel StrataFlash 28F256J3, I have to define the three > required macros accordingly: > > #define INTEL_MANUFACT 0x00890089 /*INTEL Manufacturer. ID */ > #define INTEL_ID_28F256J3 0x001D001D /*Device ID*/ > > > #define FLASH_28F256J3 /*Internal Flash Identification Code*/ > > I got the Device Id value from the Intel Site but I didn't found any thing > like Internal Flash Identification Code. Is this value is to be supplied by > the vendor if not then what value should I have to assign to the Macro > FLASH_28F256J3. > > Best Regards, > Vikrant Basotra > > ************************************************************************** > 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. > ************************************************************************** > > > --__--__-- > > Message: 5 > To: Ilan Finci > Cc: U-Boot users > From: Wolfgang Denk > Subject: Re: [U-Boot-Users] help starting > Date: Wed, 01 Dec 2004 08:22:25 +0100 > > In message <41AD683B.9080105@finci.org> you wrote: > > > > So I guess I have a basic problem in understanding how to debug the > > U-Boot with GDB. > > Did you read the "Debugging" section in the manual? > > See http://www.denx.de/twiki/bin/view/DULG/DebuggingUBoot > > Best regards, > > Wolfgang Denk > > -- > Software Engineering: Embedded and Realtime Systems, Embedded Linux > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de > Uuencode/uudecode is just a mickey-mouse archiver. > - Doug Gwyn in <1995Mar4.011139.22820@arl.mil> > > > --__--__-- > > Message: 6 > To: Vikrant_Basotra > Cc: u-boot-users at lists.sourceforge.net > From: Wolfgang Denk > Subject: Re: [U-Boot-Users] Clarification regarding the Internal Flash Identification Code. > Date: Wed, 01 Dec 2004 09:13:39 +0100 > > In message <3D9FDCA910DD4445896A0BE5ECF009D401CCAA1F@bla.satyam.com> you wrote: > > > > I got the Device Id value from the Intel Site but I didn't found any thing > > like Internal Flash Identification Code. Is this value is to be supplied by > > the vendor if not then what value should I have to assign to the Macro > > FLASH_28F256J3. > > As the name "Internal FLASH identification codes" suggests this is a > code that is _internal_ to U-Boot so you will not find it mentioned > in any vendor documentation (at least not before they are sterting to > manufacture "U-Boot flash chips" :-) > > Just chose the next unused entry, but keep in mind that odd numbers > are used only for "bottom boot sector" types! > > > Best regards, > > Wolfgang Denk > > -- > Software Engineering: Embedded and Realtime Systems, Embedded Linux > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de > HEALTH WARNING: Care Should Be Taken When Lifting This Product, Since > Its Mass, and Thus Its Weight, Is Dependent on Its Velocity Relative > to the User. > > > --__--__-- > > Message: 7 > Date: Wed, 01 Dec 2004 11:06:57 +0200 > From: Ilan Finci > To: Wolfgang Denk > CC: U-Boot users > Subject: Re: [U-Boot-Users] help starting > > Hi, > Yes I've read it, but when I try this (on the older board, where the > u-boot is working), the gdb doesn't stop at that function, just continue > (and over the serial terminal, I see the normal u-boot messages, and > later auto booting into linux). > > Here is the screen dump of what I've done: > > U-Boot $ powerpc-linux-gdb u-boot > GNU gdb 5.3 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "--host=i686-pc-linux-gnu > --target=powerpc-linux"... > (gdb) target remote jtag2:2001 > Remote debugging using jtag2:2001 > _start () at /homes/ifinci/secure/work/SeeQNet/U-Boot/cpu/mpc5xxx/start.S:91 > 91 li r21, BOOTFLAG_COLD /* Normal Power-On > */ > (gdb) b cpu_init_f > Breakpoint 1 at 0xfff03a34: file cpu_init.c, line 53. > (gdb) c > Continuing. > > > and I don't get the GDB prompt back unless I press CTRL+C. > > Any idea? > > Thanks, > Ilan > > on 12/01/04 09:22 Wolfgang Denk said the following: > > In message <41AD683B.9080105@finci.org> you wrote: > > > >>So I guess I have a basic problem in understanding how to debug the > >>U-Boot with GDB. > > > > > > Did you read the "Debugging" section in the manual? > > > > See http://www.denx.de/twiki/bin/view/DULG/DebuggingUBoot > > > > Best regards, > > > > Wolfgang Denk > > > > > > --__--__-- > > Message: 8 > To: Ilan Finci > Cc: U-Boot users > From: Wolfgang Denk > Subject: Re: [U-Boot-Users] help starting > Date: Wed, 01 Dec 2004 12:13:05 +0100 > > In message <41AD89B1.2020904@finci.org> you wrote: > > > > Yes I've read it, but when I try this (on the older board, where the > > u-boot is working), the gdb doesn't stop at that function, just continue > > (and over the serial terminal, I see the normal u-boot messages, and > > later auto booting into linux). > > Is your BDI is configured to use hardware breakpoints? > > Best regards, > > Wolfgang Denk > > -- > Software Engineering: Embedded and Realtime Systems, Embedded Linux > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de > "Open the pod bay doors, HAL." - Dave Bowman, 2001 > > > --__--__-- > > Message: 9 > Date: Wed, 01 Dec 2004 13:20:46 +0200 > From: Ilan Finci > To: Wolfgang Denk > CC: U-Boot users > Subject: Re: [U-Boot-Users] help starting > > Apparently not :( > > Setting it to use hardware BP, did the trick. > > Thanks, > Ilan > > on 12/01/04 13:13 Wolfgang Denk said the following: > > In message <41AD89B1.2020904@finci.org> you wrote: > > > >>Yes I've read it, but when I try this (on the older board, where the > >>u-boot is working), the gdb doesn't stop at that function, just continue > >>(and over the serial terminal, I see the normal u-boot messages, and > >>later auto booting into linux). > > > > > > Is your BDI is configured to use hardware breakpoints? > > > > Best regards, > > > > Wolfgang Denk > > > > > > --__--__-- > > Message: 10 > Date: Wed, 1 Dec 2004 15:25:09 +0100 > From: "Santangelo Angelo (Tectel)" > To: > Subject: [U-Boot-Users] Passing parameters > > This is a multi-part message in MIME format. > > ------_=_NextPart_001_01C4D7B1.8FFD0AC8 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > Hi at all, > I'm already here with a new question. > =20 > My problem is passing bootarg on my kernel. > =20 > I set bootargs on u-boot with > set bootarg=3Droot=3D/dev/ram rw mem=3D64M console=3DttyS0,115200n8 = > initd=3D0xA2A00000,8M > but after bootm command ( bootm 40000 ) > the kernel sto with this message > Uncompressing = > Linux........................................................ done > , booting the kernel. > =20 > where I mistake ? > =20 > Thanks a lot > Angelo > > ------_=_NextPart_001_01C4D7B1.8FFD0AC8 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > Messaggio > charset=3Dwindows-1252"> > > >
Hi at=20 > all,
>
I'm = > already here=20 > with a new question.
>
size=3D2> 
>
My = > problem is=20 > passing bootarg on my kernel.
>
size=3D2> 
>
I set = > bootargs on=20 > u-boot with
>
    face=3DArial=20 > size=3D2>set bootarg=3D face=3DArial=20 > size=3D2>root=3D/dev/ram rw  mem=3D64M console=3DttyS0,115200n8=20 > initd=3D0xA2A00000,8M
>
class=3D288322014-01122004> but after bootm command ( bootm 40000=20 > )
>
class=3D288322014-01122004>the kernel sto with this=20 > message
>
class=3D288322014-01122004>Uncompressing=20 > Linux........................................................ done
, = > booting=20 > the kernel.
>
class=3D288322014-01122004> 
>
class=3D288322014-01122004>where I mistake ?
>
class=3D288322014-01122004> 
>
class=3D288322014-01122004>Thanks a lot
>
class=3D288322014-01122004>Angelo
> > =00 > ------_=_NextPart_001_01C4D7B1.8FFD0AC8-- > > > --__--__-- > > Message: 11 > Date: Wed, 1 Dec 2004 17:21:34 -0800 (PST) > From: Junita Ajith > To: u-boot-users at lists.sourceforge.net > Subject: [U-Boot-Users] crosstool for PowerPc 8540 > > > Hi > Could anyone suggest me the toolchain to be used to > compile u-boot-1.1.1 for a PowerPC 8540 board? > > I tried with the crosstool-0.27 (www.kegel.com) > which is supposed to be the stable version ,and built > a toolchain with gcc-3.3.2 and glibc-2.3.2. > > I could successfully build my toolchain and create > my u-boot binary for 8540. > > But when I flash u-boot.bin , the board doesnt come > up. > > Any help would be appreciated. > > Thanks, > Junita > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - You care about security. So do we. > http://promotions.yahoo.com/new_mail > > > > --__--__-- > > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users > > > End of U-Boot-Users Digest >