Re: [Ppcboot-users] Howto NetBSD standalone netbooting

Re: [Ppcboot-users] Howto NetBSD standalone netbooting

In message <54A1DDB4ACD5D511B0F900D0B7A8DC08978160 <at> cms1.etri.re.kr> you wrote:
> Could you tell me how to use mkimage? 

Call "mkimage" without arguments for a usage message.

Read the README for examples.

> I tries t, but it failed as just below.
> mkimage -A ppc -O netbsd -T kernel -C gzip -a 100000 -e 90000 -n netbsd.img
> -d netbsd.gz

You are missing the  name  of  the  output  file  here.  (As  called,
"netbsd.img"  is  the  descriptive  text  embedded with the image - I
think this is not what you wanted).

> And after that how to execute it??

Execute what? You mean, how to boot the image? Load it on the  target
and use the "bootm" command.

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
Harrisberger's Fourth Law of the Lab:
	Experience is directly proportional to the
	amount of equipment ruined.

Re: [Ppcboot-users] Howto NetBSD standalone netbooting

In message <54A1DDB4ACD5D511B0F900D0B7A8DC08978160 <at> cms1.etri.re.kr> you wrote:
> Could you tell me how to use mkimage? 

Call "mkimage" without arguments for a usage message.

Read the README for examples.

> I tries t, but it failed as just below.
> mkimage -A ppc -O netbsd -T kernel -C gzip -a 100000 -e 90000 -n netbsd.img
> -d netbsd.gz

You are missing the  name  of  the  output  file  here.  (As  called,
"netbsd.img"  is  the  descriptive  text  embedded with the image - I
think this is not what you wanted).

> And after that how to execute it??

Execute what? You mean, how to boot the image? Load it on the  target
and use the "bootm" command.

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
Harrisberger's Fourth Law of the Lab:
	Experience is directly proportional to the
	amount of equipment ruined.

Re: [Ppcboot-users] Serail console conflict from ppcboot to linux

On Thu, 28 Feb 2002 21:33:21 +0100
Wolfgang Denk <wd <at> denx.de> wrote:

> In message <20020228162001.2f66e817.cgagneraud <at> anfora.fr> you wrote:
> >
> > I have a mpc8260ads board and ppcboot work fine. 
> > I use HardHat linux 2.4.18-rc3.
> 
> Is there really a HHL kernel version 2.4.18-rc3 out there? Where?
yes I use rsync -rv source.mvista.com::linuxppc_2_4_devel .
> 
> 
> > Linux boot corectly (tftp+nfsroot) only if i put console=ttyS1,...
> > this way i dont see kernel messages but i have the prompt.
> > if i use ttyS0 then i dont have the login prompt and kernel stop in seria> l driver.
> 
> You must make sure that your  kernel  configuration  for  the  serial
> console  port matches that of PPCBoot; so if you use SCC1 for console
> in PPCBoot, you must make sure that the following #define's  are  set
> and  CORRECT  in  "arch/ppc/8260_io/uart.c"  when  building the Linux
> kernel: CONFIG_SCC_CONSOLE, CONFIG_SERIAL_CONSOLE_PORT
Ok, from my autoconf.h:
/*
 * Platform support
 */
#define CONFIG_PPC 1
#define CONFIG_PPC32 1
#define CONFIG_6xx 1
#undef  CONFIG_4xx
#undef  CONFIG_POWER3
#undef  CONFIG_8xx
#undef  CONFIG_PPC_ISERIES
#define CONFIG_8260 1
#define CONFIG_PPC_STD_MMU 1
#define CONFIG_SERIAL_CONSOLE 1
#define CONFIG_EST8260 1
#undef  CONFIG_SBS8260
#undef  CONFIG_RPX6
#undef  CONFIG_TQM8260
#undef  CONFIG_WILLOW
#undef  CONFIG_SMP
#define CONFIG_EMBEDDEDBOOT 1
...
/*
 * Macintosh device drivers
 */

/*
 * Character devices
 */
#undef  CONFIG_VT
#undef  CONFIG_SERIAL
#undef  CONFIG_SERIAL_EXTENDED
#undef  CONFIG_SERIAL_NONSTANDARD
#define CONFIG_UNIX98_PTYS 1
#define CONFIG_UNIX98_PTY_COUNT (256)
...
/*
 * MPC8260 Communication Options
 */
#define CONFIG_SCC_CONSOLE 1
#undef  CONFIG_SCC_ENET
#define CONFIG_FEC_ENET 1
#undef  CONFIG_FCC1_ENET
#define CONFIG_FCC2_ENET 1
#undef  CONFIG_FCC3_ENET
#undef  CONFIG_USE_MDIO

and my uart.c:
...
#ifdef CONFIG_SERIAL_CONSOLE
#include <linux/console.h>

/* SCC Console configuration.  Not quite finished.  The SCC_CONSOLE
 * should be the number of the SCC to use, but only SCC1 will
 * work at this time.
 */
#ifdef CONFIG_SCC_CONSOLE
#define SCC_CONSOLE 1
#endif

/* this defines the index into rs_table for the port to use
*/
#ifndef CONFIG_SERIAL_CONSOLE_PORT
#define CONFIG_SERIAL_CONSOLE_PORT	0
#endif
#endif
...
#ifndef SCC_CONSOLE
...
#else /* SCC_CONSOLE */
#define SCC_NUM_BASE	0	/* SCC base tty "number" */
#define SCC_IDX_BASE	0	/* table index */
static struct serial_state rs_table[] = {
	/* UART CLK   PORT          IRQ      FLAGS  NUM   */
	{ 0,     0, PROFF_SCC1, SIU_INT_SCC1,   0, SCC_NUM_BASE},
	{ 0,     0, PROFF_SCC2, SIU_INT_SCC2,   0, SCC_NUM_BASE + 1}, 
};
#endif /* SCC_CONSOLE */
...

So I have CONFIG_SERIAL_CONSOLE=1, SCC_CONSOLE=1, CONFIG_SERIAL_CONSOLE_PORT=0 
With this I normally have SCC1 as ttyS0 (rs_table[0]) and SCC2 as ttyS1 (rs_table[0]).
and with
T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100
T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
in my /etc/initab it would work but...

I think i have to resolv the Ppar,Psor,Pdir configuration.
I'm new in embedded linux and in PowerPC and i'm a young engineer (mostly hardware)!.

> 
> > I have to printk some messages because i havent debugger.
> 
> Get one. Life will be easier.
Yes, will be soon...
thanks.
Christian
> 
> 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
> Where people stand is not as important as which way they face.
>         - Terry Pratchett & Stephen Briggs, _The Discworld Companion_
> 
> _______________________________________________
> Ppcboot-users mailing list
> Ppcboot-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ppcboot-users
> 

--

-- 
/**********************************************
* Christian Gagneraud
***********************************************
* cgagneraud <at> anfora.fr
***********************************************
* ANFORA
* bat Actys, Voie3
* 31313 Labège Innopole
* FRANCE
***********************************************/

Re: [Ppcboot-users] Serail console conflict from ppcboot to linux

In message <20020301114603.2a141a06.cgagneraud <at> anfora.fr> you wrote:
>
> > Is there really a HHL kernel version 2.4.18-rc3 out there? Where?
> yes I use rsync -rv source.mvista.com::linuxppc_2_4_devel .

No.

Please note that this is NOT a MontaVista kernel.

It is just a MIRROR of the  official  source  tree  which  is  not  a
product  of MV but a result of the work of the Open Source community.
See http://penguinppc.org/dev/kernel.shtml for details.

> So I have CONFIG_SERIAL_CONSOLE=1, SCC_CONSOLE=1, CONFIG_SERIAL_CONSO> LE_PORT=0 
> With this I normally have SCC1 as ttyS0 (rs_table[0]) and SCC2 as ttyS1 (> rs_table[0]).
> and with
> T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100
> T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
> in my /etc/initab it would work but...

What do you mean "it would work"? Does this work, or not?

> I think i have to resolv the Ppar,Psor,Pdir configuration.

I rather guess it might be a problem of BRG initialization?

> I'm new in embedded linux and in PowerPC and i'm a young engineer (mostly>  hardware)!.

Don't apologize. We all started some day, it's just that some  of  us
are doing this a bit longer and/or more intense than others.

> > Get one. Life will be easier.
> Yes, will be soon...

BDI2000?

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
A person who is more than casually interested in computers should  be
well  schooled in machine language, since it is a fundamental part of
a computer.                                           -- Donald Knuth

Re: [Ppcboot-users] Serail console conflict from ppcboot to linux

In message <20020301114603.2a141a06.cgagneraud <at> anfora.fr> you wrote:
>
> > Is there really a HHL kernel version 2.4.18-rc3 out there? Where?
> yes I use rsync -rv source.mvista.com::linuxppc_2_4_devel .

No.

Please note that this is NOT a MontaVista kernel.

It is just a MIRROR of the  official  source  tree  which  is  not  a
product  of MV but a result of the work of the Open Source community.
See http://penguinppc.org/dev/kernel.shtml for details.

> So I have CONFIG_SERIAL_CONSOLE=1, SCC_CONSOLE=1, CONFIG_SERIAL_CONSO> LE_PORT=0 
> With this I normally have SCC1 as ttyS0 (rs_table[0]) and SCC2 as ttyS1 (> rs_table[0]).
> and with
> T0:23:respawn:/sbin/getty -L ttyS0 115200 vt100
> T1:23:respawn:/sbin/getty -L ttyS1 115200 vt100
> in my /etc/initab it would work but...

What do you mean "it would work"? Does this work, or not?

> I think i have to resolv the Ppar,Psor,Pdir configuration.

I rather guess it might be a problem of BRG initialization?

> I'm new in embedded linux and in PowerPC and i'm a young engineer (mostly>  hardware)!.

Don't apologize. We all started some day, it's just that some  of  us
are doing this a bit longer and/or more intense than others.

> > Get one. Life will be easier.
> Yes, will be soon...

BDI2000?

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
A person who is more than casually interested in computers should  be
well  schooled in machine language, since it is a fundamental part of
a computer.                                           -- Donald Knuth

[Ppcboot-users] On-Chip Serial Port 8245

Hi All

Is the code for the On-Chip Serial port for the 8245 entered into the CVS
repository yet ?

I tried looking for it but I didn't find it.

Best regards

Ole Andreas Torvmark

Re: [Ppcboot-users] On-Chip Serial Port 8245

Ole Andreas Torvmark writes:
> Hi All
> 
> Is the code for the On-Chip Serial port for the 8245 entered into the CVS
> repository yet ?
> 
> I tried looking for it but I didn't find it.

Its there in the Musenki parts of the tree.

I don't remember straight-off if Wolfgang put the patch in for the
Sandpoint8245 version or not.  If not, about the only real change is
this in board/sandpoint/ns16550.h:

    typedef struct NS16550 *NS16550_t;

    static const NS16550_t COM_PORTS[] = {
	    (NS16550_t) (CFG_ISA_IO + COM1),
	    (NS16550_t) (CFG_ISA_IO + COM2),
    #ifdef CONFIG_MPC8245
	    (NS16550_t) ((CFG_EUMB_ADDR) + 0x4500),
	    (NS16550_t) ((CFG_EUMB_ADDR) + 0x4600)
    #endif
    };

along with setting 

    #define CONFIG_CONS_INDEX       3               /* set to '3' for on-chip DUART port 0 */

in include/config_Sandpoint8245.h

Do let me know if/when you want the linux bits that deal with the
on-board serial port.  Hacking PPCboot to support the on-chip DUART
took < 30 minutes.  Doing the same for linux took the better part of
two days.

Jim

--

-- 
"Life begins when you can spend your spare time programming
instead of watching television."  -- Cal Keegan

RE: RE: [Ppcboot-users] Changes to default config_WALNUT405.h fil e

>FROM: Wolfgang Denk
>DATE: 01/26/2002 15:21:54
>SUBJECT: RE: [Ppcboot-users] Changes to default config_WALNUT405.h file
>Dear Steve,
>
>in message <<EMAIL: PROTECTED>> you wrote:
>> The default configuration in the header file for the 405GP Walnut
>> system is to use the serial ports in interrupt mode.  As has been
>> recently discussed here, this mode is broken since the interrupt
>> service routine pointer gets clobbered later on in the initialization.
>> When did this ever work?  The CONFIG_SERIAL_SOFTWARE_FIFO
>> define needs to be unset or set to zero to get a working image.
>> Even if the ISR thing gets worked out, I'm not sure that interrupt
>> driven should be the default mode.
>> 
>
>Thanks, both items added.
>
>Wolfgang Denk

Hmm, changing to #undef CONFIG_SERIAL_SOFTWARE_FIFO seems
to help but then if we try the "loads" command things
don't work. So removing just the isr does not solve the
real problem...

Greetings,
Bart

[Ppcboot-users] PATCH - minor buiild anoyances

This patch to the root Makefile adds a rm of include/bmp_logo.h (this 
really shouldn't be in the CVS repository) to the clean target and adds 
a disasembled image target, ppcboot.dis.

-- 
Rich Ireland
Firmware Engineer
Enterasys Networks
mailto:rireland <at> enterasys.com

Index: Makefile
===================================================================
RCS file: /projects/ppcboot/latest/ppcboot/Makefile,v
retrieving revision 1.80
diff -u -r1.80 Makefile
--- Makefile	23 Feb 2002 01:11:46 -0000	1.80
+++ Makefile	1 Mar 2002 20:58:22 -0000
 <at>  <at>  -103,6 +103,9  <at>  <at> 
 ppcboot.bin:	ppcboot
 		$(OBJCOPY) ${OBJCFLAGS} -O binary $< $ <at> 

+ppcboot.dis:	ppcboot
+		$(OBJDUMP) -d $< > $ <at> 
+
 ppcboot:	depend subdirs $(OBJS) $(LDSCRIPT)
 		$(LD) $(LDFLAGS) $(OBJS) -Map ppcboot.map -o ppcboot

 <at>  <at>  -761,7 +764,7  <at>  <at> 
 		| xargs rm -f
 	rm -f examples/hello_world examples/timer
 	rm -f tools/img2srec tools/mkimage tools/envcrc tools/gen_eth_addr
-	rm -f tools/easylogo/easylogo tools/bmp_logo
+	rm -f tools/easylogo/easylogo tools/bmp_logo include/bmp_logo.h
 	rm -f tools/gdb/astest tools/gdb/gdbcont tools/gdb/gdbsend

 clobber:	clean