This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: ecos redboot compile problem.
- From: "Doyle, Patrick" <WPD at dtccom dot com>
- To: "'Beymer, Mike'" <Mike dot Beymer at itron dot com>
- Cc: eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 30 Apr 2003 08:01:55 -0400
- Subject: RE: [ECOS] ecos redboot compile problem.
The "no link" message is from the ethernet driver. If you don't have an
ethernet MAC/PHY, then you should remove the CYGPKG_DEVS_ETH_ARM_INNOVATOR
package. If you do have one, but it is different than the innovator, then
you should remove it until you have the time to adapt the innovator package
for your target.
--wpd
> -----Original Message-----
> From: Beymer, Mike [mailto:Mike.Beymer@itron.com]
> Sent: Tuesday, April 29, 2003 7:43 PM
> To: Doyle, Patrick
> Cc: eCos Discussion
> Subject: RE: [ECOS] ecos redboot compile problem.
>
>
> Patrick,
> It appears that the build problem I was experiencing was
> due to a change
> in the memory layout file, mlt_arm_arm9_innovator_sram.ldi.
> The .data section
> was set to start at 0x8000, doing an objdump -h of
> redboot-sram.out the .data
> section is in sram at 0x20012dd0. After changing the .data
> section to follow
> the .gcc_except_table I started seeing output from the serial port.
>
> I'm now seeing "no link" on the serial port which appears
> to be coming from
> the network driver. I'm assuming at this point that these are
> some of the problems
> you dealt with getting the network driver to work properly.
> -Mike Beymer
>
> -----Original Message-----
> From: Doyle, Patrick [mailto:WPD@dtccom.com]
> Sent: Friday, April 25, 2003 1:35 PM
> To: Doyle, Patrick; Beymer, Mike
> Cc: eCos Discussion
> Subject: RE: [ECOS] ecos redboot compile problem.
>
>
> Item 2 probably would make more sense if I included all of
> the words I meant
> to include.
>
> Sigh... It's Friday... I'm going home soon.
>
> --wpd
>
>
> > 2) Even if eCos did flag certain regions of memory as
> > "readonly" (which it would do for the internal SRAM of
> ^
> ^^^
> NOT
> > the OMAP), the only time that those first two locations
> > of SRAM are written are immediately following a reset --
> > before any such protections would be enabled (which they are not).
>
>
>
>
> This message was scanned for viruses.
>
>
>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss