Steven Scholz | 4 Feb 2003 10:05
Picon
Favicon

[PPCBoot-users] [PATCH] Support for RTC DS1307

Hi there,

please find the attached patch adding support for a new I2C RTC DS1307 to u-boot 
_and_ ppcboot-2.0.0.

Please comment about how I handle the year.

Thanks a million,

Steven

CHANGELOG:
==========
* Added DS1307 RTC driver
   Patch by Steven Scholz, 4 Feb 2003

README:
=======
--- README.orig Tue Feb  4 09:52:24 2003
+++ README      Tue Feb  4 09:58:25 2003
 <at>  <at>  -624,6 +624,7  <at>  <at> 
                 CONFIG_RTC_MPC8xx       - use internal RTC of MPC8xx
                 CONFIG_RTC_PCF8563      - use Philips PCF8563 RTC
                 CONFIG_RTC_MC146818     - use MC146818 RTC
+               CONFIG_RTC_DS1307       - use Maxim, Inc. DS1307 RTC
                 CONFIG_RTC_DS1337       - use Maxim, Inc. DS1337 RTC

  - Timestamp Support:
(Continue reading)

Wolfgang Denk | 4 Feb 2003 16:55
Picon
Picon
Favicon

Re: [PPCBoot-users] [PATCH] Support for RTC DS1307

In message <3E3F8247.7090801 <at> imc-berlin.de> you wrote:
>
> please find the attached patch adding support for a new I2C RTC DS1307 to u-boot 
> _and_ ppcboot-2.0.0.

Thanks, but the development of PPCBoot has been stopped, and the code
is frozen.

_all_ further effort goes into the U-Boot project only.

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd <at> denx.de
Microsoft Multitasking:
                     several applications can crash at the same time.
Wolfgang Denk | 4 Feb 2003 16:55
Picon
Picon
Favicon

Re: [PPCBoot-users] [PATCH] Support for RTC DS1307

In message <3E3F8247.7090801 <at> imc-berlin.de> you wrote:
>
> please find the attached patch adding support for a new I2C RTC DS1307 to u-boot 
> _and_ ppcboot-2.0.0.

Thanks, but the development of PPCBoot has been stopped, and the code
is frozen.

_all_ further effort goes into the U-Boot project only.

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd <at> denx.de
Microsoft Multitasking:
                     several applications can crash at the same time.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
Edward Paul | 5 Feb 2003 05:47
Picon
Favicon

[PPCBoot-users] ppcboot build problems

I am a Linux newbie using

binutils-2.11.2
gcc-2.95.3
glibc-2.2.3
glibc-linuxthreads-2.2.3

cross compiled for PPC.  

I think I am making some silly mistake.  I ask that
your mercy fall on me...

I do a make ADS860_config and then a "make all" and
get the foll errors:
....
gcc -Wall -pedantic -O -I/opt/powerpc/include -c -o
astest.o astest.c
gcc -Wall -pedantic -O -I/opt/powerpc/include -o
astest astest.o error.o -L/opt/
powerpc/lib -lbfd -liberty
/usr/lib/libbfd.a(srec.o): In function
`srec_bad_byte':
/root/cross/builds/powerpc-linux-gdb/bfd/../../gdb-5.2.1/bfd/srec.c:293:
undefin
ed reference to `_sch_istable'
/usr/lib/libbfd.a(srec.o): In function `srec_scan':
/root/cross/builds/powerpc-linux-gdb/bfd/../../gdb-5.2.1/bfd/srec.c:420:
undefin
ed reference to `_sch_istable'
/usr/lib/libbfd.a(binary.o): 
(Continue reading)

Wolfgang Denk | 5 Feb 2003 09:10
Picon
Picon
Favicon

Re: [PPCBoot-users] ppcboot build problems

Hello,

in message <20030205044737.67101.qmail <at> web13305.mail.yahoo.com> you wrote:
> I am a Linux newbie using
> 
> binutils-2.11.2
> gcc-2.95.3
> glibc-2.2.3
> glibc-linuxthreads-2.2.3
> 
> cross compiled for PPC.  

Building a working toolchain is not exactly trivial. I guess you made
some errors. At least for a test you should try to use tools that are
known to be working, for example our ELDK.

> I think I am making some silly mistake.  I ask that
> your mercy fall on me...
> 
> I do a make ADS860_config and then a "make all" and
> get the foll errors:
> ....
> gcc -Wall -pedantic -O -I/opt/powerpc/include -c -o
> astest.o astest.c
> gcc -Wall -pedantic -O -I/opt/powerpc/include -o
> astest astest.o error.o -L/opt/
> powerpc/lib -lbfd -liberty
> /usr/lib/libbfd.a(srec.o): In function
> `srec_bad_byte':
> /root/cross/builds/powerpc-linux-gdb/bfd/../../gdb-5.2.1/bfd/srec.c:293:
(Continue reading)

Wolfgang Denk | 5 Feb 2003 09:10
Picon
Picon
Favicon

Re: [PPCBoot-users] ppcboot build problems

Hello,

in message <20030205044737.67101.qmail <at> web13305.mail.yahoo.com> you wrote:
> I am a Linux newbie using
> 
> binutils-2.11.2
> gcc-2.95.3
> glibc-2.2.3
> glibc-linuxthreads-2.2.3
> 
> cross compiled for PPC.  

Building a working toolchain is not exactly trivial. I guess you made
some errors. At least for a test you should try to use tools that are
known to be working, for example our ELDK.

> I think I am making some silly mistake.  I ask that
> your mercy fall on me...
> 
> I do a make ADS860_config and then a "make all" and
> get the foll errors:
> ....
> gcc -Wall -pedantic -O -I/opt/powerpc/include -c -o
> astest.o astest.c
> gcc -Wall -pedantic -O -I/opt/powerpc/include -o
> astest astest.o error.o -L/opt/
> powerpc/lib -lbfd -liberty
> /usr/lib/libbfd.a(srec.o): In function
> `srec_bad_byte':
> /root/cross/builds/powerpc-linux-gdb/bfd/../../gdb-5.2.1/bfd/srec.c:293:
(Continue reading)

Jeff Carr | 5 Feb 2003 18:33

Re: [PPCBoot-users] ppcboot build problems

Try giving gcc --nostdlib (also -nostdinc if you want) when you compile.
That will insure it only looks for things where you tell it to.
Jeff
gcc -Wall -pedantic -O -I/opt/powerpc/include -o astest astest.o error.o
-L/opt/ -nostdlib

On Wed, 2003-02-05 at 02:10, Wolfgang Denk wrote:
> Hello,
> 
> in message <20030205044737.67101.qmail <at> web13305.mail.yahoo.com> you wrote:
> > I am a Linux newbie using
> > 
> > binutils-2.11.2
> > gcc-2.95.3
> > glibc-2.2.3
> > glibc-linuxthreads-2.2.3
> > 
> > cross compiled for PPC.  
> 
> Building a working toolchain is not exactly trivial. I guess you made
> some errors. At least for a test you should try to use tools that are
> known to be working, for example our ELDK.
> 
> > I think I am making some silly mistake.  I ask that
> > your mercy fall on me...
> > 
> > I do a make ADS860_config and then a "make all" and
> > get the foll errors:
> > ....
> > gcc -Wall -pedantic -O -I/opt/powerpc/include -c -o
(Continue reading)

Wolfgang Denk | 5 Feb 2003 22:28
Picon
Picon
Favicon

Re: [PPCBoot-users] ppcboot build problems

In message <1044466436.642.49.camel <at> jcwork> you wrote:
> Try giving gcc --nostdlib (also -nostdinc if you want) when you compile.
> That will insure it only looks for things where you tell it to.

This should NOT be necessary with any half-sane installation of  GCC;
the U-Boot Makefile's already take care off all these things.

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd <at> denx.de
How many QA engineers does it take to screw in a lightbulb? 3:  1  to
screw it in and 2 to say "I told you so" when it doesn't work.
Wolfgang Denk | 5 Feb 2003 22:28
Picon
Picon
Favicon

Re: [PPCBoot-users] ppcboot build problems

In message <1044466436.642.49.camel <at> jcwork> you wrote:
> Try giving gcc --nostdlib (also -nostdinc if you want) when you compile.
> That will insure it only looks for things where you tell it to.

This should NOT be necessary with any half-sane installation of  GCC;
the U-Boot Makefile's already take care off all these things.

Best regards,

Wolfgang Denk

--

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd <at> denx.de
How many QA engineers does it take to screw in a lightbulb? 3:  1  to
screw it in and 2 to say "I told you so" when it doesn't work.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
scsuh | 7 Feb 2003 12:20

[PPCBoot-users] MPC8245 with Intel 82551ER

Hi,

I use intel 82551ER Ethernet chip for MPC8245.

PPCBoot version is 2.0.0. (I found that it is the only version that supports 82559ER.)

 

I have some problems about intel 82551ER.

82551ER can receive packets but cannot update Actual Count field in RFD. So, packet length is always shown as 0.

And packet payload is sometimes crashed. When I download and boot the kernel image, ppcboot shows data crc error.

(I ignore data length error.)

 

System is,

             MPC8245 with 300Mhz

             64MB sdram

             4 intel 82551ER ethernet chip.

             1 intel 21152 pci to pci bridge

             1 hpt 371 pci to ide controller.

 

Below is my log. Can anyone suffer from the similar problem??

 

1 more, Does anyone have hpt 371 driver for ppcboot?

() is little endian format.

 

=> tftpboot 400000 abc.txt

eepro100_init.

        rx_buf_addr = 0xffffffff

        rx_buf_addr = 0xffffffff

        rx_buf_addr = 0xffffffff

        rx_buf_addr = 0xffffffff

i82559#0 configured

ARP broadcast 1

        tx_ring addr = 0x03fe7940

        tx_ring[0].command = 0x0cc0 (0xc00c)

        tx_ring[0].status = 0x00a0 (a000)

        tx_ring[0].link = 0x4079fe03 (03fe7940)

        tx_ring[0].tx_desc_addr = 0x5079fe03 (03fe7950)

        tx_ring[0].count = 0x00802001 (01208000)

        tx_ring[0].tx_buf_addr0 = 0x608bfe03 (03fe8b60)

        tx_ring[0].tx_buf_size0 = 0x2a000000 (0000002a)

        rx_ring addr[0] = 0x03fe6100

        rx_ring[0].control = 0x1000 (0010)

        rx_ring[0].status = 0x20a0 (a020)

        rx_ring[0].link = 0x1067fe03 (03fe6710)

        rx_ring[0].rx_buf_addr = 0xffff0000 (0000ffff)

        rx_ring[0].count = 0x00000006 (06000000)

        rx_ring[0].data = 0x03fe6110

bad length -14 < 28

TFTP from server 150.1.1.168; our IP address is 150.1.1.1

Filename 'abc.txt'.

Load address: 0x400000

Loading: *      tx_ring addr = 0x03fe7940

        tx_ring[0].command = 0x0cc0 (c00c)

        tx_ring[0].status = 0x00a0 (a000)

        tx_ring[0].link = 0x4079fe03 (03fe7940)

        tx_ring[0].tx_desc_addr = 0x5079fe03 (03fe7950)

        tx_ring[0].count = 0x00802001 (01208000)

        tx_ring[0].tx_buf_addr0 = 0x608bfe03 (03fe8b60)

        tx_ring[0].tx_buf_size0 = 0x3a000000 (0000003a)

        rx_ring addr[1] = 0x03fe6710

        rx_ring[1].control = 0x0000

        rx_ring[1].status = 0x20a0 (a020)

        rx_ring[1].link = 0x206dfe03 (03fe6d20)

        rx_ring[1].rx_buf_addr = 0xffff2d2b (2b2dffff)

        rx_ring[1].count = 0x00000006 (06000000)

        rx_ring[1].data = 0x03fe6720

len bad -14 < 84

#       tx_ring addr = 0x03fe7940

        tx_ring[0].command = 0x0cc0 (c00c)

        tx_ring[0].status = 0x00a0 (a000)

        tx_ring[0].link = 0x4079fe03 (03fe7940)

        tx_ring[0].tx_desc_addr = 0x5079fe03 (03fe7950)

        tx_ring[0].count = 0x00802001 (01208000)

        tx_ring[0].tx_buf_addr0 = 0x608bfe03 (03fe8b60)

        tx_ring[0].tx_buf_size0 = 0x2e000000 (0000002e)

 

done

Bytes transferred = 52 (34 hex)


Gmane