[ECOS] standalone RAM application

[ECOS] standalone RAM application

[Aaron Richardson]

I am trying to create a standalone ecos RAM application.  I will be loading 
this application into RAM and then releasing the cpu from reset.  I have 2 
problems at this point:

1) no vectors are placed in RAM at 0x0 with the load of my program.

2) my program seems to want to load at 0x200000.

I can load my program in RAM and start the cpu at 0x200000.  The code prints 
out a rew things and then hangs at some point.  I think this has to do with 
the vectors missing(I havent tracked it down completely yet).  Any idea how 
to fix this?

thanks,

-- 


Aaron Richardson
aarichar@cisco.com
512-378-1286


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

Re: [ECOS] standalone RAM application

[Gary Thomas]

On Fri, 2003-10-10 at 14:38, Aaron Richardson wrote:
> I am trying to create a standalone ecos RAM application.  I will be loading 
> this application into RAM and then releasing the cpu from reset.  I have 2 
> problems at this point:
> 
> 1) no vectors are placed in RAM at 0x0 with the load of my program.
> 
> 2) my program seems to want to load at 0x200000.
> 
> I can load my program in RAM and start the cpu at 0x200000.  The code prints 
> out a rew things and then hangs at some point.  I think this has to do with 
> the vectors missing(I havent tracked it down completely yet).  Any idea how 
> to fix this?
> 

What platform?  What Architecture?  The details vary from platform to
platform.

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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

Re: [ECOS] standalone RAM application

[Aaron Richardson]

So the architecture is the IXP2400.

I have ported the Intel redboot to the current ~2.0 code(pre-release CVS).  I 
have it running (ROMRAM) from flash.  My application works booting redboot 
from flash and loading the application.  However, when I click the "Behave as 
ROM monitor" (to make standalone app) it changes my startup type to ROMRAM.  
Which I assume is not what I want.

thanks,
Aaron



On Friday 10 October 2003 04:17 pm, Gary Thomas wrote:
> On Fri, 2003-10-10 at 14:38, Aaron Richardson wrote:
> > I am trying to create a standalone ecos RAM application.  I will be
> > loading this application into RAM and then releasing the cpu from reset. 
> > I have 2 problems at this point:
> >
> > 1) no vectors are placed in RAM at 0x0 with the load of my program.
> >
> > 2) my program seems to want to load at 0x200000.
> >
> > I can load my program in RAM and start the cpu at 0x200000.  The code
> > prints out a rew things and then hangs at some point.  I think this has
> > to do with the vectors missing(I havent tracked it down completely yet). 
> > Any idea how to fix this?
>
> What platform?  What Architecture?  The details vary from platform to
> platform.
>
> --
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates

-- 


Aaron Richardson
aarichar@cisco.com
512-378-1286


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

Re: [ECOS] standalone RAM application

[Eric de Jong]

>> 1) no vectors are placed in RAM at 0x0 with the load of my program.
No, the vectors are installed by redboot, and, if selected in the configuration,
updated by your init code.

>> 2) my program seems to want to load at 0x200000.
You can change this in your linker file (target.ld ?) with the command
"ENTRY(reset_vector)". The label reset_vector must be defined globaly.

>> The code prints out a rew things and then hangs at some point.
Your code? It does seem to work then right?
Debug code? Try assembly stepping through the startup code and find out where it
does wrong. Maybe you need to change some options in your config file?

Eric.



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

[ECOS] how to create RAM redboot image

[Ramprasad]

Hello all,

I compiled the redboot for ASB2305 (for AM33 processor) and got the images
like .img, .bin, .elf and .srec. But in the manuals says you have to
download .ram of redboot image using JTAG debugger. Please can you tell me
how can I get the .ram (or .rom) image.

TIA
Ramprasad


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

Re: [ECOS] how to create RAM redboot image

[Gary Thomas]

On Wed, 2003-10-15 at 15:44, Ramprasad wrote:
> Hello all,
> 
> I compiled the redboot for ASB2305 (for AM33 processor) and got the images
> like .img, .bin, .elf and .srec. But in the manuals says you have to
> download .ram of redboot image using JTAG debugger. Please can you tell me
> how can I get the .ram (or .rom) image.
> 

The "RAM" version is simply a version which has the startup type set
to RAM.  The file name suffices have nothing to do with this.

The process should be something like this:
  % ecosconfig new asb2305 redboot
  % ecosconfig import ${ECOS_REPOSITORY}/hal/mn10300/asb2305/current/misc/redboot_RAM.ecm
  % ecosconfig tree
  % make
Then download whatever file your JTAG software wants - some want to
see raw binary (hence the .bin suffix), some an ELF image (.elf), ...

Once you have this running, build the ROM version.  In a separate directory,
using the same steps as above, except use the ..._ROM.ecm file

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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

Re: [ECOS] Bringup the asb2305 board

[Ramprasad]

Hello all,

I got the images .bin, .img, .srec and .elf after compiling redboot for
asb2305 (MN10300) reference board. I downloaded .img file(.elf and .srec
also tried) thru JTAG debugger (after setting up the hyperterminal and other
board settings). But I did not get any messages in hyperterminal.

1. Setting up hyper terminal (115200, N, 8, 1 with hardware flow control).
2. As I want to just see the redboot prompt, I didn't set the jumper (ST18)
to write enable for PROM.
3. I put the front board switch (S5) to FLASH.

Please let me know if I am doing anything wrong.

Regards
Ramprasad


----- Original Message ----- 
From: "Gary Thomas" <gary@mlbassoc.com>
To: "Ramprasad" <rprasad@pav.research.panasonic.com>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Sent: Wednesday, October 15, 2003 5:52 PM
Subject: Re: [ECOS] how to create RAM redboot image


> On Wed, 2003-10-15 at 15:44, Ramprasad wrote:
> > Hello all,
> >
> > I compiled the redboot for ASB2305 (for AM33 processor) and got the
images
> > like .img, .bin, .elf and .srec. But in the manuals says you have to
> > download .ram of redboot image using JTAG debugger. Please can you tell
me
> > how can I get the .ram (or .rom) image.
> >
>
> The "RAM" version is simply a version which has the startup type set
> to RAM.  The file name suffices have nothing to do with this.
>
> The process should be something like this:
>   % ecosconfig new asb2305 redboot
>   % ecosconfig import
${ECOS_REPOSITORY}/hal/mn10300/asb2305/current/misc/redboot_RAM.ecm
>   % ecosconfig tree
>   % make
> Then download whatever file your JTAG software wants - some want to
> see raw binary (hence the .bin suffix), some an ELF image (.elf), ...
>
> Once you have this running, build the ROM version.  In a separate
directory,
> using the same steps as above, except use the ..._ROM.ecm file
>
> -- 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
>
>
> -- 
> Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>
>


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