SCC1 on 860 Ethernet, PortA TxD (PA14) setting.

SCC1 on 860 Ethernet, PortA TxD (PA14) setting.

[Subodh Nijsure]

Hello,

I am trying to get ethernet on SCC1 going for my custom board.
PA15 is used for RXD (input) and PA14 for TXD (output).

But i noticed that in the "standard" SCC driver (file enet.c) for SCC
both PA14 (RXD) and PA15 (TXD) pins are cleared in
PADIR register. Shouldn't PA15 bit in PADIR register be set to one (output)?

Also Motorola 860 manual lists following step --
"Configure port A to enable TXD1 and RXD1. Set PAPAR( 14,15) and clear PADIR
[ 14, 15 ]
and PAODR [ 14 ]"

Why should TXD be set as input  instead of output?


/Subodh Nijsure


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: SCC1 on 860 Ethernet, PortA TxD (PA14) setting.

[Dan Malek]

Subodh Nijsure wrote:

> Why should TXD be set as input  instead of output?

When a pin is not configured as a general purpose output (as is the
case here), the other registers become special configuration registers
for that specific use.  Or, stated another way, the direction bits
only imply direction when the pin is configured for GPIO.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Question about RPXclassic (RPXCLLF)

[SangTae Ha]

I am using your BDI2000 product. I have a question about FLASH TYPE. My evaluation board is RPXclassic(RPXCLLF) from Embedded Planet. Everything works fine except flash memory. I already got the flash information from the flash. It is a kind of "Am29LV160". My flash memory consists of 4 Am29LV169 flash memory and comes 8Mbytes. I've tried many flash types found in BDI2000 manual for a few days but I didn't get it. Please tell me what FLASH TYPE, CHIPSIZE and BUSWIDTH should I use.

Thanks in advance.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RPXclassic PPCBOOT on RAM

[SangTae Ha]

I am trying to have the PPCBOOT work on RPXclassic board. I've already port the 8xxROM this board already but I've failed with PPCBOOT. All configuration parameters are same with 8xxROM and my BDI2000 didn't get the flash information of RPXClassic (FLASH TYPE, CHIPSIZE, BUSWIDTH), therefore I really want to test the PPCBOOT on RAM space first to debug. In order to make srec file run on RAM space, I changed TEXT_BASE=0x00100000 parameter in config.mk. I think there woule be many efficient debugging techniques. I am currently using BDI2000, as I mentioned above, but I couldn't get the flash work. How can I debug the PPCBOOT efficiently in my current stage? Any comments would be appreciated.

Thanks in advance.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: RPXclassic PPCBOOT on RAM

[Yoo. Jonghoon]

>From my experience, it is required at least 3 things to
be changed If ppcboot works well from flash,
(1) TEXT_BASE to be located in RAM
(2) set CFG_MONITOR_BASE equal to TEXT_BASE
(3) skip DRAM initializaion sequence in func. initdram(),
     except returning size of DRAM.

Good luck to you

===============================================
Yoo. Jonghoon,        IPone inc.
===============================================
e-mail : yooth@ipone.co.kr
tel : 82-2-02-2222-4631
===============================================

> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of SangTae Ha
> Sent: Monday, June 25, 2001 2:45 PM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: RPXclassic PPCBOOT on RAM
>
>
>
> I am trying to have the PPCBOOT work on RPXclassic board. I've
> already port the 8xxROM this board already but I've failed with
> PPCBOOT. All configuration parameters are same with 8xxROM and my
> BDI2000 didn't get the flash information of RPXClassic (FLASH
> TYPE, CHIPSIZE, BUSWIDTH), therefore I really want to test the
> PPCBOOT on RAM space first to debug. In order to make srec file
> run on RAM space, I changed TEXT_BASE=0x00100000 parameter in
> config.mk. I think there woule be many efficient debugging
> techniques. I am currently using BDI2000, as I mentioned above,
> but I couldn't get the flash work. How can I debug the PPCBOOT
> efficiently in my current stage? Any comments would be appreciated.
>
> Thanks in advance.
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: RPXclassic PPCBOOT on RAM

[Wolfgang Denk]

In message <010601c0fd39$ef0cca90$3877b5d3@dolbae> you wrote:
>
> I am trying to have the PPCBOOT work on RPXclassic board. I've

I don't see any Linux content in this message, so it's off  topic  in
this mailing list.

Chances to receive help for PPCBoot porting issues are much better in
the PPCBoot User's mailing list.

> already port the 8xxROM this board already but I've failed with
> PPCBOOT. All configuration parameters are same with 8xxROM and my
> BDI2000 didn't get the flash information of RPXClassic (FLASH TYPE,
> CHIPSIZE, BUSWIDTH), therefore I really want to test the PPCBOOT on

When you don't have such basic hardware information you better forget
about low-level work like porting PPCBoot.

> RAM space first to debug. In order to make srec file run on RAM

This is not a good idea.

Executing code from the boot device (flash memory)  is  the  simplest
thing  you  can  do.  Running  from (SD)RAM is MUCH more complicated,
since it needs a LOT of  initialization  which  must  be  correct  or
you'll just see random problems.

It is NOT a good idea to try complicated things as long as you  don't
have the muchg simpler things running first.

> there woule be many efficient debugging techniques. I am currently
> using BDI2000, as I mentioned above, but I couldn't get the flash
> work. How can I debug the PPCBOOT efficiently in my current stage?

Why not? You know the flash type. There are two ways to attach it  to
the  bus  (as  8  or as 16 bit devices), and there are 4 possibel bus
widths (8, 16, or 32 bit). Even without any further information it is
just a couple of minutes to try out these 8 possible combinations.

When you cannot get flash working, I guarantee  you  will  fail  with
SDRAM, too.

> Any comments would be appreciated.

Try simple things first.

And better post such questions to the ppcboot mailing list.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
panic: kernel trap (ignored)

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: RPXclassic PPCBOOT on RAM

[SangTae Ha]

I agree with you that this topic may not be directly related with this board. I will use appropriate mailing lists instead. Thank you very much for your valuable feedback. However, I had to say that your comment is hardly useful since I already tried possible basic things, you mentioned, such as  flash type and width. I've used BDI debugger before doing linux work since my early projects. It was very successful for my several projects. I've got the detailed information about the informations  from ABATRON's Reudi but my configuration for board is same with him. I wantd to reduce my time for checking others before Reudi answers for my question. Anyway, I will test the hardware first and finally find what's wrong with it.

Thanks.

----- Original Message -----
From: "Wolfgang Denk" <wd@denx.de>
To: "SangTae Ha" <stha@postech.edu>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Monday, June 25, 2001 5:48 PM
Subject: Re: RPXclassic PPCBOOT on RAM


> In message <010601c0fd39$ef0cca90$3877b5d3@dolbae> you wrote:
> >
> > I am trying to have the PPCBOOT work on RPXclassic board. I've
>
> I don't see any Linux content in this message, so it's off  topic  in
> this mailing list.
>
> Chances to receive help for PPCBoot porting issues are much better in
> the PPCBoot User's mailing list.

OK.

>
> > already port the 8xxROM this board already but I've failed with
> > PPCBOOT. All configuration parameters are same with 8xxROM and my
> > BDI2000 didn't get the flash information of RPXClassic (FLASH TYPE,
> > CHIPSIZE, BUSWIDTH), therefore I really want to test the PPCBOOT on
>
> When you don't have such basic hardware information you better forget
> about low-level work like porting PPCBoot.

I just wanted to know other debugging techinques to save my time.

>
> > RAM space first to debug. In order to make srec file run on RAM
>
> This is not a good idea.

OK

>
> Executing code from the boot device (flash memory)  is  the  simplest
> thing  you  can  do.  Running  from (SD)RAM is MUCH more complicated,
> since it needs a LOT of  initialization  which  must  be  correct  or
> you'll just see random problems.
>
> It is NOT a good idea to try complicated things as long as you  don't
> have the muchg simpler things running first.

OK

>
> > there woule be many efficient debugging techniques. I am currently
> > using BDI2000, as I mentioned above, but I couldn't get the flash
> > work. How can I debug the PPCBOOT efficiently in my current stage?
>
> Why not? You know the flash type. There are two ways to attach it  to
> the  bus  (as  8  or as 16 bit devices), and there are 4 possibel bus
> widths (8, 16, or 32 bit). Even without any further information it is
> just a couple of minutes to try out these 8 possible combinations.

I've tried all possible configurations already. I've got this problem for the first time in my project.
BDI2000 could be one of the suspicious problems, I guess. I will check.

>
> When you cannot get flash working, I guarantee  you  will  fail  with
> SDRAM, too.
>
> > Any comments would be appreciated.
>
> Try simple things first.

OK

>
> And better post such questions to the ppcboot mailing list.
>
> Wolfgang Denk
>
> --
> Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
> Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
> panic: kernel trap (ignored)
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/