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/
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/
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/
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/
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/