ppcboot boot-up question

ppcboot boot-up question

[Todd]

I'm using PPCBoot 2.0.0
I have my PPC 750 setup to delay for 5sec then boot
from the DiskOnChip.  This works properly, as long as
I have an active serial connection to the board.
However, I've noticed that if there is not an active
serial connection to the board, the autoboot function
will not work.  If I reset the board, with no serial
connection, then start minicom after 10 seconds I
always find the following:

=> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
syntax error
=>

Does anyone know what I am doing wrong??

These are my environmental variables:

baudrate=9600
preboot=
clocks_in_mhz=1
hostname=spyder
ethaddr=00:c0:e5:10:0:99
serverip=10.1.1.107
gatewayip=10.1.1.1
ipaddr=10.1.1.28
netmask=255.255.255.0
nfs_bootfile=gesppc2
doc_bootfile=no_nfs_pImage
bootdelay=5
rootpath=/opt/timesys/linux/4.0/gesppc2/rfs
bootcmd=docboot 6000000 0
bootargs=root=/dev/nftla1 rw
ip=10.1.1.28::10.1.1.1:255.255.255.0:spyder:eth0:off
autostart=yes
autoload=yes
stdin=serial
stdout=serial
stderr=serial

Environment size: 438/4092 bytes


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

RE: ppcboot boot-up question

[VanBaren, Gerald (AGRE)]

You probably need the serial handshake lines properly terminated, or hardware handshaking disabled, so that your boot process isn't waiting for the handshake lines to go active.  For a test, make a DB-9 (or whatever) with RTS connected to CTS and DSR connected to DTR and DCD.  Plug this into your board and I suspect it will boot fine.

The "AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0" is minicom trying to initialize your modem (which obviously doesn't exist).  This can be ignored, but a better solution is to switch to ckermit (as Wolfgang would strongly recommend ;-) or change your minicom default initialization by deleting all the modem initialization strings.

gvb


> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Todd
> Sent: Monday, February 02, 2004 4:40 PM
> To: linuxppc-embedded@lists.linuxppc.org
> Subject: ppcboot boot-up question
>
>
>
> I'm using PPCBoot 2.0.0
> I have my PPC 750 setup to delay for 5sec then boot
> from the DiskOnChip.  This works properly, as long as
> I have an active serial connection to the board.
> However, I've noticed that if there is not an active
> serial connection to the board, the autoboot function
> will not work.  If I reset the board, with no serial
> connection, then start minicom after 10 seconds I
> always find the following:
>
> => AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
> syntax error
> =>
>
> Does anyone know what I am doing wrong??
>
> These are my environmental variables:
>
> baudrate=9600
> preboot=
> clocks_in_mhz=1
> hostname=spyder
> ethaddr=00:c0:e5:10:0:99
> serverip=10.1.1.107
> gatewayip=10.1.1.1
> ipaddr=10.1.1.28
> netmask=255.255.255.0
> nfs_bootfile=gesppc2
> doc_bootfile=no_nfs_pImage
> bootdelay=5
> rootpath=/opt/timesys/linux/4.0/gesppc2/rfs
> bootcmd=docboot 6000000 0
> bootargs=root=/dev/nftla1 rw
> ip=10.1.1.28::10.1.1.1:255.255.255.0:spyder:eth0:off
> autostart=yes
> autoload=yes
> stdin=serial
> stdout=serial
> stderr=serial
>
> Environment size: 438/4092 bytes
>
>


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

Re: ppcboot boot-up question

[Wolfgang Denk]

In message <20040202213949.30276.qmail@web40408.mail.yahoo.com> you wrote:
>
> I'm using PPCBoot 2.0.0

... which is ancient.

> I have my PPC 750 setup to delay for 5sec then boot
> from the DiskOnChip.  This works properly, as long as
> I have an active serial connection to the board.
> However, I've noticed that if there is not an active
> serial connection to the board, the autoboot function
> will not work.  If I reset the board, with no serial
> connection, then start minicom after 10 seconds I
> always find the following:
>
> => AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
> syntax error

It seems you configured miniom to send a modem init string.  This  is
not expected by PPCBoot.

> Does anyone know what I am doing wrong??

You use minicom.

You post to the wrong list (u-boot-users is a much better  place  for
such questions).

You don't provide any details. Maybe the serial driver on your  board
is waiting for a hardware handshake signal (DCD?) which is down while
disconnected? What happens when you disconnect the cable?

Best regards,

Wolfgang Denk

--
See us @ Embedded World, Nuremberg, Feb 17 - 19,  Hall 12.0 Booth 440
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I see that Microsoft's campaign  to  destroy  all  knowledge  of  any
operating   environment   but  its  own  environment-of-the-year  has
succeeded in creating a generation of users who don't understand  the
concept of a shell...
            -- L. Peter Deutsch in <m0x5jNX-000R2UC@lamp.aladdin.com>

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

Re: ppcboot boot-up question

[Todd]

As Gerald suggested, I tried disconnecting the serial
cable, which allowed the board to boot.
Changing the minicom instructions in the following way
allowed the board to boot with the serial cable
connected:

ctl-a, z, o, "modem and dialing"
remove entries for items A - L
save as the default file.

I am looking into converting over to ckermit.
Thanks Wolfgang and Gerald for responding to my
question.

best regards,
Todd


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