Re: [ECOS] mips IDT334 help

[Tim michals <tcmichals at yahoo dot com>]

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
> am
> > > able to downlad the 
> > > eCos images to the onboard flash and run from
> there.
> > > 
> > > 
> > > what is confusing is that the "basic" test
> prgram
> > > image works when 
> > > complied with a template "kernel" but no output
> when
> > > i compile the same 
> > > with "net" template!
> > > 
> > > Avinash
> > > 
> > > 
> > > -----Original Message-----
> > > From: Tim michals <tcmichals@yahoo.com>
> > > To: "Avinash S." <avinash.s@inspiretech.com>,
> ecos
> > > <ecos-
> > > discuss@sources.redhat.com>
> > > Date: Wed, 28 May 2003 04:42:32 -0700 (PDT)
> > > Subject: Re: [ECOS] mips IDT334 help
> > > 
> > > > - Are you using IDTSim to load eCOS image?
> > > > - Can you provide more information where
> RedBoot
> > > is
> > > > loaded?
> > > > 
> > > > The issue with the eCOS image hanging in
> > > > cyg_hal_invoke_constructors is the complete
> image
> > > was
> > > > not downloaded into RAM. 
> > > > 
> > > > Also, I have another patch that fixes SDRAM
> and
> > > serial
> > > > issues.
> > > > 
> > > > tcmichals
> > > > --- "Avinash S." <avinash.s@inspiretech.com>
> > > wrote:
> > > > > hello,
> > > > > I am trying to port ecos to an IDT334 based
> > > custom
> > > > > board. I am using the
> > > > > latest ecos version 2.01 and the mipisa-elf-
> > > > > gnutools that came with the
> > > > > download. At first I complied the template
> with
> > > only
> > > > > the kernel. I
> > > > > convereted the tests images to srec using
> the
> > > tool
> > > > > chain objcopy . I am
> > > > > using a custom-built rom on the board and i
> have
> > > set
> > > > > the "work with rom
> > > > > monitor" as generic. my startup type is RAM
> at
> > > an
> > > > > address 80200000 with
> > > > > .text at 80200398. Initially the program was
> > > hanging
> > > > > in
> > > > > cyg_hal_invoke_constructors in the file
> > > vectors.S.
> > > > > however on commenting
> > > > > the function I managed to get the test
> program
> > > > > "basic" to run on the board
> > > > > and it displayed the PASS for the functions
> that
> > > it
> > > > > invoked. I was even
> > > > > able to run tests cache and context and
> > > bin_sem0.
> > > > > However all other test
> > > > > programs fail to run and they hang at the
> > > function
> > > > > CYGACC_COMM_IF_PUTC(*__chan, c);
> > > > > with no output whatsoever.
> > > > > 
> > > > > After this initial testing i tried to test
> the
> > > > > "basic" program with the
> 
=== 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