Re: [ECOS] mips IDT334 help

[Tim michals <tcmichals at yahoo dot com>]

Several ways:
-During the boot process redboot displays if it found
the Network card.  If you neeed to generate more
diagnostics you can select an option under PCI using
the configuration tool.  This displays all of the
information during PCI scanning.
- If you wish to download programs and the Ethernet
card is not found, use the serial download option in
redboot for example: load -m xmodem <name of
program>.elf
Consult the redboot manual for more commands:
http://sources.redhat.com/ecos/docs-2.0/ref/redboot.html



--- "Avinash S." <avinash.s@inspiretech.com> wrote:
> hi,
> my sdram size is 16 mB with 8MB on each bank, i made
> a mistake while 
> typing that out in the last mail(sorry!). anyway i
> managed to get redboot 
> work. The problem it seems was in the srec file.
> Apparently the mipsisa-
> elf-objcopy convert to srec doesnt seem to run on
> the board from bootrom, 
> i however used sde-conv (algorithmics convert) and
> it worked fine...dont 
> know where exactly the problem could be tho!
> 
> Now that i have a redboot running how do i check if
> it has detected my 
> ethernet card(82599) and how do i get it to run the
> test programs.  My 
> board is custom and it doesnt have the IDT334 ref
> ethernetcard.
> 
> Thanks in advance
> Avinash
> 
> 
> -----Original Message-----
> From: Tim michals <tcmichals@yahoo.com>
> To: "Avinash S." <avinash.s@inspiretech.com>
> Date: Thu, 29 May 2003 06:41:26 -0700 (PDT)
> Subject: Re: [ECOS] mips IDT334 help
> 
> > Several suggestions:
> > 1) Redboot: the
> mlt_mips_idt32334_refidt334_romram.h
> > needs to be changed for your SDRAM SIZE, the
> current
> > configuration is for 16MB.  Redboot uses the last
> 1K
> > or so of RAM for GDB information.
> > 
> > 2) Use the LED panel to display messages to help
> > assist in finding the location of the issue.  Some
> of
> > the places to put these are: platform.S
> > hal_memc_setup, var_misc.c hal_variant_init,
> > plf_misc.c hal_platform_init.  The LED panel is
> > helpful if you don't have a JTAG emulator.
> > 
> > 3)When creating a Redboot image don't include
> flash or
> > network stack.  This makes the code less to debug.
> 
> > But also requires flash to be externally programed
> via
> > JTAG, removable PROM etc.  Also, maybe comment out
> the
> > PCI startup for now until redboot is running. 
> Then
> > slowly start add each feature. 
> > 
> > Overall your close, just some minor issue
> somewhere. 
> > If you want, I can take look at your port and do
> some
> > minor checking.  FYI: I'll not have access to
> email
> > for one week starting 5/30
> > 
> > 
> > 
> > --- "Avinash S." <avinash.s@inspiretech.com>
> wrote:
> > > hi
> > > the bootloader that i use is for custom board.
> the
> > > memory registers are 
> > > all set up as on IDTsim.there is no real
> interrupt
> > > handling mechanism on 
> > > the boot loader. The processor is actually 1dt
> 332
> > > but ive mangaed to 
> > > make necessary changes (port control widths etc
> > > etc).also CPU speed is 66 
> > > The memory on board is 8MB SDRAM using bank 0
> and
> > > bank 1. the board is 
> > > based on the IDT board however.
> > > 
> > > 
> > > 
> > > i have made all necesarry changes to the support
> the
> > > board in all the idt 
> > > header files itself. However im still no able to
> get
> > > redboot running. As 
> > > of now im compling redboot with the ROMRAM
> option.
> > > Does redboot expect 
> > > any initialisations before it runs..because i
> just
> > > use the redboot.srec 
> > > image and burn it into my flash AMD flash.
> > > 
> > > my bootloader doesnt support any gdb tracing
> either.
> > > 
> > > Thanks,
> > > Avinash
> > > ps: here is a mem map....... of the board
> > >
> >
>
-----------------------------------------------------------------------
> > ---
> > > 
> > > * Region A (000000): Used by SDRAM
> > >  * 		Width set to 10b (32 bit)
> > >  * 		
> > >  * Region B (000001): Not used
> > >  * Region C (000010): Not used
> > >  * Region D (000011): Not used
> > >  * 		Width set to 10b (32 bit)
> > >  * 		
> > >  * Region E (000100): Used by NVRAM, LED, EPLD
> > >  * 		Width set to 00b (8 bit)
> > >  *
> > >  * Region F (000101): Used by Flash
> > >  * 		Width set to 01b (16 bit)
> > >  * 		
> > >  * Region G (000110): IDT internal/co-processor
> > >  * 		Width set to 10b (32 bit)
> > >  * 
> > >  * Region H (000111): Not used
> > >  * Region I (001xxx): Not used
> > >  * Region J (010xxx): Not used
> > >  * Region K (011xxx): Not used
> > >  * Region L (100xxx): Not used
> > >  * Region M (101xxx): Not used
> > >  * Region N (110xxx): Not used
> > >  * Region O (111xxx): Not used
> > >  * 		Width set to 10b (32 bit)
> > > 
> > > 
> > > -----Original Message-----
> > > From: Tim michals <tcmichals@yahoo.com>
> > > To: "Avinash S." <avinash.s@inspiretech.com>
> > > Date: Wed, 28 May 2003 06:38:29 -0700 (PDT)
> > > Subject: Re: [ECOS] mips IDT334 help
> > > 
> > > > 
> > > > The NET configuration also uses memory at
> > > 0xa010_0000
> > > > for the PCI driver (or 0x8010_0000).
> > > > 
> > > > The tested configuration used Redboot to load
> an
> > > eCOS
> > > > application.  I would recommend using a Built
> > > ROMRAM
> > > > version of redboot to load the eCOS
> application.
> > > > 
> > > > To futher look at this problem:
> > > > 1. Provide an Image and source to your
> bootloader
> > > for
> > > > me to test and the ecm file of your ecos
> > > application
> > > > configuration.
> > > > 2. Use Redboot
> > > > 3.Provide more information on your bootloader.
> > > Which
> > > > includes: Memory MAP (ROM, RAM), PCI mapping,
> > > > interrupt configuration, Serial ports used,
> timer
> > > > configuration, and Board jumper settings. Does
> > > your
> > > > ROM monitor provide gdb tracing? Loading the
> eCOS
> > > app
> > > > generate a execption? What is the
> confiugration
> > > > register cache setting? 
> > > > 
> > > > tcmichals
> > > > 
> > > > 
> > > > --- "Avinash S." <avinash.s@inspiretech.com>
> > > wrote:
> > > > > hello,
> > > > > 
> > > > > No, im not using IDTsim or redboot. The
> bootROM
> > > was
> > > > > written using vxworks 
> > > > > and adapted for use in linux. it however
> bears
> > > some
> > > > > resemblance to 
> > > > > IDTsim. the bootrom has ethernet support and
> i
> 
=== message truncated ===


__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss