This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Rebuilding RedBoot for EDB7212
- To: Stefano Costa <stefano dot costa at bluewind dot it>
- Subject: RE: [ECOS] Rebuilding RedBoot for EDB7212
- From: Gary Thomas <gthomas at cambridge dot redhat dot com>
- Date: Thu, 14 Jun 2001 08:10:37 -0600 (MDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com
- Organization: Red Hat, Inc.
On 14-Jun-2001 Stefano Costa wrote:
> On 14 Jun 2001, at 4:26, Gary Thomas wrote:
>
> <SKIP>
>>
>> > for EP7xxx. Flashing the image that I get with this build, it seems
>> > that RedBoot is only able to connect with serial line and download
>> > an application to RAM, but it has no Ethernet and FLASH support even
>> > if the related checkboxes are highlighted in the ConfigTool. Did
>> > anyone face the same problem?
>>
>> That's because you didn't include the drivers for any of these
>> devices.
>
> I'm using is the graphical Config Tool (1.3.1.2) for Windows; I
> choose the "Cirrus Logic EDB7XXX" template, with the RedBoot
> set of packages. Then I set EP7212 as a processor and ROM as a
> startup enviroment. Examining the configuration, yes I noticed that
> "Cirrus Logic ethernet driver" and "Cirrus Logic EDB7XXX FLASH
> memory support" sections are greyed out, but I didn't find any
> dependency to enable them. Why?
>
You have to add the enabling packages, e.g. 'flash' to get the
flash driver to be turned on.
>
>>
>> Follow the instructions in the RedBoot manual for rebuilding:
>>
>> % ecosconfig new edb7212 redboot
>> % ecosconfig import
>> ${ECOS_REPOSITORY}/hal/arm/edb7xxx/current/misc/edb7212_redboot_ROM.
>> ecm % ecosconfig tree % make
>>
>>
>
> So, should I build RedBoot only from command line, and not from
> the graphical tool?
>
No, you can import the ".ecm" file from the GUI tool just as well
as from the command line.