You ought to consider seeing if there is a port of micro monitor (
http://www.microcross.com/html/micromonitor.html ) for your adi dsp
products. We build support for umon into our Coldfire based product
and it provides the base for loading our rtems rtos and applications
as well as providing debugging tools. This would be much easier to
support than a proprietary monitor.
At 01:22 AM 7/8/2005, Burgwedel Friedrich wrote:
>As far as I know -- it's a long time since I
last used this stuff -- the
>monitor code is NOT compiled and/or linked in, as well as it is NOT
>loaded (from the PC, at last).
>
>When the EZK starts up, the monitor code is booted to the internal
>memory locations mentioned in the manual and the LDF file (they reserved
>a bit more then was actually needed for later extensions). When loading
>your own program sending it over the serial line, the monitor code is
>responsible for interpreting the tags and placing the code into memory.
>Using adresses that are reserved for monitor's usage would simply
>overwrite them and kill the monitor.
>
>Moving the monitor out of internal memory should be fairly simple if you
>could get hold of the source code... doing this to the binary boot image
>inside the EPROM is not so easy, but sure not impossible: you would
>essentially have to patch the adress marks of the code tags and adapt
>the call adresses inside the monitor code.
>
>Friedrich
>
> > -----Original Message-----
> > From: adsp@adsp... [mailto:adsp@adsp...] On
> > Behalf Of Jon Harris
> > Sent: Thursday, July 07, 2005 7:44 PM
> > To: Steve Holle; adsp@adsp...
> > Subject: Re: [adsp] 21065L Ez-kit kernel source?
> >
> >
> > The 21065L Ez-kit does have external SDRAM. If it was
> > possible to move the monitor code to external memory, that
> > would be great. But I don't know how to do that. As I
> > mentioned earlier, the way the monitor gets linked and loaded
> > in with my application is a mystery to me--you don't do
> > anything explicit that I can find. The documentation just
> > tells you "don't use these memory addresses"
(internal
> > memory) and somehow the monitor code ends up there.
> >
> > --- Steve Holle <sholle@shol...> wrote:
> >
> > > Do you have external memory space? We've moved
> > > quite a bit of our low speed code out to external memory.
> > >
> > > At 04:44 PM 7/6/2005, Jon Harris wrote:
> > > >Is the source code included for the Ez-kit monitor kernel
code? I
> > > >couldn't seem to find it. I am using the 21065L Ez-kit
Lite.
> > > >
> > > >Also, is there an easy way to tell how much code
> > > >space is actually required for
> > > >the kernel? The documentation tells you to reserve 0x9000
> > - 0x97FF for the
> > > >kernel, but my application is _very_ tight on PM space and
> > it would be nice
> > > to
> > > >be able to use some of that block for some variables.
> > Looking at the
> > > >dissasembly, it doesn't look like the whole thing is
being
> > used, but
> > > >it is a little tough to tell.
> > > >
> > > >The way the whole monitor/kernel is a bit of mystery to
> > me, since you
> > > >don't explicitly allocate any space for it, and you
don't link it
> > > >with your application.
> >
> >
> >
> >
> > ____________________________________________________
> > Sell on Yahoo! Auctions - no fees. Bid on great items.
> > http://auctions.yahoo.com/
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
Steve Holle
Link Communications, Inc.
1035 Cerise Rd.
Billings, MT 59101
sholle@shol...
